#duncan - Elements Customization
prime mantle
Hey duncan. Does this guide achieve what you're trying to do? https://stripe.com/docs/payments/accept-a-payment You shouldn't be required to enter address information
cloud cove
No, that illustrates the problem—using the custon payments flow, how do I remove the country and postal code fields?
If I hide them with Elements, I then can't confirm the setup intent without providing values for country and zip… which defeats the purpose of hiding them in the first place. Obviously it must be possible to collect card information without the user's country and zip code?
Oh, and thanks for the reply and the help by the way!
prime mantle
Gotcha. Looking into this
cloud cove
Thanks! 🙂
prime mantle
Hey sorry for the delay
Unfortunately with a SetupIntent, there's no way to only collect card information
You'll need country and zip code too
cloud cove
Wow, really? Am I mistaken, or did this used to be possible with a previous version of the API?
Well, it must be, since we have another integration from a few years ago where we did this and did not collect country or zip.
What in the world is the reason for this? The additional fields add additional hurdles to conversion.
It's also crazy that your documentation doesn't even mention this. We spent quite a bit of time banging our heads against a wall trying to figure this out. The documentation makes it seem like it's possible, but it just doesn't work in practice.
prime mantle
I believe you're referring to the card element: https://stripe.com/docs/payments/accept-card-payments?platform=web&ui=elements
That didn't require zip code or country
But for SetupIntents that's required just to further ensure those future payments go through
cloud cove
Yeah. Unfortunately, the table listing the differences between the card and the payment element in the docs don't mention that this is a key difference. We would never have gone with payment if we realized this limitation at the get-go.
It's obviously possible to perform future payments without a country/zip, since it is happening with our previous integration. It's crazy that we don't have the option to go that route if we've made the calculation regarding conversion vs fraud, for example.