Crypto as a Service (CaaS)

Crypto as a Service (CaaS)

Official API Reference

BitGo Developer Portal — Introduction to BitGo

^^ The developer portal is the primary technical resource for building a CaaS integration. Everything below complements what is covered there — it does not replace it.

What the Developer Portal Covers

The portal provides end-to-end guidance for CaaS integrations:

• Hierarchy Model — The Organization → Enterprise (Parent + Children) → Go Account structure that underpins every CaaS deployment
• Organization & Enterprise Setup — Creating and configuring your parent organization and child enterprises programmatically
• KYC/KYB Submission — Onboarding end-users and business entities through BitGo's identity verification flow
• Go Account Activation — Enabling trading and custody for verified users
• Wallet Management — Creating, listing, and managing wallets across supported assets
• Trading & Order Execution — Placing spot buy/sell orders on behalf of end-users through BitGo's liquidity network (margin trading is not available for CaaS)
• Fiat On/Off Ramps — ACH deposits and withdrawals for USD-based flows
• Policy Configuration — Setting spend limits, approval requirements, and withdrawal rules at the enterprise level
• Webhooks & Notifications — Subscribing to real-time events for transaction status, KYC completion, and account changes
• Postman Collection — A ready-to-use collection for testing every endpoint in your sandbox environment

What CaaS Is

CaaS lets any business — fintech, neobank, brokerage, wealth platform — offer crypto buying, selling, and custody under their own brand. BitGo handles the infrastructure, custody, compliance, and liquidity behind the scenes. Your users never see BitGo.

How the Regulatory Model Works

The most important question in any CaaS engagement: does your company hold a crypto-specific license?

Important: Admin Console/User Management System is disabled for CaaS Organizations/Enterprises

Jurisdictional Rules

Each BitGo Organization maps 1:1 to a single Trust Entity based on where your users are:

• US → BitGo Bank & Trust, N.A.
• EU/EEA → BitGo Europe GmbH
• APAC/International → BitGo Singapore Pte. Ltd.
• MENA (UAE) → BitGo Custody MENA FZE

Serving users across multiple regions? You'll need multiple Organizations.

Important: BitGo cannot service users in the United Kingdom (UK). If your user base includes UK residents, contact BitGo support to discuss your options.

KYC: What to Know Beyond the API

The developer portal covers the KYC submission flow. Here's the operational context:

• US (default): Full KYC via BitGo's identity verification provider. Supports doc-less verification for faster onboarding.
• US (regulated clients): If you're FINRA-regulated with an existing KYC program, BitGo can streamline onboarding by accepting your KYC data — but BitGo's compliance engine remains the final decision-maker, with spot-check rights retained.
• EU: MiCAR-compliant flow. Users who are non-EU residents are automatically declined. Users flagged with risk signals (sanctions hits, PEP status, high risk scores) are routed to manual review.
• B2B (KYB): Programmatic business entity verification via API — no end-user-facing verification UI required.
• FBO / No-KYC mode: For crypto-licensed clients using CaaS purely for ledgering under a For Benefit Of (FBO) model, KYC may not be required. Contact BitGo support to determine if this applies to your use case.

Important: Each child enterprise supports one identity verification attempt. If verification fails or expires, a new child enterprise must be created for that user. Contact BitGo support if you need assistance with recovery.

Fund Flow Patterns

How money moves through your integration depends on your operational needs:

1. Direct — User funds go straight into their Go Account. Simplest setup.
2. Mirror — Funds route through the parent enterprise first. Adds control over fund movement.
3. Centralized — All funds aggregate at the parent level. Maximum control, but requires more reconciliation on your side.

ACH: Key Details

For US fiat on-ramps:

• A fraud reserve (typically $25K minimum) is required in the parent enterprise Go Account
• ACH feature flags must be explicitly enabled in both test and production environments — they are not on by default. Contact BitGo support to activate ACH for your organization.
• Built-in risk scoring calibrates hold times before users can deploy deposited funds

Configuration Issues

CaaS integrations require specific configuration on BitGo's side during onboarding. If you encounter unexpected behavior — such as settings not inheriting to child enterprises, account activation failures, or errors during enterprise creation — contact BitGo Support. These issues typically stem from configuration that BitGo manages on your behalf.

Getting Started

1. Open the developer portal and grab the Postman collection
2. Walk through: hierarchy setup → child enterprise creation → KYC submission → Go Account activation → policy configuration → first trade
3. Use this article as context for the why behind the structure you're building