Sandbox SDK & API Transaction Flow TestingRequest
{}
1. Architecture Overview
Core actors and end-to-end flow from checkout initiation to final authorization outcome.
Consumer
Merchant Frontend
Merchant Backend
Click to Pay Layer
Authentication Layer
PSP / Gateway
Issuer
- Checkout initiated
- Consumer recognized or identity entered
- Click to Pay flow invoked
- Authentication challenge handled
- Tokenized payload retrieved
- Downstream authorization continues
- Final success or failure surfaced
2. Interactive Integration Flow Simulator
Awaiting step run
Response
{}
Integrator Guidance
Run a step to view explanation and guidance.
Likely Cause: -
Next Action: -
Execution Logs
{}
Key Configuration
Use keys from Mastercard Developer Zone > Unified Checkout Solutions. Sandbox only; do not paste production keys.
Base64 PKCS12 keys are used by the backend process for signed API calls and are not written to server disk by this app. For convenience, your entered values (including passwords) are saved in this browser's localStorage until you clear them.
Ready. Set keys to activate backend API calls.
Keys: not loaded.
Live Sandbox Flow for SDK Calls
Configuration
Consumer Details
Authentication Settings (TAS)
Passkey Setup Callout
- Enable Authentication (TAS).
- Set Payload = DSRP (Cryptogram).
- Use a passkey-eligible sandbox card (labels marked as passkey eligible in the new-card list).
- Confirm merchant settings are populated: MCC, Merchant Country, Acquirer Merchant ID, and Acquirer BIN.
- Passkey usage is confirmed by decrypted assurance with verificationMethod=07 and verificationResults=01.
Add New Card
Pick a sandbox card or key in a manual card number (manual overrides dropdown).
Live Status Recognition Token: Unknown
Idle.
Live Request
{}
Live Response
{}
Live Execution Logs (Immediate)
[]
Live Sandbox Backend API & Decryption
Process Stages
Backend Response
After running, backend response summary appears here.
Decrypted Assurance
- Method: -
- Result: -
- ECI: -
No decrypted assurance data yet.
Decrypted Payload Type
- Type: Not decrypted yet.
- Token number: -
- PAN: -
- Cryptogram / Dynamic code: -
No decrypted payload yet.
3. Integration Playbook
Quickstart Actions
Run core flow actions directly from here.
No quick action run yet.
Prerequisites & UAT
Before Testing
- Saved DPA selected and Organization ID configured
- Sandbox card brand + cryptogram type chosen
- Personal data + contact details available for OTP/auth
UAT Checks
- Returning-user and new-user paths both tested
- Checkout API and decrypt steps validated
- Failure scenarios reviewed with remediation notes
4. Failure Modes Lab
Click a scenario to simulate issue patterns and remediation.
Pick a failure scenario to run.