Outcome observability
Outcome observability closes the loop between what was decided and what actually happened. Outcomes reported to /v1/outcomes are joined to the decisions that produced them, turning approvals, retries and failovers into evidence you can inspect, and into the feedback that keeps future decisions honest.
Decisions in one system, results in another
Routing logic lives in your code; results live in PSP dashboards and data warehouses. Joining them is a manual analytics project, so nobody really knows whether the routing, retry or risk logic is helping, and the logic itself never finds out either.
Decisions and outcomes, one record
- 01Report what happenedAfter executing an instruction, your backend reports the result to POST /v1/outcomes. Reporting is always free.
- 02Joined to the decisionEach outcome is joined to the decision that produced it. Instruction, reason codes, route scores and result sit in one record.
- 03Inspect decision qualitySee how instructions performed against real results, including shadow decisions evaluated against live traffic before enforcement.
- 04Feedback keeps decisions honestOutcomes flow back into provider health and routing intelligence, so the system learns from evidence, not assumptions.
The products behind it
Every solution is the same four-part architecture doing its job. These are the parts doing the heavy lifting here.
Frequently asked questions
Common questions about outcome observability with Payinference.
Two endpoints. Your backend calls POST /v1/decision with safe payment context and receives one instruction. You execute that instruction through your own providers, then report what happened to POST /v1/outcomes so future decisions keep improving. A server-side SDK wraps both calls.
In shadow mode Payinference returns decisions and records what it would have done while your existing logic keeps executing, so you can evaluate decision quality against real traffic with zero risk. In enforce mode your stack executes the returned instruction.
One call to POST /v1/decision. Reporting outcomes to /v1/outcomes is always free, and the first 1,000 decisions each month are included at no charge. Shadow and enforce decisions run the same decision path and are billed the same.