Integrating with SWIFT Network via Cloud Global Server API

Before integrating, your institution must: (1) Have a valid BIC/SWIFT code issued by SWIFT, (2) Complete Cloud Global Server's KYC/AML onboarding, (3) Receive your institution-level API key and X.509 certificate pair, (4) Whitelist Cloud Global Server API server IPs in your firewall.

Cloud Global Server API uses OAuth 2.0 Client Credentials flow. Obtain your client_id and client_secret from the Admin Dashboard. POST to /api/auth/token with grant_type=client_credentials. The response returns a Bearer token valid for 3600 seconds. Include this token as Authorization: Bearer <token> in all API requests.

POST /api/v1/swift/mt103 with Content-Type: application/json. The request body includes: sender_bic, receiver_bic, value_date (YYYYMMDD), currency, amount, ordering_customer (name + account), beneficiary (name + account + address), and remittance_info. The response returns a transaction_id and status: ACCEPTED, PENDING_COMPLIANCE, or REJECTED with reason.

Configure settlement status webhooks at POST /api/v1/webhooks. Register your endpoint URL and select event types: transaction.accepted, transaction.settled, transaction.failed. All webhook payloads are signed with HMAC-SHA256 using your webhook secret. Verify the X-CGS-Signature header on every received webhook to prevent spoofing.

HTTP 400: Validation error — check field format and required fields. HTTP 401: Authentication failed — refresh Bearer token. HTTP 403: Compliance hold — contact support with transaction_id. HTTP 429: Rate limit exceeded — implement exponential backoff starting at 1 second. HTTP 500: Server error — retry up to 3 times with 5-second intervals, then raise an alert.