#huncsuga_code
tranquil oceanBOT
đź‘‹ 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/1417132756554616965
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
lavish halo
Hi, can you share a screenshot of the error please?
glossy fulcrum
lavish halo
The reason being, the ConfirmationToken only works with PaymenetElement or ExpressCheckoutElement: https://docs.stripe.com/js/confirmation_tokens/create_confirmation_token
Given that the CardElement is a legacy intergation, https://docs.stripe.com/payments/payment-card-element-comparison we do not add any active development.
You would either need to use PaymentElement or ExpressCheckoutElement with it.
glossy fulcrum
Thank you for quick response.
I have two follow-up questions:
-
If I absolutely need to stick with CardElement for my flow, is there still a way to collect card details on the Details step and only capture the payment on the Summary step—while ensuring that banks do not send a $0/$1 authorization during the validation on the Details page?
-
Regarding PaymentElement, is it possible to customize it deeply so that it doesn’t impose a predefined layout, but instead lets me design the full UI myself?
lavish halo
You can customize the PaymentElement some and we document those here: https://docs.stripe.com/elements/appearance-api
I've been thinking about solutions with the CardElement, let me try a couple of things.