#wqrld_ideal-paymentflow
narrow baneBOT
👋 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/1288193596738113620
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
heavy shell
@night nymph Hello! I'm happy to help but I don't fully get your question right now and what you are trying to change/fix/optimize
wqrld_ideal-paymentflow
night nymph
My old flow with the sources api used to be:
on our platform, user selects products to renew and clicks on button for appropriate payment method. then gets redirected a graphical listing of supported banks / QR code to pay with.
With the new flow:
on our platform, user selects products to renew and clicks on button for appropriate payment method. then gets redirected a stripe checkout page to fill in their name again, and only then the graphical listing of supported banks / QR code to pay with.
i would ideally remove the stripe-hosted checkout page from that equation, since i've had a few people ask about it and it's not often a normal part of an iDeal flow
https://i.wqrld.net/Cake_PoFmap this page is the one i would like to remove. the user's name is already known in my system
heavy shell
Hmmm but you explicitly integrated Stripe Checkout for this right? That's a decision you made here. You seem to not want Checkout at all if you already have your own payment flow where you ask clear information upfront?
night nymph
To my knowledge i do have to use the checkout API; but i indeed do not want to show the checkout page as it has no added benefit to the user and causes confusion
heavy shell
Yeah you likely misunderstood something (or we explained it wrong). Using Checkout is an option. It's a quick way to migrate your old integration to a simpler one where we do everything for you.
If you already have your own payment flow, your own form, have them choose the payment method type, pre-fill information, etc. then there's no reason to use Checkout
night nymph
Alright, do you have any documentation on how that should be implemented?
what part of the library should i be looking up on?
heavy shell
Can you show me what your UI and code looks before that Checkout UI you redirect them to?
Is there a reason you ask them for their payment method yourself? Why not let us show them all available options for you?
night nymph
I only need three, of which one is used by 95% of the users (ideal). Thus there is no real need for a separate page
heavy shell
hmmmm
night nymph
https://i.wqrld.net/Cake_7N88qr (ignore the half-translations 🙂 )
heavy shell
Okay so you aren't really tied to your own UI itself. You just want something that's directly on your own website/payment page where you can show all the options?
Like my advice would be to look at PaymentElement instead. See https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=elements
though this is for one-time payments and your screenshot implies recurring payments?
Sorry, it';s tough without a clear 2 sentences summary of your end goals. It looks like you went deep down the wrong path and are trying to fix that path versus going back to the original goals
night nymph
heavy shell
Okay so you basically want none of our UIs and you want to patch your existing UI to work. It's definitely possible. Not what I would do at all but doable
What do you do today in your code? Like how are you configuring a recurring payment since iDEAL is single use?
night nymph
this is all manual single-use payments. Users get an email every month to pay if they would like to renew.
Automatic payments are possible using SEPA, but by far most users prefer to manually renew every month
Usually the service duration is only 1-3 months, so that makes sense
heavy shell
Okay so it is a one-time payment after all each time
night nymph
yes, correct
heavy shell
What you need to do is confirm the PaymentIntent with payment_method_data[type]: 'ideal' and it's going to give you a URL to redirect them to. Looks like exactly what you want
night nymph
so as i understand it:
Do not use stripe checkout
Instead, make a make paymentMethod, make paymentintent, confirm paymentintent, redirect user
correct?
heavy shell
you don't need to even make a PaymentMethod. You can use create and confirm the PaymentIntent server-side all in one request
night nymph
https://docs.stripe.com/api/payment_intents/create#create_payment_intent-payment_method this paragraph seems to say that you do need to attach a paymentmethod if you want to confirm?
heavy shell
yes but you can pass payment_method_data instead. See what I said above
night nymph
ahhhhhhhhhhhhhhh
that was too hidden
thank you, that was exactly what i was looking for
Thanks!
heavy shell
yeah your UI is definitely common in various plugins for example. We do think our approach converts better on our end but it requires a different UI/checkout flow