Generic Decline on Webform - Square API

So I’m using this square up form with the newest API on my website.
And i get (Generic Decline) when the cvv or expiration dates are wrong.

But I believe when you pay an invoice directly on squareup, the user may be asked to verify the zip code for example. Is this form capable of asking for any verification? Or will it just show generic decline for anything?

Clients are often having issues with their cards, but then when I send an invoice, they can pay without problem.

:waving_hand: I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:

Additional Documentation

Get Started
Guidelines and Limitations
Take a Credit Card Payment

If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.

The Web Payments SDK performs client-side validation on card entry fields, such as improper credit card number length, wrong expiration date format, incomplete ZIP code, and non-credit card number. If the credit card details are entered correctly but specific field values are wrong (like an invalid expiration date or card number), the card will still pass the client-side validation but will fail when the payment is actually attempted.

In such cases, it’s the responsibility of the partner application to handle these errors and display a user-friendly error message on the payment form if the payment attempt fails, asking the customer to re-enter the card details.

However, the Web Payments SDK does not have the capability to ask for additional verification like ZIP code. If you’re seeing a “Generic Decline” error, it could be due to a variety of reasons, including incorrect card details or issues with the card issuer. It’s recommended to ask the customer to double-check their card details or contact their card issuer for more information.

This answer was reviewed by @Bryan-Square.