The Gcashier Pay sandbox environment uses deterministic mock rules to simulate real-world review and processing outcomes. Instead of waiting for a human review, you supply specific field values — such as the last digit of a bank account number or the unit digit of an amount — to trigger a known result automatically. Callbacks are typically delivered within 5 minutes in the sandbox. If a callback does not arrive, use the appropriate sp2x query API to check current status.
sp1101 — Merchant Access Application
The sandbox evaluates the last digit of your merNameEn (English merchant name) to determine the onboarding outcome.
Last digit of merNameEn | Simulated outcome |
|---|
0, 1, 2, 3 | Access approved — you receive an S00000 callback |
4, 5, 6 | Access rejected |
7, 8, 9 | Under review — no callback is sent |
Once merchant access is approved, your sandbox account is eligible to test the full suite of downstream features: VA opening, USD collection, international remittance (USD via LOCAL and SWIFT channels), RMB payments, USD withdrawals, and CNY/USD foreign exchange.
sp1202 — FX Trading
The sandbox evaluates the unit digit (ones place) of the trade amount to determine the exchange outcome.
| Unit digit of trade amount | Simulated outcome |
|---|
0, 1, 2, 3 | Exchange successful |
4, 5, 6 | Exchange failed |
7, 8, 9 | Exchange processing — no immediate callback |
1500.00 has a unit digit of 0, which triggers a successful exchange.
sp1303 — International Remittance Confirmation
The sandbox evaluates the unit digit of debitAmount or arriveAmount. If you supply both fields, arriveAmount takes precedence.
| Unit digit of amount | Simulated outcome |
|---|
0, 1, 2, 3 | Remittance approved |
4, 5, 6 | Remittance rejected |
7, 8, 9 | No action — no callback is sent |
arriveAmount, that value’s unit digit controls the result regardless of what debitAmount contains.
sp1305 — Withdrawal
The sandbox evaluates the last digit of bankAccountNo (the payee’s bank account number) to determine the withdrawal outcome.
Last digit of bankAccountNo | Simulated outcome |
|---|
0, 1, 2, 3 | Withdrawal successful |
4, 5, 6 | Withdrawal rejected |
7, 8, 9 | No action — no callback is sent |
sp1105 — Flow-Order Association
The sandbox evaluates the unit digit of the amount field from the corresponding sp1104 trade order to determine whether the association is approved.
Unit digit of sp1104 amount | Simulated outcome |
|---|
0, 1, 2, 3 | Association approved |
4, 5, 6 | Association rejected |
7, 8, 9 | No action — no callback is sent |
sp1301 — RMB Payment
RMB payment testing requires a pre-configured test payee account. Contact Gcashier Pay support to have a sandbox payee set up for your test merchant before running sp1301 scenarios.
Unlike other endpoints, sp1301 mock outcomes depend on the payee configuration rather than a simple numeric rule. Gcashier Pay support will provide you with the payee details and the digit-based trigger values that apply to your sandbox account.
General Sandbox Tips
- Callbacks arrive within ~5 minutes. If you do not receive a callback after 5 minutes, call the relevant sp2x query API to inspect the current status instead of re-submitting the request.
- Unit digit vs. last digit. For amount-based rules, the relevant digit is the ones place of the whole-number portion (e.g.,
250.75 → digit 0). For account-number-based rules, it is the final character of the account string.
- No-action scenarios are deliberate. Use the
7–9 range to test your timeout and polling logic — these cases simulate transactions that are accepted but never return a callback, which can occur in production due to network issues or extended review times.
