Failed Payment Response Guide
Australia
PayTo
Successful Payments
Payment Response Code | 0000 | ||
Payment Response | Success | ||
Subscription Invoice Status** | Active | ||
Invoice Status | Paid | ||
Transaction Status | Success | ||
Payment Provider Response |
| ||
Payment Response Description | The transaction was successful. | ||
Payment Method Status | 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 | AM04
| AM13
| ||
Payment Response | Insufficient_funds | limit_exceeded | ||
Subscription Invoice Status** | Inactive | Inactive | ||
Invoice Status | Past_Due | Past_Due | ||
Transaction Status | Failed | Failed | ||
Payment Provider Response | Amount of funds available to cover specified message amount is insufficient
| Transaction amount exceeds limits set by clearing system | ||
Payment Response 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. 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 - Mandate Issues
Payment Response Code | NOAS, MD20 | ||
Payment Response | mandate_expire | ||
Subscription Invoice Status** | Inactive | ||
Invoice Status | Past_Due | ||
Transaction Status | Failed | ||
Payment Provider Response | NOAS: The Payer Customer did not respond to the Authorisation request MD20: Mandate cancellation following validity expiration. | ||
Payment Response Description | The mandate has expired. Please use a different payment method. | ||
Payment Method Status | Invalidated | ||
What It Means | Expired mandate.
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 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 - Customer Issues
Payment Response Code | AC02, BE06, CTEX, M905, M906, M907, M908, M914, M915, M916, M917, M918, M920, M921 | AC06, AC13, AC14, AG01, AG03, AM03, AM06, AM12, AM14, CTAM, CTCA, MCFC, MCOC, MD07, MD08, MD09, MD21, MS02, MS03, MSUC, RR04, SL01, SL11, SL12 | ||
Payment Response | Invalid_payment_method | customer_to_contact_bank | ||
Subscription Invoice Status** | Inactive | Inactive | ||
Invoice Status | Past_Due | Past_Due | ||
Transaction Status | Failed | Failed | ||
Payment Provider Response | AC02: The nominated Payer Customer Account does not exist within the Payer Participant BE06: The nominated Payer Customer does not exist within the Payer Participant (or applicable identified Institution) customer list CTEX: Mandate suspended due to the contract that expired. M905: Debtor PayId is Invalid M906: Creditor PayId is Invalid M907: Debtor BSB in not NPP reachable M908: Creditor BSB in not NPP reachable M914: Payee Participant in Mandate and Creditor Alias Servicer are not matching M915: Payer Participant in Mandate and Debtor Alias Servicer are not matching M916: Creditor Account Details present in the Mandate and Input Request are not matching M917: Creditor Alias details present in Request and Mandate are not matching M918: Creditor details not present in Request and Mandate M920: Invalid Mandate M921: Creditor account scheme present in request and Mandate are not matching | AC06: The nominated Payer Customer Account is blocked and is unable to make payments AC13: The nominated Payer Customer Account does not allow NPP Payments AC14: Account exists but cannot accept funds (unreachable via NPP) AG01: The nominated Payer Customer Account is unable to make payments AG03: The nominated Payer Customer Account can make NPP Payments, but is not able to make NPP Payments to the Payee Customer Account type nominated in the Mandate Authorisation Request AM03: The nominated Payer Customer Account is unable to make payments in AUD AM06: Specified transaction amount is less than agreed minimum. AM12: Amount is invalid or missing AM14: Transaction amount exceeds limits agreed between bank and client CTAM: Mandate suspended due to amendment of the contract. CTCA: Mandate suspended due to cancellation of the contract, requested by the debtor. MCFC: Mandate suspended as final collection took place. MCOC: Mandate suspended as the once off collection took place. MD07: End customer is deceased. MD08: Receiving agent does not offer specified Mandate services MD09: Account is not open to specified Mandates services MD21: Mandate cancellation due to suspected fraud MS02: Reason has not been specified by end customer MS03: Reason has not been specified by agent MSUC: Mandate suspended after 7 consecutive unsuccessful collections. RR04: Regulatory Reason SL01: Due to specific service offered by the Debtor Agent SL11: Whitelisting service offered by the Debtor Agent; Debtor has not included the Creditor on its “Whitelist” (yet). In the Whitelist the Debtor may list all allowed Creditors to debit Debtor bank account. SL12: Blacklisting service offered by the Debtor Agent; Debtor included the Creditor on his “Blacklist”. In the Blacklist the Debtor may list all Creditors not allowed to debit Debtor bank account. | ||
Payment Response Description | Payment method details are invalid. Please use a different payment method. | Transaction rejected by customer's bank. Please use a different payment method or ask the customer to contact the bank. | ||
Payment Method Status | Invalidated | Valid | ||
What It Means | The account number is incorrect, and the bank is unable to match the details to any particular account.
Payment stops immediately until issue is resolved. | 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. | ||
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. | 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) | Please check that all details of the account provided to the business are correct (E.g. Account Name, Account Number). Or you can provide the business with an alternate payment method. | 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. |
** Only available to integrators on subscription model.
Failed Payments - Account Issues
Payment Response Code | CUST, MD16, MD17 | AC04, AC05, AC07
| |
Payment Response | authority_withdrawn | bank_account_closed | |
Subscription Invoice Status** | Inactive | Inactive | |
Invoice Status | Past_Due | Past_Due | |
Transaction Status | Failed | Failed | |
Payment Provider Response | CUST: Cancellation requested by the Debtor MD16: The payer Customer does not accept the payment terms in the Mandate MD17: Cancellation/amendment requested by the creditor or by the initiating party | AC04: Account number specified has been closed on the Receiver's books AC05: The nominated Payer Customer Account within the Payer Participant AC07: The account to be credited is closed. | |
Payment Response Description | The authority for the payment method has been withdrawn. Please contact the customer for more information. | The account has been closed. Please use a different payment method. | |
What It Means | A stop payment has been applied by the bank on instruction from the customer or the mandate is not accepted by the payer.
This occurs generally when a customer does not recognise a payment on their statement and puts a block on it.
Sometimes the customer puts a stop on a recurring payment when they are in dispute with the service provider.
Payment stops immediately until issue is resolved.
| The account is closed and mandate is no longer valid. Re-validate the account number for accuracy and do not reattempt with same payment method.
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) | Ask the customer to provide an alternate payment method.
To reinstate the recurring authority, they will need to agree to a new Direct Debit Request with a later date than when they put a stop on the payment. | Do not attempt to retry the payment. You should ask the customer for an alternative payment method.
Retrying a payment with the exact same details will yield the same failed payment response. | |
Suggested Actions (For Customers) | If you wish to use the same account details, please contact your bank and authorise payments to be debited by Ezypay. Or you can provide the business with an alternate payment method. | Please provide the business with an alternate payment method. |
Error Responses
Payment Response Code | AC03, AGNT, AM01, AM02, AM05, AM09, AM18, AM19, AM22, ARDT, BE05, BE08, BE18, BE22, CH17, CH20, CH21, DT01, DT02, E991, E992, ED06, FF01, FF04, FF08, FF10, FF11, FOCR, FR01, LEGL, M308, M901, M919, M922, M998, MD06, NARR, NOOR, P176, P177, P178, P179, RC05, RR05, RR07, TD03 | |
Payment Response | ezypay_error | |
Subscription Invoice Status** | Inactive | |
Invoice Status | Past_Due | |
Transaction Status | Error |
** Only available to integrators on subscription model.