Create your demo account
Sign in with a verified email. Get 30 free executions across the fixed scenario catalogue.
PAYMENT TESTING FOR AI-AGENT TEAMS
Before your agent pays,
test the decision.
See how altered authorizations, repeated requests and spending policies change a payment decision. Start with a small, synthetic test set.
30 free runs per account · Verified email required · No card
Registering is covered by how demo data is used — what is stored, where it sits and how to have it deleted.
SCENARIO 06 · AMOUNT CHANGED AFTER SIGNINGIllustrative result
DO NOT PAYThe cart changed
after it was approved.
after it was approved.
What the customer approvedEUR 49.00
What the agent is about to payEUR 4,999.00
Does the signature still match?No
The approval was signed for €49. Someone changed the cart afterwards. TrustedPAI answers before the money moves, and says which of the two figures the customer actually agreed to.
EVERY RUN10 reproducible scenariosReal signatures and policy evaluationZero real payments
FROM CURIOSITY TO EVIDENCE
A small test.
A clear explanation.
Built for developers, technical founders and integration teams exploring AI-initiated payments. Three steps, and nothing to install.
Choose what could go wrong
Run a normal purchase or an adverse case. Each run generates fresh synthetic authorizations.
Understand the decision
Compare the expected and actual outcome. Inspect the input, policy and reasons returned by the engine.
THE FREE TEST SET
Start with the cases
that deserve a check.
Normal purchases, policy exceptions and invalid authorizations. Every case states its expected result before you run it, so an unexpected outcome is visible rather than reassuring.
01
A normal purchase
A small purchase with a valid authorization.
02
A confirmed purchase
A purchase with human confirmation.
03
Over the spending limit
A transaction above the configured EUR limit.
04
A blocked merchant
A valid authorization for an excluded merchant.
05
Human review required
A higher-value purchase without human confirmation.
06
Amount changed after signing
A cart modified after the merchant signs it.
07
An untrusted signing key
A signature checked against a different trusted key.
08
An expired authorization
A correctly signed authorization used too late.
09
A different currency
USD presented to a policy configured in EUR.
10
The same authorization twice
The original submission followed by a replay.
Demo scope: synthetic AP2 legacy-format fixtures, generated with test keys. This is not AP2 v0.2 conformance testing, an independent security audit, or a test of your own integration. No payment is executed.
EVIDENCE YOU CAN INSPECT
Look beneath
the demo.
TrustedPAI sits beside your stack. Funds never pass through us, and your integration decides how to act on a recommendation. Every run returns the input, the policy that was applied and the reasons behind the outcome.
Explore the evidence model →CHECKED BY SOMEONE ELSE
Our separate PulseAP2X402Verifier project was accepted by the Pulse maintainer as one of the two qualifying implementations outside the original author for their release-evidence gate. That acceptance applies to the linked verifier and its evidence, not to a certification of this demo or of your integration.
01
Run the tests yourselfTen scenarios, thirty free runs, no card
↗02
Follow a screening decisionAuthorization, policy and evidence walkthrough
↗03
Try a record comparisonInteractive example using sample transactions
↗04
Check protocol coverageCurrent availability before planning an integration
↗05
Read the APIThe full OpenAPI document, always current
↗
WHEN THE SYNTHETIC SET IS NOT ENOUGH
Bring us your integration.
Leave with a clear next step.
The demo runs fixed scenarios against test keys. To have your own authorizations, records or checkout flow examined, tell us what you are building and we will agree the scope and the deliverable.