Test your integration

Validate notification handling and complete your programme test plan.

Use the Token Tester framework with the implementations team to exercise your integration before launch. It supports Visa and Mastercard scenarios, customer test plans, request/response inspection, result recording, and evidence export. Agree the appropriate test approach for other schemes as part of your project.

What to verify

ScenarioExpected issuer behavior
Approved provisioningRecord TAR and its outcome; use the lifecycle event to confirm activation
Declined provisioningRecord the reason; do not show the token as activated
Default fallbackConfirm unmatched requests follow the agreed fallback and its activation methods
Step-upCheck the returned methods match the rule and the supported cardholder journey
SMS/email OTPRoute the received OTP through the selected channel to the correct cardholder
Contact lookupReturn masked contact details when your system is the configured source
Token lifecycle changeUpdate the correct network token, preserving other tokens on the card
Enabled risk serviceVerify its result is available in the enriched payload and that configured rules handle it
Scheme-specific flowExercise Mastercard's parallel calls, Visa's separate step-up request, or your agreed Jaywan scenarios

Record results

Run the assigned scenarios and inspect the actual messages received by your endpoint. Some test cases have automated assertions; others require manual review. Record the result and retain evidence of the observed outcome. A successful HTTP exchange alone does not prove the expected token decision or cardholder action occurred.

Complete launch validation

Review results with the implementations team and complete applicable scheme and wallet certification requirements. The Token Tester supports this work; a test export does not itself replace certification. Repeat the affected scenarios after changing rules, activation methods, or notification handling.


Did this page help you?