#stenml
1 messages · Page 1 of 1 (latest)
hi! I don't think that can be directly tested (moving automatically to restricted after some time passes), the only option is to manually force the account to have charges/payouts disabled using the test cards for that; or mocking the object in tests.
So if currently_due requirements are due in say 14 days, theres no way for me to force the requirements to be past_due, and once they are I should just use test cards like these to disable charges and payouts?
the idea as far as I know is you can just use the test card at any time to manually get the account into the state of being blocked
I need a flow in which account goes from restricted soon to restricted (disabled) due to requirements being past due, it seems like the test clocks would do be the perfect thing to use for this, but can they also be used for accounts?
no; test clocks only operate on Subscription-related objects and not globally for other objects in the API or Accounts.
I see, thank you