Failed Payment Response Guide
New Zealand
MasterCard and Visa Card Payments
Successful Payments
Payment Response (Code) | 100 |
Payment Reason (Code) | Approved |
Subscription Invoice Status** | Active |
Invoice Status | Paid |
Transaction Status | Success |
Payment Provider Response (Description) | Successful transaction |
Payment Reason (Description) | The transaction was successful. |
Payment Method Invalid? | Valid |
What It Means | The transaction was successful. Payments will continue as scheduled. |
Suggested Actions (For Integrators) | N/A |
Suggested Actions (For Merchants) | N/A |
Suggested Actions (For Customers) | N/A |
** Only available to integrators on subscription model.
Failed Payments - Fund Issues
Payment Response Code | 204 | 210, 251, 256, 259, 260 | |
Payment Response | Insufficient_funds | limit_exceeded | |
Subscription Invoice Status** | Inactive | Inactive | |
Invoice Status | Past_Due | Past_Due | |
Transaction Status | Failed | Failed | |
Payment Provider Response (Description) | Account does not contain sufficient funds. | 210: Account reached the credit limit, or the transaction amount exceeds the approved limit. 251: Customer has exceeded the debit card's limit on frequency of use, number of PIN entry tries, or maximum amount for the day. 256: Credit amount exceeds the maximum allowed for your account. 259: Reload limit for the gift card or prepaid card was exceeded. 260: Requested amount conflicts with the minimum or maximum amount allowed on the gift card or prepaid card. | |
Failed Payment Reason (Description) | Payment method has insufficient funds at the time of the transaction. | Transaction exceeded the customer's payment method daily withdrawal or activity limit. | |
Payment Method Status | Valid | Valid | |
What It Means | At the time of the transaction, the customer did not have enough funds to cover the transaction.
Sometimes, the bank will send us this reason code when they’ve identified fraudulent activity or transactions which are outside of the customer’s regular spend pattern.
The risk rules of the customer bank are outside of our control. The vast majority of transactions that generate this response code are due to genuine insufficient funds.
Payments will stop if maximum failed attempts have been reached. | The customer or customer’s bank has imposed spend limits.
Payments will stop if maximum failed attempts have been reached. | |
Suggested Actions (For Integrators) | You can retry the transaction on a later date without having to recreate the payment method, but we would suggest not retrying on the same day. | You can retry the transaction on a later date without having to recreate the payment method, but we would suggest not retrying on the same day. | |
Suggested Actions (For Merchants) | You can retry the transaction on a later date, but we would suggest not retrying on the same day as it’s unlikely that the customer would have enough funds available within the same day. | You can retry the transaction on a later date, but we would suggest not retrying on the same day. | |
Suggested Actions (For Customers) | Please ensure there are enough funds in your account before the due date of the next transaction. | Please increase the daily transaction limit on your account, or let the business know when another attempt can be made. |
** Only available to integrators on subscription model.
Failed Payments - Bank Issues
Payment Response Code | 110, 200, 201, 208, 212, 221, 232, 234, 235, 239, 244, 254, 428, 478 | 203, 233, 237, 238, 242, 243, 246, 247 | |
Payment Response | customer_to_contact_bank | declined | |
Subscription Invoice Status** | Inactive | Inactive | |
Invoice Status | Past_Due | Past_Due | |
Transaction Status | Failed | Failed | |
Payment Provider Response (Description) | 110: Only a partial amount was approved 200: Authorization request was approved by the issuing bank but declined because the address verification system (AVS) could not verify it. 201: Issuing bank has questions about the request. Call your processor to possibly receive a verbal authorization. 208: Inactive card or card not authorised for card-not-present transactions 212: EMV transaction was rejected. 221: Customer matched an entry on the processor's negative file 232: Card type is not accepted by the payment processor 234: Information in your account is incorrect 235: The requested capture amount exceeds the authorized amount 239: Requested transaction amount does not match the previous transaction amount 244: Account number did not pass a verification check 254: Stand-alone credits are not allowed 428: Your request for a strong customer authentication (SCA) exemption was declined. SCA is required for this transaction 478: Strong customer authentication (SCA) is required for this transaction.
| 203: Card was declined. No other information was provided by the issuing bank. 233: Processor declined the card. 237: Transaction was already captured. 238: Transaction was already reversed. 242: You requested a capture, but there is no corresponding, unused authorization. This situation occurs when there is no previously successful authorization request or when the previously successful authorization has already been captured. 243: Transaction is already settled or reversed. 246: Capture or credit cannot be voided because the capture or credit information has already been submitted to your processor. Or you requested a void for a type of transaction that cannot be voided. 247: You requested a credit for a capture that was previously voided.
| |
Failed Payment Reason (Description) | Transaction rejected by customer's bank. Please use a different payment method or contact your issuing bank. | This transaction was declined by the bank. | |
Payment Method Status | Valid | Valid | |
What It Means | Due to some rules that the customer’s bank applies, the transaction is rejected.
The bank could have set up rules around duplicate detection, fraud or velocity that might have triggered the rejected transaction.
Some of these rules apply when the customer has reached their spend limit for the day.
Payment stops immediately until issue is resolved.
| General decline by the bank, that could be for different reasons:
Payments will stop if maximum failed attempts have been reached.
| |
Suggested Actions (For Integrators) | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. | |
Suggested Actions (For Merchants) | Ask the customer to contact their bank to ask why the transaction failed.
Until the matter is resolved between the customer and their bank, the transaction response will likely be the same, therefore we recommend that you request a different payment method. | Ask the customer to contact their bank to ask why the transaction failed. Until the matter is resolved between the customer and their bank, the transaction response will likely be the same, therefore we recommend that you request a different payment method. | |
Suggested Actions (For Customers) | The bank has rejected the transaction. Please contact your bank for the reason as to why the transaction had failed.
This will need to be resolved first before transactions can continue to be debited from this account. Or you can provide the business with an alternate payment method. | The bank has declined the transaction. Please contact your bank for the reason as to why the transaction had failed.
This will need to be resolved first before transactions can continue to be debited from this account. Or you can provide the business with an alternate payment method. |
** Only available to integrators on subscription model.
Failed Payments - Card Issues
Payment Response Code | 209, 231, 240 | 202 | |
Payment Response | Invalid_payment_method | expired_card | |
Subscription Invoice Status** | Inactive | Inactive | |
Invoice Status | Past_Due | Past_Due | |
Transaction Status | Failed | Failed | |
Payment Provider Response (Description) | 209: CVN did not match 231: Invalid account number 240: Card type sent is invalid or does not correlate with the payment card number | Card is expired. You might also receive this value if the expiration date that you provided does not match the date that the issuing bank has on file. | |
Failed Payment Reason (Description) | Payment method details are invalid. Please use a different payment method. | The credit card has expired. Please use a different payment method. | |
Payment Method Status | Invalidated | Invalidated | |
What It Means | The card number is incorrect and the bank is unable to match the details to any particular account.
Payment stops immediately until issue is resolved. | Expired card.
Payment stops immediately until issue is resolved.
| |
Suggested Actions (For Integrators) | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. | |
Suggested Actions (For Merchants) | Do not attempt to retry the payment.
You should ask the customer for an alternative payment method.
Retrying a payment with the same payment details will yield the same failed payment response. | Do not attempt to retry the payment.
You should ask the customer for an alternative payment method. | |
Suggested Actions (For Customers) | Please check that all details of the account provided to the business are correct (E.g. Account Name, Card Number). Or you can provide the business with an alternate payment method. | Please check that the details of the credit card (expiry date and credit card number) provided to the business are correct. Or you can provide the business with an alternate payment method. |
Payment Response Code | 205 | 211 | |
Payment Response | lost_or_stolen_card | bank_account_closed | |
Subscription Invoice Status** | Inactive | Inactive | |
Invoice Status | Past_Due | Past_Due | |
Transaction Status | Failed | Failed | |
Payment Provider Response (Description) | Card is lost or stolen. | CVN is invalid. | |
Failed Payment Reason (Description) | Transaction rejected by customer's bank due to the card being reported lost or stolen. Please use a different payment method or contact your issuing bank. | The bank account has been closed. Please use a different payment method. | |
Payment Method Status | Invalidated | Invalidated | |
What It Means | The bank has advised that payment method provided has been reported as lost or stolen.
Payment stops immediately until issue is resolved. | Applies for Visa. The account is closed. Re-validate the account number for accuracy and do not reattempt with the same PAN or token
Payment stops immediately until issue is resolved. | |
Suggested Actions (For Integrators) | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. | |
Suggested Actions (For Merchants) | Do not attempt to retry the payment. You should ask the customer for an alternative payment method. | Do not attempt to retry the payment. You should ask the customer for an alternative payment method. | |
Suggested Actions (For Customers) | Please check with your banking institution on your account. Or you can provide the business with an alternate payment method. | Please check that the details of the credit card (expiry date and credit card number) provided to the business are correct. Or you can provide the business with an alternate payment method. |
** Only available to integrators on subscription model.
Failed Payments - Suspected Fraud
Payment Response Code | 213 | |
Payment Response | suspected_fraud | |
Subscription Invoice Status** | Inactive | |
Invoice Status | Past_Due | |
Transaction Status | Failed | |
Payment Provider Response (Description) | Account is in fraud watch status. | |
Failed Payment Reason (Description) | Transaction rejected by customer's bank due to suspected fraud on the account. Please use a different payment method or contact your issuing bank | |
Payment Method Status | Invalidated | |
What It Means | The transaction is suspected to be fraudulent by the bank.
Payment stops immediately until issue is resolved. | |
Suggested Actions (For Integrators) | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. | |
Suggested Actions (For Merchants) | Do not attempt to retry the payment. You should ask the customer for an alternative payment method. | |
Suggested Actions (For Customers) | Please check with your banking institution on your account. Or you can provide the business with an alternate payment method. |
** Only available to integrators on subscription model.
Error Responses
Payment Response (Code) | 101, 102, 104, 105, 150, 151, 152, 153, 207, 230, 236, 241, 250, 257, 262, 263, 490, 491, 520 | |
Failed Payment Reason (Code) | bank_system_error | |
Subscription Invoice Status** | Inactive | |
Invoice Status | Past_Due | |
Transaction Status | Error | |
Payment Provider Response (Description) | 101: Request is missing one or more required fields. 102: One or more fields in the request contains invalid data. 104: Merchant reference code for this authorization request matches the merchant reference code for another authorization request that you sent within the past 15 minutes. Resend this request with a unique merchant reference code. 105: Merchant transaction identifier (MTI) sent with this request has already been used in the past 60 days. 150: System error. 151: Request was received but a server timeout occurred. 152: Request was received, but a service did not finish running in time. 153: Your account is not enabled for the OCT service. 207: Issuing bank is unavailable. Wait a few minutes and resend the request. 230: Authorization request was approved by the issuing bank but declined because CVN could not be verified. 236: Processor failed. Wait a few minutes and resend the request. 241: Request ID is invalid. 250: Request was received, but a timeout occurred at the payment processor. 257: Gift card account or prepaid card account is already active. 262: Request is still in progress. Wait for a response from Cybersource. 263: Mass transit transaction (MTT) was declined. 490: Your aggregator or acquirer is not accepting transactions from you at this time. 491: Your aggregator or acquirer did not accept this transaction. 520: Authorization request was approved by the issuing bank but declined based on your Smart Authorization settings.
| |
Failed Payment Reason (Description) | An error occurred while processing the transaction. Please contact Ezypay support. | |
Payment Method Invalid? | Valid | |
What It Means | An error has occurred while communicating with the payment provider. This could be due to a timeout issue that has caused the payment to be rejected. | |
Suggested Actions (For Integrators) | N/A | |
Suggested Actions (For Merchants) | N/A | |
Suggested Actions (For Customers) | N/A |
** Only available to integrators on subscription model.