Common Payment Processing Errors

This article will list the top common processing errors clients and vendors experience.

Melissa Teague avatar
Written by Melissa Teague
Updated over a week ago

Your client could encounter a variety of errors while submitting an online payment. You can review the Project Logs to see the details about why your client is not able to pay online.

Here are a few of the most common Payment Processing Errors and the next steps for your client.

Zip Code Error

When a payment fails due to a zip code error, it is because of a message coming directly from your client's bank.

As an added level of security, Stripe verifies the zip code provided with the client's bank, and should there be a discrepancy, the client's bank will not allow the payment.

Solution

The best course of action in this case would be to have the customer confirm they have the correct zip code on file with their bank.

As a quick note: The client may see a pending transaction on their statement for 3-5 business days.

Insufficient Funds

When a payment fails due to Insufficient funds, it means that the card does not have enough funds to cover the order. Payment attempts where insufficient funds were the cause will appear as 'Fraudulent' in the project logs, specifically when a card has been tried multiple times

Solution

The client will need to contact their bank to find out if there's a problem with the account or try again with a different payment method.

Card Missing

This can happen due to suspected fraudulent activity. Many different things can trigger this code: large purchases, too many charge attempts, or a large volume of charges over a short period. The bank doesn’t always provide Stripe with enough information to give exact details on why the client was blocked.

Solution

The client will need to contact their bank for further insight or use a different card.

Card Expired

Vendors often can't capture a payment when the card on file has expired.

Solution

The customer will need to update their card on file.

Did this answer your question?