Sandbox Testing

Why sandbox matters

Sandbox lets your merchant team test the full SMS Pay flow without moving real money. Use it before live launch and whenever you change backend fulfillment, webhooks, receiver accounts, or device setup.

Sandbox data is separate from live data.

Recommended test flow

Create a sandbox API key.
Configure a sandbox receiver account.
Add and verify a sandbox webhook endpoint.
Create a sandbox payment intent from your backend.
Open the returned checkout URL.
Use Dashboard -> Sandbox -> SMS Simulator to submit matching SMS evidence.
Confirm the payment intent becomes PAID.
Confirm your backend receives payment.paid.
Run review, expiry, duplicate, wrong amount, wrong reference, and webhook failure cases.

Sandbox tools

Tool	Merchant admin use
Overview	Check readiness, recent activity, and recommended next steps.
SMS Simulator	Generate provider-style SMS evidence for a sandbox payment intent.
Scenario Lab	Run predefined success, mismatch, duplicate, expiry, malformed, and webhook scenarios.
Webhook Testing	Send selected test events to your endpoint and inspect delivery results.
Activity Logs	Trace SMS generation, submission, parsing, matching, and webhook activity.

SMS Simulator

The simulator sends SMS evidence into the same matching pipeline used by live Android device messages.

To test a successful match:

Create a sandbox payment intent.
Open checkout and note the amount, receiver, method, and reference.
In SMS Simulator, use the same amount, receiver, method, and reference.
Submit the SMS.
Confirm the payment intent becomes PAID.

The simulator does not create payment intents. It only creates SMS evidence.

Required scenarios

Scenario	Expected result
Exact amount and reference	Payment becomes `PAID`; webhook `payment.paid` is sent.
Correct reference, wrong amount	Payment becomes `REVIEW_REQUIRED`; do not fulfill.
Wrong reference	Payment stays pending unless TrxID recovery succeeds.
Customer TrxID fallback	Exact TrxID and amount can confirm payment.
Duplicate TrxID	Duplicate evidence does not confirm twice.
Expired payment	Payment becomes `EXPIRED`; do not fulfill.
Webhook failure	Delivery shows failed/retrying and can be retried after your endpoint is fixed.

What to inspect

After each test, inspect:

Payment Intents for status and transaction history
SMS Events for parsed amount, TrxID, reference, and match status
Reconciliation for review-required cases
Webhooks for delivery status and response
Activity Logs for the full trace

Completion checklist

Sandbox is complete when:

your backend can create payment intents
hosted checkout opens correctly
exact match becomes PAID
wrong amount does not fulfill
expired payment does not fulfill
duplicate SMS does not fulfill twice
webhook signature verification works
webhook idempotency works
merchant admins know where to investigate failures

Recommended test flow

Create a sandbox API key.

Configure a sandbox receiver account.

Add and verify a sandbox webhook endpoint.

Create a sandbox payment intent from your backend.

Open the returned checkout URL.

Use Dashboard -> Sandbox -> SMS Simulator to submit matching SMS evidence.

Confirm the payment intent becomes PAID.

Confirm your backend receives payment.paid.

Run review, expiry, duplicate, wrong amount, wrong reference, and webhook failure cases.

Sandbox tools

Tool	Merchant admin use
Overview	Check readiness, recent activity, and recommended next steps.
SMS Simulator	Generate provider-style SMS evidence for a sandbox payment intent.
Scenario Lab	Run predefined success, mismatch, duplicate, expiry, malformed, and webhook scenarios.
Webhook Testing	Send selected test events to your endpoint and inspect delivery results.
Activity Logs	Trace SMS generation, submission, parsing, matching, and webhook activity.

SMS Simulator

The simulator sends SMS evidence into the same matching pipeline used by live Android device messages.

To test a successful match:

Create a sandbox payment intent.

Open checkout and note the amount, receiver, method, and reference.

In SMS Simulator, use the same amount, receiver, method, and reference.

Submit the SMS.

Confirm the payment intent becomes PAID.

The simulator does not create payment intents. It only creates SMS evidence.

Required scenarios

Scenario	Expected result
Exact amount and reference	Payment becomes `PAID`; webhook `payment.paid` is sent.
Correct reference, wrong amount	Payment becomes `REVIEW_REQUIRED`; do not fulfill.
Wrong reference	Payment stays pending unless TrxID recovery succeeds.
Customer TrxID fallback	Exact TrxID and amount can confirm payment.
Duplicate TrxID	Duplicate evidence does not confirm twice.
Expired payment	Payment becomes `EXPIRED`; do not fulfill.
Webhook failure	Delivery shows failed/retrying and can be retried after your endpoint is fixed.

Completion checklist

Sandbox is complete when:

your backend can create payment intents

hosted checkout opens correctly

exact match becomes PAID

wrong amount does not fulfill

expired payment does not fulfill

duplicate SMS does not fulfill twice

webhook signature verification works

webhook idempotency works

merchant admins know where to investigate failures