Architecture
Financial OS architecture
Orangepill provides the orchestration layer between applications and financial rails.
Financial OS
The Financial Operating System
Modern digital products need programmable access to financial infrastructure.
Payments, wallets, tokens, and bank rails are typically fragmented across multiple providers.
Orangepill acts as the orchestration layer between applications and financial rails.
Instead of integrating each provider individually, developers integrate once with Orangepill.
Layer 1 — Applications
Products and platforms that initiate financial activity.
- Marketplaces
- Fintech apps
- Platforms
- Superapps
Layer 2 — Orangepill Financial OS
Orchestration layer that manages logic, routing, and flows.
- Payment orchestration
- Wallet infrastructure
- Token issuance
- Flow automation
- Agent integrations
Layer 3 — Financial Rails
Execution layer where transactions settle.
- Bre-B
- Cards
- Wallet networks
- Bank transfers
Control Plane vs Data Plane
Orangepill separates orchestration logic from financial execution.
Control Plane
- Routing decisions
- Payment orchestration
- Flow automation
- Risk rules
- Observability
Data Plane
- Financial transactions
- Ledger entries
- Wallet balances
- Token movements
Canonical financial objects
Orangepill exposes a consistent set of objects that abstract rail-specific complexity.
Payment
Represents a financial transaction initiated by an application.
Checkout Session
Customer-facing payment experience that can route across methods.
Payment Attempt
A specific execution attempt against a financial rail.
Wallet
Programmable account storing balances and movements.
Ledger Entry
Immutable record of value movement for reconciliation.
Token
Programmable unit of value such as vouchers or loyalty points.
Flow
Automated workflow coordinating payments, wallets, and tokens.
Why orchestration matters
Financial infrastructure is fragmented. Orchestration solves the integration and operational burden.
- Each payment provider requires a different API and settlement model.
- Wallet systems are difficult to build, reconcile, and maintain at scale.
- Token programs require custom infrastructure for issuance and tracking.
- Payment retries and routing logic are complex to manage across rails.
Orangepill orchestration
Centralize routing, retries, wallets, and token logic in a single control plane while rails execute the underlying transactions.
Global financial rails
Orangepill connects applications to multiple rails so products can expand without rebuilding infrastructure.
- Bre-B (instant payments)
- Card networks and local card processors
- Digital wallets and stored value systems
- Bank transfers and push payments
Operate across ecosystems
Integrate once to support new rails, providers, and regions through Orangepill orchestration.
From infrastructure complexity to programmable finance
Orangepill abstracts financial complexity behind simple APIs and consistent objects.
const checkout = await orangepill.checkout.sessions.create({
amount: 50000,
currency: "COP"
})Start building with Orangepill
Get access to programmable financial infrastructure and launch faster.