#meet_docs

1 messages · Page 1 of 1 (latest)

faint juniperBOT
#

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

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

solar ingotBOT
#

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.

solar ingotBOT
hazy delta
#

Hi 👋 you don't want to use that combination of parameters, as explained in the error. You should omit the off_session parameter and just use setup_future_usage: 'off_session' if you want to use the intent to set up a Payment Method for future usage.

#

Setting up a Payment Method for future usage typically requires customer interaction, which can't be completed if the customer isn't on-session.

narrow gulch
#

so to sum this up, setup_future_usage is for saving the payment details for future and off_session (when set to True) is for identifying if the customer is on session or not !

#

so let's say the customer is on session, then how can I proceed with both the params at the same time (when I want to save the details for future as well)

hazy delta
#

Exactly. If the Customer is on-session, you can set off_session to false, or omit it as it defaults to false.

narrow gulch
#

in which scenarios, off_session value could/ should be set to true ?

hazy delta
#

When the Customer isn't on session. So typically it's used after you've collected and saved payment method details for them and are then processing a payment intent for them while they aren't on your site/in your app.

narrow gulch
#

in that scenario, to save the payment method details (as you have mentioned) I will need setup_future_usage: off_session right?
but to show that they are not in my site/ app, will I not need to include off_session: true ?

hazy delta
#

Those are two distinct steps.

#

You can't collect payment method details from a customer if they aren't on your site/in your app.

#

So it doesn't make sense to have a scenario where you would use off_session: true and setup_future_usage: 'off_session'.

#

First payment you process, you use setup_future_usage. In there you either omit off_session or use off_session: false. That results in a Payment Method being set up for future usage.

Then when you want to charge the customer later, you can create a Payment Intent with off_session: true. For this one you won't use setup_future_usage because the Payment Method being used was already set up.

narrow gulch
#

i understand the difference now. to conclude,
I do not have the customer in my site when the payment is being processed.
I will need setup_future_usage: off_session when doing the first time sale. and when I need to charge them later, I will be replacing setup_future_usage: off_session with off_session: true !!!

hazy delta
narrow gulch
#

thanks for clarification