Cross-Border Funds Transfer (CBFT) APIs enable seamless international payments, allowing businesses to transfer funds across borders efficiently and securely. CBFT supports multiple currencies and adheres to international standards, making it an essential service for companies involved in global trade.


Capabilities

  • Multi-Currency support: Handle payments in a wide range of currencies, supporting global business operations.
  • Compliance and standards: Adheres to international payment standards, including SWIFT messaging, to ensure compliance with global financial regulations.
  • End-to-End tracking: Monitor the status of your international transfers with tracking capabilities that provide transparency throughout the transaction lifecycle.
  • Cost efficiency: Optimise transfer costs with competitive foreign exchange rates and lower processing fees compared to traditional bank transfers.

Technical requirements

  • Authentication: Utilize OAuth 2.0 with the Client Credential Grant to obtain a bearer token, which is required for API access.
  • Endpoints: Access CBFT APIs through the /payment/au/v1.0/cbft endpoint for initiating cross-border payments.
  • Security: All transactions are secured with HTTPS and OAuth 2.0, ensuring the protection of sensitive financial data during transfer.
  • Data format: JSON is used for request and response payloads, facilitating easy integration with web applications and services.

Key features for developers

  • Asynchronous payment processing: Submit cross-border payment requests and handle responses asynchronously, allowing your application to operate without waiting for immediate confirmation.
  • Detailed error messages: Comprehensive error handling with detailed messages to assist in troubleshooting and resolving issues swiftly.
  • Testing environment: A dedicated UAT environment is available for testing and validating integrations before moving to the production environment.
  • Extensive documentation: Access to thorough API documentation, including example code, request structures, and common use cases to support developers during integration.

Example workflow

sequenceDiagram participant Developer participant CBFT API Developer->>CBFT API: POST /v1.0/auth (Client Credentials) CBFT API-->>Developer: 200 OK (Bearer Token) Developer->>CBFT API: POST /payment/au/v1.0/cbft (CBFT Payment Request) CBFT API-->>Developer: 202 Accepted (Payment Processing) Developer->>CBFT API: GET /payment/au/v1.0/cbft/status/{requestId} alt Payment Successful CBFT API-->>Developer: 200 OK (Payment Details) else Payment Pending CBFT API-->>Developer: 204 No Content (Payment Pending) else Payment Failed CBFT API-->>Developer: 400 Bad Request (Error Details) end