Appearance
Overview
We are introducing a dedicated failure status for JomPAY transactions where the customer’s NRIC cannot be accepted during the identity or sanctions verification process.
Previously, these transactions were returned with the generic status “Invalid Account No”. This made them difficult to distinguish from transactions that failed because the JomPAY account reference was genuinely invalid.
What's Changing
For affected JomPAY transactions, the response will now contain:
Field | New Value |
|---|---|
data.statusCode | 62 |
data.status | Failed |
data.remarks | NRIC not eligible |
This applies to the transaction response and subsequent transaction callbacks.
Previous Response
{
"data": {
"statusCode": 40,
"status": "Failed",
"account": "1234567890",
"product": "JOMPAY",
"productName": "JomPAY",
"amount": 100,
"sn": "",
"pin": "",
"expiry": "",
"cost": 0,
"balance": 500,
"remarks": "Invalid Account No",
"refid": "your-reference-id",
"timestamp": "2026-07-23 12:00:00",
"note": "",
"voucherlink": ""
}
}Updated Response
{
"data": {
"statusCode": 62,
"status": "Failed",
"account": "1234567890",
"product": "JOMPAY",
"productName": "JomPAY",
"amount": 100,
"sn": "",
"pin": "",
"expiry": "",
"cost": 0,
"balance": 500,
"remarks": "NRIC not eligible",
"refid": "your-reference-id",
"timestamp": "2026-07-23 12:00:00",
"note": "",
"voucherlink": ""
}
}The values above are illustrative. Transaction-specific fields such as account, amount, balance, refid, and timestamp will vary.
Impact
Status code 62 represents a final failed transaction.
This failure should not be treated as an invalid JomPAY account reference.
Existing status codes for genuine invalid-account failures remain unchanged.
There are no changes to the API request or response structure.
Action Required
Please update your integration to recognise status code 62 and display or handle it as “NRIC not eligible.”
If your integration currently treats all unknown failure codes as “Invalid Account No,” update the mapping before the effective date.
