Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
The agreement authorizes Stripe to debit any linked user bank account and to offset amounts owed across any affiliated user entity accounts and bank accounts without prior separate notice, with this authorization remaining in effect until all user entity accounts are closed and all amounts are paid.
This analysis describes what Stripe's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes that Stripe may collect unpaid amounts by debiting any linked bank account or offsetting across any affiliated entity accounts without separate advance notice; the authorization persists until all associated accounts are closed and all outstanding amounts are settled.
Under this clause, Stripe may debit linked bank accounts and setoff amounts across affiliated entity accounts to collect fees or other amounts owed, without separate notice for each debit; the authorization continues even after a primary account is closed if any User Entity account remains open or amounts remain outstanding.
Cross-platform context
See how other platforms handle Multi-Entity Bank Account Debit and Cross-Account Setoff Authorization and similar clauses.
Compare across platforms →Monitoring
Stripe has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"Without limiting Section 7.2 of these General Terms, User authorizes Stripe to debit and credit each User Bank Account without separate notice, and according to the applicable User Bank Account Debit Authorization, to collect amounts User or another User Entity owes under this Agreement. If Stripe is unable to collect those amounts by debiting a User Bank Account, then User immediately grants to Stripe a new, original authorization to debit each User Bank Account without notice and according to the applicable User Bank Account Debit Authorization. Stripe may rely on this authorization to make one or more attempts to collect all or a subset of the amounts owed. User's authorization under this Section will remain in full force and effect until (i) all User Entity Stripe Accounts are closed; or (ii) all fees and other amounts User owes under this Agreement are paid, whichever occurs later.Excerpt from Stripe's Terms of Service
1. REGULATORY LANDSCAPE: Bank account debit authorization and payment processor setoff rights engage applicable ACH network rules, Nacha operating rules, and CFPB oversight of payment processors. The cross-entity setoff provision, which permits Stripe to offset amounts owed by any user entity against funds payable to any other user entity, may interact with applicable state law governing account setoff rights and commercial banking practices. 2. GOVERNANCE EXPOSURE: High. The cross-entity setoff in Section 7.2(c) authorizes Stripe to deduct amounts owed by any user entity from funds payable to any other user entity, including from each user bank account. For corporate groups operating multiple Stripe accounts, this creates consolidated financial exposure across entities that treasury and finance teams should evaluate. 3. JURISDICTION FLAGS: The waiver of debit scheme revocation rights in Section 7.5 states that to the extent Law permits, User waives any right granted by applicable debit scheme rules to revoke debit authorization; the enforceability of this waiver may vary by jurisdiction and applicable banking regulation. EU and UK users should assess whether this waiver is consistent with payment services regulations applicable in their jurisdiction. 4. CONTRACT AND VENDOR IMPLICATIONS: Organizations with multi-entity corporate structures using Stripe should identify all User Entity accounts and linked bank accounts subject to cross-entity setoff. Treasury teams should assess whether the persistent debit authorization, which survives until all User Entity accounts are closed and all amounts paid, creates operational risk in account closure scenarios. 5. COMPLIANCE CONSIDERATIONS: Finance and treasury teams should review which corporate entities and bank accounts are linked to Stripe accounts and assess the cross-entity setoff exposure. Legal teams should evaluate whether the waiver of debit scheme revocation rights is enforceable in applicable operating jurisdictions and whether internal cash management policies should be updated to account for this authorization.
This provision establishes that Stripe may collect unpaid amounts by debiting any linked bank account or offsetting across any affiliated entity accounts without separate advance notice; the authorization persists until all associated accounts are closed and all outstanding amounts are settled.
Under this clause, Stripe may debit linked bank accounts and setoff amounts across affiliated entity accounts to collect fees or other amounts owed, without separate notice for each debit; the authorization continues even after a primary account is closed if any User Entity account remains open or amounts remain outstanding.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Stripe.