#rosie-3ds
1 messages · Page 1 of 1 (latest)
It sounds like the Payment you created was timeout-ed. How did you create the Payment?
we use payment intent. it fails during the 3d secure authentication simulation process immediately after "payment_intent.requires_action". this part of the flow is supposed to be after clicking on the "authorization success" button to simulate successful authorization but it just automatically cancels the transaction.
Could you paste me a sample PaymentIntent Id? pi_xxx
thanks orakaro. this is one: pi_3KgmtaBSRoY85hcC0TBAptai
The PI looks good to me, it's just not authorized yet. Can you screenshot or screenrecord the error on your authentication screen?
It works fine to me, same test card
sure. ill send a loom video in a bit.
in this case, it proceeded to the "source is canceled" screen. sometimes it goes to the screen where you choose success or failure.
pi_3Kh76h2UL0kEbo9w1DS6kaAq
it only affects transactions that go through our connect accounts
Let me take a closer look
Check this request req_SYGVNzcgLSrP9V
Something in your system is triggering this cancel request
Stripe/v1 PhpBindings/7.112.0
hi orakaro. thats part of our flow wherin when a payment fails, it deletes the subscription. its in the later part of the flow.
the issue is right before that happens.
acct_1Kh31x2UL0kEbo9w , cus_LNssCEUZ5RIs2k is the user in question
and this is the root cause which ends up with the cancel request because the authentication fails: evt_1Kh76i2UL0kEbo9w2UcIlXvB
Hmm I see. Any chance that Cancel API could fire unexpectedly? If you comment that logic out, can you reproduce the issue?
sure. ill try and report back.
👋 I am stepping down for the day. If you come back feel free to open another thread. Good luck!