AlexElba

[solar kelp]

not sure what you mean by a "stripe client id"?

[versed mulch]

I mean customer id

[solar kelp]

then no. The only thing that happens with client_reference_id is that we send it back to you in the webhook when the CheckoutSession completes, so you can recognise it at that point.

[versed mulch]

if I pass customer id for customer does not exists will it create customer with that id? customer string
expandable

The ID of the customer for this Session. For Checkout Sessions in payment or subscription mode, Checkout will create a new customer object based on information provided during the payment flow unless an existing customer was provided when the Session was created.

[solar kelp]

no

the ID of a customer should not be considered something you can directly control. It's just an ID cus_xxx and it's created randomly when a Customer object is created.

[versed mulch]

is there way to pass meta data CheckoutSession to new created customer?

[solar kelp]

not automatically, but for example you could listen to the checkout.session.created webhook event and then call the Update Customer API on the Customer that was used in the Session and set any values you want on it.

maybe take a step back and explain the overall problem you're trying to solve in general?

[versed mulch]

some times webhooks are called after /success page redirect was done. I want to show client amount they paid on thank you page