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
Failed Payment Reason (Code)	Insufficient_funds	limit_exceeded
Subscription Invoice Status**	Inactive	Inactive
Invoice Status	Past_Due	Past_Due
Transaction Status	Failed	Failed
Payment Provider Response (Description)	Insufficient funds in the account	Card has reached the credit limit
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 Invalid?	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.	The customer or customer’s bank has imposed spend limits.
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, 221, 232	203, 233
Failed Payment Reason (Code)	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: Request approved by issuing bank but declined by CS because it did not pass AVS (address verification system) check 201: Issuing bank has questions - call the processor for verbal authorisation 208: Inactive card or card not authorised for card-not-present transactions 221: Customer matched an entry on the processor's negative file 232: Card type is not accepted by the payment processor	203: General decline of the card 233: General decline by the processor
Failed Payment Reason (Description)	Transaction rejected by customer's bank. Please use a different payment method or ask the customer to contact the bank.	This transaction was declined by the bank.
Payment Method Invalid?	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.	General decline by the bank, that could be for different reasons: Spend limit reached Possible fraud No authority held Account suspended
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
Failed Payment Reason (Code)	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	Expired card
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 Invalid?	Invalidated	Invalidated
What It Means	The BSB or account number is incorrect, and the bank is unable to match the details to any particular account.	Expired card.
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, BSB Number, Account 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
Failed Payment Reason (Code)	lost_or_stolen_card
Subscription Invoice Status**	Inactive
Invoice Status	Past_Due
Transaction Status	Failed
Payment Provider Response (Description)	Stolen or lost card
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.
Payment Method 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.
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)	150, 151, 152, 207, 211, 230, 236, 250	101, 102, 104, 234, 235, 237, 238, 239, 241, 242, 243, 246, 247, 254, 256
Failed Payment Reason (Code)	bank_system_error	ezypay_error
Subscription Invoice Status**	Inactive	Inactive
Invoice Status	Past_Due	Past_Due
Transaction Status	Error	Error
Payment Provider Response (Description)	150: General system failure 151: Request received but there was a server timeout 152: Request received but a service did not finish running in time 207: Issuing bank unavailable - wait a few minutes and resend the request 211: Invalid CVN 230: Request approved by issuing bank but declined by CS because it did not pass CVN check 236: Processor failure - wait a few minutes and re-send 250: Request was received but there was a timeout at the payment processor	101: Request is missing one or more required fields 102: One or more fields in the request contains invalid data 104: Merchant Ref code for this request matches one of another request sent within the last 15 minutes (re-send with unique ref code) 234: There is a problem with the information in your CS account 235: Capture amount exceeds the originally authorised amount 237: Authorisation has already been reversed 238: Authorisation has already been captured 239: Request transaction amount must match previous transaction amount 241: Request ID is invalid 242: You requested a capture, but there is no corresponding, unused authorisation record. Occurs if there was not a previously successful authorisation request or if the previously successful authorisation has already been used by another capture request 243: Transaction has already been settled or reversed 246: Capture or credit is not voidable because capture or credit information has already been submitted to your processor OR you requested a void for a type of transaction that cannot be voiced 247: You requested a credit for a capture that was previously voided 254: Stand-alone credits are not allowed 256: Credit amount exceeds maximum allowed for your CS account
Failed Payment Reason (Description)	An error occurred while processing the transaction. Please contact Ezypay support.	An error occurred while processing the transaction. Please contact Ezypay support.
Payment Method Invalid?	Valid	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.	Due to a timeout issue at Ezypay’s end, the payment has been rejected.
Suggested Actions (For Integrators)	You can retry the debit without having to recreate the payment method token.	You can retry the debit without having to recreate the payment method token.
Suggested Actions (For Merchants)	N/A	N/A
Suggested Actions (For Customers)	N/A	N/A

** Only available to integrators on subscription model.

Contact

Level 10, 21 Queen St, Auckland 1010

hello@ezypay.com | 0800 399 011

www.ezypay.com