#alko89
1 messages · Page 1 of 1 (latest)
Do you have a specific example?
But sure, it's entirely possible that a bank can request auth/3DS for a card previously 'setup'
sure, here is a customer that added a card on 6th, he then created a subscription, but all billing threshold payments are failing
https://dashboard.stripe.com/customers/cus_Nf8iYNuVNvbVRy
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Can you share a specific payment please
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
This is an Indian customer/card which are subject to tighter auth restrictions imposed by the RBI
The user has to authentication for each recurring payment. See: https://stripe.com/docs/india-recurring-payments
I see, thank you for the lookup, guess we'll have to create mandates for all overage charges in this case? 🤔
and trigger manual payments after verification
its an extreme case though, users usually don't do that many
I don't understand the question. Why would you need to create mandates?
What's an 'overage charge'?
I guess you're referencing: https://stripe.com/docs/products-prices/pricing-models#thresholds
@latent creek how can we identify that a mandate needs to be created?
I am reading https://stripe.com/docs/india-recurring-payments?integration=paymentIntents-setupIntents at the moment.
Also do I understand correct that the bank will send the email to the user aboutr the upcoming charge and we dont need to handle that?
Not really sure why you'd need to create anything manually in that flow? The threshold triggers an Invoice creation, which in turns triggers the payment request. Because of RBI regulations, the customer must authorise each recurring payment manually – there's no action required from your side
You don't need to create a mandate – the Subscription creation flow and payment method collection handles that: https://stripe.com/docs/india-recurring-payments?integration=paymentIntents-setupIntents#:~:text=Subsequent off-session,authorise the payment.
I thought a mandate was created so the user dont have to authenticate every payment and we can continue doing off-session charges?
Not for Indian customers, as that document explains. There's additional, non-Stripe regulations in place that mean customers must authenticate every off-session payment
Ok, I have misunderstood it.
How come under the Integration part of that page it is explained how we on our side should change our integration for SetupIntents to be able to create off-session payment on India-issueed cards?
From my understanding that is what we want to do, use SetupIntents to create off-session payments on India-issueed cards.
No, you're using recurring payments via a Subscription. Not ad-hoc off-session payments
are subscription_thresholdconsidered recurring payments?
Is usage based pricing a ad-hoc off-session payments ?
We have both flat rate subscription and usage based subscription.
No, as I stated earlier. The usage thresholds just trigger recurring, invoice based payments
Ok thanks for the answers and explanations! @latent creek