happycappie

[patent gull]

I believe the current way to do this is to add in the client-reference-id when embedding the Pricing Table, which allows you to set client_reference_id on the Checkout Session object. That would then show up in the checkout.session.completed event

[opal grotto]

is there documentation for how to add the client-reference-id when embedding?

and does that mean we can also set other Checkout params (like customer_creation ) when embedding?

[patent gull]

Ah! Apologies, I meant to also give you the docs I was looking at. Here you go: https://stripe.com/docs/payments/checkout/pricing-table#track-subscriptions

and does that mean we can also set other Checkout params (like customer_creation ) when embedding?
No. You can only modify a few things like client_reference_id and the Customer email (see here: https://stripe.com/docs/payments/checkout/pricing-table#customer-email)

[opal grotto]

do you have an explicit list of which attributes can be set when embedding?

[patent gull]

No, but they are all included in the above docs, so I'd start by reviewing there

[opal grotto]

I found one of those attributes in the doc, but you said that customer_creation is not supported. Are you recommending we just do trial and error when we think we want to use an attribute?

[patent gull]

Not necessarily. This a new product and has very few customizable attributes (I think there are literally only the 2 I mentioned above) so I would expect that you could get the info you needed from the docs first, and then devise a solution to run by me here (assuming you had follow-up questions