Getting Started
Use this section to prepare and sequence a Institutional Crypto Buy/Sell Solution integration within Crypto-As-A-Service (CAAS).
Before you begin
This module uses a server-to-server integration model. Most requests require a userId, which is the customer's Binance sub-account ID created or mapped through the approved CaaS onboarding flow — see CAAS Overview for the account model and KYC SaaS for the customer onboarding flow that produces it.
Two things must be in place before you call anything:
- A CAAS account with this module enabled by the Link team. It is enabled per partner, on top of your CAAS integration.
- The customer's sub-account KYC passed through KYC SaaS. A sub-account cannot trade until its KYC has passed, so Buy and Sell will not work for that customer before then.
Recommended integration order
-
Complete CAAS onboarding.
-
Confirm the institutional account structure and customer userId lifecycle.
-
Agree the fiat fund flow, settlement model, supported currencies/assets, limits, and spread configuration.
-
Apply for Developer's Account, exchange public keys, configure API credentials, and allowlist server IP addresses.
-
Implement request signing and verify a discovery endpoint in QA.
-
Implement the required Buy and/or Sell flow.
-
Implement the required partner-hosted fiat confirmation, refund, and payout APIs.
-
Implement webhook signature verification and transaction-status recovery by polling.
-
Complete negative-path testing, reconciliation validation, operational readiness, and production approval.