#Chung-Yi
1 messages · Page 1 of 1 (latest)
You'll want to look at the requirements hash to check for currently_due and eventually_due requirements. You can always cross-reference the contents of that hash with this resource to get an idea of what needs to be provided: https://stripe.com/docs/connect/required-verification-information
Thank you! We're still on an old API version, so I guess we'll look for verfication instead. (https://stripe.com/docs/connect/required-updates/accounts-arguments). Does the verification[due_by]( or requirements[current_deadline]) map to the deadline in the "restricted soon" tab in the dashboard UI?
I believe it maps to the currently_due deadline, if I recall correctly
currently_due is a new field under requirements that's not available in our API version it seems. I guess we'll base on what we have in verification.
A general question: to surface these account issues via webhook events, we'll have to compare with previous_attributes in the event to tell the exact changes right?
Is there a simpler way we, as the platform, can get notified when our connected account is about to be restricted? Or relying on the webhook would be the recommended way.
A general question: to surface these account issues via webhook events, we'll have to compare with previous_attributes in the event to tell the exact changes right?
On the older API version, I believe this was the case yes.
Is there a simpler way we, as the platform, can get notified when our connected account is about to be restricted? Or relying on the webhook would be the recommended way.
Webhooks are the only reliable way to do this