#jayrodrigues_api

1 messages ¡ Page 1 of 1 (latest)

rustic wraithBOT
#

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

hexed wing
#

Hello! The Card Element uses the BIN of the card number to determine if it should collec the postal code or not. There are scenarios where the BIN indicates the wrong thing and the Card Element won't collect the postal code even though it should. This is one of the things we fixed with the Payment Element, which we recommend you upgrade to: https://docs.stripe.com/payments/payment-element/migration

arctic dagger
#

How can I tell which version is being used just from the element being loaded on the front-end?

hexed wing
#

You can verify the publishable key being used matches the Stripe account with the validated domain.

rustic wraithBOT
arctic dagger
#

Sorry, what I mean is how can I tell from the front-end form if it is using the latest version of the payment element?

hexed wing
#

If you're loading Stripe.js from Stripe (which you're required to do) you're using the latest version. You can't really use an old version of the Payment Element.

arctic dagger
#

So if that's loading the latest version, what part do we have to upgrade? WOulnd't it brign in the latest element?

hexed wing
#

You're using the Card Element, not the Payment Element. They're completely different Stripe Elements.

#

The migration guide I linked to above explains the differences and how to migrate from Card Element to Payment Element.

arctic dagger
#

Thanks, sorry I don't do the dev part so wanted to check to avoid delays

#

Is this a quick and straight forward migration?

bitter pumice
#

Hello
If you're using PaymentIntents API already for payments then it should be quite straight forward. I'd recommend reading through the doc Rubeus linked above

arctic dagger
#

Is there any other way around this without doing the ugprade as there is an event happening and they are trying to collect payments

bitter pumice
arctic dagger
#

So we pass it via the API - the address details?

bitter pumice
#

You'd still pass it via client-side but yeah you're passing it manually basically

arctic dagger
#

Is it required to be passed?

bitter pumice
#

It depends on the bank/issuer as they may block the payment for fraud reasons if one isn't provided

arctic dagger
#

On the new payments elements, is the postal code passed the same way with the new elements block? Bc if the postal code is being collected on the form, no need for them to fill it out agian on the payment element

bitter pumice
#

PaymentElement collect the zip code by default yes

arctic dagger
#

On the web form if the zip code is there, on the new payment elemnet, how can I pas that? - same way as you sent here?

One option could be to disable the postalCode collection on the card element and add your own input field to collect the zip instead - https://docs.stripe.com/js/elements_object/create_element?type=card#elements_create-options-hidePostalCode

Once you collect it yourself, you can pass it in with confirmParams
https://docs.stripe.com/js/payment_intents/confirm_payment#confirm_payment_intent-options-confirmParams-payment_method_data-billing_details