Integration guide:Payment, Settlement and payout APIsReconciliation and Webhooks
Payment API handles multi-channel collection; settlement and bill payout APIs map to large-value conversion and mid/small payouts respectively. Webhook and reports make all three flows trackable and reconcilable inside the merchant’s systems.
Start a merchant enquiry
Confirm permissions, signatures and reconciliation rules before integrating
The public site describes core integration capabilities; full API docs, sandbox, event naming and status flows are provided after merchant review, within the approved service scope.
- API key permissions should be separated by use — avoid mixing collection and payout permissions.
- Webhook should use signature verification, retry handling and idempotent design.
- Finance systems should reconcile across four data types: transactions, fees, settlement and payouts.
- Higher-risk transactions or large payouts may enter manual review.
Three API types: who calls, which events, who reconciles
Designed for real operations — not just a pay button.
- Payment API: create orders, obtain payment addresses, query status, handle payment-confirmation events.
- Settlement API: request large-value settlement quotes, query conversion or crypto-retention status and fees.
- Bill payout API: initiate payouts, query status and failure reasons.
- Webhook and Dashboard: receive events for operations and finance to view in one place.
Integration design
Beyond APIs: reconciliation, status sync, wrong-chain, failed payouts and fees.
- Idempotency keys to prevent duplicate orders or payouts.
- Webhook signature verification and retries.
- High-risk or large amounts may return review_required.
- CSV reports for reconciliation and fee breakdown.
Understand first, then start.
On scope, settlement vs payout, and what to prepare before onboarding.
Which merchants suit an API?
Platforms, high-volume traders, and merchants that need auto order creation, payment-status sync, batch payouts or connection to internal finance systems.
Must review complete before API docs are provided?
The public page explains core integration capabilities; full field specs, sandbox, event naming and permission configuration are provided after merchant review, within the approved service scope.
Does Webhook need signature verification?
Signature verification, retry handling and idempotent design are recommended to avoid duplicate credits or incorrect status sync.
Can I use Dashboard only without an API?
Yes. Lower-volume merchants can start with Dashboard, Payment Link or Invoice; high-volume or platform merchants can add API later.
Ready to enquire? Bring the basics in one go
Company, region, use case and expected scale — clearer notes get faster replies.IDs can follow the review checklist later; copies are not needed on first contact.
Start a merchant enquiry