Common bank transaction errors
Updated 28 months ago
This article outlines some common bank transaction errors and their causes to help you guide your customer if a transaction error occurs.
Transaction error | Reason |
---|---|
Account number, phone number validation failed. Received invalid response from remote entity | This is usually a temporary error from the customer's bank. The customer should retry the transaction with a different payment method or contact their bank |
An error occured | This is an error from the customer's bank. The customer should retry the transaction or contact their bank |
Bank could not send SMS | The customer's bank could not send an SMS to validate the account. The customer should retry the transaction or contact their bank |
Daily transaction limit exceeded | The transaction has exceeded the transaction limit on the customer's bank account. They can retry the transaction with a different payment method or contact their bank to increase their transaction limit. |
Gateway timeout | The payment gateway timed out while processing the transaction. The customer should retry the transaction |
Inactive merchant | The customer is trying to pay a merchant that is currently inactive on Flutterwave. The customer can reach out to support for more details |
Incorrect date of birth | The customer's bank declined the transaction because they put in the wrong date of birth. The customer should confirm the right date of birth and retry the transaction |
Insufficient funds / No sufficient funds | The customer doesn't have enough funds in their bank account. They should credit their account and try again |
Invalid hash value | The customer should try a different payment method |
No message | The payment processor timed out before completing the payment. The customer should retry the transaction |
Oops! Duplicate transaction reference. Please check and try again | This happens when a customer is retrying a transaction in a new window/tab without closing the former transaction window/tab. The customer should close the former transaction window/tab and try again |
Pending OTP validation | The customer's bank is trying to authenticate the OTP. The customer should retry the transaction |
Pending redirect | This usually comes up when the authentication is still in progress. The customer needs to contact support for the final status. |
Pending validation | This means the customer's bank is trying to authenticate the transaction. The customer should try the transaction again. |
Please enter the OTP from your secure pass or hard token to validate your payment or Please enter the OTP sent to your mobile to link your account | The customer failed to input the correct OTP. The customer should retry the transaction and enter the OTP sent to their secure pass or hard token. |
Press the white button on your GTB token and type the transaction code generated. | This is a pending message instructing the customer to access their GTBank token to authenticate their transaction. |
Sorry payment already processed | This means that the payment has been processed successfully |
Sorry payment not found | The original transaction was not found after multiple attempts to validate the transaction. The customer should retry the transaction. |
Sorry that account number is invalid. Please check and try again | The customer has entered an account number that is incorrect or invalid. They should try again or use a different payment method. |
Sorry transaction not found | The original transaction was not found after multiple attempts to validate the transaction. The customer should reach out to support and send an email to hi@flutterwavego.com |
Sorry, that account is not permitted | The customer’s bank has declined the transaction as the account cannot be used for this type of transaction. The customer should try again with a different payment method. |
Sorry, that OTP is invalid (FALSE). Please check and try again | The customer has entered an incorrect OTP. They should retry the transaction and enter the correct OTP sent to their mobile number |
Sorry, that reference could not be found | This can be as a result of connectivity issues. The customer should retry the transaction |
Sorry, unable to create a token for your account, please try again later. | The customer's bank failed to create a token to authenticate the transaction. The customer should try a different payment method |
Sorry, we could not connect to your bank | There has been an error connecting to the banking connector to process the payment. This may occur due to an outage. The customer should retry the transaction after some time or use a different payment method |
Sorry, we could not find that transaction | The transaction was not processed successfully. The customer should retry the transaction |
Sorry, we could not retrieve that account | This happens when an invalid account is entered. The customer should check their account details before retrying the transaction. |
Sorry, you have exceeded your allowed limit for a single transaction | The customer’s bank has declined the transaction as it will exceed the customer’s allowed transaction limit. The customer should retry the transaction the next day or contact their bank to extend their limits. |
Sorry, you have exceeded your allowed limit for today | The customer’s bank has declined the transaction as it will exceed the customer’s allowed daily limit. The customer should retry the transaction the next day or contact their bank to extend their limits |
Sorry, you need to add email to your request | The customer did not enter a valid email address on the merchant's platform. The customer should re-check the transaction details they entered |
Sorry, you need to add firstname to your request | The customer did not enter their first name on the merchant's platform. The customer should re-check the transaction details they entered |
Sorry, your payment failed. Please try again | The transaction failed as a result of downtime on our provider. The customer should retry the transaction later. |
System Malfunction | The customer’s bank could not be contacted during the transaction. The customer should retry the transaction later or use a different payment method |
Transaction failed | This error is usually directly from the customer's bank. The customer should retry the transaction |
Transaction failed(Amount mismatch) | This happens when we are unable to confirm the amount paid by the customer. The customer should retry the transaction later. |
Unknown error or an unexpected error occurred during processing | The customer should retry the transaction later. |
User account is not active at the bank | This happens when the account number has been left dormant for a long time. The customer should use a different payment method or contact their bank. |
User not registered / mandate does not exist | The customer is attempting the transaction with an unregistered/blocked account. The customer should use a different payment method or contact their bank. |
User's mobile number is invalid | The customer didn't enter the correct mobile number. The customer should retry the transaction and enter a valid mobile number or use a different payment method |
User's token has expired or Wrong or invalid token | The customer entered an expired or incorrect token. The customer should retry the transaction with a valid token. |
We'd like to hear from you
Suggest the type of support articles you'd like to see
Still need help?
Get in touch if you have more questions that haven’t been answered here