#monove
1 messages ยท Page 1 of 1 (latest)
why generic_decline instead of authentication_required
Hello ๐
Can you share the request ID?
Most likely because the decline is coming from radar rules and not from the issuer directly.
Hmm not finding much on why this was a decline
Ah I think its a bug with the test card
ok
when the server-cide response for creating the paymentintent is authentication_required we want to then let our front-end prompt for 3DS auth but in the response payload we don't see any next steps
req_zXFl0WaAgGQ02B
Have you tried using other test cards listed here
https://stripe.com/docs/testing#authentication-and-setup
https://stripe.com/docs/testing#three-ds-cards
yes, this is the first card:
3DS2 Required 4000000000003220
are we supposed to pass request_three_d_secure?
we dont want to trigger it unless the card requires it
Hi ๐
I"m stepping in as @honest sun needs to go.
What is the exact flow you are looking to test?
we want to attempt to create a paymentintent server side. if it fails due to 3ds we need a plan B for server and client.
Okay so do you want to test the scenario where 3DS is required?
correct
we've got the 3ds setupintent flow downpat
now we're up to the paymentintent flow
Have you tried using the card 4000002760003184?
we have a 2-step process where cards are stored on our platform then used for orders
will try now
That should always require 3DS authentication so should provide reliable test
req_vDSO8KIRhxUbak
still unsure about the flow. what do we do after we receive an error like that
or do we start the process client-side
You are passing confirm: true which means it automatically attempts to confirm the payment intent
i see
Also you are passing off-session: true which means the customer is not able to authenticate the purchase
So it fails, rather than asking you to do something you just told us you can't (because the customer is not on-session)
thanks
Can you try a request with confirm: false and off-session: false?
perfect, we got baack next_action object. thanks