#db1900_api
frigid lanceBOT
đ 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/1229503835832188981
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
oak oasisBOT
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.
- db1900_payment-element-testing, 1 hour ago, 10 messages
quaint mantle
As far as I am aware, off_session is only a parameter when creating or confirming the intent. It tells Stripe to tell the bank that the user is not around for that specific confirmation attempt but it is not a property on the PaymentIntent or the related charge object it looks like.
So if you want to check in future, I think you would want to either set metadata on the intent, or make your own record on your side that you tried to confirm the intent off session on your side
quaint mantle
The Stripe.js modes entirely refer to whether you are confirming a PaymentIntent or SetupIntent (though I do understand the confusion). setup_future_usage is specific to PaymentIntents, it is how you take a payment and save a card for future usage at the same time.
formal latch
hmm
it kind of sounds like, if our intention is to capture a payment when a customer is not in the flow, we could only use "setup_future_usage" and not "off_session" ?
it also feels like we could do this when we create the SetupIntent (use off_session )?
quaint mantle
That depends on how you want your flow to work here. Can you tell me what you want this process to look like? When the customer saves their payment method with you, do you want to capture funds then, or is that not until later when they are away?
formal latch
hmm
its the 2nd one - when the customer saves their payment method we will charge later when theyre away
quaint mantle
Gotcha, so you will want to use a SetupIntent and not specify off_session when creating that intent. Later when you are charging the saved payment method you will want to create a PaymentIntent and pass off_session: true when confirming it.
The off_session parameter when confirming intents is saying whether the customer is the one initiating the payment right now. Because the user is present when filling out their card details for the SetupIntent, you won't want to pass off_session then.