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

DimensionOpen-loopClosed-loop
ModelBalances move between your platform and external destinationsBalances remain inside your platform ecosystem
DescriptionUsers send and receive value via fiat rails and crypto networksUsers operate within your internal balance ledger
Use casesWallets, payout products, cross-border transfersInvestment apps, broker experiences, internal treasury
DepositUser funds from an external bank account or crypto addressUser may fund via internal credit or transfer
WithdrawalUser settles to external bank account or crypto addressUser redeems within the platform; no external payout required
SettlementFunds 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.


Did this page help you?