Common Objects
Shared request/response building blocks that recur across the digital endpoints. Full field-level schemas are in the API reference.
transaction
Identifies a single operation — a client reference (ref), a timestamp, and a type (e.g. TOKEN_REDEMPTION). Present on transactional requests.
channelInfo
Describes the originating channel — a type (e.g. MOBILE_APP) and optional deviceId.
originator
The party initiating the operation — a tokenAccount and fiatAccount (each with id and type), the party name and id, and their institution.
tokenAmount
A tokenized value — currency (ISO 4217), tokens (amount), and tokenType (e.g. TOKENIZED_DEPOSIT).
institution
A financial institution reference — id, name, bin, and routingNumber. Used across onboarding, transfers, and originator/beneficiary blocks.
Account types
Operations distinguish core accounts, digital asset accounts, wallets, and tokenized-deposit holdings. Account validation and balance inquiry support each type.
ExperienceErrorResponse (error envelope)
Every error response is a Problem-style ExperienceErrorResponse with a machine-readable code, message, and correlation id. See Error Handling.
These objects are consumer-facing canonical shapes — they never expose chain, wallet, or ledger internals, so your integration code stays stable regardless of the backing implementation.