#yash_error
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1338470862898331719
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
I'm not sure I understand the use case here.
Could you please clarify?
Stripe card payments handle natively 3dS and no additional action is needed
some cards from japan not supporting 3ds and some are supporting how can i handle that
You don't need to do any additional action. That's handled natively by Stripe
Are you willing to use Stripe Payment Element ?
i am not aware of that
What part exacty ?
Stripe Payment Element
Have you had a chance to test our Quickstart?
https://docs.stripe.com/payments/quickstart
You can then do tests using Card with 3ds and other without
For example:
- 4242424242424242 without 3DS
- 4000002500003155 with 3DS
https://docs.stripe.com/testing
I Tested on production live cards
from stripe showing error card does not support 3ds
pi_3QmefYEmTmhFycAF13VvSyBS
It seems like this decline was issued by the bank issuer.
Stripe supports 3ds
Is this a test you made by your own card on your Stripe own account ?
yeah we were testing card but execting subscription are going well with same card but while doing new payment we are facing problem
You shouldn't be testing on your live account, because it's will increase risk score and it would be suspect of blocking..
You need to use test mode for testing and not live mode.
ok but can you tell me next step to handle this
I don't remember right now but somewhere was showing card does not support 3ds
I don't see that on the payment you shared. Authentication just failed โ if/when that happens re-confirm the intent
that issue came from stripe sdk
There's no issue here at all โ the bank notificed us that payment authentication failed for whatever reason, so we convey that via the SDK/API
Ultimately the bank determines whether or not to approve the payment, not us. As noted you shouldn't be testing in live mode as this can impact your merchant standing
As I said, this can aand will happen in your integration. You need to build your integration to handle these declines/failures and prompt your customer to retry the payment
Not sure how that's relevant at all