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 NumberEffect (non Batch)Effect (Batch)
000000000Failure (immediate)Failure(this single payment)
000000001Failure (later)Failure(this single payment)
000000002SuccessFailure (entire batch)

Direct Debit Authorizations

In the test mode for the Direct Debit Authorizations API (Singapore only), a successful authorization returns null for payerIdType and payerIdHash by default. Create the authorization with this bill reference number to receive mock payer identification fields instead. The value must match exactly, including case: s1234567d is a valid bill reference number but returns null for both fields.

Bill Reference NumberEffect
S1234567DA successful authorization returns the mock payer identification fields below

The mock values are hardcoded and 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.

FieldValue
payerIdTypeNRIC
payerIdHash3578b829767388a631b999b7049e830827b3e99b7504581bcfefa72def689658

Direct Debit Payments

In the test mode for the Direct Debit Payments API, these customer references will trigger a payment failure.

Customer ReferenceEffect
failFailure

Hosted Payments

In the test mode for the Hosted Payments API, these hosted payment method IDs will trigger specific scenarios.

Hosted Payment Method IDEffect
hpm_TESTMODESUCCEEDEDsuccessful payment
hpm_TESTMODEFAILED_PAYLAHWALLETDELINKEDfailure - customer has unlinked their PayLah! wallet
hpm_TESTMODEPENDING_INSUFFICIENTFUNDSPENDINGTOPUPfailure - there is insufficient balance in the customer's PayLah! wallet, and they have been prompted to top up.

On this page