Date by which the fields in currently_due must be collected to keep the capability
enabled for the account. These fields may disable the capability sooner if the next threshold
is reached before they are collected.
Fields that need to be collected to keep the capability enabled. If not collected by
current_deadline, these fields appear in past_due as well, and the capability is
disabled.
If the capability is disabled, this string describes why. Learn more about handling
verification issues. Can be requirements.fields_needed,
pending.onboarding, pending.review, rejected.other, platform_paused,
rejected.inactivty, or rejected.unsupported_business.
rejected.unsupported_business means that the account's business is not supported
by the capability. For example, payment methods may restrict the businesses they support in
their terms of service, such as in Afterpay Clearpay's
terms of service.
rejected.inactivity means that the capability has been paused for inactivity. This
disabled reason currently only applies to the Issuing capability. See Issuing:
Managing Inactive Connects for more details.
Fields that need to be collected assuming all volume thresholds are reached. As they become
required, they appear in currently_due as well, and current_deadline becomes
set.
Fields that might become required depending on the results of verification or review. It's an
empty array unless an asynchronous verification is pending. If verification fails, these
fields move to eventually_due, currently_due, or past_due. Fields
might appear in eventually_due, currently_due, or past_due and in
pending_verification if verification fails but another verification is still pending.
Date by which the fields in currently_due must be collected to keep the capability
enabled for the account. These fields may disable the capability sooner if the next threshold
is reached before they are collected.
Fields that need to be collected to keep the capability enabled. If not collected by
current_deadline, these fields appear in past_due as well, and the capability is
disabled.
If the capability is disabled, this string describes why. Learn more about handling
verification issues. Can be requirements.fields_needed,
pending.onboarding, pending.review, rejected.other, platform_paused,
rejected.inactivty, or rejected.unsupported_business.
rejected.unsupported_business means that the account's business is not supported
by the capability. For example, payment methods may restrict the businesses they support in
their terms of service, such as in Afterpay Clearpay's
terms of service.
rejected.inactivity means that the capability has been paused for inactivity. This
disabled reason currently only applies to the Issuing capability. See Issuing:
Managing Inactive Connects for more details.
Fields that need to be collected assuming all volume thresholds are reached. As they become
required, they appear in currently_due as well, and current_deadline becomes
set.
Fields that might become required depending on the results of verification or review. It's an
empty array unless an asynchronous verification is pending. If verification fails, these
fields move to eventually_due, currently_due, or past_due. Fields
might appear in eventually_due, currently_due, or past_due and in
pending_verification if verification fails but another verification is still pending.