Documentation Index
Fetch the complete documentation index at: https://docs.zuba.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Payouts are the core functionality of the Zuba platform, enabling you to send money to beneficiaries worldwide through various payment rails including SEPA, SWIFT, crypto networks, and local payment methods.Payout Lifecycle
Beneficiaries & Accounts
Beneficiary Management
Before sending payouts, you must create beneficiaries with their payment details:Account Types
Zuba supports multiple account types for maximum flexibility:- Bank Accounts
- Crypto Wallets
- Card Payouts
SEPA (European Union)US ACHUK Bank AccountNigerian Bank Account
Creating Payouts
Single Payout
After creating a beneficiary, use their ID to create payouts (recommended approach). Currency Fields:inputCurrency is the currency from your account you’ll be paying from, while currency is what the beneficiary will receive (automatic conversion if different):
Batch Payouts
Process multiple payouts in a single API call for efficiency:Payment Routes
Zuba automatically selects the optimal payment route, but you can specify preferences:| Route | Regions | Speed |
|---|---|---|
sepa_credit | European Union | 1-2 business days |
sepa_inst | EU (SEPA Instant banks) | < 10 seconds |
bank_transfer | Multiple regions | Varies by destination |
ach | United States | 1-3 business days |
fedwire | United States (domestic wire) | Same business day |
swift | International (10 supported countries) | 1-3 business days |
USD rails
For USD payouts, three rails are surfaced byGET /payouts/available-rails?accountId=<uuid>:
fedwire— domestic wire to a US bank. Requires routing + account number on the beneficiary.ach— batched same-day-to-3-day transfer to a US bank. Same required fields as fedwire.swift— international wire via SWIFT. Requires BIC + IBAN/account number + the beneficiary’s bank country. Currently supported destinations: AU, BM, BR, CA, DE, FR, GB, HK, NL, PT.
route field stored on the account, so payouts against an existing account don’t re-prompt the sender to pick a method. New beneficiary accounts intended for SWIFT must be created with type: "swift" and supply swiftCode, accountNumber, beneficiaryCountry, and (optionally) bankName / beneficiaryAddress in data.
SWIFT payouts always pass through a cross-rate quote (POST /quotes/cross-rate) — the sender is debited in their source currency (e.g. NGN) and Zuba satisfies the USD outflow from a pre-funded pool on the destination bank.
Route Selection Logic
Tracking & Status
Payout Statuses
| Status | Description | Next Actions |
|---|---|---|
created | Payout has been created | Can be cancelled |
queued | Queued for processing | Monitor for updates |
processing | Being processed by payment provider | Monitor for updates |
paid | Successfully delivered to beneficiary | Download receipt |
failed | Processing failed | Review error, retry |
cancelled | Cancelled by user or system | Funds returned |
Real-time Tracking
Best Practices
Beneficiary Validation
Beneficiary Validation
- Always validate beneficiary details before creating
- Use SEPA reachability check for EU transactions
- Store beneficiary IDs for repeat payments
- Keep beneficiary information up to date
Error Handling
Error Handling
- Implement proper error handling for all API calls
- Use exponential backoff for retries
- Monitor webhook notifications for status updates
- Log all transactions for audit purposes
Security
Security
- Never expose API keys in client-side code
- Validate webhook signatures
- Use HTTPS for all API communications
- Implement proper access controls
Next Steps
First Payout Guide
Step-by-step guide to send your first payout
Batch Processing
Learn how to process multiple payouts efficiently
Webhooks
Set up real-time notifications for payout status
API Reference
Complete API documentation for payouts