Concepts#
Use concepts when you need the platform model before you read workflows or raw API reference. This section explains the typed reference system, the nesting of tenant and financial objects, the canonical operation model, and the control and delivery surfaces that sit around execution.
These pages are not procedural guides. They are the fastest way to understand how public resources relate to each other, which identifiers belong where, and which API surfaces act as topology boundaries, execution boundaries, governance boundaries, or audit boundaries.
Quick Access#
T
Topology And Refs
Understand how typed refs separate topology boundaries, financial account boundaries, and broader resource references.
A
Accounts
Read how master and client accounts hold balances, how available, held, and total split a balance, and where overdraft fits.
I
Identity
Read how human actors, service principals, platform-hosted and federated humans, and on-behalf-of flows establish who is making a call.
G
Access
Understand how capabilities, scopes, and role assignments combine into authorization, and how machine-native and human-governed actions differ.
R
Rail Classes
Read the fiat-vs-crypto contract that governs how funding endpoints, withdrawal destinations, and deposit instructions are configured and routed.
F
Funding Endpoints
Define the durable inbound routes for a tenant: which rail, which asset, and how the platform tags inbound activity back to the right perimeter.
W
Withdrawal Destinations
Define the durable outbound routes for a tenant: which rail, which asset, and where the platform delivers funds when a withdrawal executes.
C
Conversions And Pricing
Read the three-layer model that splits conversion discovery, pricing previews, and execution into distinct surfaces with distinct semantics.
X
On-Ramp And Off-Ramp
Coming soon: canonical model for on-ramp and off-ramp operation families, including sessions and settlement records.
O
Operations
Read the canonical money-movement model that unifies multiple families behind one operation lifecycle and read model.
K
Idempotency And Concurrency
Use `Idempotency-Key` to make creates retry-safe and `If-Match` to make updates concurrency-safe; read both as separate cross-cutting tools.
P
Policies And Approvals
Coming soon: canonical policy resources and approval cases that gate sensitive operations through the runtime lifecycle.
$
Commercial Agreements
Coming soon: versioned configuration that controls how fees apply to operations, split between platform-level and enterprise-level agreements.
E
Events And Webhooks
Separate pull-based audit history from push delivery, and understand how events and webhook endpoints complement each other.