A payout times out, but may still settle.
Resolve
When money gets stuck between systems, Resolve figures out what happened and what can safely happen next.
Orangepill Resolve investigates financial operations that cannot safely continue because their outcome or next valid action is uncertain. It gathers evidence across your existing PSPs, banks, risk systems and internal infrastructure, establishes what can be known, and determines what can safely happen next.
No rip-and-replace. Start with one exception flow.
Problem
Payment automation handles the happy path. Resolve handles what escapes it.
As PSPs, banks, risk systems and orchestration layers multiply, the happy path becomes more automated. But the remaining exceptions become harder to resolve. The hardest exceptions are rarely owned by one system.
A withdrawal fails and it isn’t clear whether retrying is safe.
A refund is accepted and later reversed.
A transaction is blocked while another system waits for verification.
The PSP reports one state while your internal system reports another.
A customer asks where their money is and operations must investigate across multiple systems.
These unresolved exceptions pull people into multiple systems to reconstruct what happened, decide what is safe, update the customer and determine whether the transaction can continue. Resolve turns that investigation into a governed machine process and sends only the irreducible remainder to people.
The Distinction
Generic automation knows a task failed. Financial infrastructure needs to know something harder.
Can the previous action still create an economic effect?
That question determines whether retrying, rerouting, refunding or continuing is safe. Retry systems recover failed attempts. Resolve handles cases where you first need to establish whether retrying, or doing anything else, is safe.
Resolve is built around financial evidence, finality, authority and explicit resolution semantics. Not merely workflow status.
Example
An uncertain payout.
Your platform sends a payout to a provider. The request times out.
Resolve doesn't turn uncertainty into a guess. If the evidence cannot support a conclusion, the case remains explicitly unresolved and escalates to a person.
How It Works
How Resolve works.
Resolve doesn't replace your payment stack. It complements it.
Orchestration
More providers shouldn't mean more operational complexity.
Routing and orchestration automate execution across providers. But each provider introduces different statuses, failure modes, finality semantics and operational procedures.
Resolve sits above that fragmentation and handles the cases where orchestration can no longer safely determine what should happen next.
Integration
Start without replacing anything.
Connect Resolve to an existing payment exception flow. Your existing infrastructure stays in place. Resolve observes the systems involved and coordinates resolution around them.
- Your PSPs stay.
- Your orchestration stays.
- Your ledger stays.
- Your operations systems stay.
One exception flow to start.
This makes it possible to begin with one bounded operational problem rather than a payment infrastructure migration.
PSPs and payment gateways · fintechs · wallets · superapps · marketplaces · gaming operators · remittance platforms
Technical Foundation
Built on the Orangepill financial runtime.
Understand financial state
Normalize evidence and provider-specific semantics without pretending conflicting signals agree. Resolve distinguishes observations from established facts and preserves conflicting or insufficient evidence.
Determine the safe next step
Apply resolution semantics and governed intelligence to establish what can safely happen next. AI can assist investigation and reasoning without becoming a source of financial truth or authority.
Keep authority where it belongs
Recommendation, decision and financial execution remain distinct. Resolve can investigate and recommend while the system that owns the financial operation remains responsible for its execution. Resolve then observes authoritative evidence to verify the resulting outcome.
Architecture
How Resolve sits in your stack.
Domains execute. Resolve governs uncertainty.
Show us one exception your team still investigates manually.
We'll map how it is resolved today and determine what Resolve could automate.