Institutional product desk
Family offices, crypto-native managers, and bank or broker product leads lose months reconstructing gated white-label crypto rails from scattered public docs. The worked example is getting started with Binance Crypto-as-a-Service — CAAS, also documented as Binance Link and formerly Exchange Link — published here as an independent buyer screen, not as official vendor documentation.
Primer Desk does not operate that product, does not onboard anyone onto it, and does not speak for its publisher.
Ripple's 6 October 2026 release says Ripple Prime will provide multi-asset prime brokerage, clearing, and financing to Brevan Howard funds. This desk does not adopt the release's figures.
Why a desk wastes the cycle
01
Gated white-label and rails products are sold in meetings. The spec, when it exists, is split across overviews, integration guides, FAQs, and changelogs. Buyers rebuild it by hand.
02
Which key signs which call. Whether a sandbox exists. Whether two commercial models can run together. Whether a client account can withdraw. Those are onboarding decisions. They are costly to discover in production.
03
Each primer ends in something a product lead can take into a vendor meeting. Plan-band pages show the frame before the evidence is filled. Nothing here is a license, an affiliation, or a performance claim.
MENA and APAC books that need the operating facts before a rail is approved.
Teams that already trade, and still have to explain the custody and fiat path to an IC.
Product owners shopping CaaS and white-label crypto APIs against an existing control framework.
From the public CAAS docs, compressed on Getting started with Binance CaaS. Primer Desk is independent of the vendor. Custody, OTC, and fiat are a separate plan-band screen, still unscored.
The public getting-started page lists the order. Finish onboarding and confirm the commercial model: revenue share or markup, not both. Map each end user to one sub-account and create it. Pass KYC before creating the key. Enable extra wallets, including futures, before the key. Create the sub-account API key, set permissions and IP restrictions, then prove readiness on a small set of real accounts. Availability depends on institutional onboarding, jurisdiction, the contracting entity, and the approved commercial model. Primer Desk does not open those accounts.
No. The public docs say CAAS, KYC SaaS, and Markup have no separate test environment. Readiness is checked on production, on a few real sub-accounts, with minimal balances. Institutional Buy/Sell has a QA environment for that module only. The CAAS accounts under it are still production.
The master key signs broker calls: create accounts, transfer, commission, and withdrawals. The partner creates that key. The vendor does not issue it, and it stays on the backend. A sub-account key trades for one end user, fetches that user's deposit address, and opens that user's stream. It does not withdraw to an external address.
The 10 September 2026 change log is a documentation rename, not a behaviour change. Exchange Link is presented as CAAS. Link and Trade is presented as OMS Toolkit. Paths sit under /products/caas/. The change log says old links redirect. A previously bookmarked Exchange Link introduction has also been observed to 404, so confirm any saved URL still resolves.
Newest first
01
24 Oct 2026 · 14 min
Primer 01
Getting started with Binance Crypto-as-a-Service from public docs: master key versus sub-account, no sandbox, revenue share or markup, and withdrawals that leave only from the master.
02
17 Oct 2026 · 5 min
Primer 02
A plan-band scorecard. Twelve controls for custody, OTC, and fiat, with the pass test written and every score left open.
03
10 Oct 2026 · 4 min
Primer 03
A plan-band frame for off-exchange settlement, triparty collateral, and capital introduction. The test is operational weight. Nothing is scored.
Start with the published screen.
The filled primer is getting started with Binance CaaS. Two are plan-band outlines, so you can see the frame before the evidence is in.