Payment Intelligence
Payment Intelligence is the input layer of every decision. It continuously gathers payment context, PSP telemetry, provider health, risk signals, cost and retry data, and outcome feedback, and keeps them cached so the Decision API always evaluates current signals without calling a provider on the hot path.
The inputs every decision is made from
Signals are gathered and refreshed off the decision path, so the decision itself is pure computation over cached inputs.
Frequently asked questions
Common questions about Payment Intelligence and how Payinference works.
No. The API accepts only safe payment context, such as amount, currency, country, payment method and network-level signals. Request schemas are strict and reject PANs, CVVs and customer identity at the boundary, so card data cannot enter the system even by accident.
Payinference is provider-neutral by design. Because it never calls a PSP itself, it needs no provider integration to work. Each decision request lists the providers available to you, and you execute the instruction through the stack you already run.
The decision path is built for the authorization hot path. It computes from cached policy, cached provider health and cached pricing, with no PSP calls and no LLM calls, targeting under 50 ms at p95 with typical decisions around 1 ms.