#daken-3ds
1 messages · Page 1 of 1 (latest)
@deep badge hi! at a certain level that is sometimes how 3D Secure works yep — we attempt to charge the card, the bank declines it wit a specific decline reason (authentication_required ) which means, "try again after doing 3D Secure", and then we do 3DS and re-attempt the charge.
having said that I thought that we hide that initial attempt and don't really show it as a full charge in the dashboard. So i'm a little curious to see the exact page you're looking at
I think that's the "risk insights" section? yeah, maybe that exposes those initial attempt charges.
ah yeah. If you have an ID like the customer ID cus_xxx I can take a quick look
cool thanks
so yes this is what I described — the failed charges there are just part of the process (attempt charge -> fail -> do 3DS -> re-attempt -> success)
we usually hide those initial attempts but that section of the dashboard does show them
either way this all looks normal to me!
Thanks a lot for your help