TAP · IMPLEMENTATION GUIDE
Trusted Agent Protocol verification checklist
Combine Visa TAP message-signature verification with transaction policy, freshness and replay controls.
What the protocol establishes
Visa's Trusted Agent Protocol helps a merchant recognize an approved agent through signed, time-bound request evidence. Identity recognition is one input to a payment decision, not the complete authorization decision.
Official Visa TAP specification ↗Five checks before execution
- Verify the HTTP message signature against a trusted key.
- Check created, expiry, nonce, authority and path binding.
- Confirm the signature tag matches browsing or payment intent.
- Evaluate amount, currency, merchant and user-approved limits.
- Store and atomically reject replayed transaction identifiers.
The gap MandateShield closes
A recognized agent can still submit a transaction outside the specific amount, merchant or time window the user approved.
MandateShield normalizes execution facts and returns a deterministic decision with exact findings and a tamper-evident receipt. It complements protocol-native signature verification; it does not replace it.
Test the normalized payment boundary
No account and no payment credentials required. Change the amount, merchant or consent and inspect the machine-readable result.
Open free validator →