Solution: Exchange & OTC Desk

A worked walkthrough for an exchange, OTC desk, or buy-and-sell crypto operation that needs a custodial wallet stack with the full order lifecycle: customer pays in fiat, you confirm receipt, you transfer crypto from custody to the customer.

The scenario

You operate a crypto exchange, an OTC desk, or a buy-and-sell crypto product. Your business model is not “merchants accepting crypto”; it is “customers buying and selling crypto from us”. Your operational reality is:

A customer initiates an order to buy or sell crypto.
They pay you in fiat (bank transfer, card, or local-payment-rail).
Your team confirms receipt of the fiat.
You disburse crypto from your treasury to the customer’s wallet, or you settle a sell order in the opposite direction.
You reconcile every leg of the trade against your accounting.

You need a custodial backend that supports this order flow natively, not a payments-acceptance system that sees individual on-chain transactions in isolation.

Recommended custody model: custodial Asset Pro with order lifecycle

This scenario uses a specific extension of our custodial Asset Pro model: the Asset Pro Order workflow. Where a basic Asset Pro transfer is “send X stablecoins to address Y”, an Asset Pro Order is a structured order:

Order created — customer indicates they want to buy a quantity of a specific asset on a specific chain at an agreed rate.
Customer pays in fiat — typically a bank transfer to your operating account on your existing fiat rail.
Your operations team confirms the fiat received — through the Studio order detail view, capturing the customer transfer time, amount, and the last few digits of the source account for reconciliation.
Crypto disbursement — the order’s “transfer” action releases the crypto from your treasury, going through the same multi-sig (Maker / Approver / Signer) pattern as any other Asset Pro transfer.
Order settled — full audit trail captured.

For sell-side flows, the operational direction is reversed: the customer sends crypto to a designated receive address, your team confirms receipt, you disburse fiat through your existing rails.

Recommended auth model: your customers in your app, your operators in Studio

Your customers authenticate to your app or website with whatever auth you already use. They do not log into KryptoGO. From their perspective, “buying crypto” is a feature of your product.

Your operations team — the people who confirm fiat receipts and authorise the crypto disbursements — log into the Studio control panel directly under the Maker / Approver / Signer roles described in Team, Roles, API Keys & Risk Limits.

For automated paths (a fiat-rail webhook that confirms receipt without human intervention; a programmatic order disbursement after policy checks), you use a Studio API key with the appropriate scoping.

Architecture, end to end


┌────────────────────────────────────────────────────────────────┐
│  Your exchange / OTC desk                                      │
│                                                                │
│   Customer initiates "buy 100 USDT" in your app                │
│           │                                                    │
│           ▼                                                    │
│   Your backend creates an Asset Pro Order via Studio API       │
│           │                                                    │
│           ▼                                                    │
│   Customer pays fiat to your operating account                 │
│           │                                                    │
│           ▼                                                    │
│   Operations confirms fiat received in Studio                  │
│           │                                                    │
│           ▼                                                    │
│   Order's "transfer" action submitted                          │
└────────────────────────────────────────────────────────────────┘
                               │
                               ▼
┌────────────────────────────────────────────────────────────────┐
│  KryptoGO platform                                             │
│                                                                │
│   Asset Pro Order ──► Maker / Approver / Signer multi-sig      │
│        │                                                       │
│        ▼                                                       │
│   Crypto disbursed from treasury to customer's wallet          │
│        │                                                       │
│        ▼                                                       │
│   Order marked complete                                        │
│        │                                                       │
│        ▼                                                       │
│   Reconciliation entry in your accounting                      │
└────────────────────────────────────────────────────────────────┘

What ships in under one month

Studio organisation provisioned with treasury wallet.
Asset Pro Order workflow integrated into your backend.
Operations team trained on the Studio order-detail view.
A first end-to-end test order: order created, fiat received, crypto disbursed, reconciliation entry confirmed.

What ships in one to three months

Pricing layer integrated — your backend or operations team configure the spread, fees, or profit margin you charge per service (buy, send, swap, gas-sponsored send, batched send). Asset Pro supports per-service profit-rate configuration.
High-volume order processing — multiple operators handling orders concurrently, with per-operator daily limits enforced.
Programmatic fiat-rail confirmation — your fiat provider’s webhook auto-marks the order as “fiat received”, removing manual confirmation for low-risk transactions.
Customer KYC integrated through our Compliance suite, configured for your target markets.
AML risk screening on every order, with policy-driven decision routing.
Sell-side order flow — the inverse direction, customer sends crypto to a receive address you provision per order, your team confirms receipt, you disburse fiat.
Webhook integration for order lifecycle events into your backend.

What needs additional scoping

Order book / matching engine — if you operate as an exchange with a real order book rather than a quote-based desk, the matching engine itself sits outside our scope. We provide the custody and settlement layer beneath it.
Margin or derivatives products — these are a separate regulatory and infrastructure conversation.
Cross-chain settlement — if your treasury holds USDC on Arbitrum but a customer’s order needs to settle on a different chain, the bridging step is a scoping conversation.
Hardware-secured custody for very large positions — beyond the existing TronLink integration.
Custom asset coverage beyond our supported chain and token list.

Compliance posture inherited

For an exchange or OTC desk, the compliance story is central. Operating on KryptoGO infrastructure means:

The custody layer beneath your operation is regulated under a Taiwan VASP licence.
ISO 27001, ISO 27701, and SOC 2 Type II controls cover the storage, access, and operational handling of customer assets in custody.
Per-operator daily transfer limits and per-transaction risk limits are enforceable inside Studio, not bolted on after the fact.
The audit log captures every step of every order — fiat confirmation, approval, signing, on-chain settlement — in a format your compliance team and your auditors can review.
Sanctions screening on customer wallet addresses is inline.
KYC and KYB workflows are operated by us under regulator-approved policies.

Your own regulatory permissions in your target jurisdiction remain your responsibility. We supply the infrastructure layer beneath.

A realistic 12-week timeline

Weeks	Workstream
1–2	Kick-off, security review, paperwork. Studio organisation and treasury wallet provisioned.
3–4	Asset Pro Order integration into your backend. Operations team trained on Studio order-detail view.
5–6	First test orders end-to-end on testnet. Pricing layer configured.
7–8	Customer KYC integration. AML policy configured.
9–10	Programmatic fiat-rail confirmation if applicable. Sell-side flow implemented.
11	Pre-launch operational dry runs. Audit log review with compliance.
12	Soft launch to a controlled customer cohort.

Where to go next

White-Label Wallet — for the underlying custody backend.
Team, Roles, API Keys & Risk Limits — for Maker / Approver / Signer detail.
KYB / KYC Workflow — for customer onboarding.
Custody Options — for the custodial model.
To start a partnership conversation, contact our partnerships team via the address on www.kryptogo.tw .