Who this is for.
We've seen four use cases drive most of our B2B API integrations:
Crypto exchanges
Add fiat on/off-ramp without building a P2P module from scratch. Route MYR ↔ USDT trades through our matching engine; users on your platform never see CoinOrder.
Fintechs and neobanks
Offering stablecoin balances or USD-exposure products. You hold customer balances; we provide the rail to source/dispose of USDT against MYR.
OTC desks
Routing larger flow that doesn't fit into a single retail order. Programmatic access lets you split trades across multiple counterparties automatically.
Treasury and corporate users
Managing crypto operations programmatically — payroll, vendor payments, cross-border settlement.
If you're building something in this space and not sure if it fits, reach out — we'd rather have an honest 20-minute call than a misaligned integration.
What the API gives you.
Order matching
Submit buy or sell orders programmatically. Get matched against the live counterparty book. Receive match events via webhook.
Escrow management
On match, the asset side is locked in escrow automatically. Status changes (locked, payment-confirmed, released, disputed) flow through webhooks.
Settlement and dispute
Confirm payment receipt or release programmatically. Open or respond to disputes with evidence attachments. Get final-state events (released or refunded) via webhook.
Account and balance queries
Standard REST endpoints for balance, trade history, account status, and KYC tier verification.
Webhook events
order.createdorder.matchedescrow.lockedpayment.confirmedescrow.releaseddispute.openeddispute.resolved(Confirm exact event names with team before publishing.)
Authentication.
API access uses signed requests with API key + secret. Standard pattern:
- • API key in header:
X-CoinOrder-Key - • Request signature in header:
X-CoinOrder-Signature(HMAC-SHA256 over the request body and timestamp) - • Timestamp in header:
X-CoinOrder-Timestamp
IP allowlisting available for production keys. Sandbox keys are permissive for development.
Sandbox before production.
Every approved partner gets sandbox access before production keys. The sandbox:
- • Mirrors production endpoints, schemas, and webhook events
- • Uses test USDT and simulated counterparties
- • Lets you build and test against real-shape data before any real funds move
- • Resets nightly so you can replay scenarios from a clean state
Standard onboarding flow
- 1Request access via the form below
- 220-minute discovery call with our team
- 3KYB review (company docs, beneficial ownership, AML check)
- 4Sandbox keys issued
- 5Integration build + testing
- 6Production review + production keys
- 7Go live
Most integrations finish in 2–4 weeks of development work depending on scope.
Pricing.
Same flat 1 USDT per trade as the retail platform — no percentage cuts as your volume grows. At scale this matters: if you're routing $10M of monthly volume, percentage-based fees on a competing platform run $10K–$50K/month. Our flat structure keeps that closer to a few hundred dollars regardless of volume.
Volume tiers and contractual rates are negotiated for partners doing meaningful flow. Talk to us.
Security and operational guarantees.
Segregated escrow
Partner-routed escrow held in addresses operationally separated from retail and from other partners.
Audit logs
Every API action logged with request signature, timestamp, and result, exportable on request.
SLA
Production uptime targets and incident response timelines disclosed in the partner agreement.
Compliance
KYB/KYC, transaction monitoring, sanctions screening at the partner and counterparty level.
Request access.
Tell us a bit about what you're building and we'll get back to you within 1 business day.