Maxpay receives various decline codes from the bank participants of the transaction and maps them under the general decline codes for your convenience. Since the reasons for the decline may be various, from fraud reasons to connection errors, they should be handled differently. Such an approach will allow you to improve your approve ratio and save you from unnecessary financial losses.
In the table below you may find the list of Maxpay decline reasons, codes, and the recommendation from us how the specific code should be handled.
|
Error code |
Error code explanation mapped |
Recommendation for retry logic |
|
1 |
Internal system error |
Yes, you can try to rebill again |
|
1 |
Internal service constrain mismatch |
Yes, you can try to rebill again |
|
2 |
Internal database error |
Yes, you can try to rebill again |
|
2005 |
MID is not active |
Clarify that MID is still active |
|
4 |
Access denied |
Yes, you can try to rebill again. If the error persists, please contact support. |
|
10 |
Internal communication error |
Yes, you can try to rebill again |
|
11 |
Internal timeout |
Yes, you can try to rebill again |
|
3000 |
Proxy frontend error occured |
Yes, you can try to rebill again |
|
3000 |
Transaction core general error |
Yes, you can try to rebill again |
|
3000 |
General processing error |
Yes, you can try to rebill again |
|
3001 |
Client unique transaction id [your ID] already presents |
Yes, you can try to rebill again. Just change transaction unique id |
|
3002 |
Invalid bill token |
You need to check the billtoken value and try to rebill with a correct one. If the value is correct and the error persists, please contact support. |
|
3122 |
Invalid reference |
Commonly occurs on SETTLE, VOID, SALE by token transactions. You need to check the original transaction (SALE3D, SALE by CC, AUTH) and make sure it had a SUCCESS status. |
|
3003 |
Transaction [reference] has wrong status |
Commonly occurs on SETTLE transactions. Check the status of AUTH transaction and make sure it had a SUCCESS status. |
|
3004 |
Void not possible |
Check if the transaction has been already voided or refunded. |
|
3005 |
Refund not possible |
If it's not related to chargeback or other tech settings - yes, you can try to rebill |
|
3006 |
Transaction is Cb / Transaction already CB |
Forbidden |
|
3009 |
Already refunded |
Check the refund reason |
|
3010 |
Transaction was already settled |
You can try to do a refund |
|
3015 |
Invalid currency |
Check the currency value and clarify with account manager if it was opened for you by the acquirer. You can try to rebill again with correct currency. If the error persists, please contact support. |
|
3017 |
Bank MID access credentials are incorrect |
Please contact support for clarification. |
|
3018 |
Bank refused the connection |
Yes, you can try to rebill again |
|
3019 |
Invalid fields lastName |
Check validation of this parameter - Yes, you can try to rebill again |
|
3019 |
Validation failed with N error(s) |
Check validation of this parameter. Make sure the callback and redirect URL are valid and are https. - Yes, you can try to rebill again |
|
3022 |
The amount is incorrect |
Check if the amount of refund or settle does not exceed the amount of the initial transaction |
|
3023 |
Transaction is aborted by the customer |
Yes, you can try to rebill again |
|
3134 |
Transaction is expired |
Yes, you can try to rebill again |
|
3100 |
Declined |
No specific reason was provided. Yes, you can try to rebill again |
|
3101 |
Insufficient funds |
Yes, you can try to rebill again |
|
3102 |
Lost or stolen card |
Forbidden |
|
3103 |
3D secure failed |
Send a customer back on 3D Secure form |
|
3104 |
Invalid CVV |
Send a customer back on 3D Secure form |
|
3105 |
Card expired or expiration date invalid |
Send a customer back on 3D Secure form |
|
3106 |
Invalid amount |
Check the value of the amount - Yes, you can try to rebill again. If the error persists, please ask the client to contact his bank for clarification |
|
3107 |
Invalid card number |
Send a customer back on 3D Secure form. If occurs on SALE by token, not recommended to rebill, please ask the client to contact his bank for clarification |
|
3203 |
Refund limit exceeded |
Yes, you can try to issue a refund later or ask Support team to issue the refund for you |
|
3109 |
Timeout between PSP and bank |
Yes, you can try to rebill again |
|
3110 |
Incorrect field |
Check the validation with the Support team and - Yes, you can try to rebill later |
|
3110 |
Required field are missing |
Check the validation with the Support team and - Yes, you can try to rebill later |
|
3111 |
Unauthorized transaction |
Check this issue with the Support team |
|
3111 |
Invalid credentials |
Check this issue with the Support team |
|
3111 |
IP not whitelisted |
Check this issue with the Support team |
|
3112 |
Card type not supported |
Only if the card type is going to be changed |
|
3113 |
Transaction type not supported |
Check that transaction type is supported for the current acquirer - Yes, you can try to rebill |
|
3114 |
Currency [currency] supported |
Make sure that you send a correct currency. If the error persists, please contact support. |
|
3115 |
Refund not possible by bank |
Check this issue with the Support team |
|
3116 |
Country is not supported by MID |
Check with the account manager if the processing country is allowed on this acquirer |
|
3117 |
Malformed bank response |
Check this issue with the Support team |
|
3118 |
Communication error with bank. |
Yes, you can try to rebill again |
|
3119 |
Referal or restricted card |
Forbidden. The issuer will never approve this card |
|
3120 |
Risk Bank Decline |
Not recommended. Check this issue with the Support team |
|
3121 |
Invalid token |
Check this issue with the Support team |
|
3123 |
Card 3D secure is not enabled. |
For EU countries - not recommended. For non-EU, yes, you can try to charge via SALE by CC |
|
3124 |
Unknown acquirer processing status. |
Yes, you can try to rebill again |
|
3125 |
Acquirer internal error. |
Yes, you can try to rebill again. If the error persists, please contact support. |
|
3126 |
Withdrawal frequency limit exceeded |
Yes, you can try to rebill again |
|
3127 |
Bank negative list |
Forbidden |
|
3128 |
Fraud bank decline |
Not recommended. Please ask the client to contact his bank for clarification |
|
3129 |
Authorization declined |
Yes, you can try to rebill again |
|
3130 |
Revocation of authorization order |
Forbidden. The cardholder requested that payment of all recurring or initial payment transactions for a specific merchant account be stopped |
|
3132 |
Recurring is stopped by the customer |
Forbidden. The cardholder requested that payment transaction for a specific merchant account be stopped |
|
3133 |
Unexpected acquirer behavior |
Yes, you can try to rebill again |
|
3135 |
Verification required by issuer |
You can rebill again by sending a SALE3D transaction |
|
3140 |
General bank decline |
Yes, you can try to rebill again |
|
3150 |
Invalid transaction |
Forbidden. The issuer will never approve this card |
|
3157 |
Transaction not permitted |
Forbidden. The issuer will never approve this card |
|
3170 |
Invalid or closed account |
Forbidden. The issuer will never approve this card |
|
3200 |
Declined by anti-fraud system. |
Check this issue with the Support team |
|
3202 |
Volume limit exceeded |
Payout limit exceeded and should be checked on a manual basis |
|
3220 |
Declined by trust list. |
Not recommended |
|
3330 |
Unregistered card |
Make sure you send a payout to the card that was previously used to make a deposit |
|
7101 |
Internal payment gate sender error |
Yes, you can try to rebill later |
|
7103 |
External communication timeout |
Yes, you can try to rebill later |