Special Test Mode Values
In test mode, you may specify some special values to trigger some common scenarios.
Payments
In the test mode for the Payments (and Batch Payments) API, these account numbers for the receiver will trigger a payment failure.
| Account Number | Effect (non Batch) | Effect (Batch) |
|---|---|---|
000000000 | Failure (immediate) | Failure(this single payment) |
000000001 | Failure (later) | Failure(this single payment) |
000000002 | Success | Failure (entire batch) |
Direct Debit Authorizations
In the test mode for the Direct Debit Authorizations API (Singapore only), a successful authorization always returns these hardcoded payer identification fields. They are not derived from a real payer ID.
To verify the hash, uppercase S1234567D, SHA-256 it, and hex-encode the digest (64 characters). The result should match payerIdHash.
| Field | Value |
|---|---|
payerIdType | NRIC |
payerIdHash | 3578b829767388a631b999b7049e830827b3e99b7504581bcfefa72def689658 |
Direct Debit Payments
In the test mode for the Direct Debit Payments API, these customer references will trigger a payment failure.
| Customer Reference | Effect |
|---|---|
fail | Failure |
Hosted Payments
In the test mode for the Hosted Payments API, these hosted payment method IDs will trigger specific scenarios.
| Hosted Payment Method ID | Effect |
|---|---|
hpm_TESTMODESUCCEEDED | successful payment |
hpm_TESTMODEFAILED_PAYLAHWALLETDELINKED | failure - customer has unlinked their PayLah! wallet |
hpm_TESTMODEPENDING_INSUFFICIENTFUNDSPENDINGTOPUP | failure - there is insufficient balance in the customer's PayLah! wallet, and they have been prompted to top up. |