stavros-malakoudis_api | Stripe Developers | Page 1

fathom gardenBOT Dec 16, 2025, 11:22 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/1450448026098339912

📝 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.

stavros-malakoudis_api, 8 minutes ago, 39 messages

#

lunar thorn Dec 16, 2025, 11:24 AM

#

Hey, I tried to answer to the previous thread but it is locked. So basically I was trying to understand the difference between the off_session flag and the payment_method_options->card->setup_future_usage flag on the payment intent. Previously we relied on the react component and the setup_future_usage flag, but now its removed. We need the user to verify their card the moment the payment method is created, in order to use the same payment method in the future

#

without requiring the user to re-verify the card

weary wagon Dec 16, 2025, 11:25 AM

#

Previously we relied on the react component and the setup_future_usage flag, but now its removed
What's removed? Can you share a link to what exactly you're referencing?

So basically I was trying to understand the difference between the off_session flag and the payment_method_options->card->setup_future_usage flag on the payment intent
setup_future_usage is the parameter to use when you want to save the card to be used again. off_session is the parameter you use to denote that the customer is not present in your checkout flow. They're somewhat related and are mutually exclusive

#

We need the user to verify their card the moment the payment method is created, in order to use the same payment method in the future
Sounds like you're describing setup_future_usage then

lunar thorn Dec 16, 2025, 11:26 AM

#

What's removed? Can you share a link to what exactly you're referencing?
the flag setup_future_usage from the createConfirmationToken call on the js component https://docs.stripe.com/js/confirmation_tokens/create_confirmation_token

Stripe JS Reference

weary wagon Dec 16, 2025, 11:28 AM

#

I don't think that was ever supported? At least not publicly. You'd use this instead: https://docs.stripe.com/js/elements_object/create_without_intent#stripe_elements_no_intent-options-setupFutureUsage

Stripe JS Reference

lunar thorn Dec 16, 2025, 11:28 AM

#

What we used to do is always set the off_session flag on the confirmation token and this was enough to satisfy the 3ds rules

      elements,
      setup_future_usage: "off_session",...

weary wagon Dec 16, 2025, 11:29 AM

#

Well that wouldn't 'satisfy 3DS', in fact using s_f_u would likely trigger a 3DS challenge flow

lunar thorn Dec 16, 2025, 11:29 AM

#

by 'satisfy' I mean we to trigger the 3ds authentication component

#

Okay so since the s_f_u is removed, how can we achieve the same thing?

weary wagon Dec 16, 2025, 11:33 AM

#

Why are you using createConfirmationToken? Is there an initial payment here or is this to save cards for future usage only?

lunar thorn Dec 16, 2025, 11:33 AM

#

We are saving cards for future usage only

#

We don't support one-time payments without saving the card to the system

weary wagon Dec 16, 2025, 11:35 AM

#

Then you should be using Setup Intents, not Confirmation Tokens: https://docs.stripe.com/payments/save-and-reuse?payment-ui=elements

Save a customer's payment method without making a payment

Learn how to save a payment method and charge it later.

#

Confirmation Tokens don't hit the card networks, they're just tokenising data from the Element. So they won't trigger a 3DS flow until they're used in an actual payment

#

Setup Intents do hit the card networks, so the bank is able to request 3DS/authentication

lunar thorn Dec 16, 2025, 11:37 AM

#

We are using a SetupIntent after creatingthe confirmation token from the js component

weary wagon Dec 16, 2025, 11:38 AM

#

The Confirmation Token step is redundant, IMO. I don't understand why you need that

#

What issues are you having overall with Setup Intents? Is there an example one that doesn't trigger 3DS?

lunar thorn Dec 16, 2025, 11:40 AM

#

The issue is that we are not really sure how to handle the removal of the setup_future_usage field from the createConfirmationToken js function. Using this token, 3DS was being triggered as we want it to.

weary wagon Dec 16, 2025, 11:41 AM

#

As I said, the Confirmation Token is redundant here. Why do you need it? Are you sending it to the backend for any reason?

#

Share a seti_xxx ID please

lunar thorn Dec 16, 2025, 11:42 AM

#

Are you sending it to the backend for any reason?
yes, to create the SetupIntent

weary wagon Dec 16, 2025, 11:43 AM

#

weary wagon Then you should be using Setup Intents, not Confirmation Tokens: https://docs.st...

Seems redundant to me, you should just follow the guide I linked

#

In any case, please share a seti_xxx ID that didn't trigger 3DS

lunar thorn Dec 16, 2025, 11:43 AM

#

seti_1SdWxCHxNT300n1JuJjV06WA

#

Oh, you mean one that **didn't ** trigger it

weary wagon Dec 16, 2025, 11:43 AM

#

Yes, a one that is problematic and you want to solve

lunar thorn Dec 16, 2025, 11:44 AM

#

Right. I 'll get back

#stavros-malakoudis_api