Architecture
Deterministic financial execution architecture.
Orangepill executes financial workflows through a deterministic runtime that coordinates providers, wallets, tokens, and ledger state. The architecture ensures that every financial action resolves once and produces a verifiable outcome.
Core Principle
Every financial action must resolve deterministically.
No partial settlement. No ambiguous lifecycle.
Execution Model
Lifecycle-controlled financial execution.
Each financial operation progresses through a controlled lifecycle. The runtime enforces deterministic state transitions that ensure authorization, settlement, fulfillment, and ledger recording occur in the correct sequence.
Intent → Authorization → Settlement → Fulfillment → Ledger
Flow Orchestration
Flows orchestrate financial workflows.
Flows define the steps required to complete a financial operation. Each step coordinates providers, wallets, tokens, and ledger updates while the execution engine enforces lifecycle rules and idempotent processing.
- Collect payment
- Reserve wallet balance
- Split settlement
- Trigger payout
- Issue token
- Record ledger entry
Execution Runtime
Composable financial primitives.
The execution runtime operates on a set of composable primitives that represent financial state and actions.
- Flows — orchestrate financial workflows
- Orders — represent financial intent
- Wallets — manage balances and custody
- Tokens — represent programmable assets
- Providers — connect to external financial rails
- Ledger — authoritative record of financial outcomes
Ledger Authority
Ledger as ground truth.
The ledger is not a reporting layer. It is the authority — double-entry enforced, referential integrity protected, and reconciliation invariants continuously verifiable.
Wallet Primitive
Wallets are core objects.
Wallet logic lives inside settlement boundaries: reservations, capture/refund semantics, hybrid wallet and external flows, merchant accounts, and multi‑currency support.
Proof of Record
Verifiable execution outcomes.
Every completed financial operation produces an auditable record that links lifecycle state, ledger entries, and execution context. These records provide a verifiable proof of how a financial outcome occurred.
Audit-Ready by Design
Every execution result is documented, reconcilable, and reviewable without manual stitching.
Provider Orchestration
Provider and rail orchestration.
Providers connect the execution runtime to external financial systems such as banks, payment processors, and settlement networks. Flows coordinate these providers while the runtime enforces lifecycle integrity and ledger recording.
Deterministic Processing
Deterministic and idempotent execution.
The runtime enforces idempotent processing and deterministic replay rules. Retries and duplicate requests collapse into a single authoritative outcome recorded in the ledger.
Tenant Isolation
Tenant isolation.
Each tenant operates within an isolated execution context. Financial state, permissions, and ledger records remain scoped to the tenant environment.
Agent‑Ready
Autonomous systems can execute safely.
Financial primitives are exposed through deterministic boundaries. Agents can initiate payins, trigger payouts, create orders, query balances, and execute workflows without violating integrity.
Architecture Diagram
Review the execution control plane.
Understand how deterministic execution ensures reliable financial operations.