#Virtus-checkout

1 messages · Page 1 of 1 (latest)

tiny aspen
#

Can you clarify - are you trying to take your own customer ID (not one that we generate) and set that as customer in the Checkout session?

mossy shuttle
#

Yes, I am

tiny aspen
#

That won't work - customer for the Checkout Session needs to be one that is generated by us (Stripe). When we say that it's expandable that means that we don't include the full Customer object in the response by default, but you can expand it to get the full object (see our docs for details https://stripe.com/docs/expand).

#

If you want to tie your own unique customer ID to a Checkout Session I'd suggest including that information in the metadata of the Session

mossy shuttle
#

Okay. Will that metadata be stored with the customer, or would I have to rely on storing that customer ID on my end?

#

Stored as in for good

tiny aspen
#

If you want it to be tied to a customer, then you can set the metadata on the Customer object itself and not on the Checkout Session. That will store it on the Customer object until you go and remove it