PaySwiftly Payout API
Send payments to anyone, anywhere. Our RESTful API makes global payouts simple, secure, and lightning-fast.
API Base URL
https://api.payswiftly.ioAll API requests should be made to this base URL using HTTPS.
Send payouts worldwide with local payment methods
Support for fiat and cryptocurrency payouts
How It Works
From setup to settlement in 6 simple steps. Build a complete payout integration in under an hour.
Authenticate
Secure your integration with HMAC-SHA256 signatures. Get your API credentials and start building in minutes.
Setup AuthenticationCreate Receiver
Create a receiver entity to represent the person or business receiving funds. This is required before adding payment accounts.
Create ReceiverAdd Receiver Account
Link bank accounts, virtual cards, or regional payment networks. Support 100+ countries and currencies.
Add AccountCreate Payout
Initiate instant or scheduled payments. Transfer funds globally with real-time status tracking.
Create PayoutMonitor Transactions
Track payout status, check balances, and access detailed transaction history through our API.
Get Payout StatusHandle Events
Receive real-time webhooks for status changes. Stay informed on every transaction update.
Configure WebhooksIntegration Notes — Async Processing
All API operations are processed asynchronously. When you call our API to create a receiver, create a receiver account, or create a payout, you'll get an immediate response with the resource ID — but the resource may not be fully created in our system yet at that moment.
Listen for webhooks before proceeding
We strongly recommend listening for webhooks before proceeding to the next step.
| Step | Wait for Webhook | Then proceed to |
|---|---|---|
| Create Receiver | receiverCreated | Create Receiver Account |
| Create Receiver Account | accountCreated | Create Payout |
| Create Payout | payoutCreated | Monitor status via payoutUpdate |
Why?
Each API call queues the operation for background processing. The ID in the response is generated immediately, but the record may take a moment to be fully available. If you call the next endpoint too quickly using that ID, you may get a "not found" error.
Recommended Pattern
- 1Call the API endpoint
- 2Store the returned ID
- 3Wait for the corresponding webhook event
- 4Once the webhook confirms the resource is created, proceed to the next step
Why Developers Love PaySwiftly
RESTful Design
Intuitive endpoints following REST principles
JSON Everything
Clean, structured JSON requests and responses
Comprehensive Docs
Detailed guides with code examples
Sandbox Testing
Test your integration without real money
Real-time Webhooks
Instant notifications for every event