Bank errors

This is an error from the customer's bank telling Paystack that the customer's account cannot be charged at that time.

You can have the customer retry the transaction later or escalate to the Paystack support team (via email at support@paystack.com or our contact form) if the error persists.

This is an error from the card issuer and is specific to Verve cards.

You can have the customer retry the transaction later or escalate to the Paystack support team (via email at support@paystack.com or our contact form) if the error persists.

This means that the customer's bank account has been closed by the bank.

Kindly have them contact their bank for further assistance, as the bank will be in the best position to resolve this.

This means that the customer's card issuer cannot generate a token to complete the transaction at that time.

Kindly have the customer retry the transaction later or reach out to their bank if the issue persists.

This error is due to a downtime from the customer's bank. It is most common with UBA Pay with Bank transactions.

Kindly advise the customer to retry the transaction later or escalate to the Paystack support team if the error persists.
They can also use alternative channels on the checkout to complete the transaction.

This error is specific to the USSD GTB 737 channel.
It occurs when the customer does not complete the USSD transaction on their mobile phone.

Kindly have the customer retry the transaction by dialling the USSD code to complete the transaction.

This means the customer's bank is experiencing downtime during the transaction and cannot send an OTP.

Kindly have the customer retry the transaction later or escalate to their bank if the error persists.
They can also use alternative channels on the checkout to complete the transaction.

This means that the customer's bank is experiencing a downtime at the time of the transaction.

Kindly have the customer retry the transaction later or escalate to the Paystack support team if the error persists.

This means the customer's card has not been enabled for online payments by their bank.

Kindly have the customer contact their bank to enable their card for online payments.

This error means there was a downtime when the transaction was attempted.

Kindly have the customer retry the transaction later or escalate to the Paystack support team (via email at support@paystack.com or our contact form) if the error persists.
They can also use alternative channels on the checkout to complete the transaction.

This means that the customer's bank is experiencing a downtime at the time of the transaction.

Kindly have the customer retry the transaction later or escalate to the Paystack support team if the error persists.

This means the customer is not enrolled at their bank to receive OTPs.

Kindly have them reach out to their bank to lodge a complaint to get their card enrolled to receive OTPs.

This is an error message returned by the customer's Card Acquirer (their bank), which means they cannot process the transaction at the time.

Kindly have the customer reach out to their bank for further assistance, as they'd be in a position to help.

This means that the attempted transaction will bring the customer's bank balance below the minimum limit set by their bank or that they have exceeded their transaction limit for that day.

They can contact their bank to increase their limit or try the transaction again after 24 hours.

This means that the customer's bank declined the transaction for reasons best known to them.

The customer can retry the transaction at a later time. If the error persists, however, they will need to escalate to their bank for further assistance.

Do not honour is an error response sent by a customer’s bank when they decline a transaction for reasons best known to them or when a restriction has been placed on a customer’s account.
This error is very common with international transactions where a customer's bank blocks their transaction attempts from being successfully processed until they can verify that their customer is the one initiating the transaction.

As a Paystack business owner, please advise your customer to reach out to their bank to confirm why their transaction attempt was blocked and to help resolve this. As a customer, we also suggest contacting your bank for further assistance.

This means there is a downtime either at the bank or Paystack at the time of the transaction.

You can have the customer retry the transaction later or escalate to the Paystack support team (via email at support@paystack.com or our contact form) if the error persists.

This means there was a processor downtime when the transaction was attempted.

You can have the customer retry the transaction later or escalate to the Paystack support team (via email at support@paystack.com or our contact form) if the error persists.

This means that the customer's bank could not generate a token at the time of the transaction due to an error on their end.

The customer can retry the transaction at another time and escalate to their bank for further assistance if the error persists.

This means that the customer's bank could not authenticate the token at the time of the transaction due to an error from their end.

The customer can retry the transaction later or escalate to their bank for further assistance if the error persists.

This means that the customer has exceeded the number of times they can withdraw from their account daily. Their bank sets this limit.

They can retry the transaction after 24 hours or reach out to their bank to increase their limit.

This error is most common with payment attempts made using virtual cards and typically occurs when the transaction amount falls below the set minimum amount for the card or exceeds the maximum amount.

Try freezing and unfreezing your card, then retry the payment.
If the error persists, kindly contact the Paystack support team for further assistance.

This is a fraud block system implemented by the customer's bank.
This means that the customer's bank declined the transaction.

Kindly have the customer retry the transaction later or escalate to their bank for further assistance if the error persists.

This is an error from the customer's card issuer.
This error is common to Verve cards and typically means that the transaction cannot be processed at that time.

They can retry the transaction later or escalate to their bank if the error persists.

This means the customer's bank or card network is temporarily unavailable due to downtime.

They can retry the transaction later or escalate to the Paystack Support team for further assistance if the error persists.

This means the customer's card has been reported as lost at the bank and cannot be charged again or used to complete any transaction.

