anastasiia_best-practices

[potent condor]

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

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

[humble river]

Hi, you'd need to use a Confirmation Token flow for this: https://docs.stripe.com/payments/build-a-two-step-confirmation

Token will hold data about the details entered in the Element, like the brand, then you can throw an error in your integration saying that the card type is not supported or whatever

[shell mirage]

Thank you for the quick response! Going to check it out now.

[humble river]

See the fields here: https://docs.stripe.com/api/confirmation_tokens/object#confirmation_token_object-payment_method_preview-card

General flow is to create the CT, send it to your backend, and then error if unsupported, or create the intent otherwise

[humble river]

This guide mentions Payment Intent, but they're interchangeable with a Setup Intent