Withdrawals through the same contract
A payout is created like a payment: recipient, amount, currency and method; routing picks the provider by country and amount, cascades on a failure and reports the result. The merchant cabinet shows the balance a payout draws on, the limits and the fees. A merchant that pays out to players, sellers, drivers or affiliates integrates once and gets every rail the client enables, in every country of the catalogue.
The rails
| Rail | Examples | Typical time | Recipient details |
|---|---|---|---|
| Cards | Visa Direct, Mastercard Send through acquirers that support them | Minutes to a day | Card token or number entered once |
| Instant bank transfers | SEPA Instant, Faster Payments, IMPS, PIX keys, UPI | Seconds to minutes | Account or key, name |
| Bank transfers | SEPA, Havale/EFT, local transfers | Same day to two days | Account, bank code, name |
| Wallets | Kaspi, Payme, Click, M-Pesa, MTN MoMo, Airtel Money | Seconds | Wallet number |
| Crypto | USDT, USDC and others through licensed or registered providers | Minutes | Address and network |
The catalogue marks payout support for every method and provider, so a client sees which rails exist for a country before it signs with a provider.
Mass payouts
For affiliates, sellers, players and suppliers: a file of hundreds or thousands of rows, checked before anything is sent. Each row becomes a payout with its own reference, routing and status, and the file keeps its own summary: sent, paid, failed, returned, with the reasons.
Control
- Roles in the back office: who creates payouts and who sends them.
- Limits per merchant and per day, balances per currency, and a rolling reserve that a payout cannot touch.
- The journal: who created the payout, which provider paid it and what the provider answered, kept five years.
- Returns and failures written back to the balance when the provider reports them, with a webhook to the merchant.
A typical setup
A gaming operator licensed in two countries enables two payout rails per country: instant bank transfers first, a wallet as the cascade’s second terminal where the bank is slow at night. Withdrawals go out within the merchant’s daily limit and the terminals’ limits. Affiliates are paid from a file every Monday morning: the operator uploads the spreadsheet, the rows with a wrong account format are rejected, the rest are sent, and the file’s summary shows the returned ones with the provider’s reason. Every payout and return is in the journal, and the merchant’s balance never goes below the reserve.
For whom
iGaming and trading businesses that pay winnings and withdrawals within minutes; marketplaces and gig platforms that settle thousands of sellers on a schedule; affiliate networks and remittance-style flows run by licensed clients; companies paying contractors in regions where bank transfers are slow and wallets are not. The funds are the client’s and move through the client’s accounts at its providers; the platform instructs, records and reconciles.