Identity and idempotency
Payment intent, economic attempt, and provider request remain distinct.
Build on a payment model you can reason about.
Financial truth is deterministic. Provider evidence is traceable. Intelligence operates through bounded tools. Your systems keep their responsibilities.
Explore the architectureIdentity, evidence, and outcome stay distinct.
A lost response stays unknown until the original provider reference is verified. A network retry does not become a second economic attempt.
Preserve the distinctions that matter under uncertainty.
Events and callbacks
Signed raw evidence is verified before it contributes to financial truth.
Unknown outcomes
The same provider reference is verified before a new attempt is considered.
Authority and Intelligence
Recommendations have no execution authority of their own.
Representative API contract
POST /payments/{payment}/verify
Idempotency-Key: example-verification
{
"provider_reference": "existing-reference",
"scope": "status_verification"
}Developer access
Integration scope is agreed directly for the applicable account, environment, and reviewed contract.
Discuss an integration