Inactive connected accounts offboarding
Learn how connected accounts can be affected due to inactivity.
Manage inactive connected accounts
Inactive issuing accounts can pose a risk to platforms due to an increased chance for lost or compromised cards, which could result in transaction fraud. To mitigate this risk, Stripe disables the issuing capability on inactive connect accounts globally. Stripe sends notices to connected accounts that have lost access to Issuing due to inactivity. Preview the template along with customization options.
Remarque
If you previously received communication from Stripe about deactivating access to Issuing for connected accounts without Issuing activity, review this guide to understand additional changes coming with this update.
Inactivity criteria
Stripe disables Issuing on accounts that haven’t authorized 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 Financial Accounts for platforms transactions in the prior 395 days, and the Treasury balance is $9.99 or less.
Identify disabled accounts
You can listen to a webhook event that we send 30 days (US) or 60 days (UK and Europe) before a connected account loses Issuing access because of inactivity. Listen to the capability. or account. webhooks with the card_ parameter in the requirements hash. Use this event to display or send notifications to connected accounts about the impending inactivity closure. During this timeframe, users can prevent the inactivity closure by executing a transaction or performing any action that qualifies as issuing activity.
When Issuing is disabled for inactivity, the connect account’s card_ capability status is marked as inactive.
Effect of disabling Issuing for inactivity
When Issuing is disabled, all card authorizations from cards associated with this account are declined, but other capabilities such as payments and Financial Accounts for platforms will remain unaffected. To reactivate Issuing on an account, re-collect the Terms of Service acceptance from the account and pass the new acceptance date and IP address in the tos_acceptance parameter of the Accounts API. Previously created cards in reactivated accounts will become active again and can be used for transactions.
Improve your user experience
Consider these updates for a better user experience:
- Update your UX by notifying users that their card will be closed due to inactivity 30 days (US) or 60 days (UK and Europe) in advance, after receiving the
account.webhook with theupdated card_parameter in the requirements hash.issuing. activity - Minimize inactive Issuing accounts by delaying Issuing capability requests until users show interest.
Impact to inactive cards or cardholders
Issuing is only disabled if all cardholders and cards within a connected account are inactive. There is no inactivity process for individual inactive cards or cardholders.