#tocaologist-subscription-schedules
steep yachtBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- tacologist., 2 days ago, 10 messages
tocaologist-subscription-schedules
visual heart
Yes but you'd need to do this: https://stripe.com/docs/payments/build-a-two-step-confirmation
That gives you a chance to check the funding type on the payment method object prior to making the charge: https://stripe.com/docs/api/payment_methods/object#payment_method_object-card-funding
woven magnet
Okay, great. I'll try it out, Thank you!
visual heart
The main thing is the confirmation step should be done client side in that flow
That's so the customer has a chance to complete 3ds auth if necessary
Oh and actually since this is for subscription payments, it makes more sense to use a setupintent to create the payment method: https://stripe.com/docs/payments/save-and-reuse
That way the payment method is actually set up for future usage properly when you create it
Then you can create the subscription schedule with that created payment method (assuming it's not a debit card)
woven magnet
So this approach doesn't use payment intent?
What we are doing right now is creating a payment intent, and we look for the user in stripe, if it exists we update payment info from the payment info in the payment intent and if it doesn't exist we create a new one, because all of our subscriptions are set to auto renew by default
And if they do that with a debit card and run out of funds we just revoke access on the auto renew, but for installment payments we are trying to only accept credit cards so they pay for the whole subscription
visual heart
Wait if you're doing installments/subscriptions, why are you creating a payment intent?
woven magnet
Is that not what we should be doing? I did not implement that, so I wouldn't have an answer to that wuestion, since I saw it I thought that was what we were supposed to do
visual heart
well payment intents are for one-off charges
Do you need to charge the customer a one-off amount in addition to the subscription?
woven magnet
No, we have monthly and yearly subscriptions, so say a monthly costs $10, we charge them 10 when they purchase and we set to auto renew
visual heart
Oh there's no need for a payment intent then
The subscription will charge them the first $10 and handle auto renew
woven magnet
So what would be the right process to do that?
The same one you showed me for installment payments?