Send money
Pay a recipient from your wallet, with conversion built in, and track it to delivery.
A payout debits one of your wallets and pays a recipient. If the wallet currency differs from the recipient's, MigraPay converts as part of sending.
Send a payout
Save the recipient once. Create a recipient with the destination details its payout method needs. See Recipients.
Quote it. GET /payouts/estimate shows the rate, the fees and what the recipient receives. Make sure your wallet covers the amount plus fees.
Send it. POST /payouts with fromCurrency, amount and recipientId, and always an Idempotency-Key: if the request times out, retry with the same key and body and you get the original payout back instead of paying twice.
Track it. Listen for payment.settled, payment.failed and payment.reversed on your webhooks, or read it with GET /payouts/{id}.
What happens to a payout
Your wallet is debited when the payout is created (processing). It ends successful, or failed with your wallet credited back. A delivered payout can later be reversed by the receiving bank, which also credits you back. Some routes settle instantly, so the create response can already say successful. See the lifecycle.
Approvals
If your business has approval rules that match the payout, nothing is debited yet: the response has "approvalRequired": true and the status is pending_approval. Once an approver signs off in the dashboard the payout proceeds and your webhooks report the outcome.
When a payout is refused
The create call tells you why with a code you can branch on: not enough balance, below or above the limits for that route, an inactive recipient, a method that is switched off. If the payout was declined after your wallet was debited, the money is credited back before you get the error. Every code is in the payout errors table.
Test it
In Sandbox, the last four digits of the recipient's account number decide the outcome (0000 declines, 0001 settles a few minutes later, anything else settles at once), so you can test every path. See Sandbox.