standup75 | Stripe Developers | Page 1

warm violetBOT Jan 30, 2023, 3:43 AM

#

brave herald Jan 30, 2023, 3:44 AM

#

Hi there, it's really up to you, you can create ad-hoc price through price_data or use a pre-existing price id

junior thistle Jan 30, 2023, 3:44 AM

#

ok, just wanted to check.

brave herald Jan 30, 2023, 3:45 AM

#

Note that the ad-hoc price/product created during checkout session creation will be archived automatically.

junior thistle Jan 30, 2023, 3:45 AM

#

ok, good, I guess that's what I wanted to hear, they won't pollute the account with tons of duplicate data

#

Sorry, since it was another q, thought I would create another thread... no problem... The other question ==> we want to let Stripe save the payment method for future payments, there seem to be confusingly 2 ways to specify that with the create session command. mode: "setup" and/or payment_intent_data.setup_future_usage, what's the difference?

brave herald Jan 30, 2023, 3:50 AM

#

OK. I think you are using Checkout Session API.
The payment_intent_data.setup_future_usage is a param for payment mode checkout session, which allows you to set up the payment method that was used in the payment for future usage

#

When using setup mode checkout session, you don't need to (or even can't) specify a payment_intent_data.setup_future_usage

junior thistle Jan 30, 2023, 3:53 AM

#

set up the payment method that was used in the payment for future usage. 🤔 Sorry, not super clear to me. It's in the case the buyer already left his payment info and they're available for Stripe to reuse it?

#

I guess instead of hinting at the solution, I should just ask what I want to do. I want to make sure that if a buyer buys for the second time the info he gave the first time are saved. Is there any param in the create Checkout Session API that need to be set for this or is it automatically saved for future usage?

brave herald Jan 30, 2023, 3:56 AM

#

I see. Checkout supports it out of the box. As long as you specify the same customerID (https://stripe.com/docs/api/checkout/sessions/create?lang=java#create_checkout_session-customer).

In payment mode, the customer’s most recent card payment method will be used to prefill the email, name, card details, and billing address on the Checkout page.

junior thistle Jan 30, 2023, 3:57 AM

#

Alright, thank you, this has been SUPER helpful

junior thistle Jan 30, 2023, 4:15 AM

#

Sorry, something else I am seeing that's not clear to me, I already use connect with Element and paymentIntent, and I was referring to the connect account like this when creating the payment intent: transfer_data: { destination: product.user.stripeAccountId, },

#

I see that the Create Checkout Session API has a on_behalf_of parameter. Should I just use on_behalf_of and nothing in transfer_data? Will the amount still appear correctly on the connect account?

brittle river Jan 30, 2023, 4:17 AM

#

👋 taking over here

junior thistle Jan 30, 2023, 4:18 AM

#

Hi! Thanks for taking over

brittle river Jan 30, 2023, 4:18 AM

#

No they are different parameters. It's explained in https://stripe.com/docs/connect/destination-charges#settlement-merchant

Creating destination charges on your platform

With Connect, you can create charges on your platform account, take fees, and then transfer remaining funds to your connected accounts.

#

transfer_data[destination] specifies the target account you want to move the fund to, and on_behalf_of does an extra step to set it as MOR (merchant of record) appearing in customer's bank record etc

#standup75