Key Features
Global Reach
Transfer to any country worldwide
Multi-Currency
Support for multiple currencies
Correspondent Banking
Automatic routing through intermediary banks
Real-time Tracking
Status updates via webhooks
API Reference
Create SWIFT Payment
Initiate international wire transfer
Sign Transactions
Approve payments requiring signature
Approve Transaction
Single transaction approval
Decline Transaction
Reject a pending transaction
Business Requirements
Use idempotency for payment creation
Use idempotency for payment creation
Always send an
Idempotency-Key header when creating payments to prevent duplicates during retries.BIC/SWIFT code is required
BIC/SWIFT code is required
SWIFT payments require the beneficiary bank’s BIC/SWIFT code.
Use the Bank Information API to look up BIC codes.
Specify charge bearer
Specify charge bearer
SWIFT transfers may incur correspondent bank charges. Options:
DEBT- You (debtor) pay all chargesSHAR- Charges shared (default)CRED- Beneficiary pays all charges (charge amount becomes mandatory when used)
Create a SWIFT Payment
Request Fields
The request uses nested objects (debtor, creditor, settlement). See the Create SWIFT Payment API reference for the full, authoritative request schema.
Transaction Statuses
- Success Flow
- Error States
SWIFT payments take longer than SEPA due to correspondent banking. Track status via webhooks and allow 2-5 business days for settlement.
Charge Bearer Options
DEBT
You pay all chargesBeneficiary receives full amount
SHAR
Shared chargesEach party pays their bank’s fees
CRED
Beneficiary paysCharges deducted from amount
Integration Checklist
1
Implement idempotency
Generate and persist
Idempotency-Key for each payment2
Validate BIC codes
Ensure beneficiary bank BIC/SWIFT code is valid
3
Handle multi-currency
Specify source and target currencies correctly
4
Implement webhook receiver
Track payment status via webhooks
Next Steps
Track and Reconcile
Monitor transactions and reconcile
Bank Information
Look up BIC codes from IBAN