Operating Models
Operating Models
Crypto as a Service supports two operating models. The choice determines how balances enter and leave your platform perimeter, not how core primitives work, as both models share the same APIs.
Comparison
| Dimension | Open-loop | Closed-loop |
|---|---|---|
| Model | Balances move between your platform and external destinations | Balances remain inside your platform ecosystem |
| Description | Users send and receive value via fiat rails and crypto networks | Users operate within your internal balance ledger |
| Use cases | Wallets, payout products, cross-border transfers | Investment apps, broker experiences, internal treasury |
| Deposit | User funds from an external bank account or crypto address | User may fund via internal credit or transfer |
| Withdrawal | User settles to external bank account or crypto address | User redeems within the platform; no external payout required |
| Settlement | Funds exit to external destinations (fiat rails or blockchain) | Funds stay within platform; settlement is internal |
Shared primitives
Both models use the same building blocks:
- Onboarding and account readiness
- Pricing and order execution
- Deposits and withdrawals (scope differs by model)
- Async lifecycle tracking and reconciliation
The operating model determines what qualifies as a "destination", not which APIs you call.
For rails and country scope, see Ramps Coverage. For reconciliation architecture, see Reconciliation & Reporting.
For endpoint contracts, see the API Reference.
Updated 27 days ago
Did this page help you?