#Nepotist-moto

1 messages · Page 1 of 1 (latest)

shell solstice
#

Hey! Can you share how you're currently creating your Payment Intents?

#

You generally need to provide the payment method at time of PI creation for MOTO payments, so the flow will likely look a little different

plain wolf
#

For sure, one moment

#

Do you want to see code? or should I describe the flow?

#

We currently gather customer info in the frontend, then create the customer in Stripe, create a Subscription/Invoice (depending on the type of product) with payment_behavior 'default_incomplete' to have a finalized invoice with PI and client secret, then we pass the client secret back to the frontend to gather Payment Method details, then we use stripe.confirmPayment to include the 'elements' and confirmParams for payment.

shell solstice
#

You can justr share a pi_xxx ID

plain wolf
#

Oh!

#

😄

#

pi_3LhTuLGeos9eOLE81b7pjPDY

#

From our live system

shell solstice
#

Ok, so you can't do MOTO with subscriptions AFAIK

plain wolf
#

Ah ha

shell solstice
#

Confirming

#

Yep, no parameter on subscriptions to enable that

plain wolf
#

Well darn. Could we make a single purchase, setup the card for future payments, then create the subscription and use that PM as the subscription default?

shell solstice
#

Sure, that will work and we'll apply for SCA exemptions as an off-session recurring payment

plain wolf
#

Great, we will try that out. Thanks for your help!