nickdnk-payments | Stripe Developers | Page 1

sly flax Mar 9, 2022, 1:16 PM

#

cedar knot Mar 9, 2022, 1:17 PM

#

The user ended in our "payment succeeded" state which should be absolutely impossible when the payment has not completed

#

The only explanation we have is that the JS modal does not handle the SCA attempt properly and somehow calls its successblock

#

This is a foreign card and a very high amont so maybe that could affect it

sly flax Mar 9, 2022, 1:19 PM

#

hmm, not sure I follow. That payment went through 3D Secure.

cedar knot Mar 9, 2022, 1:19 PM

#

okay it just updated

#

That's super weird

#

new card

#

Amex instead of visa

#

We still quite perplexed though about the user ended where he ended with the previous attempt

#

If you look at the logs for evt_3KbOZzIFDslEWhBA0kLfZeVX is where it went wrong - but no idea how

#

this response was sent to our backend and in turn to the frontend which somehow considered it a success. Never seen that before or since.

#

Can you perhaps dig internally on the request and see if it somehow sticks out?

sly flax Mar 9, 2022, 1:28 PM

#

All I see is :

you create the PaymentIntent
you confirm it , 3DSv2 is required and the PI goes to next_action status
it seems like that action was never completed
an hour later you updated the PI with a payment method and confirm again
this time the customer completes 3D Secure

cedar knot Mar 9, 2022, 1:29 PM

#

Yes, I know. But " it seems like that action was never completed " -> Success in the JS Stripe SDK

#

which should be impossible

#

so that's why I was wondering if maybe there was something special about this particular request

sly flax Mar 9, 2022, 1:29 PM

#

hard to say, we don't have logs or observability there, so there's nothing I can see

cedar knot Mar 9, 2022, 1:29 PM

#

like some edge-case being incorrectly handled

#

alright

sly flax Mar 9, 2022, 1:30 PM

#

I wouldn't imagine the Promise from confirmCardPayment would resolve , we'd need specific logs from your side as you console.log the flow and the values the promise resolves to unfortunately

cedar knot Mar 9, 2022, 1:31 PM

#

Yeah but it did resolve without an error, somehow. That's the weird thing. Looking at our code, that's the only way it could end up where it ended. That's why I'm so confused.

#

But alright, we'll just have to monitor for it

#

see if we can figure out why

#

If it happens again

#

Thanks though

#

we use handleCardAction though because of manual confirmation

#

but it normally works fine

#

Customer says:
"It seem to have gone through (he sent screenshot of success), but when I went to finalize on Google Pay, it changed the card details to another one I had stored"

Maybe it's something with Google Pay not doing what it's supposed to.

sly flax Mar 9, 2022, 1:41 PM

#

possibly, I don't really know and this is not a great venue to talk about specific details of a livemode payment

#nickdnk-payments