Sandbox Testing
Test card and APM flows in the sandbox environment
Use the Exirom sandbox environment to test your integration before going live. The sandbox supports both card and APM payment flows with configurable test behaviors.
#Sandbox Environment
- Base URL:
https://sandbox.${host}.com/api/ - Use sandbox credentials provided by Exirom during onboarding.
- All transactions in sandbox are simulated — no real money is moved.
Credentials required
#Card Testing
Use these card numbers to simulate different 3DS authentication outcomes.
| Card Number | Behavior |
|---|---|
4263982640269299 | Challenge flow — a challenge page is returned with ACCEPT / DECLINE buttons |
4580271111111234 | Frictionless success — redirects to success URL automatically after a short delay |
4111111111111111 | Successful payment (no 3DS) |
| Any other number | Failed flow — redirects to failure URL after a short delay |
#APM Testing
For APM transactions, use the customFields.flow field inside apmPayload to control test behavior.
#Supported Test Values
| Value | Behavior |
|---|---|
challenge | Simulates a user confirmation flow. The user is redirected to a test page where the transaction can be approved or declined. |
frictionless | Simulates a successful frictionless flow. The transaction is completed automatically without user interaction. |
#Example Request Payload
{
"apmPayload": {
"paymentMethod": "SMART_QR",
"paymentType": "E_WALLET",
"customFields": {
"flow": "challenge"
}
}
}To simulate a frictionless flow, set:
"flow": "frictionless"These values are supported only in sandbox environments. In production, providers may ignore this field or apply their own logic.
#Try It — Live Sandbox
Send a real request to the sandbox right here. Select a payment method from the dropdown, add your sandbox credentials, and click Send Request.
Authentication: Get a sandbox token first via Authenticate, then paste it in the Auth Token field below.
#Testing Webhooks
- Sandbox callbacks are sent to your
callbackUrljust like in production. - Use tools like webhook.site or ngrok to inspect callbacks during development.
- Verify your callback handler returns HTTP 200 quickly — Exirom may retry on timeout or non-200 responses.