Execution ambiguity
A timeout does not tell you whether money moved. Retrying blindly can move it twice.
Financial Execution Control Plane
The financial execution layer across providers and rails.
Orangepill is the financial runtime that orchestrates, executes, verifies, and resolves financial operations across fragmented providers and rails.
- Orchestrate Journeys, policy and decisions
- Execute Authorized movement of value
- Verify Internal state vs. provider reality
- Resolve Governed action when evidence is unclear
The problem
Fragmented financial execution breaks in three predictable ways.
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.
What do you need to solve?
Start from the problem.
Payment Performance
Increase payment success and reduce the cost and fragility of multi-provider acceptance.
See how →Payout Reliability
Execute payouts across multiple providers without unsafe retries or duplicate beneficiary payments.
See how →Financial Operations
Turn multi-step money operations into governed, auditable financial lifecycles.
See how →Agentic Finance
Give software agents bounded authority to initiate financial actions under identity, policy, budgets, and approvals.
See how →Platform overview
One runtime between your product and the rails.
Workflows decide. Execution moves value. The runtime checks each outcome against what the provider actually did, and governs the cases where the two disagree.
- Customer / Merchant / Agent
- Orchestrate
- Execute
- Verify
- Verified outcome Internal and external state agree
- Resolve Mismatch or ambiguity
Why Orangepill
Most stacks route transactions. Few govern what happens to them.
Lifecycle authority
Each operation is governed as one financial lifecycle, from intent through provider attempts to a final state.
Execution →Ledger-backed financial state
A balance is not a number. It is the result of financial events in a double-entry ledger.
Wallet & Ledger →Proof + Resolve
Explain how every outcome was produced, and govern the ones that are ambiguous instead of guessing.
See how Resolve works →Payment platforms, orchestration layers and ledger infrastructure each solve part of this well. How Orangepill differs →
Show me
A payout through a fragmented provider stack.
- Intent Payout requested, idempotency key checked
- Reserve Reservation recorded against the wallet
- Attempt Provider selected, attempt sent
- Observe Provider outcome recorded
- Post Ledger updated
- Verify Checked against provider reality
Provider A declines, and the decline is final
Nothing left through Provider A, so an attempt with Provider B under the same intent is safe.
Provider A times out
The money may still move. Do not guess and do not send it again: establish finality first, and only then retry, wait, or escalate. That decision is what Resolve governs.
Status: payouts and ledger posting run in production. Automatic failover exists today only for pay-in payment requests (such as Bre-B QR and key). Payout failover and Resolve are in development.
Developers
One request. The runtime owns the rest.
The v4 API is described by an OpenAPI contract. Send a payout with an idempotency key, follow its status, and receive signed webhooks for payments. In the sandbox, test failure outcomes, not only success.
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": "1500000", "currency": "COP" },
"recipient": { "scheme": "ALIAS", "value": "<beneficiary alias>" },
"source": { "type": "wallet", "wallet_account_id": "<wallet account id>" }
}Integrations
Connected to the financial and operational systems you already use.
- Kushki
- Wompi
- Movii Bre-B
- Vita Wallet
- Infobip
- Meta WhatsApp Cloud API
- Shopify
- WooCommerce
- Didit
- OpenAI
- Anthropic
Trust
Explicit about what is guaranteed, and what no runtime can guarantee.
Unknown is recorded as unknown. There are no exactly-once promises across external systems Orangepill does not control, and no claimed certifications that do not exist.
Bring one real flow.
A payout, a wallet funding path, a remittance corridor. We will walk through how the runtime would govern it.