leo_error | Stripe Developers | Page 1

fallow sparrowBOT Jan 10, 2025, 10:12 AM

#

👋 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/1327218454297837709

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

keval_best-practices, 22 hours ago, 9 messages

#

tulip flower Jan 10, 2025, 10:13 AM

#

hi! if you want to simulate cards that can be charged for recurring payments without 3D Secure being required, use the test card that simulates that exemption (3155) : https://docs.stripe.com/testing#authentication-and-setup

robust sable Jan 10, 2025, 10:22 AM

#

@tulip flower Thanks for the answer .

But In my case Test card are not working in live environment.

tulip flower Jan 10, 2025, 10:23 AM

#

correct, they do not

robust sable Jan 10, 2025, 10:24 AM

#

Yes so can you share any another way so it will very helpful to me.

tulip flower Jan 10, 2025, 10:24 AM

#

not sure what you're looking for exactly

fallow sparrowBOT Jan 10, 2025, 10:25 AM

#

tulip flower Jan 10, 2025, 10:25 AM

#

if this is in livemode the answer is

the recurring payment might require 3D Secure, it's up to the issuing bank as they choose whether or not to require it or to grant exemptions that we request. It's a normal outcome and something you have to have a means to handle in your integration.
if you think the rate of this happening is more than you expect, you can open a support ticket at https://support.stripe.com/?contact=true to look into multiple examples

if you have something like the pi_xxx PaymentIntent ID of the example you're describing in your initial post, I can have a quick look at that.

robust sable Jan 10, 2025, 10:31 AM

#

@tulip flower Here is details what exactly i needed .

I want to save 3D secured card for future use.
Steps as implemented right now:

create token by card elements in frontend
create source by using card token and attach that card id with stripe customer.
We have flow like this first make a payment then after call saved card api
first time payment was successfully by 3D approved.
Then after i attach that card to stripe customer.
Then by use of this card id if i make payment then it will give authentication error.

So how can i store 3D card for future use with out presence of a customer?

tranquil frigate Jan 10, 2025, 10:32 AM

#

hi! I'm taking over this thread.

#

first, you should be using Token and Source. this is a very old integration that we no longer recommend. Instead use PaymentIntent and PaymentMethod. you can learn more about this here: https://docs.stripe.com/payments/payment-methods/transitioning

#

second, it's up to the bank to decide if 3DS is request or not. so your integration needs to handle the case where 3DS is requested.

#

so if you try to make a payment while the customer is off session, and 3DS is requested, you have to tell teh customer to come back to your website to go though the 3DS flow.

#leo_error