I am using a custom Stripe checkout form, which works perfectly with a credit card.
For many other payment method types like sepa debit confirmation is required, so I checked the Confirm option in the createPaymentIntent sc action.
I also set the required return url and then this error remains in the console:
You cannot confirm this PaymentIntent because it's missing a payment method. You can either update the PaymentIntent with a payment method and then confirm it again, or confirm it again directly with a payment method.
So I suppose the payment method should be set here:
You really don’t have to enable payment confirmation and also specify specific payment method.
It is all done automatically when you use the hosted stripe checkout.
The payment method you see in the UI is for a very specific workflow where you create a very specific payment method first. But that is very advanced and you really don’t need it.
So just follow the stripe checkout tutorial and when you use the stripe hosted checkout, stripe handles all your redirects and confirmation, also for ideal and sepa.
I followed @Teodor’s tutorial for custom Stripe checkout with multiple payment methods and it all works fine for card payments, so far so good!
However for iDeal and sepa_debit payment methods it doesn’t.
Here’s the error output on the checkout page when iDeal payment method is chosen:
So the missing return_url is required for this payment method it seems.
But that parameter can only be used if confirm is set to true:
Continuing, when confirm is enabled and a return_url is added, this error is thrown on the checkout page:
error: "You cannot confirm this PaymentIntent because it's missing a payment method. You can either update the PaymentIntent with a payment method and then confirm it again, or confirm it again directly with a payment method."
Hence my question about how to retrieve and set the payment method to make the confirmation work properly for other payment methods than cards?
Any news on this topic @George?
I know and understand that you are all very busy with the new beta versions, but this problem is still unsolved after more than a month and it seems nobody can help. Any assistance from the Wappler team would be very much appreciated. Thanks in advance!