Skip to main content

Onboarding Checklist

The path from first sandbox call to production keys. Your TBook contact tracks this with you.

Sandbox phase​

  • Keys received — tbk_test_* issued; you can call GET /v1/assets.
  • Account model chosen — individual / omnibus / treasury / business per product line (guide); custody approach confirmed (WaaS provider, backend keys, or multisig).
  • Compliance attestations wired — compliance.kyc.attested (individual/omnibus) or compliance.kyb.attested (business) set before the first deposit; unattested deposits return 403.
  • Quickstart completed — full deposit → settle → webhook → positions loop on rcusdp-sui (Quickstart).
  • Webhook endpoint live — signature verification passing against real sandbox deliveries (trigger a deposit and POST /v1/sandbox/settle), idempotent consumption keyed on event.id.
  • Full cycle on your integration — deposit, queued redeem, claim, and cancel-deposit executed through your code, not curl.
  • Error handling reviewed — cycle_closed retry, expiresAt rebuild, 409 vault_paused handling, idempotency keys on all money movements.
  • Omnibus only: reconciliation demonstrated — your sub-ledger total equals the pool position across two settlement cycles, including a simulated rollback reversal.
  • Treasury/business only: allowlist + (if enabled) dual-approval flow exercised; multisig signing within expiresAt confirmed.
  • XAUa only: whitelist process agreed (pool/treasury wallet whitelisted, or individual batch flow scheduled).

Production phase​

  • Compliance docs exchanged — organization KYB, attestation process for your account types, user-disclosure language (omnibus).
  • Production keys issued — stored in your secrets manager; never in code or logs.
  • Webhook endpoint(s) for production — separate URL + secret from sandbox.
  • Deposit caps agreed — initial per-organization caps and the raise schedule.
  • Go-live — first production deposit witnessed end-to-end with your TBook contact; hypercare channel open.

After go-live​

  • Monitor GET /v1/events for failed deliveries and your reconciliation job (omnibus).
  • New assets appear in your catalog when enabled for your organization — no code change needed.
  • Production support and escalation paths are in your onboarding pack.