#chckdra_api
vivid roverBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1289202506320052224
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
ebon bridge
hi there!
event if you set hidePostalCode: true, you still need to provide the postal code when confirming the PaymentIntent
native flame
Does this Postal code affect the payment? Adress verification?
We want to use IP data to collect zipcodes for the taxes, so having it used for address verification would cause issues.
ebon bridge
Does this Postal code affect the payment? Adress verification?
yes: https://docs.stripe.com/disputes/prevention/verification
We want to use IP data to collect zipcodes for the taxes, so having it used for address verification would cause issues.
I'm not sure I follow. you want to guess the zip code based on the IP address of the user?
native flame
I see lots of our competitors, not asking for Zipcode on their payment page when using Stripe
We also dont want to have users fill it in
ebon bridge
We want to use IP data to collect zipcodes
technically it would work. but I see two issues with this:
- The mapping IP address <> zipcode will not be perfect
- Users might be in location A, but the zipcode associated with their payment method is completely different
vivid roverBOT
native flame
Yes, so how would we solve this?
I do see other sites not asking for the zipcode?
ebon bridge
well, by default the Payment Element doesn't ask for the zipcode
well actually it depends on the country
for example in the US it does ask for the zipcode
native flame
Yes, I am talking about the US and CA
ancient spoke
Hi taking over here
native flame
Hi there
ancient spoke
So as my colleague said, you can't force the zipcode to never be collected via the payment element unfortunately. I don't recommend trying to force customers to not input it if our optimization determines the need to collect zip. However, you technically could set postal code to never when creating payment element: https://docs.stripe.com/js/elements_object/create_payment_element#payment_element_create-options-fields-billingDetails-address-postalCode. However, that will require you to manually pass in the zip code when confirming the payment intent via: https://docs.stripe.com/js/payment_intents/confirm_payment#confirm_payment_intent-options-confirmParams-payment_method_data-billing_details
native flame
I see, and will this zipcode that is passed through the Payment Intent be used for Address Verification (AVS)?
Since we were thinking we might use a geolocator to get the zipcode, but this would be sometimes inaccurate and if it does affect AVS it might not be smart
ancient spoke
Yes
That's why I can't recommend doing that approach
I recommend just letting us handle showing/hiding it automatically if possible
native flame
But now I am comfused. How are our competitors not collecting the zipcode in the US? They are using Stripe too
ancient spoke
I have no idea
They could be using a custom form
Or they could just be letting us auto hide/show the field
It doesn't always show
native flame
Yes if they used a custom form, dont they also need to provide it in the payment intent?
ancient spoke
No because in that integration path, they would be handling raw card details and they can pass whatever they collect to our api
But that integration path generally isn't recommended because you're responsible for the pci compliance burden
native flame
I see, could you tell me which countries require zipcode in the payment intent?