#ryan.badger
subtle bison
long sigil
we'd like to help streamline the UX by passing the data we have to the checkout (name, email, address) but it seems thats no supported?
You can prefill the email field (https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-customer_email) but not name and/or address(es)
from what I can tell, Stripe suggests creating a customer first via the API, is that right?
If you want to prefill other fields, sure: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=checkout#prefill-customer-data
My concern is that we won't know if the customer was already created previously in the connected stripe account, and I worry it will add more latency to the checkout if we make a "Create customer" call first, wait for the response, then create the checkout.
Can you elaborate more on this? Sounds like you have a Connect setup?
runic pecan
yeh we use connect
we're a bit like shopify
we let merchants connect their own stripe account
then we init checkouts on their behalf, so payments are processed in their own account, not ours
long sigil
Ok, so direct charges. Are you implementing Customer objects in your Connect integration? Or is that something the connected account would manage?
runic pecan
i dont think so, but let me double check
no it doesnt look like we use Stripe Customers at all
basically this
long sigil
Then if you want to prefill beyond the email address you're going to need to adopt Customers into your overall integration
runic pecan
ok thanks - so you think we should?
i mean, does stripe suggest using Customers in general?
or is it fine to just use the checkout and expect customers to fill in their own details?
long sigil
i mean, does stripe suggest using Customers in general?
There's no expectation, they're only required for recurring payments. But I'd probably say they're recommended overall
runic pecan
ok thanks!
sorry me again
im a vit confused by your docs here? https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-shipping
because it says you can send payment_intent_data.shipping?
long sigil
Yes but I believe that doesn't prefill the fields in the UI
long sigil
i.e. the user can't configure them on the payment page
Well it's if you collect shipping details elsewhere
runic pecan
its the billing address we care about, because currently customers enter it all in our cart, then they have to enter some of it again in stripe
and we're getting complaints
it'd be great if we could find a way to streamline it
(if that means using the Customer object, i think thats fine, but i just want to be sure we're not missing something else)
long sigil
Yep billing address can only be prefilled via a Customer object
runic pecan
i ssee
so this:
"In the Stripe Create Checkout Session API, the payment_intent_data parameter is used to provide specific details about the Payment Intent associated with the Checkout Session. It allows you to customize and pre-fill certain fields related to the shipping address for the customer."
is only referring to shipping address?
but we dotn show shipping address in stripe as its no needed there (we handle all the shipping stuff our side)
long sigil
Correct