#jamie_97274

1 messages · Page 1 of 1 (latest)

warm bladeBOT
stable turtle
#

hi, that is not the right way to integrate, as you say it leads to two auths

silk pendant
#

The problem is we also use iDeal/google wallet/apple pay

#

and then that method you sent through does not work

stable turtle
#

it definitely works for Google/Apple Pay at least

silk pendant
#

Also had issues with that parts of docs because we have everything as a one-pager, so creating a user in our backend comes from the same click button as the payment

stable turtle
#

it's technically possible to use https://stripe.com/docs/payments/accept-a-payment-deferred to let you mount and display the PaymentElement without creating anything on the backend, and then you create the Subscription and get + return the PaymentIntent client_secret, when the button is clicked; we just don't document that exact flow right now

#

but should work

silk pendant
#

yes but that is the part that does not work with certain payment methods

#

(trying to find the docs on it again)

stable turtle
#

yes I know a few methods don't work with it

#

I don't have a better answer than to special case those and use the SetupIntent -> Subscription Create flow instead, only for them. The area is really messy unfortuantely(much easiser if you use Checkout instead)

silk pendant
#

I am thinking to go that way only for iDeal/applepay&googlewallet, and then the other method for card

#

it becomes really convoluted process however

stable turtle
#

but yes for some methods like iDEAL you'd have to special case unfortuantely yes, as I said I don't think I have a better answer

silk pendant
#

I can't find the list of the paymentmethodtypes that work with mode subscription where I found out iDeal wasn't supported this way

#

do you know where in the docs I could find this? I thought it was the elements options

stable turtle
#

I don't think we list them unfortuantely

silk pendant
#

you definitely do somewhere

stable turtle
#

if you find them let me know!

silk pendant
#

I am looking for them now, but we have no way of knowing whether the user will pay with ideal or card before loading the payment elements, bit of an issue as the creation of the elements needs to be different (setupintent secret for ideal vs mode=subscription for cards)

stable turtle
#

yeah it's problematic I agree, usually I just use Checkout and avoid all this