dai

[coral crow]

• diff: example guide covers single payment
  • whereas we create a subscription (reoccurring payments)
• diff: the only backend implementation is an endpoint for setting up payment intents
• diff: the guide calls for stripe.confirmPayment to submit checkout action
  • whereas we call our own backend endpoint(s)
• diff: guide calls for paymentIntents.create
  • whereas we call setupIntents.create

Steps that occur during our checkout submit

1. Create setupIntent
2. Validate captcha
3. Create token representing the payment element input
   1. Update the customer and attach that payment method via source with the token
4. Update the customer's billing information (address, country, etc)
5. Create the subscription and relevant data models on our side corresponding to that subscription

Seems like between guide and our implementation - the expectations are different.

At a high level - we'd like to implement a on-session checkout that creates a subscription for reoccurring payments. This checkout is looking to accept 3DS payments

[waxen prism]

Recommend just following this guide: https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements&element=payment

It handles 3ds

[coral crow]

woah this guide appears on the nose! 🙌 will have to review

[waxen prism]

Cool yeah it's our recommended subscription flow

Uses the payment element

[coral crow]

I'll have to take some time to read and review for what this means for my team - is the suggestion on this discord to open a new thread or could we keep this open for some async time?

[waxen prism]

We close threads after a period of inactivity, so recommend you just return with a new thread in the main channel

[coral crow]

understood 🫡 - appreciate the quick and helpful response thus far!