DORIC · ConceptPreview
Understand the DORIC banking model
Learn how owners, accounts, balances, payments and continuous control form the current DORIC preview model.
- Audience
- Developer, Solution architect, Risk and compliance
- Owner
- DORIC product architecture
- Last reviewed
- Jul 19, 2026
- Reading time
- 10 min
On this page
Resource boundaries
An account represents one owner's position in one settlement currency. Its balance is expressed in the currency's minor unit and its lifecycle is independent from payment execution.
A payment represents controlled movement from one account to another through a supported rail. Payment requests retain the source, destination, currency and amount required to validate the movement.
Customer, lending, treasury and broader control capabilities are part of the DORIC product direction. The repository's public preview contract currently documents accounts and payments as the available resource surface.
From relationship to movement
- 01OwnerA customer or legal-entity identifier anchors the banking relationship.
- 02AccountOne owner can hold distinct accounts for supported settlement currencies.
- 03PaymentA movement connects source and destination accounts through a declared rail.
- 04EvidenceRequest IDs, idempotency keys and resulting state preserve operational context.
Account lifecycle states
pendingstate- Provisioning or required controls are not complete.
activestate- The account can participate in supported workflows.
frozenstate- Movement is restricted while the account remains represented.
closedstate- The account has reached a terminal lifecycle state.
Continue learning