#ionu_docs
feral estuaryBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1308430772322959402
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
cerulean haven
hi! not too sure since our support for India is a private beta, but I think it should work. Best to ask your account manager/support team if you're in our India beta
mental harness
hi, so the stripe account needs to be in private beta. I do not think we are. Is there a way to test it in development mode ?
cerulean haven
to be clear I mean you can not have a Stripe merchant account in India without working with our sales team.
are you talking about something else? like maybe you have an existing Stripe account not in India and you're asking about charging customers who are in India?
mental harness
yes, sorry for the confusion. The account can be anywhere, and so can be the charges. And we had issues with india credit cards before
cerulean haven
yeah issues are common unfortunately
AFAIK that ConfirmationToken integration should work, for one-off payments. If you need to do recurring payments and have it work for Indian customers, you must use our Subscription product(i.e. https://docs.stripe.com/payments/finalize-payments-on-the-server?platform=web&type=subscription) , not your own logic to create PaymentIntents off-session.
mental harness
yeah, we use our own logic for recurring, with stored payment profiles and using them off-session
so the way to go would be to create the payment intent normally, and than confirm it
cerulean haven
AFAIK recurring payments won't work that way for Indian customers because you need to create an e-mandate in order for off-session payments to work, and that only gets created when using our Subscriptions products
mental harness
right now we are using createToken in the front end, and than capture with payment intent in the backend, and on "rebill" we do not use off_session, and they will need to go and proceed with the sca (send an email with the link to an sca confirmation page).
Will this work the same with createConfirmationToken ?
And is there a way to test this, since I do not have an india card 🙂
Thanks
cerulean haven
if the recurring payments are all processed as on-session payments with the customer present on your site, then I think that works in general
in terms of testing we have these numbers : https://docs.stripe.com/india-recurring-payments?integration=paymentIntents-setupIntents#testing
mental harness
ok, so in the end, either way we choose, be it createConfirmationToken or paymentIntent on server -> confirm payment in front-end. Indian customers will have the same issue with the next payments. But the first payment should work
cerulean haven
I don't think they would have problems if the "next payments" are all done on-session, the issue arises with off-session charges on saved cards. But overall yes, sounds about right