Hey José,
Thanks for the message and reaching out.
The zip requirement is something that Stripe recommends at a minimum to help prevent fraud on your account. See their link on that here:
https://stripe.com/docs/disputes/prevention
The good news is that if any of your users use Apple Pay, Google Pay, or Microsoft Pay, they won’t have to type any of their details, including their zip, to make a payment.
The zip field is required for Stripe’s all-in-one card element as well, which is the field which combines the card number, expiry, cvc, and zip all in a single field. If we remove the zip requirement, we wouldn’t be able to use that field, which is a super great user experience!
Hi,
Thanks for the quick reply. I understand, but there are two issues:
(a) I’ve seen websites using stripe which do not require the zipcode
(b) There’s also a more immediate (but, I guess, easier to solve) problem:
When I try to test paying with my CC in my website (with the plugin installed), I get the “incomplete zip code” message, but I don’t even HAVE the zip-code field visible in the form to begin with!
I’ve tried zooming in and out, but that doesn’t do it.
Can you help?
Definitely!
a) While it is possible, it would go against Stripe’s recommendations, and also prevent being able to use the all-in-one field. For those reasons, while we aren’t completely closed to the idea, it would be something that requires planning and consideration, as well as some research to see if it would be worth the added overhead.
b) Definitely happy to help make sure that gets fixed! What is your URL, where the payment form is?
I tested your payment form on iPhone, Mac OSX, and Android, and all are showing the zip field on my end.
Are you able to email a screenshot of how it looks on your end to [email protected]?
@pimenteljm Just following up. We just released version 1.0.2.3 of Tip Jar WP which removes the requirement for a zip code, and relies on Stripe to show-or-not-show the zip code field, based on the card’s requirements.
Thanks for your assistance on this issue!