bensif88

[iron blade]

Hi
Currently there is no clear mention for using Test Clock with Connect

checking...

[fickle summit]

It does nto appear it is supported with test clocks. What I am unclwear on is how to actually test our integration to connect for subscriptions without this functionality.

We can test one off payments, that isnt an issue. But we have various hooks and functions that rely on the subscripiton cycle that would need ot be tested before put live

[iron blade]

You are using Direct Charge or Destination Charges ?

[fickle summit]

direct and subscriptions only

I think our best bet is to set up a sub on a daily cycle and then manually resend the hooks to do our testing

[iron blade]

direct and subscriptions only
If you are using Direct Charges, then you can do the tests on the Connect Account Side using Test clocks

[queen rock]

👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!

[fickle summit]

I dont believe you can use test clocks to test connected account subscriptions though

which is what we need to simulate

[queen rock]

I think you can but you need to create the test clock where you create the customer

so depending on the type of charge

that's what my colleague was trying to explain

[fickle summit]

It isnt immediately apaprent to me how you would do this. When you create aa test clock, you can create a customer but not specifiy where the customer sits

right i see how you can do it now, you need ot log into stripe as the connect account, not as the platform

(dashboard)

[queen rock]

if you're using the dashboard yes that's correct you need to log into the Connect Account

but if you're using the API you would just need to pass in the Stripe-Account Header