Observability
Observability is the evidence layer. Every decision is recorded with its instruction, matched rules, reason codes, confidence and the reported outcome, so you can replay why any instruction was issued, audit how policy behaved, and see how decisions perform against real results.
Replay why any instruction was made
Decisions are only trustworthy if they are explainable after the fact, so every record is built for review.
Frequently asked questions
Common questions about Observability and how Payinference works.
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.
Deciding what should happen to a payment before it touches a rail. Payinference evaluates provider health, cost, risk and your merchant policy in real time and turns them into a single instruction with reason codes, so routing, retries, step-ups and blocks are deliberate, explainable decisions instead of static defaults.
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.