Intent and limits
See the amount, payee, and payment-method limits behind the proposed payment. The VeriProof SDK can check the payment against the mandate's limits inside your application, before anything is sent.
Agent payments, AP2
Keep payment authority in view
What was the agent allowed to spend, and did it stay inside that? Keep the mandate, the policy decision, and any review with the payment, so the question has an answer before anyone has to ask it.
Follow the payment from authority to outcome
A payment reference tells only part of the story. Bring the mandate, the decision, and the reported outcome into one record.
Policy decision
An allowed payment and an exception need different handling. Your application applies the policy result before it proceeds, and the decision is kept for review.
Outcome and review
Connect the payment system's reported outcome with any reviewer's decision, so your team can find the payment again when questions come up.
Give reviewers the decision and its evidence
A record to investigate
An evidence pack brings the mandate context, policy results, review history, and integrity proofs together. Reviewers can examine the decision without piecing it together from separate conversations.
Integrity that can be checked
Records are sealed in Azure SQL Database Ledger by default, or on the Solana blockchain if your environment was set up that way. A reviewer can check that a protected record hasn't changed.
Keep your payment infrastructure
Your payment provider, wallet, and mandate service keep their roles. VeriProof adds policy checks and evidence around the payment action your application controls.
See the AP2 integration for how mandate checks, policy decisions, and payment records connect.
Planning an AP2 payment workflow?
Talk with us about the payment decisions your team needs to control and explain.