If you're experiencing server errors or timeouts, check the Sandbox Health Page for real-time updates on service status. If an outage is indicated, rest assured that our team is already on it, working to restore services as soon as possible.
Maya uses HTTP Status codes when returning errors. Additionally, details about the errors are provided in the body of the response using a derivative format of vnd.error.
See list of response codes below.
Example:
[
{
"logref": "906c2d36-48a1-40ed-84c0-71a37a35a233",
"code": "1996",
"message": "[1996] Some error",
"receiptNo": "806403672030",
"links": [
{
"rel": "self",
"href": "https://cdn.paymaya.com/sandbox/payments_api/paymayap3/paymayap3.html"
}
]
},
{
"logref": "906c2d36-48a1-40ed-84c0-71a37a35a234",
"code": "2593",
"message": "[2593] Another error",
"receiptNo": "806403672030",
"links": [
{
"rel": "self",
"href": "https://cdn.paymaya.com/sandbox/payments_api/paymayap3/paymayap3.html"
}
]
}
]
HTTP Status Codes
| HTTP Status | Description |
|---|---|
200 |
Request OK |
400 |
Validation error OR transaction failed |
401 |
Unauthorized request |
404 |
Resource was not found |
50x |
PayMaya server error, or timeout occurred |
Response Codes
GENERAL AND REQUEST VALIDATION ERROR CODES
Error (code) |
Description (message) |
|---|---|
1996 |
General error |
1997 |
API key is incorrect |
Payments Processing Platform General Error Codes
Error (code) |
Description (message) |
|---|---|
2501 |
Merchant ID does not exist |
2522 |
Merchant is not configured properly - contact Maya |
2545 |
TRN does not exist |
2546 |
Excessive refund |
2547 |
Transaction already voided |
2548 |
Transaction already refunded |
2549 |
A final capture has already been done for this transaction |
2552 |
Invalid RRN |
2562 |
Card BIN is invalid and/or unknown |
2563 |
Client ID, Merchant ID, and BIN combination does not exist |
2564 |
Merchant Slug must be provided |
2565 |
Merchant RefNo must be provided |
2566 |
Merchant is not a PF, but Payment Facilitator Details were provided |
2567 |
Merchant is a PF, but Payment Facilitator Details were not provided |
2569 |
Transaction is no longer valid for void |
2570 |
Transaction is not yet valid for refund |
2571 |
Payment RRN, Merchant ID, and Amount does not exist |
2572 |
Account number will not be honored |
2575 |
Transaction is not allowed for contactless interface |
2576 |
Manual PAN Entry not allowed |
2577 |
POS Entry does not match specified Terminal Input Capability |
2578 |
MagStripe or Key Entry only terminal is not allowed |
2581 |
Invalid funding instrument |
2592 |
Transaction cannot be routed |
2593 |
Request contains one or more invalid fields |
2599 |
Backend encountered timeout while processing the transaction |
ACQ011 |
Transaction is not valid for capture |
ACQ012 |
Excessive capture |
ACQ013 |
Captured authorization transaction cannot be voided |
ACQ024 |
Concurrent operations on a transaction is not allowed |
ACQ025 |
Merchant configuration is invalid |
ACQ062 |
Transaction cannot be routed / processed |
ACQ065 |
Key ID Does Not Exist |
ACQ066 |
Key ID is not valid for this transaction |
ACQ067 |
PIN translation failed |
ACQ068 |
PIN block is invalid |
ACQ069 |
Key operation failed |
ACQ070 |
Key is already expired |
ACQ073 |
BIN Does Not Exist/Not Supported |
ACQ084 |
Transaction was blocked by the Acquirer |
ACQ089 |
General Network Communication Error |
ACQ090 |
Acquirer Network Communication Error (type 1) |
ACQ091 |
Scheme Network Communication Error (type 1) |
ACQ092 |
Scheme Network Communication Error (type 2) |
ACQ096 |
General Error |
ACQ105 |
Scheme is not supported by merchant |
ACQ700 |
Acquirer host synchronization error |
ACQ791 |
Acquirer Network Communication Error (type 2) |
Error Codes Generated by Acquiring Network and/or Issuer Network
Error (code) |
Description (message) |
|---|---|
2001 |
Declined - Refer to issuer |
2003 |
Invalid merchant |
2004 |
Issuer requests to capture card |
2005 |
Declined - Do not honor the transaction |
2006 |
Issuer generic error |
2012 |
Invalid transaction |
2013 |
Invalid amount |
2014 |
Invalid card number |
2015 |
Invalid issuer |
2030 |
Message format error |
2041 |
Lost card |
2042 |
Stolen card |
2051 |
Insufficient funds |
2054 |
Expired card |
2055 |
Invalid PIN |
2057 |
Transaction not permitted to issuer |
2058 |
Transaction not permitted to acquirer |
2059 |
Issuer suspected fraud |
2061 |
Withdrawal/Transaction amount limit exceeded |
2062 |
Restricted card |
2063 |
Security violation |
2070 |
Invalid transaction - contact issuer |
2071 |
PIN not changed |
2074 |
PIN encryption error |
2075 |
PIN try limit exceeded |
2076 |
Invalid “To” account specified |
2077 |
Invalid “From” account specified |
2078 |
Invalid account specified |
2080 |
System currently not available |
2088 |
PIN unacceptable. Retry PIN verification |
2089 |
Card Security Code/Card Verification Value is incorrect |
2090 |
Declined for 3DS verification failure |
2091 |
Issuer system inoperative |
2092 |
Scheme/Issuer routing error |
2093 |
Declined - 3DS ECI downgraded by issuer |
2094 |
Duplicate transmission detected |
2096 |
Issuer system error |
2098 |
Issuer encountered timeout |
2099 |
Issuer declined with a non-generic error |
201A |
Authentication is required |
20R0 |
Cardholder requested a stop payment order for the subscription/vaulted payment |
20R1 |
Cardholder requested a stop payment order for all subscription/vaulted payments for this merchant |
20R3 |
Cardholder requested a stop payment order for all subscription/vaulted payments |