#elonored_best-practices

1 messages · Page 1 of 1 (latest)

lucid cobaltBOT
#

👋 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/1432664002445574165

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

quick tundra
#

hey there 👋

#

the address fields that show are driven by country and payment method type, broadly speaking

#

auto will use Stripe's algorithmic best judgment about which address fields to surface based on country and payment method type, whereas if_required will only surface fields the payment method requires

#

that's the general rule - getting more specific around the logic for SEPA may be a little tricky but I'm taking a deeper look

#

checking internally, I can confirm that at least for some countries/locations, an address is required to successfully process a SEPA transaction

#

so the Element likely treats it as a requirement for SEPA across the board to avoid issues with this

#

the address requirement doesn't come from the issuing bank, so there's no error to catch - it's something Stripe determines based on payment method

#

it doesn't seem to be possible to configure the Payment Element to match the IbanElement component

rocky robin
#

thanks for all this answers. Do you know what address fields banks really usually requires : is it always a full address or could it work by just asking few information like country or postal code ?

quick tundra