Crypto payment API. Connect the whole payment journey.
Connect payment requests, deposit addresses, status callbacks and supported payouts with XBO’s Crypto Processing API.
-
Request
Create a payment intent or supported deposit flow.
-
Collect
Receive the supported payment and apply configured conversion.
-
Notify
Handle signed payment-status callbacks.
-
Reconcile
Connect identifiers, statuses and reports to your records.
Give testing its own environment.
The merchant sandbox uses separate credentials for supported payment and payout simulations. Prepare these five things before your first request.
- API key and secret
- HMAC-signed requests
- Source-IP allowlisting
- Payment and payout status handling
- Separate sandbox credentials
One merchant integration. Several payment jobs.
| Workflow | Available functions |
|---|---|
| Collection | Payment intents, hosted links and reusable deposit addresses |
| Conversion | Quote and supported conversion operations |
| Crypto payouts | Payout intents and approved managed-account payouts |
| Fiat wires | Supported merchant fiat withdrawals and fee estimates |
| Crypto refunds | Fee, quote, execution and refund-link functions for eligible payment exceptions |
| Records | Callback notifications, payment/payout live-status channels and scheduled CSV/PDF reports |
The API belongs to a business workflow.
-
Customer checkout
Connect crypto collection inside the purchase journey.
-
Individual requests
Create and share a hosted payment request.
-
Outbound crypto batches
Understand file requirements, approval and reconciliation.
Before you connect payments.
Details for your next decision.
-
What payment functions are available?
The merchant API covers payment intents, deposit addresses, quote and conversion workflows, supported crypto payouts, managed-account flows and fiat wire withdrawals. Eligibility and account configuration determine access.
-
How are changes delivered to our systems?
Configure signed merchant callbacks for payment-status notifications. Use payment-intent search and scheduled CSV or PDF reports to reconcile your records. Checkout live-status channels show individual payment progress; they are not a merchant-wide reconciliation feed.
-
What refund model does the API support?
Eligible failed, excess or duplicate-payment cases can use crypto-refund fee, execution and refund-link functions. Refunds go on-chain in a supported crypto asset, not in merchant settlement fiat. This is not a normal sale-return API.
-
How do we authenticate and test?
The published merchant reference requires API credentials, signed requests and allowlisted source IPs. Its sandbox uses separate credentials and supports documented payment and payout test flows.
-
Where is the endpoint catalogue?
Use the current merchant documentation linked on this page for exact paths, payloads and permissions. It is published under XBO’s Crypto Processing API documentation name.
Explore what else your business can do with crypto.
Explore the services that work alongside this one.
-
API Infrastructure
Connect trading, account operations and crypto payments, with public market data and Virtual Wallets for embedded services.
-
Crypto Trading API
Automate spot orders, OTC conversion and account operations, with signed callbacks that keep your systems informed.
-
Crypto Payment Gateway
Accept crypto payments at checkout and receive supported fiat or crypto settlement in your XBO business account.
-
Crypto Payouts
Prepare bulk crypto payments, validate recipients, confirm the batch and track each transaction through approval and processing.