#hannes_best-practices
1 messages ยท Page 1 of 1 (latest)
๐ 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/1311017380645830747
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there
There's no concept of "authorization" followed by "capture" for bank debit payment methods, unlike cards
If you're not able to change your app logic, you likely want to avoid using bank debit payments altogether
OK, thanks. It would have been nice to be able to handle all payment methods similarly ๐
We do need to accept sepa debits, that is a must by some customers. However, the tricky problem we're facing is the following: if we "reserve" the ticket for some time, the user might complete the payment intent on the client side right when the reservation expires -> payment done, but ticket might have been bough
So there's no way to have the user input the IBAN and accept the mandate, but only kick off that payment intent from our server after the ticket has been marked as "ordered"?
but only kick off that payment intent from our server after the ticket has been marked as "ordered"?
How long after the user has inputted their payment details would you create the PI?
The reason I ask is because there are a couple of ways you can go about this. You can use SetupIntents to collect their payment details now if you plan to charge them hours/days+ later when they're off session
immediately. When the user submits the form, some checks are done (form is validated server side, ticket is "booked" and so on) and the payment intent is captured.
I see, okay
At least that's how it works with the other payment methods.
So you probably want this: https://docs.stripe.com/payments/build-a-two-step-confirmation
You'll essentially present the PaymentElement before creating the PaymentIntent and use ConfirmationTokens to create a PaymentMethod first before deciding whether or not to proceed with PI creation