Sometimes after providing all required information, an account might need to provide additional details or documents. These new requirements appear in the requirements.eventually_due array or in requirements.currently_due. Set up your integration to listen for changes to account requirements by using webhooks.
If the capability is already
active and the account doesn’t satisfy new requirements due on that capability before the current deadline, the capability becomes
inactive until the requirements are satisfied.
If an account’s information can’t be verified, Stripe might require a document to verify the identity of a person (for example, a Passport) or to verify information about the legal entity (for example, a letter from the tax authority). To satisfy document requirements, platforms can send the user to Connect Onboarding (where they’ll be prompted to upload the document), or collect the document from the account in another interface and upload it through the API.
Failure to verify identity within 29 days of the initial application
After an account submits all the required information for Issuing and accepts the Issuing terms of service, Stripe considers the application complete. If we can’t verify an account’s information, the capability remains
inactive until the account provides additional information or uploads a document.
If the account remains
inactive 29 days after completing the application, you must send an email notice to the account informing them that we couldn’t verify their identity (see the template).
Stripe monitors for completed applications with unverified identities, and takes the following action after 29 days in live mode and after 1 hour in test mode:
You can submit a new application at any time by updating the business information and recording a new acceptance of Issuing’s terms.
Stripe recommends that you present the terms of service as the last step of onboarding, which allows you to track the timing of application completion by referring to the term’s acceptance date.
Terms of service violations
If Stripe identifies a connect account that has violated Stripe’s terms of service, Stripe sets the Issuing capability on the account to
inactive, deactivates any cards, and notifies the account (see the email template). This might happen when an account’s cards are used in relation to prohibited or restricted businesses, such as illegal activities, gambling, firearms, adult content, or cryptocurrencies, or in relation to prohibited activities for Issuing , such as consumer spending, primarily international use, lending, or other abusive or noncompliant use.
Accounts inactive for more than 395 days
Stripe disables issuing on accounts that haven’t completed any card transactions in the past 13 months (395 days). For accounts with additional capabilities, Stripe only disables Issuing if there have also been no payments or Treasury transactions in the prior 395 days, and the Treasury balance is 9.99 USD or less. When Issuing is disabled for inactivity, the Connect account’s card_issuing capability status changes to
inactive and the capability requirements show a disabled_reason of
rejected.inactivity. Learn more about managing inactive accounts with Issuing.