kurio

[velvet glen]

Hi there! This isn't possible with SetupIntents since the "intent" in this case is to reflect the fact that this customer is giving you permission to charge them at some point in the future, but not for a specific amount only

If you need to charge a customer at this point in time for a specific amount and get permission from them for charges at a later date, you'll want to use PaymentIntents and setup_future_usage

https://stripe.com/docs/payments/save-during-payment

[hollow sparrow]

thanks roadrunnder for your answer...
setup_future_usage unfortunately doesn't work with 3Ds... we are unable to charge the current card on file if we use PaymentIntent + setup_future_usage. Only SetupIntent works...

any idea what we might have been doing incorrectly....?

[velvet glen]

hm, PaymentIntents can be used with 3DS so that seems odd

[hollow sparrow]

it can be used but it can't be used for future off session payment is what i've been seeing

i'll do another test

[velvet glen]

got it okay

if you try to charge an existing saved PaymentMethod and 3ds is required, the customer will have to come back on session

[hollow sparrow]

yeah... but the main point is to avoid having them back on session

we are able to that with SetupIntent, but the problem is that it is showing $0 amount

which causes confusion to the customer as it is not $0 but the whole amount they've been charged for

actually...

i just retested

it went thru

💯

[velvet glen]

let's take a step back. when collecting a customer's card details for the first time, you should use PaymentIntent + setup_future_usage if you intend to charge them at that specific point in time and also store their payment details for future off-session payments

[hollow sparrow]

not sure why it didn't work before...

but thank you so much!!

[velvet glen]

if you're collecting a customer's card details but don't intend to charge them at that point as well, you should use SetupIntents

[hollow sparrow]

thanks roadrunner, I got it sorted out 🙂