The Card 39;s Zip Code Failed Validation
Kum Filteau
The bank account number provided is invalid (e.g., missing digits). Bank account information varies from country to country. We recommend creating validations in your entry forms based on the bank account formats we provide.
The payment requires authentication to proceed. If your customer is off session, notify your customer to return to your application and complete the payment. If you provided the error_on_requires_action parameter, then your customer should try another card that does not require authentication.
The bank account provided already exists on the specified Customer object. If the bank account should also be attached to a different customer, include the correct customer ID when making the request again.
The Subscription or Invoice attempted payment on a PaymentMethod without an active mandate. In order to create Subscription or Invoice payments with this PaymentMethod, it must be confirmed on-session with a PaymentIntent or SetupIntent first.
This card has been declined too many times. You can try to charge this card again after 24 hours. We suggest reaching out to your customer to make sure they have entered all of their information correctly and that there are no issues with their card.
The card has been declined. When a card is declined, the error returned also includes the decline_code attribute with the reason why the card was declined. Refer to our decline codes documentation to learn more.
You must have a phone_number on file for Issuing Cardholders who will be creating EU cards. You cannot create EU cards without a phone_number on file for the cardholder. See the 3D Secure Documenation for more details.
The source cannot be used because it is not in the correct state (e.g., a charge request is trying to use a source with a pending, failed, or consumed source). Check the status of the source you are attempting to use.
An invoice cannot be generated for the specified subscription as there are no pending invoice items. Check that the correct subscription is being specified or create any necessary invoice items first.
The specified invoice can no longer be edited. Instead, consider creating additional invoice items that will be applied to the next invoice. You can either manually generate the next invoice or wait for it to be automatically generated at the end of the billing cycle.
This object cannot be accessed right now because another API request or Stripe process is currently accessing it. If you see this error intermittently, retry the request. If you see this error frequently and are making multiple concurrent requests to a single object, make your requests serially or at a lower rate. See the rate limit documentation for more details.
One or more of the parameters requires an integer, but the values provided were a different type. Make sure that only supported values are provided for each attribute. Refer to our API documentation to look up the type of data each attribute supports.
One or more provided parameters was not allowed for the given operation on the PaymentIntent. Check our API reference or the returned error message to see which values were not correct for that PaymentIntent.
The latest payment attempt for the PaymentIntent has expired. Check the last_payment_error property on the PaymentIntent for more details, and provide a new payment method to attempt to fulfill this PaymentIntent again.
The latest payment attempt for the PaymentIntent has failed. Check the last_payment_error property on the PaymentIntent for more details, and provide a new payment method to attempt to fulfill this PaymentIntent again.
The payment or setup attempt was declined by the issuer or customer. Check the last_payment_error or last_setup_error property on the PaymentIntent or SetupIntent respectively for more details, and provide a new payment method to attempt to fulfill this intent again.
The payment method failed due to a timeout. Check the last_payment_error or last_setup_error property on the PaymentIntent or SetupIntent respectively for more details, and provide a new payment method to attempt to fulfill this intent again.
The API key provided by your Connect platform has expired. This occurs if your platform has either generated a new key or the connected account has been disconnected from the platform. Obtain your current API keys from the Dashboard and update your integration, or reach out to the user and reconnect the account.
One or more provided parameters was not allowed for the given operation on the SetupIntent. Check our API reference or the returned error message to see which values were not correct for that SetupIntent.
The latest setup attempt for the SetupIntent has expired. Check the last_setup_error property on the SetupIntent for more details, and provide a new payment method to attempt to complete this SetupIntent again.
Reader is currently offline, please ensure the reader is powered on and connected to the internet before retrying your request. Reference the integration guide for details on how to handle this error.
This has happened several times to my knowledge and probably many other times. When I have tried to process a card payment through Shopify it keeps rejecting the card saying the zip code doesn't match the card. Today a customer called and we tries 3 different cards with 2 different zip codes and none would work. I asked the customer to try to make payment through the cart at his side and he still could not pay. This has happened before.
I'm sorry to hear you'd had some difficulty here, I can definitely understand the frustration when a card is not going through. If you are seeing the error "the zip code you supplied failed validation.", then the customer needs to ensure that the zip code they entered on their order matches what is on file with their credit card company. This failure indicates that it does not. When you enable the Shopify Payments setting to decline charges that fail ZIP code verification, any time the zip code doesn't match, the payment will fail.
It could happen that the customer has moved addresses but still has their old one on file with the credit card company! Would you be able to reach out to the customer and ask them to check the zip they have on file? Is the order still failing?
Ava Social Care @ Shopify
- Was my reply helpful? Click Like to let me know!
- Was your question answered? Mark it as an Accepted Solution
- To learn more visit the Shopify Help Center or the Shopify Blog
Thank you for your reply. In this instance the customer was a long established business, so the zip code was correct for 2 out of 3 cards that I tried and the customer tried to pay with. The third card was the customers personal card and we used his home zip code. All which I am assured are the correct zip codes. After 2 failed attempts does the collection company decline due to multiple payment attempts?
I too am looking for a solution to this. One particular customer has an issue with a card they have had a long time. No moving, no changing and zip code matches. Is there a resolution for this? She has had this happen multiple times over years. Only with Shopify!
I have had the same issue today. The Customer had successfully used the card on other sites with no issue but on Shopify it failed. This is not the first time a customer of mine has had a message "The zip code you supplied failed validation".
You saved me, but I have a more complex problem and I would appreciate it if you could help me. a customer placed an order and received this error (Your payment details couldn't be verified. Check your card details and try again) but after the error he was charged with the amount of my product. it appeared in the bank application that the money was withdrawn, I don't see any order placed in the menu of my store or that I received any money, what can I do so that customers are no longer charged for any error they receive??
When a payment fails, the customer's bank, the payment network or the payment processor returns an error code. The code gives an indication of what went wrong during the payment, which can help you to identify problems in your payment handling.
Different payment processors and banks generate different error codes when payments fail. ProcessOut uses its own set of error codes as an abstraction over these different systems. This means that you will see the same ProcessOut code for a particular type of error, regardless of which code the bank or provider originally returned.
Some banks and providers return just a single generic error code (such as card.do-not-honor) for all failures. This confirms that the transaction failed but does not give you much help when you try to identify the problem.
Use the error_code field of a Transaction object to retrieve the code returned after an authorization or capture. The operations field of the Transaction object contains a list of Transaction operations that also have their own error_code fields. The sequence of operations in a transaction can give you more detail about what went wrong along the way and what ProcessOut did to correct the errors.
ProcessOut may automatically block a transaction to comply with scheme rules. For example, an authorization will return request.transaction-blocked if Mastercard sends a 03: Do Not Retry Merchant Advice Code. Future transactions on the same gateway with the same card and amount will be blocked for 30 days to avoid compliance fees.
It's also possible to configure transaction retries on a fallback gateway based on specific error codes returned by a prior gateway. This configuration is set at the routing rule level and can be disabled or enabled based on your preferences.
The list does not contain every possible error that ProcessOut can generate. This is because banks and providers update their error code schemes from day to day without notice.
We strongly recommend that you design your code to treat unfamiliar error codes as payment declines.