Crypto mass payouts. One file. Many destinations.
Send bulk crypto payments in one currency per file. Validate recipients, confirm the batch and track each transaction.
One integration. One file. Infinite payouts.
Prepare once. XBO handles the rest.
| Information | What to include |
|---|---|
| Every payout row | Currency, Network Code, Amount, Destination Address. Use the same currency throughout the file. |
| Person beneficiary, when required | Beneficiary type, first and last name, date of birth and address |
| Company beneficiary, when required | Beneficiary type, company name, registration number and address |
| Address data, when required | Country code, city, street and postal code |
Confirm exact optional column names, the row limit and applicable approval thresholds with XBO before preparing the file. A customer can have up to ten unfinished batches.
-
The workflow is shared. The fees depend on the transfer.
Review the fee estimate for the asset and network. Multi-destination processing is available in supported configurations; a batch does not guarantee a network-fee saving.
-
Set an amount in fiat. Get a delivery in crypto.
Fiat-denominated crypto batches still deliver crypto to recipients. Merchant fiat wire withdrawals are a separate workflow with their own requirements.
Prepare the batch correctly.
Details for your next decision.
-
What CSV format should we use?
Use a comma-separated file with the exact mandatory headers Currency, Network Code, Amount and Destination Address. Every file must use one payout currency. Include only supported columns; unsupported extra columns reject the file.
-
What beneficiary information is required?
Where Travel Rule checks apply, include the required person or company identity, registration and address information using the current template. Missing or invalid beneficiary data can reject the entire file.
-
Will batching always reduce network fees?
No. Multi-destination processing is available for supported configurations, but batching alone does not guarantee lower network fees. Review the estimate for the actual asset and network.
-
Can one file contain different payout currencies?
No. Every file must use one payout currency.
-
What limits apply?
The system uses a configured maximum row count and allows up to ten unfinished batches per customer. Check your account’s current template and row limit.
-
Does confirmation immediately send every payment?
No. Confirmation requires 2FA, and batches above the applicable automatic-approval threshold also need XBO operator approval. Plan timing around those checks and network processing.
-
Can we pay in fiat?
A fiat-denominated crypto batch still delivers crypto to the recipient. Supported merchant fiat wire withdrawals are a separate payment workflow, described on the payment API page.
Explore what else your business can do with crypto.
Explore the services that work alongside this one.
-
Multi-Currency eMoney Account
Receive, hold, convert and pay in EUR and GBP through XBO eMoney, a separate workspace for business fiat operations.
-
Crypto Payment API
Connect payment requests, deposit addresses, status callbacks and supported payouts with XBO’s Crypto Processing API.
-
Payment Links
Create a crypto payment link, share it with your client and track the payment through to supported settlement.
-
Trust Center
Review the entities, security controls, terms and pricing that apply to your business.
Many payouts. One clear next step.
Tell us your payout currency, network and recipient volume. We will help define the right batch setup.
