#bart
modern shoal
Hm. Can you share a payment intent id where you're seeing this happen?
forest reef
pi_3NH5OfHhzXcPYLMM1MSwK3ct
pi_3NH5KtHhzXcPYLMM07mj0THv
(last one has only successful payment so may be easier to inspect)
modern shoal
Is the end-goal that you want to set up the payment method for future 1-time payments I assume?
forest reef
not really so I use:
- paymentIntent for recurring "subscriptions" that are charged immediately and later monthly basis
- setupIntent I use for same "subscriptions" but if we want to give clients free trial
i'm mainly focusing at recurring rather than one-time
modern shoal
Sorry for the delay
I see a mandate on the successful PI you provided
It's on the charge object
Also it's mentioned:
in this section: https://stripe.com/docs/india-recurring-payments?integration=paymentIntents-setupIntents#create-mandate
forest reef
right i do see it now
i was checking the webhook event thus i've missed it
as at the time of charge.succeeded event
its yet populated
is that correct?
is there a way to detect whether payment is going to involve e-mandate from webhook?
atm i'm allowing people to access content as soon as I get paymentIntent.suceeded webhook event. I'm wondering how to code it for e-mandate payments?
if e-mandate is involved does it mean that payment_intent.succeeded will not be issued until Indian customer will accept payment & bank will let it through (up to 26 hours?)
modern shoal
Yeah you won't get payment_intent.succeeded unless the payment was successful
So if it takes up to 26 hours before we charge the customer, then you won't get that event until that charge happens
forest reef
ok that's good
is there any indication that e-mandate process has kicked in for paymentIntent
so i can detect immidately and feedback clients to wait for access
?
modern shoal
Which part?
dusty thistleBOT