#franco
true ruin
supple cliff
Hi there. So if you're doing recurring payments, why do you use SetupIntents?
fading thistle
We use SetupIntents to capture the card information and store it along with the mandate required for Indian cards.
We're using Stripe Elements (PaymentElement)
supple cliff
Ok I see, but are you using Stripe Subscriptions? If so, creating a SetupIntent is an unnecessary step
fading thistle
We're using subscriptions, yes. How should we be doing card info capture?
I should mention that we're using metered-pricing subs, not fixed price ones
supple cliff
Gotcha. The recommended flow is to create the subscription and then pass the client secret of the payment intent attached to it to the Payment Element: https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements
Basically the flow covered in the above guide is the recommended flow
From what I understand, compliance is handled automatically if you use that flow: https://stripe.com/docs/india-recurring-payments#impact-subscriptions
fading thistle
Thing is, we may collect payment details and create the customer without subscribing the customer to any plan yet. This wouldn't be possible with this flow right? Is there a way of making this work with SetupIntents?
fading thistle
We're following the flow described in the "Other products" section https://stripe.com/docs/india-recurring-payments#impact-other-products
supple cliff
So that section for other products is meant to be if you aren't using Stripe Subscriptions at all. That's for if you manually implement subscriptions on your end with Payment Intents. However, you still are using Stripe Subscriptions (that Payment Intent was generated by a Stripe Subscription). So, I think it's just using the automatic process that's outlined here: https://stripe.com/docs/india-recurring-payments#subscription-creation
fading thistle
Is the only option to migrate to use pure subscriptions then?
Isn't there a way to set the mandate created by the setup intent to the subscription?
supple cliff
Try setting the mandate options here: https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_settings-payment_method_options-card-mandate_options
When you create the sub
Don't know if that will work off the top of my head but you can try it out
Why do you want to set it manually exactly?
fading thistle
I don't, I just want to make sure this will work for indian cards. Right now our test payments are succeeding where they should be failing if I understand correctly
We understood that by setting the mandate params in the Setup Intent, it would work.
supple cliff
The issue is you use Subscriptions, where there isn't a way to carry over the mandate from the SetupIntent to the Sub. So, a mandate is created when you set up the payment method, but the automatic process outlined here is what's actually being taken into effect: https://stripe.com/docs/india-recurring-payments#subscription-creation. So, why not let it manage it automatically for you?
Is there a need to limit the amount you want to charge in the future when you set up the payment method? Is that the core issue?
fading thistle
No no, the only issue I see from our side with this is that we have to subscribe the user to one of our plans when we ask for payment info, which differs from our current UX.
Now you can add your card, we register the user as a Stripe customer, but do not subscribe it to anything. Then when they decide to upgrade, they already have their card on file
We also use this flow to setup Enterprise customers (have them to register as a Stripe customer from the dashboard, then manually set up ACH/other payment forms in the Stripe dashboard)
supple cliff
But you can continue to use that flow. The mandate that will be used will just be the one auto generated by the subscription; not the one from the setupintent