Please advise the customer to request a new card from their bank, but in the meantime, they can complete the transaction using any of the other channels on the Paystack checkout form.

This means that the card the customer is using to attempt the transaction has been reported as lost, and a new card has been printed, but they are yet to pick it up from their bank.

Kindly advise the customer to visit the bank and pick up their new card.
In the meantime, the transaction can be completed using any of the other channels on the Paystack checkout form.

This means the customer does not have the OTP and Hardware token activated on their bank account.

The customer needs to contact their bank to enable them to receive OTPs.

These error messages mean that the card being used to attempt the transaction has been hotlisted by the issuing bank after being reported lost or stolen, and a new card has been printed, but the customer has yet to pick it up from their bank.

Please advise the customer to visit their bank and pick up their new card. In the meantime, the transaction can be completed using other payment options on the checkout.

This means that the customer’s bank account appears to be dormant.

You can advise the customer to lodge a complaint at their bank for further assistance.

This is an error from the customer's bank.
It is very common with Ecobank and First Bank transactions and typically means that the transaction was attempted during a temporary downtime at the customer's bank.

The customer needs to retry the transaction later or escalate to the Paystack support team if the error persists.

This error is generated when an OTP has been successfully generated by the customer's bank, but the customer did not proceed with the transaction because they did not get the OTP.

The customer needs to retry the transaction later and enter the OTP sent to them via SMS or email to complete the transaction. If they still do not get an OTP, they’ll need to contact their bank.

This error is generated when the bank has identified this card/user as concerning.
This can mean that the issuer has cancelled the card, the customer's account has been closed, or this use of the card is suspected of being fraudulent.

The customer will need to escalate this to their bank for further assistance.

This means that the customer has issues that need to be resolved with their bank, and this has prevented the transaction from being processed.

Kindly advise the customer to lodge a complaint at their bank for further assistance.

This means that the customer's issuing bank has declined the transaction most typically because the customer is yet to provide a proper means of identification on their account.

Kindly advise the customer to visit their bank to lodge a complaint for further assistance.

This response means that the customer's card has been restricted by their bank.

The customer will need to visit their bank to lodge a complaint. In the meantime, the transaction can be completed using other payment options on the checkout.

This is an error generated by the customer's bank caused by their fraud system blocking the transaction due to suspicious activities.

The customer will need to escalate to their bank to investigate and understand why they're getting that error.

This means the customer's bank is currently experiencing a downtime and cannot process the transaction.

Please advise the customer to use alternative channels on the checkout to complete the transaction or try again at a later time.

This error is generated when a recurring payment isn’t possible on a Verve card.

Please advise the customer to report the error to their bank who will then escalate to the card issuer.

This error is generated when a recurring payment isn’t possible on a Verve card.

You can re-tokenize the customer's card to create a new authorization.
If the error still persists with the new authorization, please advise the customer to report the error to their bank who will then escalate to the card issuer.

This is an error sent by the bank or processor if a transaction cannot be successfully completed at that particular time.

Please advise the customer to wait for a while and retry the transaction, but if the error persists, they should escalate to their bank for further assistance.

This error means that the card issuer is experiencing a downtime. It is most common with Verve cards.

The customer will need to retry the transaction later or try other channels on the Paystack checkout.

This error means there is a downtime at the customer's bank.

The customer needs to retry the transaction later or escalate to their bank if the error persists.

The customer’s bank could not verify the token provided by the customer at the time of the transaction.

The customer will need to retry the transaction later or escalate to their bank if the error persists.
The customer can also use alternative channels on the checkout to complete the transaction.

This error typically occurs when there is a brief transaction processing downtime.
It can also mean the customer has insufficient funds to complete the transaction.

Kindly wait for about an hour before retrying the transaction.
It's also helpful to confirm if the mobile money wallet being used to transact is sufficiently funded.
If the error persists after 24 hours, please get in touch with us via email at support@paystack.com or via our contact form.

This error is due to a temporary downtime from the bank.
It is most common with UBA and Zenith Bank Pay with Bank transactions.

The customer needs to retry the transaction later or escalate to their bank if the error persists.

This error is due to a downtime from the bank. It is most common with Zenith Bank Pay with Bank transactions.

The customer needs to retry the transaction later or escalate to their bank if the error persists.

This is a bank error, and it is most common with First bank transactions initiated via the Pay with Bank channel on the checkout form.

The customer needs to retry the transaction later or escalate to the Paystack support team if the error persists.

This error is from the bank, and it means the customer's account has not been activated at the bank.

The customer will need to contact their bank to activate their account.

All banks, aside from Zenith Bank, Sterling Bank and Guaranty Trust Bank, require registration on Central Pay.
This error occurs when a user of any of these banks uses the Pay with Bank channel for the first time and hasn't been registered.

The customer would need to contact their bank to activate their account for Pay with Bank transactions.

This means the customer has yet to have a phone number linked to their account to receive an OTP.

The customer needs to reach out to their bank to have their account enabled to receive OTPs.