#thefyrewire

1 messages · Page 1 of 1 (latest)

regal doveBOT
patent ferry
#

👋 happy to help

#

When we show the user the edit form (which is on our side), we have to validate the post code. How can we tell when Stripe requires a post code or not?
are you using your own inputs?

#

are you PCI compliant?

#

the easiest thing is to use Payment Element

storm dome
#

We're still using Stripe to store the payment method data, we just need to provide a way for the user to edit certain details

regal doveBOT
storm dome
#

I think we were using Payment Element before but it didn't really suit our needs because we wanted to enable future payments

young wadi
#

mainly we ask for the postal code in countries where banks support a check on that information(US/UK/CA/AU I think) (https://stripe.com/docs/disputes/prevention/verification#avs-check). There's no programatic way to know that.

The best solution is to do what the PaymentElement does and ask the customer what country they are in and then collect a postal code in the correct format for that country(or don't collect if that country doesn't use one). Our recommendation is to use the PaymentElement for everything.

storm dome
#

Ahh I see. What would be ideal is if we could just display the SetupIntents Element again, but prefilled with the existing payment method data (minus anything that can't be changed or should be obfuscated, like card number or CVC)

young wadi
#

not possible right now

#

mostly we recommend collecting cards as a completley fresh form and not just editing the details of an existing PaymentMethod