#chirp

1 messages · Page 1 of 1 (latest)

worn geodeBOT
rocky mesa
lilac tree
#

yeah I went through that. i dont get how to ...

#

wait what?

#

I went through the steps of the first doc . didnt show me what I needed.

#

ahhh thats what i was missing.

#

so adding something like

test_clock: '{{CLOCK_ID}}',

to the creation of the checkout link will give me what I need right?

#

oh wait thats about creating a customer.

#

I have to create a customer to use checkout?

frail snow
#

It's not a requirement to create a Customer before using Checkout in general, but it is a requirement if you want to use Test Clocks

lilac tree
#

i see.

#

does that mean I also have to create subscriptions the same way? In the context of a test clock?

frail snow
#

and no, you shouldn't have to pass the test clock anywhere else - it's just something you set on the customer

#

but when you create a subscription you pass in a customer, and that's how we konw which test clock to use

lilac tree
#

I see. Ok. So i must create the customer first and associate the test clock, the when creating the checkout link associate the customer id.

frail snow
#

yup!

lilac tree
#

Ok. Thanks a lot for clarifying. I was thinking I was going crazy trying to figure out how to link the two in the web portal.

#

Begs the question - why not allow the association of the test clock with an existing user in the portal while in test mode?

frail snow
#

It's just not something we support yet - right now, you can only add a test clock to a customer upon creation. You can't add one after the fact (it's something that's on our radar as a possible improvement, but hasn't been fixed yet)

lilac tree
#

Got it. Ok. Thanks Karbi. Have a good weekend.

frail snow
#

👍 you too! glad we could help