#juls-india-rbi

1 messages · Page 1 of 1 (latest)

lofty radishBOT
stuck urchin
#

juls-india-rbi

#

@wild tide you say "why this payment failed" but never gave a payment failure details. Can I ask you to be explicit about what exactly you are looking at?

wild tide
#

It failed due to the 3DS validation not passing.

stuck urchin
#

which exact docs are you following to work through this?

wild tide
#

We're supposed to be able to charge payment intents with 3DS secure cards, if the previous setup intent for the card was successful

#

My doubt is related to the second setup intent that was created..

#

The card I'm using is 4000003560000297

stuck urchin
#

Ack, sorry the server is quite busy so it will take me a while to figure this out. I barely understand RBI rules. But I'll circle back once I know more

#

okay so the SetupIntent you did had a max amount of $9 right?

wild tide
#

yes

stuck urchin
#

But then, I don't understand why, a second setup intent was created here
you said this but you linked the exact same event id

wild tide
#

This is the second one created, right after the first setup intent succeeded

stuck urchin
#

you seem to update the Subscription multiple times, is that expected? what exactly are you trying to model here?

#

Like each SetupIntent is associated with a Subscription update

wild tide
#

At this point, the only update should have been the payment details. Where do you see this updates?

stuck urchin
#

yeah sorry I am so lost right now trying to track down what you are doing. Clearly you are creating a Subscription, that creates a SetupIntent for you and you seem to never use or touch it, and then you update the Subscription which causes another SetupIntent

#

this feels quite abnormal and not adapted to how the RBI rules/flow is supposed to work

wild tide
#

The 2/ is correct. We used it and validated it correctly. It is our usual flow to validate 3DS cards

#

I'm looking at the 3/ update

stuck urchin
#

yeah I'm trying to grasp why you do this. Why aren't you using the SetupIntent from Subscription creation? Also why do you keep using trial_end: "now" for some reason?

wild tide
#

Ok, you have a point here. The setup intent that succeeded was the one we triggered when adding the CC. The others I'm not sure why. I'll look into it

#

It is our usual flow for 3DS cards

#

You mean that a subscription update triggers a new setup intent?

#

Or that it may happen?

stuck urchin
#

yeah sorry right now I am saying nothing. I am just trying to understand what you are even trying to model because you code keeps changing a Subscription that is mostly a no op

#

like that first update is keeping a Subscription on a trial, same Price, no change, but passes proration_date for some reason, but on a trial this doesn't really make sense?

#

Overall I am also confused why you get a new SetupIntent on taht last update. You have the card with a Mandate + you also have a real Invoice with a PaymentIntent so that part seems like a bug. Unfortunately you'll have to contact our support team to discuss this https://support.stripe.com/contact

wild tide
#

Thanks for your time. I'll go over the logs, try to fix our setup intent flow and try again

stuck urchin
#

ohhhh wait

#

Simulates a cardholder receiving a pre-debit notification for an off-session payment either canceling or pausing the payment for a mandate of any amount.
this is the description of the card. It's explicitly used to simulate the cardholder not approving/blocking the mandate

wild tide
#

Yes, I expected to receive a notification

stuck urchin
#

what do you mean by "receive a notification"?

wild tide
#

I expect that when the payment is going to be processed, the cardholder (me) should receive a specific notification for the payment. I didn't expect the setup intent to fail using this card

#

If I understood the description correctly

stuck urchin
#

So when you say "I" you mean the end user/cardholder, not you the merchant accepting payments? I'm super confused because you originally asked why the payment failed and you seemed to know why it failed? 😅

#

Have you received such a notification in Test mode before? I would assume none of that happens in Test mode

wild tide
#

What happened:
According to the logs, the payment failed because the bank declined due to the validation failing. It failed due to the previous setup intent that failed

What I expected:
That the payment would not fail on CC validation, but I would receive a notification asking me to validate this payment

#

Now that you mention it.... Never received anything automatically on Test Mode...

stuck urchin
#

yeah we don't really send emails in Test mode in almost all cases

#

and that test card is specifically here to simulate a failure

wild tide
#

How can I test the pre-debit notifications on Test Mode? Can they be seen on the dashboard?

stuck urchin
#

None of this can be seen in the Dashboard or anywhere no

wild tide
#

Wow... if all the problems come because of me not understanding the card's description, or the Test Mode not sending notifications.... I'll be happy 😆

stuck urchin
#

I think that's it. I'd still recommend talking to our support team about those rules. They are unfortunately quite complex and my team doesn't really know much about those

wild tide
#

I will. Thank you for your time 🙇‍♂️