Execution ambiguity
A timeout does not tell you whether money moved. Retrying blindly can move it twice.
Financial Execution Control Plane
Build financial systems across providers and rails.
Orangepill is the execution runtime that composes payments, wallets, financial state, workflows, and external providers into governed financial operations.
Keep the providers, rails, and customer relationships that make your product valuable. Orangepill gives them one programmable execution layer.
The problem
Financial applications span fragmented systems.
Financial-state drift
Providers, wallets, and internal systems can disagree about the same operation.
Operational recovery
When automation stops, teams reconstruct failures by hand across multiple systems.
Composition
Specialized capabilities are useful. Composition is hard.
Excellent specialists exist for payments, rails, ledgers, identity, messaging, commerce and AI. Real financial applications span several of them. Providers execute capabilities. Orangepill keeps the operation coherent while each of them performs its part.
Your product
Orangepill runtime Intent · Authority · State · Execution · Evidence · Verification · Resolve
Capabilities Orangepill native primitives + banks · PSPs · local rails · FX · identity · messaging · commerce · AI
A financial operation is more than an API request.
- Intent
- Collection
- Financial state
- FX / settlement
- Payout
- Evidence
- Verified outcome
Today, remittance intents track the collection and payout legs of a cross-border transfer as one operation. A single operation object for every kind of multi-step flow is not generalized yet.
Lifecycle
Financial correctness means knowing when to execute, when to wait, and when more evidence is required.
- Orchestrate Journeys, policy and decisions
- Execute Authorized movement of value
- Verify Internal state vs. provider reality
- Resolve Governed action when evidence is unclear
- A timeout is not a decline.
- Provider observations are kept apart from established financial outcomes.
- Retries and failover are allowed only when prior execution can be treated safely.
- No exactly-once promises across external systems Orangepill does not control.
Platform
Three families, one runtime.
Money Movement
Move value across providers and rails without losing track of what each attempt did. Payments, payouts, routing, local rails, FX, cross-border.
Explore →Financial State
Balances that are the result of recorded financial events, not numbers kept in sync. Wallets, ledger, balances, settlement, treasury.
Explore →Programmable Execution
Software, workflows and agents that initiate financial operations under explicit authority. Flows, policies, approvals, Agent Runtime, MCP, economic intents.
Explore →Across all three: Observe · Explain · Reconcile · Verify · Resolve
Examples
Where the runtime earns its place.
Payout reliability
A timed-out payout is not sent again on a guess. Know when to retry, when to wait, and when to resolve.
Handle a payout timeout →Cross-border
Collection, FX and payout run on different providers. Operate the transfer, not a collection of provider calls.
Cross-border execution →Wallet & platform
Balances, reservations and settlement derived from recorded financial events, for products that hold customer value.
Wallet & financial state →Agentic operation
Software initiates financial actions through scoped tools and approvals instead of holding provider credentials.
Agent Runtime →A payout times out.
- Payout submitted
- Provider times out
- Outcome unknown Settlement may still occur
- Resend blocked Paused for review
- Evidence gathered Provider status checks
- Continue / wait / remediate
Status: in production, an ambiguous payout send is paused for operator review instead of being sent again, and
finality is checked with the provider. Governed continuation through
Resolve In Development
is in development. When status checks run out today, the payout is marked failed with
RETRY_EXHAUSTED even without a provider answer, so integrators treat that code as unknown.
Integrations
Keep the providers and rails you already rely on.
Orangepill does not require the whole financial stack to come from Orangepill.
- Kushki
- Wompi
- Movii Bre-B
- Vita Wallet
- Infobip
- Meta WhatsApp Cloud API
- Shopify
- WooCommerce
- Didit
- OpenAI
- Anthropic
Customers
Customers running on Orangepill.
LAQO
Digital insurance
Digital insurance using Orangepill to power Q points loyalty.
CoraSend
Cross-border money movement
Cross-border execution using Orangepill for local pay-ins, cross-border movement, FX / liquidity coordination, local payouts, and wallet / transaction state across multiple rails.
Cross-Border & Remittance →Built on Orangepill
The same runtime underneath specialized applications.
Our venture studio uses the same runtime to build specialized economic applications. The ventures own their product logic, customer experience, distribution, and outcome. Orangepill provides the reusable execution substrate underneath.
Stealth venture · Conversational commerce
An AI-native commerce product that combines customer context, messaging, product discovery, checkout, payment execution, and revenue recovery.
Stealth venture · Community markets
A community and prediction product combining participant identity, incentives, financial state, and settlement around market-specific economics.
Stealth venture · Events finance
A financial operating system for event businesses, composing collections, balances, settlements, payouts, and financial operations around the event lifecycle.
Developers
Build financial operations that survive the real world.
Connect providers, move value, preserve financial state, and handle asynchronous outcomes without rebuilding execution logic for every integration.
Start with a real job: Build a payout · Handle a timeout safely · Build a wallet
POST /v4/payouts
{
"idempotency_key": "payout-000123",
"product_key": "bank_transfer.bre_b",
"amount": { "value": "150000000", "currency": "COP" },
"recipient": { "scheme": "ALIAS", "value": "<beneficiary key>" },
"source": { "type": "wallet", "wallet_account_id": "<wallet account id>" }
}Bring us the financial system you're building.
A payout flow, a wallet program, a cross-border corridor. We will walk through how the runtime would govern it.