Being listed in the Service Terms does not mean a Service is available in your country
The opening notice says the list of Service Terms does not indicate that a Service, or part of one, is available in any particular country. Country availability is described on the Stripe Website and in the Documentation, which are linked but not part of this analyzed text.
Supporting quotations
The list of Service Terms below does not indicate that a Service or part of a Service is available in a particular country.
for more information on Stripe’s Services and their availability
Qualifications & exceptions
Availability information lives on the Stripe Website and Documentation; neither is supplied here.
Not stated here
Which Services are available in which countries is not stated in this document.
Legal Rights & Agreement Rules · Context
Translated versions of the Stripe Services Agreement are informational only
Stripe says it has translated the Stripe Services Agreement into selected languages for informational purposes only. The translations are linked, not supplied, and this analysis covers only the English text as saved.
Supporting quotations
For informational purposes only, we have translated the Stripe Services Agreement into
Qualifications & exceptions
Translations are described as informational only; the English text analyzed here is the operative one in this source.
Not stated here
Which languages are offered, and whether any translation is stated elsewhere to control, is not in this text.
Legal Rights & Agreement Rules · Context
A linked support article describes changes made on September 28, 2026
The page points readers to a Stripe support article about changes made September 28, 2026. That article is linked but not supplied, so what changed is not known from this text. The assignment records this version's stated date as October 2, 2026; the relationship between the two dates is not explained here.
Supporting quotations
Read more about the
changes made September 28, 2026
Qualifications & exceptions
Only this saved version is analyzed; the change summary is an external, unsupplied page.
Not stated here
What the September 28, 2026 changes were.
How the September 28, 2026 change date relates to the October 2, 2026 stated date of this version.
Charges & Financial Obligations · Context
The Service Terms open with the Financial Services Terms and list payment and money-movement terms
The index of Service Terms begins with the Stripe Financial Services Terms and includes separate sets of terms for Stripe Payments, Adaptive Pricing, Billing, Capital for Platforms, Fee Credit Terms, Financial Connections, Global Payouts Fiat, Invoicing, Managed Payments, Next-Day Settlement, Orchestrated Services, Radar, Revenue Recognition, Tax and Treasury (formerly Financial Accounts). Each linked set is analyzed in its own section of this document; the index itself states no rules.
Supporting quotations
Stripe Financial Services Terms
Stripe Payments
Stripe Adaptive Pricing
Stripe Billing
Stripe Capital for Platforms
Stripe Fee Credit Terms
Stripe Financial Connections
Stripe Global Payouts Fiat
Stripe Invoicing
Stripe Managed Payments
Stripe Next-Day Settlement
Stripe Orchestrated Services
Stripe Radar
Stripe Revenue Recognition
Stripe Tax
Stripe Treasury (formerly Financial Accounts)
Qualifications & exceptions
Each entry is a link to a later section of this same document, where its terms are analyzed.
Legal Rights & Agreement Rules · Context
Five sets of Service Terms are labeled Preview in the index
The index marks five services as Preview: Stripe Agentic Commerce Agent Services, Stripe Agentic Commerce Seller Services, Stripe Global Payouts Stablecoin, Link Agent Wallet and Stripe Stablecoin Treasury (formerly Stablecoin Financial Accounts). The index does not say what Preview status means; any consequences are set out in those sections or elsewhere in the Agreement.
The Preview label appears in the index entry; its meaning is not defined in this packet.
Not stated here
What Preview status entails (for example limited availability, changed warranties or termination rights) is not stated in the index.
Legal Rights & Agreement Rules · Context
The index also lists terms for Atlas, Climate, Data Pipeline, Identity, Issuing fraud tools and more
Beyond payments, the index links separate Service Terms for Stripe Atlas Services, Stripe Climate, Stripe Data Pipeline, Stripe Identity, Stripe Issuing—Advanced Fraud Tools, Stripe Organizations and Stripe Professional Services. Each is analyzed in its own section; the index entry itself states no rules.
Supporting quotations
Stripe Atlas Services
Stripe Climate
Stripe Data Pipeline
Stripe Identity
Stripe Issuing—Advanced Fraud Tools
Stripe Organizations
Stripe Professional Services
Qualifications & exceptions
Each entry is a link to a later section of this same document.
Legal Rights & Agreement Rules · Context
Connect, Issuing, Terminal and Treasury for Platforms have separate terms by role and, for some, by region
The index splits several products into separate sets of terms by the user's role: Stripe Connect has Platform and Infrastructure terms; Stripe Terminal has user and Platform terms; Stripe Treasury for Platforms has Connected Accounts and Platform terms. Stripe Issuing is further split by region, with Accountholder and Platform terms for the United Kingdom and European Economic Area and separate ones for the United States, and Stripe Treasury for Platforms has United Kingdom variants of both its Connected Accounts and Platform terms. Which set applies depends on the user's role and region as defined in those sections.
Supporting quotations
Stripe Connect—Platform
Stripe Connect—Infrastructure
Stripe Issuing—Accountholder (United Kingdom and European Economic Area)
Stripe Issuing—Platform (United Kingdom and European Economic Area)
Stripe Issuing—Accountholder (United States)
Stripe Issuing—Platform (United States)
Stripe Terminal
Stripe Terminal—Platform
Stripe Treasury for Platforms—Connected Accounts
Stripe Treasury for Platforms—Platform
Stripe Treasury for Platforms—Connected Accounts (United Kingdom)
Stripe Treasury for Platforms—Platform (United Kingdom)
Qualifications & exceptions
Role and region are defined in the linked sections, not in the index.
Not stated here
Whether the non-UK Treasury for Platforms terms are limited to the United States or another region is not stated in the index.
Legal Rights & Agreement Rules · Context
The Financial Services Terms supplement the General Terms and apply to a Service only when incorporated by reference
The Stripe Financial Services Terms, last modified September 28, 2026, supplement the General Terms and apply to a Service only if the Service Terms for that Service incorporate them by reference. Their Regional Terms, in Section 5 (Regional Terms) of these Financial Services Terms, apply according to the User's Stripe Account Country. Capitalized terms not defined here take their meaning from the General Terms, which are a separate document not supplied with this source.
Supporting quotations
Stripe Financial Services Terms
Last modified: September 28, 2026
supplement the General Terms and apply to a Service if incorporated by reference into the applicable Services Terms
The Regional Terms in Section 5 (Regional Terms) of these Stripe Financial Services Terms apply based on User’s Stripe Account Country.
Capitalized terms that are not defined in these Stripe Financial Services Terms have the same meanings given to them in the General Terms.
Qualifications & exceptions
These terms apply to a Service only where that Service's own Service Terms incorporate them.
Regional Terms apply based on the User's Stripe Account Country.
Not stated here
The General Terms are not supplied, so definitions taken from them are not verified here.
The 'Section 5' reference is read as Section 5 (Regional Terms) of these Financial Services Terms; the source numbering restarts in each set of Service Terms.
Account & Service Control · Restriction or exception
You must be a business, public body or non-profit in the country where Stripe serves you, and Stripe must approve you
To use the Services under these terms, the User must be a business (including a sole proprietor), a governmental or public sector entity, or a non-profit organization. The User must be located in the same country where Stripe is providing the Services to it, or in a country Stripe has approved for those Services. Use of the Services is subject to Stripe's approval.
Supporting quotations
2.1 User’s Business.
User must be a business (including sole proprietor), governmental or public sector entity, or non-profit organization, and must be located in the same country where Stripe is providing the Services to User, or in a country approved by Stripe with respect to the Services.
User’s use of the Services is subject to approval by Stripe.
Qualifications & exceptions
A sole proprietor counts as a business.
A different country is acceptable only if Stripe has approved it with respect to the Services.
Not stated here
How Stripe approves a User or a country, and on what criteria, is not stated here.
Account & Service Control · Procedure
You must give Stripe complete User Information, keep it current and report ownership, financial and regulatory changes
To access the Services, and whenever Stripe asks, the User must promptly provide complete and accurate User Information in a form satisfactory to Stripe and keep it current in its Stripe Account, including changes to its business activities, Representatives, beneficial owners and principals. The User must also promptly notify Stripe and update its information if it experiences or anticipates a Change of Control or a material change in business or financial condition (including a likely Insolvency Event), if the regulatory status of its business changes, or if a Governmental Authority has told it that it or its business is under investigative action.
Supporting quotations
2.2 User Information.
To access the Services, and upon Stripe’s request, User must promptly provide complete and accurate User Information to Stripe in a form satisfactory to Stripe, and must keep the User Information in its Stripe Account current.
User also must promptly notify Stripe and provide updated User Information if (a) User experiences or anticipates experiencing a Change of Control; (b) User experiences or anticipates experiencing a material change in User's business or financial condition, including if User experiences or is likely to experience an Insolvency Event; (c) the regulatory status of the business for which User is using the Services changes, including if it becomes subject, or no longer subject, to regulatory oversight; or (d) a Governmental Authority has notified User that it or its business is the subject of investigative action.
Qualifications & exceptions
The notice duty covers anticipated events, not only ones that have already happened.
User Information, Change of Control, Insolvency Event and Governmental Authority are capitalized terms defined in the General Terms, which are not supplied.
Not stated here
What counts as a 'form satisfactory to Stripe' is not specified.
Data Access & Collection · Permission or license
You authorize Stripe to obtain your and your Representatives' credit, banking and financial history from third parties
The User authorizes Stripe to obtain information about the User and its business from Stripe's service providers and other third parties, including credit reporting agencies, banking partners and information bureaus, for the purposes of this Agreement. That information may include the User's or its Representative's name, addresses, credit history, banking relationships and financial history. The User must also authorize and direct those third parties to compile and provide the information to Stripe.
Supporting quotations
2.3 Information Stripe Obtains.
User authorizes Stripe to obtain information about User and its business from Stripe’s service providers and other third parties, including credit reporting agencies, banking partners and information bureaus, for the purposes of this Agreement.
This information may include User's, or User's Representative’s, name, addresses, credit history, banking relationships, and financial history.
User must authorize and direct those third parties to compile and provide this information to Stripe.
Qualifications & exceptions
The stated purpose limit is 'for the purposes of this Agreement'.
The information may concern the User's Representatives as well as the User.
Not stated here
Which specific providers or bureaus Stripe uses is not stated.
Legal Rights & Agreement Rules · Restriction or exception
Financial Provider Terms bind you, override conflicting terms and can change; Stripe disclaims provider failures
The User must comply with all Financial Provider Terms that apply to its use of the Services, meaning the rules and terms a Financial Provider sets for its services plus the PCI Standards. If a Financial Provider Term conflicts with this Agreement, the Financial Provider Term prevails to the extent of the inconsistency. Those terms may be amended from time to time, and continuing to use the applicable Services counts as agreement to the amended terms. To the extent Law and the applicable Financial Provider Terms permit, Stripe and its Affiliates are not liable for a third-party Financial Provider's failures or delays, including failing to settle a Transaction to Stripe or its Affiliates, or its default, insolvency or bankruptcy.
Supporting quotations
2.4 Financial Providers.
User must comply with all Financial Provider Terms that apply to User's use of the Services. If there is any inconsistency between any provision of this Agreement and the Financial Provider Terms, the applicable Financial Provider Terms will prevail to the extent of the inconsistency.
The Financial Provider Terms may be amended from time to time, and User’s continued use of the applicable Services constitutes User’s agreement to those amended terms.
To the extent Law and applicable Financial Provider Terms permit, Stripe and its Affiliates are not liable for failures or delays in performance by any third party Financial Provider, including as a result of (a) its failure to settle a Transaction to Stripe or its Affiliates; or (b) its default, insolvency, or bankruptcy.
“Financial Provider Terms” means (a) the rules and terms a Financial Provider specifies that apply to that entity’s services; and (b) the PCI Standards.
Qualifications & exceptions
The liability exclusion applies only to the extent Law and the applicable Financial Provider Terms permit.
Continued use after an amendment is treated as acceptance of the amended Financial Provider Terms.
Not stated here
The Financial Provider Terms themselves are external documents not supplied here.
How or whether the User is told of amendments to Financial Provider Terms is not stated.
Charges & Financial Obligations · Restriction or exception
You bear all Assessed Fines and reimburse Stripe, except fines caused by Stripe’s own fault or breach
The User is responsible for all Assessed Fines and must reimburse Stripe when Stripe pays them. The exception is any part of the fines that results from Stripe's own negligence, fraud, willful misconduct or breach of this Agreement.
Supporting quotations
2.5 Assessed Fines.
User is responsible for all Assessed Fines and must reimburse Stripe for its payment of Assessed Fines, except to the extent the Assessed Fines result from Stripe’s negligence, fraud, willful misconduct, or breach of this Agreement.
Qualifications & exceptions
The exception applies only to the extent the fines result from Stripe's negligence, fraud, willful misconduct or breach.
Not stated here
'Assessed Fines' is a capitalized term whose definition is not in this packet.
Charges & Financial Obligations · Company practice
Stripe keeps interest on funds it holds and may invest them, unless a Service's terms say otherwise
Unless particular Service Terms state otherwise, Stripe (or its Affiliate) owns any interest earned on funds it holds, and the User receives none. To the extent Law and any applicable Financial Provider Terms permit, Stripe and its Affiliates may invest held funds in liquid investments; they will hold those investments separately from investments of their own funds, and they own all earnings from them. Investing the funds does not affect or delay Stripe's obligations under the Agreement.
Supporting quotations
3. Stripe’s Rights and Obligations.
3.1 Holding of Funds.
Unless stated otherwise in Service Terms, Stripe will own, and User will not receive, any interest earned on funds held by Stripe or an applicable Affiliate.
to the extent Law and applicable Financial Provider Terms (if any) permit, Stripe and its Affiliates may invest funds they hold in liquid investments. Stripe or its applicable Affiliates will (a) hold these investments separate from investments made with their own funds; and (b) own, and User will not receive, any earnings from these investments.
Stripe’s and its Affiliates’ investment of funds will not affect or delay Stripe’s obligations under this Agreement.
Qualifications & exceptions
Another set of Service Terms can displace the default rule on interest.
Investment is permitted only to the extent Law and applicable Financial Provider Terms allow, and only in liquid investments.
Not stated here
Which Service Terms, if any, provide otherwise on interest is not identified here.
Charges & Financial Obligations · Company practice
A long-inactive positive balance may be handed to a government authority as abandoned property
If the User has a positive account balance that stays inactive for an extended period, Stripe may be required to deliver the funds to the appropriate Governmental Authority as abandoned property. Stripe or its Affiliate will attempt to notify the User beforehand only where Law requires it.
Supporting quotations
3.2 Dormant Accounts.
If User has a positive account balance that remains inactive for an extended period, Stripe may be required to deliver the funds to the appropriate Governmental Authority as abandoned property. However, if Law requires, Stripe or its applicable Affiliate will attempt to notify User before doing so.
Qualifications & exceptions
Prior notice is attempted only if Law requires it.
How long counts as an 'extended period' is not defined here.
Not stated here
The inactivity period and the governing abandoned-property Law are not stated.
Charges & Financial Obligations · Company practice
Where allowed, Stripe may hold a Reserve it fully controls, change its terms and release it only when risk is mitigated
Where the applicable Service Terms permit, Stripe may establish a Reserve, collateral funds it holds and controls to cover the User's actual or potential liabilities, and will notify the User of the Reserve terms in a Reserve Notice. The Reserve is held in a pooled Reserve Account and may be used to offset amounts owed to Stripe Entities. Stripe has sole control over it; the User has no right to any earnings on it and cannot draw from it. Stripe releases Reserve funds only if, and to the extent that, it is satisfied the relevant risk has been mitigated. Stripe may change the Reserve terms if it believes the risk from the User Group's use of the Services has changed or is likely to, or when a Financial Provider requires, and it may fund and replenish the Reserve through the means listed in the following subsection. These rights do not limit Stripe's other remedies.
Supporting quotations
3.3 Reserve.
Where permitted in the Service Terms, Stripe may establish a Reserve and will notify User of the Reserve terms (the “Reserve Notice”). The Reserve will be held by Stripe in a Reserve Account and may be used to offset amounts owed to Stripe Entities in accordance with this Agreement.
User acknowledges that Stripe has sole control over the Reserve and that User has no legal or equitable right or interest in any earnings generated by any Reserve, and is not entitled to draw funds from any Reserve. Stripe will release to User any funds forming part of the Reserve only if, and to the extent that, Stripe is satisfied that the relevant risk exposure has been mitigated. This section does not limit Stripe’s other rights or remedies under this Agreement.
Stripe may change the Reserve terms if Stripe believes that there is, or is likely to be, a change in the underlying risk presented by the User Group’s use of the Services; or as a Financial Provider requires.
Stripe may fund and replenish the Reserve through any or all of:
“Reserve” means collateral funds which Stripe holds and controls to satisfy any liabilities or potential liabilities User incurs under this Agreement
“Reserve Account” means one or more pooled accounts established by Stripe to hold amounts designated as Reserves.
Qualifications & exceptions
A Reserve may be established only where permitted in the applicable Service Terms.
Release is at Stripe's satisfaction that risk exposure has been mitigated, and only to that extent.
The ways Stripe may fund and replenish the Reserve are listed in subsection (c), analyzed with the next section.
Not stated here
Which Service Terms permit a Reserve, and typical Reserve amounts or durations, are not stated here.
Charges & Financial Obligations · Company practice
Stripe may fund or top up a Reserve from money you provide, money it owes your group for payments, or your bank accounts
Stripe may fund and replenish a Reserve through any or all of three sources: funds the User provides when Stripe asks; funds a Stripe Entity owes to any User Entity for Transactions the User Group accepts through the Stripe Payments Services (the Services for accepting and refunding Customer payments); and debiting the User Bank Accounts. The Regional Terms can vary this: the Brazil Regional Term, for example, lists only the first two sources.
Supporting quotations
Stripe may fund and replenish the Reserve through any or all of:
using funds User provides upon Stripe’s request
using funds that a Stripe Entity owes to any User Entity for Transactions that the User Group accepts through the Stripe Payments Services
debiting the User Bank Accounts
“Stripe Payments Services” means the Services that enable User to accept and refund Customer payments, perform related financial transactions, and manage Customer Disputes.
If Stripe establishes a Reserve under Section 3.3 (Reserve), Stripe may fund and replenish the Reserve through any or all of: (i) using funds User provides upon Stripe’s request; or (ii) using funds that Stripe owes to User for Transactions that User accepts through the Stripe Payments Services.
Qualifications & exceptions
Applies where a Reserve has been established under Section 3.3.
Regional Terms may change the available funding sources; the Brazil Regional Term omits debiting bank accounts.
Not stated here
Whether other Regional Terms also vary the funding sources is settled in those sections, not here.
Charges & Financial Obligations · Company practice
If your balance goes negative, an equal part of the Reserve automatically becomes Stripe's and you must top it up
If the User's Stripe Account balance becomes negative, a portion of the Reserve equal to the negative amount is automatically deemed applied by Stripe against that balance and becomes Stripe's sole property. The User must then promptly replenish the Reserve using the funding sources in Section 3.3(c). This operates without limiting Stripe's other rights or remedies under the Agreement.
Supporting quotations
If User’s Stripe Account balance becomes negative, then, without limiting Stripe’s other rights or remedies under this Agreement, a portion of the Reserve equal to the amount of the negative balance is automatically deemed to be applied by Stripe to offset the negative Stripe Account balance (thereby becoming the sole property of Stripe), and the Reserve must be promptly replenished in accordance with Section 3.3(c) above.
Qualifications & exceptions
The application is automatic ('deemed'); no separate action by Stripe is described.
Replenishment follows Section 3.3(c), the funding sources listed just above this clause.
Not stated here
How quickly 'promptly' replenished must happen is not defined.
Charges & Financial Obligations · Permission or license
You grant Stripe and the other Stripe Entities a security interest in your payment funds, credits and any Reserve
The User assigns, transfers and grants to Stripe, acting as agent for every Stripe Entity (together the Secured Parties), a security interest in all of the User's rights in the Collateral, as security for payment and performance of all obligations owed to any Secured Party (the Secured Obligations). The Collateral is: all funds owed to the User for Transactions, including future Transactions and funds Stripe holds on the User's behalf; all rights to receive credits and payments under the Agreement; and any Reserve, any beneficial interest in the pooled Reserve Accounts and any funds in them. It covers property existing now or arising later. The Singapore Regional Term adds a separate lien over all funds Stripe holds for the User, including the Collateral.
Supporting quotations
3.4 Security Interest.
User assigns and transfers to, and grants to, Stripe (as agent for each other Stripe Entity, and for the benefit of itself and the other Stripe Entities (collectively, the “Secured Parties”)) a security interest in all of User’s right, title and interest (if any) in and to the following property, whether now existing or hereafter arising (collectively, the “Collateral”), as collateral security for the prompt and complete payment and performance when due of all obligations owing to any Secured Party (the “Secured Obligations”):
all funds owed to User for Transactions (including funds owed to User for future Transactions and all funds that Stripe holds on User’s behalf)
all rights to receive credits and payments under this Agreement
any Reserve and any beneficial interest in the Reserve Accounts and any funds held in them
“Reserve Account” means one or more pooled accounts established by Stripe to hold amounts designated as Reserves.
In addition to the security interest granted under Section 3.4 (Security Interest), User acknowledges that Stripe also has a lien over all funds Stripe holds on User’s behalf, including the Collateral
Qualifications & exceptions
The grant is in the User's 'right, title and interest (if any)', so it reaches only what the User actually holds.
Covers property whether now existing or hereafter arising.
Regional Terms may add to this; the Singapore Regional Term adds a lien over all held funds.
Not stated here
Which entities count as Stripe Entities is defined in the General Terms, not supplied here.
Charges & Financial Obligations · Restriction or exception
You must help Stripe perfect its security interest, even after a negative balance, and may not encumber the Reserve
The User consents to Stripe notifying any party who must be told of the Collateral under local law, and must sign all documents and give all authorizations Stripe reasonably requests to create, perfect (including by filing), maintain and enforce the security interest. That duty applies even if Stripe asks after the User's balance has gone negative. Except as this section permits, the User may not create or allow any security interest, lien, pledge, hypothec, encumbrance or charge over the Reserve, the Reserve Accounts or funds held in them.
Supporting quotations
User authorizes and consents to Stripe giving notice of the Collateral to any relevant party who may need to be notified under any local law. User must execute all documents and provide all authorizations that Stripe reasonably requests for the purpose of creating, perfecting (including filing relevant documents), maintaining and enforcing this security interest, even if the request is made after User’s applicable balance with Stripe becomes negative.
Except as permitted by this section, User will not assign, grant, create, incur, assume, agree to create, or permit to exist, any security interest, lien, pledge, hypothec, encumbrance or charge in or over the Reserve, the Reserve Accounts, or any funds held in them.
Qualifications & exceptions
Requests for documents must be reasonable.
The ban on other encumbrances covers the Reserve, the Reserve Accounts and funds in them, with the only exception being what this section itself permits.
Charges & Financial Obligations · Company practice
Stripe may demand a guarantee or letter of credit and may suspend or end your access if you cannot provide it
Stripe may require the User to provide a guarantee, which may be a personal, parent-company or bank guarantee, or a letter of credit, in a form and substance that satisfies Stripe. When it does, Stripe will tell the User the amount required and the reasons. If the User cannot meet the requirement when Stripe requires it, Stripe may suspend or terminate the User's access to the Services.
Supporting quotations
3.5 Credit Support Requirement.
Stripe may require User to provide a guarantee (including a personal, parent or bank guarantee) or letter of credit in a form and substance that satisfies Stripe. In this event, Stripe will inform User of the amount of and the reasons for the requirement. If User is unable to satisfy the requirement when Stripe requires User to do so, Stripe may suspend or terminate User’s access to the Services.
Qualifications & exceptions
Stripe commits to state the amount of and reasons for the requirement.
Suspension or termination is permitted ('may'), not automatic.
Not stated here
What triggers Stripe to require credit support is not stated.
Charges & Financial Obligations · Company practice
If your or a User Entity’s balance is negative or short, Stripe may debit your group’s bank accounts
If the User's Stripe Account balance, or that of any User Entity, is negative or lacks enough funds to pay what the User or a User Entity owes to a Stripe Entity or to Customers, Stripe may debit the User Bank Accounts, or the bank account of any User Entity under the debit authorization that entity granted, for the amount needed to collect those sums and, where applicable, pay them out to Customers. This is in addition to Stripe's rights under Sections 7.2 and 7.5 of the General Terms, which are a separate document not supplied here.
Supporting quotations
3.6 Negative Balances.
If User’s Stripe Account balance (or the Stripe Account balance of any User Entity) is negative, or does not contain funds sufficient to pay amounts that User (or a User Entity) owes to a Stripe Entity or Customers, then without limiting Stripe’s rights under Sections 7.2 and 7.5 of the General Terms, Stripe may debit the User Bank Accounts or the User Bank Account of any User Entities (pursuant to the debit authorization granted by that User Entity) by the amount necessary to collect, and pay out to Customers if applicable, the amounts User owes.
Qualifications & exceptions
Debits of another User Entity's account rely on the debit authorization that entity granted.
The rights under Sections 7.2 and 7.5 of the General Terms are preserved but their content is not in this source.
Not stated here
What Sections 7.2 and 7.5 of the General Terms provide is unknown; the General Terms are not supplied.
Security & Safeguards · Company commitment
Stripe provides the Services consistently with the PCI-DSS requirements that apply to Stripe
Stripe commits to provide the Services in a manner consistent with the PCI-DSS requirements that apply to Stripe. PCI-DSS is the Payment Card Industry Data Security Standard; the broader term PCI Standards also covers the Payment Card Industry Software Security Framework (PCI-SSF) and any successor standards. The commitment is limited to requirements that apply to Stripe itself; it says nothing about the User's own PCI obligations.
Supporting quotations
3.7 PCI-DSS.
Stripe provides the Services in a manner consistent with PCI-DSS requirements that apply to Stripe.
“PCI-DSS” means the Payment Card Industry Data Security Standard.
“PCI Standards” means PCI-DSS and Payment Card Industry Software Security Framework (PCI-SSF), including successor standards (if any).
Qualifications & exceptions
Limited to PCI-DSS requirements 'that apply to Stripe'.
Not stated here
The User's own PCI obligations are addressed elsewhere (for example in the Stripe Payments Terms), not in this clause.
Inference & Profiling · Company practice
If Stripe flags a possibly fraudulent or unverifiable party, what you do next may train Stripe's fraud model
When Stripe gives the User information about the possibility or likelihood that a transaction is fraudulent or that an individual cannot be verified, Stripe may incorporate the User's subsequent actions and inactions into its fraud and verification model, for the purpose of identifying future potential fraud. The clause points to the Stripe Privacy Center for information on Stripe's collection of end-customer data for this purpose and for guidance on notifying Customers; those pages are linked, not supplied.
Supporting quotations
3.8 Use of Fraud Signals.
If Stripe provides User with information regarding the possibility or likelihood that a transaction may be fraudulent or that an individual cannot be verified, Stripe may incorporate User’s subsequent actions and inactions into Stripe’s fraud and verification model, for the purpose of identifying future potential fraud.
Qualifications & exceptions
Applies only after Stripe has provided fraud or verification information to the User.
The stated purpose is identifying future potential fraud.
Not stated here
The Privacy Center pages on end-customer data collection and Customer notice are not supplied.
Legal Rights & Agreement Rules · Context
Defined terms: Activity, Financial Provider Terms, Payment Method Acquirer and Reserve
The Financial Services Terms define several terms used across the Service Terms. 'Activity' is any action on or related to a Connected Account's Stripe Account that a Stripe Connect Platform or Connected Account initiates through the Stripe Technology or Stripe Connect Services, including related communications. 'Financial Provider Terms' are a Financial Provider's rules and terms plus the PCI Standards. A 'Payment Method Acquirer' is an entity a Payment Method Provider has authorized to sponsor or submit Transactions for authorization and clearing and to receive and remit settlement funds. 'Reserve' means collateral funds Stripe holds and controls to satisfy the User's actual or potential liabilities, including amounts described as Reserve in the Reserve Notice, the Stripe Dashboard or other communications.
Supporting quotations
4. Definitions.
“Activity” means any action taken on or related to a Connected Account's Stripe Account that a Stripe Connect Platform or a Connected Account initiates, submits or performs, either through the Stripe Technology or through the Stripe Connect Services, including communication regarding the Services as related to that Connected Account.
“Financial Provider Terms” means (a) the rules and terms a Financial Provider specifies that apply to that entity’s services; and (b) the PCI Standards.
“Payment Method Acquirer” means an entity that a Payment Method Provider has authorized to (a) sponsor or submit Transactions at the request of merchants to the Payment Method Provider for authorization and clearing; and (b) receive and remit settlement funds for authorized and cleared Transactions.
“Reserve” means collateral funds which Stripe holds and controls to satisfy any liabilities or potential liabilities User incurs under this Agreement, including any funds described as “Reserve” amounts in the Reserve Notice, the Stripe Dashboard or in any other communications to User.
Qualifications & exceptions
Terms not defined here take their meaning from the General Terms, which are not supplied.
Legal Rights & Agreement Rules · Context
Defined terms: Reserve Account and Stripe Payments Services
A 'Reserve Account' is one or more pooled accounts Stripe establishes to hold amounts designated as Reserves, so Reserve funds are not held in an account specific to the User. 'Stripe Payments Services' are the Services that let the User accept and refund Customer payments, perform related financial transactions and manage Customer Disputes.
Supporting quotations
“Reserve Account” means one or more pooled accounts established by Stripe to hold amounts designated as Reserves.
“Stripe Payments Services” means the Services that enable User to accept and refund Customer payments, perform related financial transactions, and manage Customer Disputes.
Qualifications & exceptions
Reserve Accounts are pooled, not User-specific.
Legal Rights & Agreement Rules · Restriction or exception
Regional Terms apply by country or region and override the Financial Services Terms where they conflict
Section 5 sets out Regional Terms for listed countries and regions. Where a Regional Term conflicts with the main Stripe Financial Services Terms, the Regional Term prevails. Which Regional Terms apply depends on the User's Stripe Account Country, as Section 1 states.
Supporting quotations
5. Regional Terms.
The following Regional Terms apply for the countries or regions below. If there is a conflict between the Stripe Financial Services Terms and the Regional Terms, the Regional Terms prevail.
Qualifications & exceptions
Regional Terms prevail only to the extent of a conflict with the Financial Services Terms.
Not stated here
How a conflict between two Regional Terms, or between Regional Terms and another Service's terms, would be resolved is not stated here.
Charges & Financial Obligations · Context
United States: regulated money transmission is provided by Stripe Payments Company under separate SPC terms
For Users in the United States, certain Services involve regulated money transmission under U.S. Law. To the extent the User's use of the Services involves money transmission or other regulated services under U.S. Law, Stripe's Affiliate Stripe Payments Company (SPC) provides those regulated Services, and the SPC terms available on or from the Stripe Legal Page apply to the User, unless the applicable Service Terms say otherwise. Stripe states that it is not a bank and does not accept deposits.
Supporting quotations
United States.
The following Regional Terms apply for Users in the United States.
5.1 Regulated Money Transmission.
To the extent that User’s use of the Services involves money transmission or other regulated services under U.S. Law, Stripe’s Affiliate, Stripe Payments Company (“SPC”) provides those regulated Services, and the SPC terms located on or accessible from the Stripe Legal Page will apply to User, unless the applicable Service Terms specify otherwise. Stripe is not a bank, and does not accept deposits.
Qualifications & exceptions
Applies to Users in the United States.
The SPC terms apply unless the applicable Service Terms specify otherwise.
Not stated here
The SPC terms are on the Stripe Legal Page and are not supplied here.
Which Services involve regulated money transmission is not listed.
Charges & Financial Obligations · Restriction or exception
United States: Reserves sit in SPC's Reserve Accounts and the security interest is granted to SPC
For Users in the United States, the Reserve and Security Interest provisions (Sections 3.3 and 3.4 of these Financial Services Terms) operate through Stripe Payments Company: Reserve funds are held in Reserve Accounts established by SPC, and the User grants the security interest to SPC, acting as agent for each other Secured Party and for its own and their benefit.
Supporting quotations
5.2 Reserves and Security Interest.
For the purposes of Sections 3.3 (Reserve) and 3.4 (Security Interest), Reserve funds are held in Reserve Accounts established by SPC, and User grants the security interest to SPC (as agent for each other Secured Party and for the benefit of itself and the other Secured Parties).
Qualifications & exceptions
A regional variation of Sections 3.3 (Reserve) and 3.4 (Security Interest); the substance of those sections otherwise applies.
Legal Rights & Agreement Rules · Context
EEA: Stripe Technology Europe (Stripe PSP) is a party only for regulated services and acquiring; it is not a bank
For Users in the European Economic Area, Stripe Technology Europe, Limited (Stripe PSP) is an additional party to the Agreement solely to provide Regulated Financial Services and to act as a Payment Method Acquirer, the entity authorized by a Payment Method Provider to submit Transactions for authorization and clearing and to receive and remit settlement funds. Otherwise, 'Stripe' in the Agreement means Stripe Payments Europe, Limited. Regulated Financial Services are the Services the Central Bank of Ireland has authorised Stripe PSP to provide (listed in the linked register) and any other regulated services it may lawfully provide. The Central Bank of Ireland has authorised Stripe PSP as an electronic money institution under reference number C187865. Stripe PSP is not a bank, offers no deposit or savings account, and is not part of the Financial Services Compensation Scheme or the Deposit Guarantee Scheme. Where Services are Regulated Financial Services, Stripe PSP is their only provider.
Supporting quotations
European Economic Area.
The following Regional Terms apply for Users in the European Economic Area.
5.1 Provision of Regulated Financial Services.
Stripe Technology Europe, Limited (“Stripe PSP”) is an additional party to this Agreement solely for the purposes of (a) providing Regulated Financial Services; and (b) acting as a Payment Method Acquirer. Each reference in this Agreement to “Stripe” means Stripe Payments Europe, Limited, except to the extent that the reference relates to providing Regulated Financial Services, in which case “Stripe” means Stripe PSP.
Stripe PSP is regulated by the Central Bank of Ireland. The Central Bank of Ireland has authorised Stripe PSP as an electronic money institution under reference number C187865. Stripe PSP is not a bank and does not offer any form of deposit or savings account. Stripe PSP is not part of the Financial Services Compensation Scheme or the Deposit Guarantee Scheme. To the extent the Services are Regulated Financial Services, Stripe PSP is the only provider of those Services.
“Payment Method Acquirer” means an entity that a Payment Method Provider has authorized to (a) sponsor or submit Transactions at the request of merchants to the Payment Method Provider for authorization and clearing; and (b) receive and remit settlement funds for authorized and cleared Transactions.
Qualifications & exceptions
Applies to Users in the European Economic Area.
Stripe PSP's role is limited to Regulated Financial Services and acting as Payment Method Acquirer.
Not stated here
The list of authorised services is on the Central Bank of Ireland register, linked but not supplied.
Charges & Financial Obligations · Company commitment
EEA: only Stripe PSP is liable to you for collecting, safeguarding and settling your payment proceeds
For Users in the European Economic Area, Stripe PSP, as the provider of Regulated Financial Services, is the only Stripe party liable to the User for collecting payment proceeds from Transactions on the User's behalf, safeguarding those proceeds according to Law, and settling them to the User Bank Account or as the User otherwise directs.
Supporting quotations
5.2 Collection of Payment Proceeds.
As the provider of Regulated Financial Services, Stripe PSP will be the only Stripe party liable to User for collecting payment proceeds from Transactions on User’s behalf, safeguarding those proceeds according to Law, and settling those proceeds to the User Bank Account or as User otherwise directs.
Qualifications & exceptions
Applies to Users in the European Economic Area.
Liability for these functions sits with Stripe PSP alone, not Stripe Payments Europe, Limited.
Charges & Financial Obligations · Company practice
EEA: Stripe may offer E-money; you earn nothing on it, Stripe PSP alone is liable for it, and you can redeem it at par
Depending on the User's location and, where relevant, its Connected Accounts' locations, Stripe may offer E-money Services to Users in the European Economic Area. E-money is electronic money as defined in the cited Irish regulation (SI No. 183/2011). The section applies only if Stripe actually provides E-money Services. The User may buy E-money from Stripe, send and receive it and, if applicable, transfer it to and from Connected Accounts, but receives no earnings on E-money Stripe issues or holds. Stripe PSP is the only Stripe party liable for issuing, redeeming and transferring E-money, and when it issues E-money it safeguards the funds received in exchange according to Law. The User may use the Stripe Technology to redeem E-money Stripe PSP holds for it at par value.
Supporting quotations
5.3 E-money Services.
Depending on User’s location and, if applicable, User’s Connected Accounts’ locations, Stripe may offer E-money Services to User. “E-money” means electronic money as defined in SI No. 183/2011 – European Communities (Electronic Money) Regulations 2011. The terms in this section only apply if Stripe provides E-money Services to User.
User will not receive any earnings from E-money that Stripe issues or holds. As the provider of Regulated Financial Services, Stripe PSP will be the only Stripe party liable to User for issuing, redeeming and transferring E-Money. If Stripe PSP issues E-money to User, Stripe PSP will safeguard funds received from User in exchange for that E-money according to Law. User may use the Stripe Technology to redeem E-money Stripe PSP holds for User for par value.
Qualifications & exceptions
Applies to Users in the European Economic Area and only if Stripe provides E-money Services.
The User receives no earnings from E-money.
The regulation is cited by name only; its text is not supplied.
Not stated here
Which locations receive E-money Services is not stated.
Account & Service Control · User right or choice
EEA: you may let an authorised third-party provider (TPP) access your Payment Account, but you answer for its acts
For Users in the European Economic Area, a Payment Account is as defined in the cited Irish regulation (SI No. 6/2018), and a TPP is a third-party payment service provider that a Governmental Authority authorises to provide account information or payment initiation services. If Stripe provides the User a Payment Account, the User may enable a TPP to access its information or make payments from it according to Law, and may give the TPP its Stripe Account credentials if necessary for that access. The User must ensure each TPP it uses is authorised or registered with the relevant authority and, as between the parties, is liable for the TPP's acts and omissions. Stripe may refuse a TPP access if it reasonably believes the TPP's actions are unauthorised, fraudulent or illegal, and will notify the User unless Law prohibits it. The User must notify Stripe immediately if it believes a payment made through a TPP was unauthorised or incorrect.
Supporting quotations
5.4 Payment Account.
“Payment Account” means a payment account as that term is defined in SI No. 6/2018 – European Union (Payment Services) Regulations 2018.
5.5 Using a Third-Party Payment Services Provider (TPP).
“TPP” means a third-party payment service provider that a Governmental Authority authorises to provide account information services or payment initiation services. If Stripe provides a Payment Account to User, User may enable a TPP to access information regarding that Payment Account or make payments from the Payment Account according to Law. User must ensure that each TPP User uses (if any) is authorised or registered with the applicable Governmental Authority. Notwithstanding anything to the contrary in this Agreement, as among the parties, User is liable for the TPP’s acts and omissions.
Stripe may refuse to allow any TPP to access information regarding User’s Payment Account if Stripe reasonably believes that the TPP’s actions are unauthorised, fraudulent or illegal. Unless Law prohibits notification, Stripe will notify User if Stripe takes this action. User must notify Stripe immediately if User believes a payment made through a TPP was unauthorised or incorrect.
Qualifications & exceptions
Applies to Users in the European Economic Area and only if Stripe provides a Payment Account.
The User's liability for the TPP applies 'notwithstanding anything to the contrary in this Agreement'.
Stripe's refusal must rest on a reasonable belief of unauthorised, fraudulent or illegal action.
Not stated here
The cited regulation's text is not supplied.
Charges & Financial Obligations · Restriction or exception
EEA: Stripe safeguards your funds as Law requires, but funds it moves into a Reserve stop being safeguarded
For Users in the European Economic Area, and in addition to the holding-of-funds rules in Section 3.1 of these Financial Services Terms, Stripe safeguards the funds it holds for the User as Law requires. However, if Stripe uses safeguarded funds to fund a Reserve, those funds are no longer safeguarded on the User's behalf.
Supporting quotations
In addition to the further provisions on holding of funds in Section 3.1 (Holding of Funds), Stripe safeguards funds Stripe holds for User as required by Law. However, if Stripe uses safeguarded funds to fund a Reserve, then Stripe will no longer safeguard those funds on User’s behalf.
Qualifications & exceptions
Applies to Users in the European Economic Area.
Safeguarding is 'as required by Law', not a broader commitment.
The exception covers safeguarded funds that Stripe uses to fund a Reserve.
Not stated here
The safeguarding Law that applies is not named.
Legal Rights & Agreement Rules · Company commitment
EEA: Stripe notifies you of changes to the Agreement affecting Regulated Financial Services as Law requires
For Users in the European Economic Area, when the Agreement is modified in relation to Regulated Financial Services, Stripe will notify the User as Law requires. The clause sets no notice period or method of its own; it defers to the applicable Law.
Supporting quotations
5.7 Notifications for Modifications to this Agreement related to Regulated Financial Services.
For modifications to this Agreement related to Regulated Financial Services, Stripe will notify User as Law requires.
Qualifications & exceptions
Applies to Users in the European Economic Area and only to modifications related to Regulated Financial Services.
Not stated here
The notice period and method required by Law are not stated.
How other modifications are notified is governed elsewhere, presumably the General Terms, which are not supplied.
Legal Rights & Agreement Rules · User right or choice
EEA: you can complain about regulated services to complaints@stripe.com and may escalate to the Irish FSPO
A User in the European Economic Area with a complaint about Regulated Financial Services provided by Stripe may contact complaints@stripe.com; Stripe's Complaints Policy is linked for more information. If the complaint is unresolved, the User may be entitled to refer it to the Irish Financial Services and Pensions Ombudsman (FSPO), whose details and eligibility requirements are in the Complaints Policy and on the FSPO website.
Supporting quotations
5.8 Complaints.
If User has a complaint about Regulated Financial Services provided by Stripe, User may contact complaints@stripe.com.
If User’s complaint is unresolved, User may be entitled to refer it to the Irish Financial Services and Pensions Ombudsman (FSPO).
Qualifications & exceptions
Applies to Users in the European Economic Area and to complaints about Regulated Financial Services.
Referral to the FSPO is subject to eligibility requirements ('may be entitled').
Not stated here
The Complaints Policy and FSPO eligibility rules are linked but not supplied.
Charges & Financial Obligations · Restriction or exception
EEA: Stripe PSP holds Reserves and keeps title; you have no interest in them, but release once risk ends still applies
For Users in the European Economic Area, Reserve funds under Section 3.3 are held in Reserve Accounts established by Stripe PSP. On top of Section 3.3, the User acknowledges it has no legal, beneficial or equitable right or interest in any Reserve or Reserve Account, and that title to the Reserve funds and accounts remains solely with Stripe PSP. The clause confirms it does not limit Stripe's obligation under Section 3.3(a) to return Reserve funds to the extent Stripe is satisfied the risk exposure has been mitigated.
Supporting quotations
5.9 Reserves.
For the purposes of Section 3.3 (Reserve), Reserve funds are held in Reserve Accounts established by Stripe PSP. In addition to the provisions under Section 3.3, User acknowledges that User has no legal, beneficial or equitable right or interest in any Reserve or Reserve Account and that title to the Reserve funds and Reserve Accounts remains solely with Stripe PSP. To avoid doubt, this section does not limit Stripe’s obligation under Section 3.3(a) to return to User any funds forming part of the Reserve to the extent that Stripe is satisfied the risk exposure has been mitigated.
Qualifications & exceptions
Applies to Users in the European Economic Area.
The return obligation of Section 3.3(a) is expressly preserved.
Legal Rights & Agreement Rules · Context
UK, Switzerland, Gibraltar: Stripe Payments UK Ltd (Stripe PSP) is a party only for regulated services and acquiring
For Users in the United Kingdom, Switzerland and Gibraltar, Stripe Payments UK Ltd (Stripe PSP) is an additional party to the Agreement solely to provide Regulated Financial Services and to act as a Payment Method Acquirer; otherwise 'Stripe' means Stripe Payments Europe, Limited. Regulated Financial Services are the Services the U.K. Financial Conduct Authority has authorised Stripe PSP to provide, listed on the linked FCA register. The FCA has authorised Stripe PSP as an electronic money institution under reference number 900461. Stripe PSP is not a bank, offers no deposit or savings account, and is not part of the Financial Services Compensation Scheme or the Deposit Guarantee Scheme. Where Services are Regulated Financial Services, Stripe PSP is their only provider.
Supporting quotations
United Kingdom, Switzerland, Gibraltar.
The following Regional Terms apply for Users in the United Kingdom, Switzerland and Gibraltar.
5.1 Provision of Regulated Financial Services.
Stripe Payments UK Ltd (“Stripe PSP”) is an additional party to this Agreement solely for the purposes of (a) providing Regulated Financial Services; and (b) acting as a Payment Method Acquirer. Each reference in this Agreement to “Stripe” means Stripe Payments Europe, Limited, except to the extent that the reference relates to providing Regulated Financial Services, in which case “Stripe” means Stripe PSP.
The U.K. Financial Conduct Authority has authorised Stripe PSP as an electronic money institution under reference number 900461. Stripe PSP is not a bank and does not offer any form of deposit or savings account. Stripe PSP is not part of the Financial Services Compensation Scheme or the Deposit Guarantee Scheme. To the extent the Services are Regulated Financial Services, Stripe PSP is the only provider of those Services.
Qualifications & exceptions
Applies to Users in the United Kingdom, Switzerland and Gibraltar.
Unlike the EEA clause, Regulated Financial Services here are only those the FCA has authorised; there is no 'any other regulated services' limb.
Not stated here
The FCA register entry is linked but not supplied.
Charges & Financial Obligations · Company commitment
UK, Switzerland, Gibraltar: only Stripe PSP is liable to you for collecting, safeguarding and settling proceeds
For Users in the United Kingdom, Switzerland and Gibraltar, Stripe PSP, as the provider of Regulated Financial Services, is the only Stripe party liable to the User for collecting payment proceeds from Transactions on the User's behalf, safeguarding them according to Law, and settling them to the User Bank Account or as the User otherwise directs.
Supporting quotations
5.2 Collection of Payment Proceeds.
As the provider of Regulated Financial Services, Stripe PSP will be the only Stripe party liable to User for collecting payment proceeds from Transactions on User’s behalf, safeguarding those proceeds according to Law, and settling those proceeds to the User Bank Account or as User otherwise directs.
Qualifications & exceptions
Applies to Users in the United Kingdom, Switzerland and Gibraltar.
Charges & Financial Obligations · Company practice
UK, Switzerland, Gibraltar: Stripe may offer E-money; no earnings for you, Stripe PSP alone liable, redeemable at par
Depending on the User's location and, where relevant, its Connected Accounts' locations, Stripe may offer E-money Services to Users in the United Kingdom, Switzerland and Gibraltar. E-money is electronic money as defined in the cited UK regulation (Electronic Money Regulations 2011, SI 2011/99). The section applies only if Stripe actually provides E-money Services. The User may buy E-money from Stripe, send and receive it and, if applicable, transfer it to and from Connected Accounts, but receives no earnings on it. Stripe PSP is the only Stripe party liable for issuing, redeeming and transferring E-money and safeguards the funds received for it according to Law. The User may redeem E-money Stripe PSP holds for it at par value through the Stripe Technology.
Supporting quotations
5.3 E-money Services.
Depending on User’s location and, if applicable, User’s Connected Accounts’ locations, Stripe may offer E-money Services to User. “E-money” means electronic money as defined in the Electronic Money Regulations 2011 (SI 2011/99). The terms in this section only apply if Stripe provides E-money Services to User.
User will not receive any earnings from E-money that Stripe issues or holds. As the provider of Regulated Financial Services, Stripe PSP will be the only Stripe party liable to User for issuing, redeeming and transferring E-Money. If Stripe PSP issues E-money to User, Stripe PSP will safeguard funds received from User in exchange for that E-money according to Law. User may use the Stripe Technology to redeem E-money Stripe PSP holds for User for par value.
Qualifications & exceptions
Applies to Users in the United Kingdom, Switzerland and Gibraltar and only if Stripe provides E-money Services.
The regulation is cited by name only; its text is not supplied.
Not stated here
Which locations receive E-money Services is not stated.
Account & Service Control · User right or choice
UK, Switzerland, Gibraltar: you may let an authorised TPP access your Payment Account, but you answer for its acts
For Users in the United Kingdom, Switzerland and Gibraltar, a Payment Account is as defined in the cited UK regulation (Payment Services Regulations 2017, SI 2017/752), and a TPP is a third-party payment service provider that a Governmental Authority authorises for account information or payment initiation services. If Stripe provides a Payment Account, the User may enable a TPP to access its information or make payments from it according to Law, and may give the TPP its Stripe Account credentials if necessary. The User must ensure each TPP is authorised or registered and, as between the parties, is liable for the TPP's acts and omissions. Stripe may refuse a TPP access on a reasonable belief that its actions are unauthorised, fraudulent or illegal, notifying the User unless Law prohibits it, and the User must notify Stripe immediately of any payment through a TPP it believes was unauthorised or incorrect.
Supporting quotations
5.4 Payment Account.
“Payment Account” means a payment account as that term is defined in the Payment Services Regulations 2017 (Statutory Instrument 2017/752).
5.5 Using a Third-Party Payment Services Provider (TPP).
If Stripe provides a Payment Account to User, User may enable a TPP to access information regarding that Payment Account or make payments from the Payment Account according to Law. User must ensure that each TPP User uses (if any) is authorised or registered with the applicable Governmental Authority. Notwithstanding anything to the contrary in this Agreement, as among the parties, User is liable for the TPP’s acts and omissions.
Stripe may refuse to allow any TPP to access information regarding User’s Payment Account if Stripe reasonably believes that the TPP’s actions are unauthorised, fraudulent or illegal. Unless Law prohibits notification, Stripe will notify User if Stripe takes this action. User must notify Stripe immediately if User believes a payment made through a TPP was unauthorised or incorrect.
Qualifications & exceptions
Applies to Users in the United Kingdom, Switzerland and Gibraltar and only if Stripe provides a Payment Account.
The User's liability for the TPP applies 'notwithstanding anything to the contrary in this Agreement'.
Not stated here
The cited regulation's text is not supplied.
Charges & Financial Obligations · Restriction or exception
UK, Switzerland, Gibraltar: Stripe safeguards your funds as Law requires, except funds it moves into a Reserve
For Users in the United Kingdom, Switzerland and Gibraltar, in addition to the holding-of-funds rules in Section 3.1, Stripe safeguards the funds it holds for the User as Law requires. If Stripe uses safeguarded funds to fund a Reserve, those funds are no longer safeguarded on the User's behalf.
Supporting quotations
In addition to the further provisions on holding of funds in Section 3.1 (Holding of Funds), Stripe safeguards funds Stripe holds for User as required by Law. However, if Stripe uses safeguarded funds to fund a Reserve, then Stripe will no longer safeguard those funds on User’s behalf.
Qualifications & exceptions
Applies to Users in the United Kingdom, Switzerland and Gibraltar.
Safeguarding is 'as required by Law'.
Not stated here
The safeguarding Law that applies is not named.
Legal Rights & Agreement Rules · Company commitment
UK, Switzerland, Gibraltar: Stripe notifies you of changes affecting Regulated Financial Services as Law requires
For Users in the United Kingdom, Switzerland and Gibraltar, when the Agreement is modified in relation to Regulated Financial Services, Stripe will notify the User as Law requires. No notice period or method is set in the clause itself.
Supporting quotations
5.7 Notifications for Modifications to this Agreement related to Regulated Financial Services.
For modifications to this Agreement related to Regulated Financial Services, Stripe will notify User as Law requires.
Qualifications & exceptions
Applies to modifications related to Regulated Financial Services only.
Not stated here
The notice period and method required by Law are not stated.
Legal Rights & Agreement Rules · User right or choice
UK, Switzerland, Gibraltar: complain to complaints@stripe.com; unresolved complaints may go to the FOS
A User in the United Kingdom, Switzerland or Gibraltar with a complaint about Regulated Financial Services provided by Stripe may contact complaints@stripe.com; Stripe's Complaints Policy is linked. If the complaint is unresolved, the User may be entitled to refer it to the Financial Ombudsman Service (FOS), subject to eligibility requirements described in the Complaints Policy and on the FOS website.
Supporting quotations
5.8 Complaints.
If User has a complaint about Regulated Financial Services provided by Stripe, User may contact complaints@stripe.com.
If User’s complaint is unresolved, User may be entitled to refer it to the Financial Ombudsman Service (FOS).
Qualifications & exceptions
Referral to the FOS is subject to eligibility ('may be entitled').
Not stated here
The Complaints Policy and FOS eligibility rules are linked but not supplied.
Charges & Financial Obligations · Restriction or exception
UK, Switzerland, Gibraltar: Reserves sit with Stripe PSP and your security interest to it is a fixed first charge
For Users in the United Kingdom, Switzerland and Gibraltar, the Reserve and Security Interest provisions (Sections 3.3 and 3.4) operate through Stripe PSP: Reserve funds are held in Reserve Accounts established by Stripe PSP, and the User grants the security interest to Stripe PSP as agent for each other Secured Party. The security interest is taken by way of a fixed first charge.
Supporting quotations
5.9 Reserves and Security Interest.
For the purposes of Sections 3.3 (Reserve) and 3.4 (Security Interest), Reserve funds are held in Reserve Accounts established by Stripe PSP, and User grants the security interest to Stripe PSP (as agent for each other Secured Party and for the benefit of itself and the other Secured Parties). The security interest is taken by way of a fixed first charge.
Qualifications & exceptions
A regional variation of Sections 3.3 (Reserve) and 3.4 (Security Interest).
The form of security is a fixed first charge.
Charges & Financial Obligations · Restriction or exception
Australia: a Reserve Notice plus Section 3.3 counts as a separate security agreement under the PPSA from delivery
For Users in Australia, the Reserve Notice, read together with Section 3.3 (Reserve), is taken to constitute a separate security agreement for the purposes of the Personal Property Securities Act 2009 (Cth). That agreement takes effect on and from the date the Reserve Notice is delivered in accordance with its terms.
Supporting quotations
Australia.
The following Regional Terms apply for Users in Australia.
5.1 Security Interest.
The Reserve Notice, read together with the terms of Section 3.3 (Reserve), shall be taken to constitute a separate security agreement for the purpose of the Personal Property Securities Act 2009 (Cth) which will take effect on and from the date the Reserve Notice is delivered in accordance with its terms.
Qualifications & exceptions
Applies to Users in Australia.
Effective from delivery of the Reserve Notice in accordance with its terms.
Not stated here
The statute is cited by name only; its text and consequences are not supplied.
Charges & Financial Obligations · Company commitment
Australia: if Stripe requires a guarantee or letter of credit, it gives you reasonable notice to provide it
For Users in Australia, if Stripe requires a guarantee or letter of credit under the Credit Support Requirement, Stripe will give the User reasonable notice to satisfy the requirement. This adds a timing commitment to the general rule that Stripe may suspend or terminate access if the requirement is not met.
Supporting quotations
5.2 Credit Support Requirement.
If Stripe requires a guarantee or letter of credit, Stripe will provide User with reasonable notice to satisfy the requirement.
Qualifications & exceptions
Applies to Users in Australia.
Supplements Section 3.5 (Credit Support Requirement), which otherwise sets no notice period.
Not stated here
What counts as reasonable notice is not defined.
Legal Rights & Agreement Rules · Context
Brazil: Stripe is not a bank, lender, e-money issuer or payment-account provider; a Stripe Account is neither account
For Users in Brazil, Stripe states that it is not a bank and does not accept bank deposits, provide loans or extend credit; it is also not an e-money issuer and does not offer payment accounts, as those terms are defined under Brazilian Law. A Stripe Account is not a deposit account or a payments account as defined under Brazilian Law.
Supporting quotations
Brazil.
The following Regional Terms apply for Users in Brazil.
5.1 Stripe’s Status.
Stripe is not a bank and does not accept bank deposits, provide loans or extend credit. Stripe is also not an e-money issuer and does not offer payment accounts (as those terms are defined under Brazilian Law). A Stripe Account is not a deposit account or a payments account (as defined under Brazilian Law).
Qualifications & exceptions
Applies to Users in Brazil; the terms are as defined under Brazilian Law.
Account & Service Control · Restriction or exception
Brazil: you warrant no User Entity acts as a Subacquirer or Closed-Loop Network; breach allows immediate suspension
For Users in Brazil, the User warrants that no User Entity uses or will use the Services in Brazil as a Subacquirer, or as a Closed-Loop Network with an interoperability agreement with the Card Networks, both as defined by the Brazilian Central Bank's Resolution No. 150 of October 6, 2021 or any other meaning the Central Bank adopts. If Stripe allows Subacquirer use, the User must notify Stripe at least 5 days before acting as one; if Stripe allows Closed-Loop Network use, the User must enter into additional written agreements with Stripe and the Card Networks. Using the Services in breach of this section lets Stripe immediately suspend or terminate the User's access.
Supporting quotations
5.2 Subacquirer Activities; Closed Loop Networks.
User warrants that no User Entity is using or will use the Services in Brazil in the capacity of a Subacquirer. If Stripe allows User to use the Services in Brazil in the capacity of a Subacquirer, then User must notify Stripe at least 5 days before acting as a Subacquirer in Brazil.
User warrants that no User Entity is using or will use the Services in Brazil in the capacity of a Closed-Loop Network with an interoperability agreement with the Card Networks. If Stripe allows User to use the Services in Brazil in the capacity of a Closed-Loop Network, then User must enter into additional written agreements with Stripe and Card Networks.
If User uses the Services in breach of this section, then Stripe may immediately suspend or terminate User’s access to the Services.
Qualifications & exceptions
Applies to Users in Brazil.
Both roles require Stripe's permission; Subacquirer use also requires 5 days' advance notice and Closed-Loop use requires further written agreements.
The Central Bank resolution is cited by name; its text is not supplied.
Charges & Financial Obligations · Restriction or exception
Brazil: Stripe funds or tops up a Reserve only from money you provide or money it owes you for Transactions
For Users in Brazil, if Stripe establishes a Reserve under Section 3.3, it may fund and replenish the Reserve through funds the User provides on Stripe's request or funds Stripe owes the User for Transactions accepted through the Stripe Payments Services. Unlike the general rule in Section 3.3(c), debiting the User Bank Accounts is not listed.
Supporting quotations
5.3 Reserve.
If Stripe establishes a Reserve under Section 3.3 (Reserve), Stripe may fund and replenish the Reserve through any or all of: (i) using funds User provides upon Stripe’s request; or (ii) using funds that Stripe owes to User for Transactions that User accepts through the Stripe Payments Services.
Qualifications & exceptions
Applies to Users in Brazil and replaces the general three-source funding rule.
Account & Service Control · Procedure
Brazil: you must tell Stripe if anyone associated with you or your account is or was a politically exposed person
For Users in Brazil, the User must notify Stripe if any of its representatives, beneficial owners, principals or other individuals associated with the User or its Stripe Account is or was a politically-exposed person as defined under Brazilian Law.
Supporting quotations
5.4 Politically Exposed Persons.
User must notify Stripe if any of User’s representatives, beneficial owners, principals, and other individuals associated with User or User’s Stripe Account is or was a “politically-exposed person” as defined under Brazilian Law.
Qualifications & exceptions
Covers current and former status ('is or was').
The definition comes from Brazilian Law, not supplied.
Not stated here
No deadline for the notification is stated.
Sharing & Disclosure · Restriction or exception
Brazil: you may pledge card receivables only as Law allows; Stripe shares related data with registration offices
For Users in Brazil, Payment Card Receivables are card receivables from card charges that Stripe captures, processes and settles on the User's behalf. The User may grant or assign a lien on or interest in them to a third party only as Law authorizes; if it does, further conditions apply. In accordance with Law, Stripe will share data related to Payment Card Receivables with Card Receivables Registration Offices. The User must tell Stripe about any negotiation of Payment Card Receivables with third-party beneficiaries that are non-financial institutions within 10 business days of the negotiation starting, and must give Stripe accurate and complete information about those negotiations. Stripe's role in communicating with the registration offices continues in the next clause.
Supporting quotations
5.5 Lien or Interest in Payment Card Receivables.
“Payment Card Receivables” means card receivables generated from card charges that Stripe captures, processes and settles on User’s behalf. User may only grant or assign to any third party a lien on or interest in Payment Card Receivables as authorized by Law. If User does so, then the following applies:
In accordance with Law, Stripe will share data related to Payment Card Receivables with Card Receivables Registration Offices. User must inform Stripe about any negotiation with third party beneficiaries that are non-financial institutions related to Payment Card Receivables within 10 business days from the start of the negotiation. User must provide Stripe with accurate and complete information related to the negotiations of Payment Card Receivables.
Qualifications & exceptions
Applies to Users in Brazil.
Liens or interests may be granted only as authorized by Law.
The 10-business-day notice applies to negotiations with non-financial-institution beneficiaries.
Not stated here
Which Law governs the registration and sharing is not named.
Sharing & Disclosure · Company practice
Brazil: Stripe manages dealings with card-receivables registration offices on opt-ins, releases and contestations
For Users in Brazil, a Card Receivables Registration Office is any competent Payment Card Receivables registration office in Brazil. Stripe will manage communication with the appropriate offices on three matters: third-party requests to access, or to stop accessing, information about the User's Payment Card Receivables preferences (opt-in and opt-out); release of assignments or encumbrances, including those tied to a Promessa de Cessão or similar contract; and measures associated with contestations.
Supporting quotations
“Card Receivables Registration Office” means any competent Payment Card Receivables registration office in Brazil. Stripe will manage communication with the appropriate Card Receivables Registration Offices related to (i) requests from third parties to access or refrain from accessing information about User’s Payment Card Receivables preferences (opt-in, opt out); (ii) release of assignments or encumbrances, including those associated with a Promessa de Cessão or similar contracts; and (iii) measures associated with contestations.
Qualifications & exceptions
Applies to Users in Brazil who have granted a lien or interest in Payment Card Receivables (Section 5.5).
Not stated here
The procedures of the registration offices themselves are governed by Brazilian Law, not supplied.
Charges & Financial Obligations · Procedure
Brazil: you must register and maintain a Domicile Institution; Stripe may hold settlements if it becomes insolvent
For Users in Brazil, the Domicile Institution is the financial or payment institution holding the User Bank Account to which the User transfers funds received from Customers. The User must register that account with a Domicile Institution, keep the registration current and notify Stripe of any change. If the registered institution becomes subject to an Insolvency Event, the User must regularize it or register a new Domicile Institution within 10 business days of becoming aware, and Stripe may withhold settlement transfers for Transactions until it receives confirmation that a new valid Domicile Institution is registered or the existing one is regularized.
Supporting quotations
5.6 Domicile Institution.
“Domicile Institution” means the financial institution or payment institution where User holds its User Bank Account. User will register its User Bank Account with a Domicile Institution to which User transfers funds User receives from Customers. User is responsible for maintaining User’s Domicile Institution registration current.
If the bank or financial institution registered as User’s Domicile Institution becomes the subject of an Insolvency Event, User must arrange for its regularization or register with a new Domicile Institution within 10 business days from the day User becomes aware of the Insolvency Event. Stripe may withhold any transfer of settlement funds for Transactions until we receive confirmation that User has registered with a new valid Domicile Institution, or has regularized the existing Domicile Institution. User must notify Stripe if User changes its Domicile Institution.
Qualifications & exceptions
Applies to Users in Brazil.
The 10-business-day period runs from the day the User becomes aware of the Insolvency Event.
Withholding of settlement funds is permitted ('may') until confirmation is received.
Data Access & Collection · Permission or license
Brazil: you authorize Stripe to audit any information you provided, with full access to where it is stored
For Users in Brazil, the User authorizes Stripe to audit any information or document the User provided, directly or through third parties, and to have full access to any physical or digital places or environments where that information or those documents are stored.
Supporting quotations
5.7 User Information Audit.
User authorizes Stripe to audit any information or document provided, directly or through third parties, allowing for full access to any physical or digital places or environments where the information or documents are stored.
Qualifications & exceptions
Applies to Users in Brazil.
The authorization covers information provided directly or through third parties and extends to physical and digital storage locations.
Not stated here
No notice, frequency or scope limit for audits is stated.
Charges & Financial Obligations · Company practice
Brazil: if you cease to exist or die, Stripe pays out only to a documented legal successor or beneficiary
For Users in Brazil, if the User no longer exists because of termination or death, Stripe will carry out any payouts due only in favor of the User's legal successor or another legal beneficiary, as shown by proper legal documentation sent to Stripe by the User or the User's legal representative.
Supporting quotations
5.8 Legal Successor.
If User no longer exists due to termination or death (as applicable), Stripe will only carry out any due payouts in favor of User’s legal successor or any other legal beneficiary, as evidenced by the proper legal documentation sent to Stripe by User or User’s legal representative.
Qualifications & exceptions
Applies to Users in Brazil.
Payouts depend on proper legal documentation being sent to Stripe.
Not stated here
What documentation Stripe treats as proper is not specified.
Charges & Financial Obligations · Restriction or exception
Canada: Stripe holds your funds in trust as trustee as Law requires, except funds it moves into a Reserve
For Users in Canada, in addition to the holding-of-funds rules in Section 3.1 and as Law requires, Stripe safeguards the funds it holds for the User in trust, as trustee, and the User appoints Stripe as trustee for that limited purpose. If Stripe uses safeguarded funds to fund a Reserve, those funds are no longer safeguarded on the User's behalf.
Supporting quotations
Canada.
The following Regional Terms apply for Users in Canada.
5.1 Safeguarding of Funds.
In addition to the further provisions on holding of funds in Section 3.1 (Holding of Funds), as required by Law, Stripe safeguards funds Stripe holds for User in trust, as trustee, and User appoints Stripe as trustee for such limited purpose. However, if Stripe uses safeguarded funds to fund a Reserve, then Stripe will no longer safeguard those funds on User’s behalf.
Qualifications & exceptions
Applies to Users in Canada.
The trust is for the limited purpose of safeguarding, as required by Law.
Funds used to fund a Reserve leave the safeguarding arrangement.
Not stated here
The safeguarding Law that applies is not named.
Legal Rights & Agreement Rules · Procedure
Canada: Code complaints go to Stripe Complaints, acknowledged in 5 and resolved or explained in 20 business days
For Users in Canada, the Financial Consumer Agency of Canada (FCAC) has established a Code of Conduct for the Payment Card Industry in Canada, available on its website. Stripe has a process for potential Code violations: a User with a complaint about an element of the Code is asked to submit it to Stripe Complaints with the requested information and identify which of the thirteen Code elements (or the complaint-handling process itself) it concerns. Stripe will acknowledge receipt within 5 business days and will either resolve the complaint within 20 business days of receipt or explain why it has not been resolved in that time. If the complaint remains unresolved after this process, the User may contact the FCAC by phone or email.
Supporting quotations
5.2 Code of Conduct, Complaint Handling Disclosure.
The Financial Consumer Agency of Canada (the “FCAC”) has established a Code of Conduct for the Payment Card Industry in Canada (the “Code”), a copy of which is available at the
Stripe has established a process for managing potential Code compliance violations. If User has a complaint about a particular element of the Code, User is asked to submit User’s complaint to
Element 1: Transparency and Disclosure by Acquirers and Downstream Participants; Element 2: Notice to Acquirers of PCNO Core Fee Changes; Element 3: Ability to Cancel Agreements without Penalty
Element 13: Branding of Cards; or the Code Complaint Handling Process.
Stripe will acknowledge receipt of User’s email within 5 business days of receipt in accordance with the Code. Stripe will either resolve the complaint within 20 business days of receipt of User’s email, or provide User information as to why it has not been resolved within that period.
If User’s complaint has not been resolved after following this process, User may contact the Financial Consumer Agency of Canada by calling 1-866-461-3222 or emailing info@fcac-acfc.gc.ca.
Qualifications & exceptions
Applies to Users in Canada and to complaints about elements of the Code.
The 20-business-day commitment is to resolve or to explain why not, not to resolve in every case.
Not stated here
The Code's text is linked but not supplied.
Account & Service Control · User right or choice
Canada: you are bound when you accept at account setup and may close your account at any time for free
For Users in Canada, the User is bound by the Agreement when it accepts it while setting up its Stripe Account. Unless the User and Stripe agree otherwise in writing, the User may close its Stripe Account and terminate the Agreement at any time, with no fee for doing so. Pricing is on the linked Stripe Pricing Page.
Supporting quotations
User is bound by this Agreement when User accepts it as part of setting up User’s Stripe Account. Unless otherwise agreed in writing between User and Stripe, User may close User’s Stripe Account and terminate this Agreement at any time, and there is no fee to do so.
Qualifications & exceptions
Applies to Users in Canada.
A written agreement between the User and Stripe can displace the free, any-time closure right.
Not stated here
The Pricing Page is linked but not supplied.
Whether closure ends obligations already accrued is governed by the General Terms, not supplied.
Charges & Financial Obligations · Restriction or exception
Québec: the security interest is a hypothec held by Stripe as hypothecary representative under Québec law
For Users located in the Province of Québec, the security interest in Section 3.4 is instead called a hypothec. Stripe acts as hypothecary representative under the Civil Code of Québec on behalf of the Secured Parties to receive and hold it. The User consents to the Collateral securing the Secured Obligations and agrees that the Collateral constitutes monetary claims under the Civil Code, that Québec law governs the validity, publication and effects of publication of the hypothec regardless of any account documentation or other agreement, and that Stripe as hypothecary representative has control over those monetary claims in the manner the Civil Code provides.
Supporting quotations
For Users located in the Province of Québec, the security interest referred to in Section 3.4 (Security Interest) is instead referred to as a hypothec. Stripe acts as hypothecary representative as contemplated in the Civil Code of Québec on behalf of the Secured Parties in order to receive and hold such hypothec.
the laws of the Province of Québec are applicable to and govern the validity, publication and effects of publication of the hypothec on the Collateral, and (b) Stripe, in its capacity as hypothecary representative, has control over the monetary claims comprised in the Collateral in the manner provided for in the Civil Code of Québec.
Qualifications & exceptions
Applies to Users located in the Province of Québec.
A regional restatement of Section 3.4 (Security Interest); the Collateral and Secured Obligations are as defined there.
Not stated here
The Civil Code of Québec is cited by name; its text is not supplied.
Account & Service Control · Restriction or exception
Hong Kong: you warrant you are the entity using the Services, act for no one else and gave no one account rights
For Users in Hong Kong, the User represents and warrants that it is the entity accessing and using the Services, that it is not entering into the Agreement on behalf of or for any other entity, and that it has not granted any rights in its Stripe Account to any other entity.
Supporting quotations
Hong Kong.
The following Regional Terms apply for Users in Hong Kong.
5.1 Specific Representations and Warranties.
User represents and warrants that User is the entity accessing and using the Services, is not entering into this Agreement on behalf of or for any other entity, and has not granted any rights in the Stripe Account to any other entity.
Qualifications & exceptions
Applies to Users in Hong Kong.
Legal Rights & Agreement Rules · Context
Hong Kong: no deposit account, stored value facility or money service; your balance only reflects Transactions
For Users in Hong Kong, Stripe does not provide a deposit account, offer a stored value facility or operate a money service. References to funds or a balance held in the User's Stripe Account reflect only Transactions that Stripe has processed for the User.
Supporting quotations
5.2 No Deposit Account, Stored Value Facility or Money Service.
Stripe does not provide User a deposit account, offer User a stored value facility, or operate a money service. References to the funds or balance held in User’s Stripe Account reflect Transactions that Stripe has processed for User only.
Qualifications & exceptions
Applies to Users in Hong Kong.
Charges & Financial Obligations · Restriction or exception
Hong Kong: the Section 3.4 security interest is taken as a fixed first charge
For Users in Hong Kong, the security interest the User grants under Section 3.4 (Security Interest) is taken by way of a fixed first charge.
Supporting quotations
5.3 Security Interest.
The security interest referred to in Section 3.4 (Security Interest) is taken by way of a fixed first charge.
Qualifications & exceptions
Applies to Users in Hong Kong; otherwise Section 3.4 applies as written.
Charges & Financial Obligations · Company commitment
India, Indonesia and Malaysia: Stripe safeguards the funds it holds for you as Law requires
The Regional Terms for India, Indonesia and Malaysia each contain the same single safeguarding clause: in addition to the holding-of-funds rules in Section 3.1, Stripe safeguards the funds it holds for the User as Law requires. Unlike the EEA, UK and Canada clauses, these three do not state that funds moved into a Reserve stop being safeguarded; whether that follows from the applicable Law is not stated.
Supporting quotations
India.
The following Regional Terms apply for Users in India.
5.1 Safeguarding of Funds.
In addition to the further provisions on holding of funds in Section 3.1 (Holding of Funds), Stripe safeguards funds Stripe holds for User as required by Law.
Indonesia.
The following Regional Terms apply for Users in Indonesia.
5.1 Safeguarding of Funds.
In addition to the further provisions on holding of funds in Section 3.1 (Holding of Funds), Stripe safeguards funds Stripe holds for User as required by Law.
Malaysia.
The following Regional Terms apply for Users in Malaysia.
5.1 Safeguarding of Funds.
In addition to the further provisions on holding of funds in Section 3.1 (Holding of Funds), Stripe safeguards funds Stripe holds for User as required by Law.
Qualifications & exceptions
Applies to Users in India, Indonesia and Malaysia respectively.
Safeguarding is 'as required by Law'; the applicable Law is not named.
Not stated here
Whether Reserve funding affects safeguarding in these countries is not addressed in the text.
Security & Safeguards · Procedure
India: you own your security controls, must match Stripe's baseline standards and must do assessments Stripe requests
For Users in India, the User is responsible for assessing its business's security requirements and for selecting and implementing security procedures and controls appropriate to mitigate its exposure to security incidents. The User must ensure its systems at all times conform to the same baseline technology standards and security controls that apply to Stripe's capacity for providing the Services under applicable Law. Stripe may require the User to undertake comprehensive security assessments or obtain periodic assessment reports, and the User must do so promptly on request.
Supporting quotations
5.2 Security Requirements.
User is responsible for assessing the security requirements of User’s business, and selecting and implementing security procedures and controls appropriate to mitigate User’s exposure to security incidents. User will ensure that its systems will, at all times, conform to the same baseline technology standards and security controls that are applicable to Stripe’s capacity for providing the Services under applicable Law. Stripe may require User to undertake comprehensive security assessments or obtain periodic assessment reports and User will do so promptly upon request.
Qualifications & exceptions
Applies to Users in India.
The baseline is the standards and controls applicable to Stripe under applicable Law, not a stated list.
Not stated here
The specific standards and the frequency of assessments are not identified.
Legal Rights & Agreement Rules · Context
Mexico: Stripe is an aggregator or acquirer under Bank of Mexico rules, not a bank, money transmitter or MSB
For Users in Mexico, Stripe states that it is not a bank, money transmitter or money services business (MSB) and does not accept deposits or offer banking or MSB services as defined by the Credit Institutions Law and the Law for Credit Auxiliary Organizations and Activities. Stripe acts as an aggregator or acquirer under the General Rules Applicable to the Payment Processing Networks published by the Bank of Mexico on March 11, 2014, as amended, and under any other applicable regulation issued by the Bank of Mexico, the National Banking and Securities Commission or another government authority for participants in Mexican payment processing networks.
Supporting quotations
Mexico.
The following Regional Terms apply for Users in Mexico.
5.1 Stripe’s Status as an Aggregator or Acquirer.
Stripe is not a bank, money transmitter, or a money services business (“MSB”) and does not accept deposits or offer banking or MSB services as defined by the Credit Institutions Law (Ley de Instituciones de Crédito), and the Law for Credit Auxiliary Organizations and Activities (Ley General de Organizaciones y Actividades Auxiliares del Crédito). Stripe is acting as an aggregator or acquirer under the terms of the General Rules Applicable to the Payment Processing Networks (Disposiciones de Carácter General Aplicables a las Redes de Medios de Disposición), published by the Bank of Mexico on March 11, 2014, as amended from time to time
Qualifications & exceptions
Applies to Users in Mexico.
The Mexican laws and rules are cited by name; their text is not supplied.
Charges & Financial Obligations · Restriction or exception
Mexico: the Section 3.4 security interest is a first-priority non-possessory pledge under the LGTOC
For Users in Mexico, the User grants the security interest described in Section 3.4 (Security Interest) in accordance with Section Sixth of Title Second of the General Law of Negotiable Instruments and Credit Transactions (LGTOC), as a first priority non-possessory pledge.
Supporting quotations
5.2 Security Interest.
For the avoidance of doubt, User grants the security interest as described in Section 3.4 (Security Interest) in accordance with Section Sixth of Title Second of the General Law of Negotiable Instruments and Credit Transactions (Ley General de Títulos y Operaciones de Crédito or “LGTOC”) as a first priority non-possessory pledge.
Qualifications & exceptions
Applies to Users in Mexico; a restatement of Section 3.4 in Mexican legal form.
Not stated here
The LGTOC is cited by name; its text is not supplied.
Charges & Financial Obligations · Context
Mexico: the maximum Fees Stripe charges for payment services are registered with the Bank of Mexico
For Users in Mexico, the maximum amount of Fees Stripe charges for payment services in Mexico is registered with the Bank of Mexico. The clause states where the ceiling is registered; it does not state the amounts.
Supporting quotations
5.3 Maximum Amount of Fees.
The maximum amount of Fees Stripe charges for payment services in Mexico are registered with the Bank of Mexico.
Qualifications & exceptions
Applies to Users in Mexico and to payment services.
Not stated here
The registered maximum amounts are not stated in this document.
Data Access & Collection · Context
Mexico: a regional clause replaces Section 2.3 on the information Stripe obtains about you
For Users in Mexico, Section 5.4 (Information Stripe Obtains) replaces Section 2.3 of the Financial Services Terms entirely, rather than supplementing it. The replacement text, which names Mexican credit reporting agencies, follows in the next clause and is explained there.
Supporting quotations
5.4 Information Stripe Obtains.
This Section replaces Section 2.3 (Information Stripe Obtains).
Qualifications & exceptions
Applies to Users in Mexico.
This is a replacement of Section 2.3, not an addition to it.
Data Access & Collection · Permission or license
Mexico: Stripe may pull your credit and financial history from named bureaus and share it with Stripe Affiliates
For Users in Mexico, replacing Section 2.3, the User authorizes Stripe to retrieve information about the User and its business from Stripe's service providers and other third parties, including Mexican credit reporting agencies (Sociedades de Información Crediticia, including Trans Union de México, S.A. SIC and Dun & Bradstreet, S.A. SIC.), banking partners and information bureaus, and authorizes and directs those third parties to compile and provide it. The information may include the User's or its Representative's name, addresses, credit history, banking relationships, credit report and financial history. Unlike the general clause, the User also authorizes Stripe to share any financial information obtained, including credit report results, with any Stripe Affiliates.
Supporting quotations
User authorizes Stripe to retrieve information about User and User’s business from Stripe’s service providers and other third parties, including credit reporting agencies (Sociedades de Información Crediticia, including Trans Union de México, S.A. SIC and Dun & Bradstreet, S.A. SIC.), banking partners and information bureaus, and User authorizes and directs those third parties to compile and provide that information to Stripe. This information may include User’s, or User’s Representative’s, name, addresses, credit history, banking relationships, credit report, and financial history. User also authorizes Stripe to share any financial information obtained, including the results of the credit reports, with any Stripe Affiliates.
Qualifications & exceptions
Applies to Users in Mexico and replaces Section 2.3 (Information Stripe Obtains).
Adds a credit report to the information list and an express authorization to share the financial information with Stripe Affiliates.
Unlike Section 2.3, no 'for the purposes of this Agreement' purpose limit is stated.
Not stated here
What the Affiliates may do with the shared information is not stated.
Charges & Financial Obligations · Company commitment
New Zealand: if Stripe requires a guarantee or letter of credit, it gives you reasonable notice to provide it
For Users in New Zealand, if Stripe requires a guarantee or letter of credit under the Credit Support Requirement, Stripe will give the User reasonable notice to satisfy the requirement, adding a timing commitment to the general rule in Section 3.5.
Supporting quotations
New Zealand.
The following Regional Terms apply for Users in New Zealand.
5.1 Credit Support Requirement.
If Stripe requires a guarantee or letter of credit, Stripe will provide User with reasonable notice to satisfy the requirement.
Qualifications & exceptions
Applies to Users in New Zealand.
Supplements Section 3.5 (Credit Support Requirement).
Not stated here
What counts as reasonable notice is not defined.
Account & Service Control · Restriction or exception
Japan: individuals who are not businesses can be Users only with Stripe's prior approval
For Users in Japan, individuals that are not businesses, including individuals who are not sole proprietors, are eligible as Stripe Users only if Stripe pre-approves them. This widens the general eligibility rule in Section 2.1, which otherwise requires a business, public body or non-profit.
Supporting quotations
Japan.
The following Regional Terms apply for Users in Japan.
5.1 Additional Eligible Users.
Individuals that are not businesses (including individuals that are not sole proprietors) are only eligible as Stripe Users if pre-approved by Stripe.
Qualifications & exceptions
Applies to Users in Japan.
Eligibility of non-business individuals depends on Stripe's pre-approval.
Not stated here
How pre-approval is requested or granted is not stated.
Account & Service Control · Restriction or exception
Singapore: you warrant you are the entity using the Services, act for no one else and gave no one account rights
For Users in Singapore, the User represents and warrants that it is the entity accessing and using the Services, is not entering into the Agreement on behalf of or for any other entity, and has not granted any rights in its Stripe Account to any other entity. The clause matches the Hong Kong warranty.
Supporting quotations
Singapore.
The following Regional Terms apply for Users in Singapore.
5.1 Specific Representations and Warranties.
User represents and warrants that User is the entity accessing and using the Services, is not entering into this Agreement on behalf of or for any other entity, and has not granted any rights in the Stripe Account to any other entity.
Qualifications & exceptions
Applies to Users in Singapore.
Charges & Financial Obligations · Restriction or exception
Singapore: besides the security interest, Stripe has a self-executing lien over all funds it holds for you
For Users in Singapore, in addition to the Section 3.4 security interest, the User acknowledges that Stripe has a lien over all funds Stripe holds on the User's behalf, including the Collateral, so that Stripe can collect Fees and other amounts the User owes and cover contingent liabilities the User may owe in future under the Agreement. The lien is effective and enforceable without any further steps; if steps are ever required, the User must take them as Stripe requests, even if the request comes after the User's Stripe Account balance has gone negative.
Supporting quotations
5.2 Lien.
In addition to the security interest granted under Section 3.4 (Security Interest), User acknowledges that Stripe also has a lien over all funds Stripe holds on User’s behalf, including the Collateral, for the purpose of enabling Stripe to collect Fees and other amounts User owes and for contingent liabilities User may in the future owe to Stripe under this Agreement. The lien is effective and enforceable without the need for any steps to be taken, but in the event if any such steps are required to be taken for any purposes, User agrees to take all such steps as requested by Stripe, even if the request is made after User’s Stripe Account balance becomes negative.
Qualifications & exceptions
Applies to Users in Singapore and is in addition to the Section 3.4 security interest.
Covers present amounts owed and future contingent liabilities.
Charges & Financial Obligations · Company commitment
Thailand: Stripe safeguards the funds it holds for you as Law requires
For Users in Thailand, in addition to the holding-of-funds rules in Section 3.1, Stripe safeguards the funds it holds for the User as Law requires. Like the India, Indonesia and Malaysia clauses, no Reserve carve-out is stated. A 'Back to Top' navigation link closes the Financial Services Terms.
Supporting quotations
Thailand.
The following Regional Terms apply for Users in Thailand.
5.1 Safeguarding of Funds.
In addition to the further provisions on holding of funds in Section 3.1 (Holding of Funds), Stripe safeguards funds Stripe holds for User as required by Law.
Qualifications & exceptions
Applies to Users in Thailand.
Safeguarding is 'as required by Law'; the Law is not named.
Legal Rights & Agreement Rules · Context
The Payments Terms govern the Stripe Payments Services with the General Terms and Financial Services Terms
The Stripe Payments Terms, last modified September 28, 2026, supplement the General Terms and the Stripe Financial Services Terms; together the three govern use of the Stripe Payments Services, the Services for accepting and refunding Customer payments, performing related financial transactions and managing Customer Disputes. Their Regional Terms, in Section 15 (Regional Terms) of these Payments Terms, apply according to the User's Stripe Account Country. Capitalized terms not defined here take their meaning from the General Terms (not supplied) or the Financial Services Terms.
Supporting quotations
Stripe Payments
Last modified: September 28, 2026
1. Stripe Payments Services.
These terms (“Stripe Payments Terms”) supplement the General Terms and the Stripe Financial Services Terms, which together govern the use of the Stripe Payments Services. The Regional Terms in Section 15 (Regional Terms) of these Stripe Payments Terms apply based on User’s Stripe Account Country.
“Stripe Payments Services” means the Services that enable User to accept and refund Customer payments, perform related financial transactions, and manage Customer Disputes.
Qualifications & exceptions
Regional Terms in Section 15 apply based on the User's Stripe Account Country.
The General Terms are a separate, unsupplied document.
Not stated here
The 'Section 15' reference is read as Section 15 (Regional Terms) of these Payments Terms; numbering restarts in each set of Service Terms.
Account & Service Control · Restriction or exception
You alone are responsible for your goods, customer support, receipts and verifying each Customer
The User is solely responsible for the nature and quality of the goods and services it provides (or, for donations, their intended use) and for supporting Customers on all issues related to its goods, services and business, including delivery, refunds, returns and ancillary services. The User must give each Customer a complete and accurate receipt for every Transaction; if Stripe or an Affiliate, acting as the User's agent, gives a Customer a receipt, that receipt binds the User. The User is also solely responsible for verifying each Customer's identity, determining the Customer's eligibility and authority to transact, and all other issues related to its business.
Supporting quotations
2. User’s Business.
User is solely responsible for (a) the nature and quality of the goods and services User provides (or if User accepts donations, the intended use of those donations); and (b) providing support to Customers regarding all issues related to User’s goods and services and business activities, including delivery, refunds, returns, and for all other ancillary services User provides to Customers.
User must offer each Customer a complete and accurate receipt for each Transaction. If, in the capacity as User’s agent, Stripe or its Affiliate provides a Customer with a receipt for a Transaction, that receipt is binding on User. User is solely responsible for verifying each Customer’s identity, determining a Customer’s eligibility and authority to complete a Transaction, and all other issues related to User’s goods and services and business activities.
Qualifications & exceptions
A receipt issued by Stripe or its Affiliate as the User's agent is binding on the User.
Legal Rights & Agreement Rules · Restriction or exception
Submitting a Transaction accepts the Payment Method Rules and Terms, which are Financial Provider Terms
The User may accept payment from Customers through various Payment Methods by submitting Transactions to Stripe through the Stripe Technology. It must comply with each Payment Method's acceptance and use requirements, which may be built into the Stripe API and other Stripe Technology as described in the Documentation, or set out in the Payment Method Rules, the Payment Method Terms (terms on the Stripe Website, including the Stripe Legal Page, described there as 'Payment Method Terms'), or both. Using the Stripe Payments Services to accept a Payment Method or submit a Transaction counts as acceptance of the applicable Rules and Terms. Both are Financial Provider Terms, so under the Financial Services Terms they prevail over the Agreement where inconsistent and may change over time.
Supporting quotations
3. Payment Methods and Transactions; Payment Method Rules and Payment Method Terms.
3.1 Acceptance and Use Requirements.
User may accept payment from Customers using various Payment Methods by submitting Transactions to Stripe through the Stripe Technology. User must comply with Payment Method acceptance and use requirements which may be incorporated into the Stripe API and other Stripe Technology described in the Documentation, or set out in the Payment Method Rules, the Payment Method Terms, or both. Using the Stripe Payments Services to accept a Payment Method or submit a Transaction constitutes User’s acceptance of the applicable Payment Method Rules and Payment Method Terms. Payment Method Rules and Payment Method Terms are Financial Provider Terms for purposes of this Agreement.
“Payment Method Terms” means terms that apply to User’s acceptance and use of a Payment Method, located on or accessible from the Stripe Website, including on the Stripe Legal Page, and which as of the Effective Date are described on that page as “Payment Method Terms.”
Qualifications & exceptions
Acceptance of the Rules and Terms happens by use, not by a separate signature.
As Financial Provider Terms, they prevail over conflicting Agreement provisions and can be amended (Financial Services Terms Section 2.4).
Not stated here
The Payment Method Rules and Payment Method Terms are external documents not supplied here.
Legal Rights & Agreement Rules · Restriction or exception
Some card networks require Acquirer Terms, a direct contract you accept by submitting Transactions
Some Payment Method Providers require that their Payment Methods be accepted only through a Payment Method Acquirer, which may be Stripe, a Stripe Affiliate or a Financial Provider. Some, such as Visa and Mastercard in certain countries, require the User to enter into Acquirer Terms, which identify the acquirer responsible for Transactions with that Payment Method, create a direct contractual relationship between the User and the acquirer, and may include additional agreements the User must accept. Acquirer Terms are Financial Provider Terms; they state which Payment Methods they cover and when they take effect. By using the Stripe Payments Services to submit certain Card Network Transactions, the User agrees to the Acquirer Terms of the applicable acquirers listed on the Acquirer Disclosure on the Stripe Legal Page.
Supporting quotations
3.2 Acquirer Terms.
Some Payment Method Providers require that their Payment Methods be accepted only through a Payment Method Acquirer, which may be Stripe, a Stripe Affiliate, or a Financial Provider. Some of these Payment Method Providers, such as Visa and Mastercard in certain countries, require User to enter into Acquirer Terms, which (a) will identify the Payment Method Acquirer responsible for Transactions using that Payment Method Provider’s Payment Method, (b) will establish a direct contractual relationship and terms between User and the Payment Method Acquirer, and (c) may include additional agreements that User must accept in order to accept Transactions via that Payment Method Acquirer, as those Acquirer Terms further describe.
By using the Stripe Payments Services to submit certain Card Network Transactions, User agrees to the Acquirer Terms for the applicable Payment Method Acquirers, if any, listed on the
“Acquirer Disclosure” means information on applicable Payment Method Acquirers, which is accessible from the Stripe Legal Page.
“Acquirer Terms” means the terms that a Payment Method Acquirer has specified that apply to that Payment Method Acquirer’s services, located on or accessible from the Stripe Legal Page.
“Payment Method Acquirer” means an entity that a Payment Method Provider has authorized to (a) sponsor or submit Transactions at the request of merchants to the Payment Method Provider for authorization and clearing; and (b) receive and remit settlement funds for authorized and cleared Transactions.
Qualifications & exceptions
Applies only where a Payment Method Provider requires acceptance through a Payment Method Acquirer and Acquirer Terms.
Agreement is by submitting the relevant Card Network Transactions, not a separate signature.
Not stated here
The Acquirer Terms and the Acquirer Disclosure are on the Stripe Legal Page and not supplied; which acquirers apply in which countries is not stated here.
Legal Rights & Agreement Rules · Company practice
Payment Method Providers can enforce the Agreement against you and end your access to a method at any time
Payment Method Providers and Payment Method Acquirers are Financial Providers. A Payment Method Provider may enforce the Agreement directly against the User with respect to its own Payment Methods. A Provider or Acquirer may terminate the User's ability to accept a Payment Method at any time and for any reason, after which the User can no longer accept that method under the Agreement. Stripe may add or remove Providers or Acquirers at any time and, with notice to the User, may change the Payment Methods in the User's integration.
Supporting quotations
3.3 Payment Method Providers and Payment Method Acquirers.
Payment Method Providers and Payment Method Acquirers are Financial Providers. Payment Method Providers may enforce the terms of this Agreement directly against User with respect to that Payment Method Provider’s Payment Method(s). A Payment Method Provider or Payment Method Acquirer may terminate User’s ability to accept a Payment Method at any time and for any reason, in which case User will no longer be able to accept that Payment Method under this Agreement. Stripe may add or remove Payment Method Providers or Payment Method Acquirers at any time. Stripe may, with notice to User, change Payment Methods in User's integration of the Services.
Qualifications & exceptions
Termination by a Provider or Acquirer needs no reason.
Stripe's change to the Payment Methods in the User's integration comes with notice; adding or removing Providers or Acquirers does not require notice under this clause.
Not stated here
The form and timing of Stripe's notice for integration changes are not stated.
Legal Rights & Agreement Rules · Restriction or exception
You must follow the card network rules, which can change without notice, and may not split one sale into several charges
When accepting payment card Transactions, the User must comply with all applicable Card Network Rules, the Payment Method Rules published by a Card Network (Visa, Mastercard, American Express, Discover and others), including the linked Visa Rules, Mastercard Rules and American Express Merchant Operating Guide. The User must not split payment for a single transaction into multiple Transactions except where the Payment Method Rules, Payment Method Terms and Acquirer Terms expressly permit it. Each Card Network may amend its rules at any time without notice to the User.
Supporting quotations
3.4 Card Transactions.
When accepting payment card Transactions, User must comply with all applicable Card Network Rules, including the
User must not split payment for a single transaction into multiple Transactions except as the Payment Method Rules, Payment Method Terms and Acquirer Terms expressly permit. Each Card Network may amend its Card Network Rules at any time without notice to User.
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
“Card Network Rules” means the Payment Method Rules published by a Card Network.
Qualifications & exceptions
Splitting is allowed only where the Rules, Terms and Acquirer Terms expressly permit it.
Card Network Rules can change at any time without notice to the User.
Not stated here
The Card Network Rules are linked external documents, not supplied.
Account & Service Control · Restriction or exception
Accept cards only where authorized, disclose your name, address and country up front, never act as a facilitator
The User may accept payment card Transactions only in locations authorized by Stripe and the applicable Card Network; the Card Networks may request location information and certification and make the final determination of the User's location. Before Customers are prompted for card details, the User must prominently and clearly disclose its name, address and country, and must ensure Customers understand the User is responsible for the Transactions. The User must not act as, or hold itself out as, a payment facilitator, intermediary or aggregator, or otherwise resell the Stripe Payments Services.
Supporting quotations
User may only accept payment card Transactions in locations authorized by Stripe and the applicable Card Network. The Card Networks may request information and certification relating to User’s location, and make a final determination of User’s location. User must prominently and clearly disclose User’s name, address, and country location to Customers before Customers are prompted to provide payment card information. User must ensure that Customers understand that User is responsible for the Transactions. User must not act as or hold itself out as a payment facilitator, intermediary or aggregator, or otherwise resell the Stripe Payments Services.
Qualifications & exceptions
Location authorization comes from both Stripe and the Card Network, with the Card Networks making the final location determination.
The disclosure must come before Customers are prompted to provide card information.
Charges & Financial Obligations · Restriction or exception
No cash refunds or cash-outs on card payments without Law or Stripe approval, and no cards to collect bad debt
For completed Transactions made with a payment card, the User must not give cash refunds unless Law requires it, must not use the Stripe Payments Services for cash disbursements or purchases of cash vouchers without Stripe's approval, and must not let Customers use payment cards to disburse cash to a third party except to the extent the Card Network Rules permit. The User must also not accept card Transactions to collect or refinance debt it has deemed uncollectible or that is uncollectible by Law, to pay previous card charges, or to collect a dishonored check; debt repayment is allowed only in compliance with the Card Network Rules.
Supporting quotations
User must not provide cash refunds for a completed Transaction made with a payment card, unless required by Law. User must not use Stripe Payments Services for any transaction for a cash disbursement or purchase of cash vouchers without approval from Stripe. User must not permit Customers to use payment cards to disburse cash to a third party, except to the extent the Card Network Rules permit.
User must not accept payment card Transactions (i) to collect or refinance existing debt that User has deemed uncollectible or that is uncollectible by Law; (ii) for previous card charges; or (iii) to collect a dishonored check. Debt repayment is only permitted when performed in compliance with the Card Network Rules.
Qualifications & exceptions
Cash refunds are allowed where Law requires them; cash disbursements need Stripe's approval; third-party cash disbursement is allowed only to the extent the Card Network Rules permit.
Debt repayment by card is permitted only when performed in compliance with the Card Network Rules.
Charges & Financial Obligations · Restriction or exception
No surcharges, fees or Taxes for card acceptance unless the Card Network Rules or Law permit, with conditions
The Card Network Rules limit the User's ability to discriminate by payment card brand or type and to charge surcharges, other fees or Taxes for accepting payment cards. Except to the extent the Card Network Rules or Law permit, the User must not charge any surcharge, fee or Taxes for card acceptance. Where surcharging is permitted, the User must comply with all notice or registration requirements imposed by Stripe, a Payment Method Provider or another Financial Provider, and must collect surcharge amounts only as part of the submitted Transaction amount.
Supporting quotations
The Card Network Rules limit User’s ability to (i) discriminate by payment card brand or type and (ii) charge surcharges or other fees, or Taxes for acceptance of payment cards. Except to the extent the Card Network Rules or Law permits, User must not charge surcharges, other fees, or Taxes for accepting payment cards.
If surcharging is permitted, User must comply with all applicable notice or registration requirements imposed by Stripe or a Payment Method Provider or other Financial Provider and must collect surcharge amounts only as part of the submitted amount of the Transaction.
Qualifications & exceptions
Surcharging is allowed only to the extent the Card Network Rules or Law permit.
Permitted surcharges must follow notice or registration requirements and be collected within the submitted Transaction amount.
Not stated here
Which jurisdictions or networks permit surcharging is not stated here.
Security & Safeguards · Restriction or exception
Use card numbers only for Transactions, within Law and network rules; never store the security code after authorization
The User must not request or use a payment card account number for any purpose other than a Transaction, and may use card account numbers and card Transaction data only in compliance with Law, the Card Network Rules and the Agreement. The User must not store the card verification value or similar security code after the card has been authorized. These details are among the Payment Method Account Details the PCI Standards require to be protected, which may include the Customer's name, account number, expiration date and security code.
Supporting quotations
User must not request or use a payment card account number for any purpose other than for a Transaction. User may only use payment card account numbers and payment card Transaction data in compliance with Law, the Card Network Rules and this Agreement. User must not store the card verification value (or similar security code) data after card authorization.
“Payment Method Account Details” means the Payment Method account details for a Customer that the PCI Standards require to be protected, which may include the Customer’s name, and with respect to credit and debit cards, the Customer’s account number, card expiration date, and card verification value or similar security code.
Qualifications & exceptions
The purpose limit is strict: card account numbers may be requested or used only for a Transaction.
The storage ban covers the card verification value or similar security code after authorization.
Legal Rights & Agreement Rules · Restriction or exception
You may not make Customers waive their right to dispute a charge, and may not disparage or harm a Card Network
The User must not require a Customer, as a condition of accepting their card, to waive the right to dispute a Transaction; a Dispute is a Customer-initiated instruction to reverse or invalidate a processed Transaction, including what Payment Method Providers call chargebacks. The User must also not disparage any Card Network or its services, or submit any Transaction that harms a Card Network.
Supporting quotations
User must not require, as a condition to card acceptance, a Customer to waive a right to dispute a Transaction.
User must not disparage any Card Network or any of their services, or submit any Transaction that harms any Card Network.
“Dispute” means an instruction a Customer initiates to reverse or invalidate a processed Transaction (including “chargebacks” and “disputes” as those terms may be used by Payment Method Providers).
Qualifications & exceptions
The waiver ban applies to conditions of card acceptance.
Not stated here
What conduct counts as disparaging or harming a Card Network is not defined.
Security & Safeguards · Procedure
Cooperate fully with Card Network audits and investigations, even after termination, and meet their security programs
A Card Network may initiate audits and forensic investigations under its Card Network Rules, and the User must fully cooperate with them; this duty survives termination of the Agreement. The User must also comply with the Card Networks' security standards, requirements and programs, such as the Visa Account Information Security Program, and with all Card Network Rules governing the privacy, protection, use, storage and disclosure of data.
Supporting quotations
A Card Network may initiate audits and forensic investigations in accordance with its Card Network Rules. User must fully cooperate with these audits and forensic investigations. This subsection (i) will survive termination of this Agreement.
User must comply with the Card Networks’ security standards, requirements and programs (e.g., the Visa Account Information Security Program), and all Card Network Rules governing the privacy, protection, and User’s use, storage and disclosure of data.
Qualifications & exceptions
The audit-cooperation duty survives termination of the Agreement.
Security obligations are those set by the Card Networks, not a list in this document.
Not stated here
The content of the security programs and Card Network Rules is external and not supplied.
Account & Service Control · Restriction or exception
Networks may limit which cards you take; no minimums or maximums, no exposed-detail mail forms, show accepted cards
Each Card Network may allow the User to accept only a subset of its cards, in which case the User must follow the Card Network Rules on limited acceptance. The User must not set minimum or maximum amounts for payment card Transactions except as the Card Network Rules permit. The User must not require a Customer to complete a form that, when mailed, shows the Customer's signature or Payment Method Account Details in plain view. If the User accepts payment cards, it must say so wherever it tells Customers which Payment Methods it accepts, including on its website.
Supporting quotations
Each Card Network may allow User to accept only a subset of that Card Network’s cards, in which case User must comply with the Card Network Rules that govern limited acceptance.
User must not establish minimum or maximum amounts for payment card Transactions, except as the Card Network Rules permit.
User must not require any Customer to complete a form that includes the Customer’s signature or any Payment Method Account Details displayed in plain view when mailed.
If User accepts payment cards, then User must indicate that fact wherever User informs its Customers of the Payment Methods User accepts, including on User’s website.
Qualifications & exceptions
Minimum or maximum amounts are allowed only as the Card Network Rules permit.
Charges & Financial Obligations · Procedure
Estimated-amount authorizations need prior Customer consent, prompt capture and a new authorization if the total grows
If the User wants to obtain authorization for an estimated Transaction amount, it must get the Customer's consent to the estimated amount before requesting the authorization. As soon as the User knows the full amount to capture, it must submit the capture request. If the full charge exceeds the authorized amount, the User must obtain a new authorization for the full amount.
Supporting quotations
If User wishes to obtain authorization for the estimated amount of a Transaction, User must obtain its Customer’s consent to the estimated amount before requesting the authorization. As soon as User becomes aware of the full amount to be captured, User must submit the request to capture funds. If the full amount of the charge exceeds the amount for which User obtained an authorization, User must obtain a new authorization for the full amount.
Qualifications & exceptions
Consent must precede the authorization request.
A higher final amount requires a new authorization, not an adjustment of the old one.
Charges & Financial Obligations · Company practice
Above its volume threshold, American Express may make you a direct merchant with its own agreement and pricing
This clause applies only to the American Express Card Network. If the User's American Express Transaction volume exceeds the threshold American Express sets, American Express may convert the User to a direct American Express merchant. The User and American Express would then enter into a separate agreement governing acceptance of American Express cards and agree directly on pricing and other fees for processing. Stripe would continue to process the User's American Express Transactions under this Agreement, incorporating the new pricing and fees into the applicable Stripe fees.
Supporting quotations
3.5 American Express Conversion – Only Applicable to the American Express Card Network.
If User’s American Express Transaction volume exceeds the applicable threshold amount set by American Express, American Express may convert User to a direct American Express merchant. As a direct American Express merchant, User and American Express will enter into a separate agreement, which will govern User’s acceptance of American Express payment cards, and User and American Express must directly agree to User’s pricing and other fees payable for American Express Transaction processing. Stripe will continue to process User’s American Express Transactions in accordance with this Agreement, except that Stripe will incorporate the new pricing and fees into the applicable Stripe fees.
Qualifications & exceptions
Applies only to the American Express Card Network and only above a threshold set by American Express.
Conversion is at American Express's option ('may').
Not stated here
The threshold amount is set by American Express and not stated here.
Sharing & Disclosure · Company practice
Stripe may share your account data, including Protected Data, with payment providers; you waive claims over it
Stripe may share information about the User's Stripe Account, including User Information, with Payment Method Providers and Payment Method Acquirers as it believes necessary to verify the User's eligibility for the Stripe Payments Services, set up accounts or credit with Financial Providers, monitor Transactions and other activity, run risk management and compliance reviews, and take other actions needed to provide the Services. Stripe may also share data, including Protected Data, with Financial Providers, who may use and share it to manage a Dispute, assess the User's compliance with Financial Provider Terms, and support compliance with Law, Payment Method Rules and Payment Method Terms. The User waives any claim against Stripe arising from such sharing about the User Group, including being placed on a terminated merchant list as a result. Stripe may periodically review the User's account information to verify eligibility.
Supporting quotations
Stripe may share information about User’s Stripe Account, including User Information, with Payment Method Providers and Payment Method Acquirers as Stripe believes necessary to verify User’s eligibility to use the Stripe Payments Services, establish any necessary accounts or credit with Financial Providers, monitor Transactions and other activity, conduct risk management and compliance reviews, and take any other actions as may be necessary to enable Stripe to provide the Stripe Payments Services to User.
Stripe may also share data, including Protected Data, with Financial Providers, and they may use and share this data, for the purpose of managing a Dispute, assessing User’s compliance with Financial Provider Terms and facilitating Stripe’s, the Payment Method Providers’, and the Payment Method Acquirers’ compliance with Law, Payment Method Rules and Payment Method Terms.
User waives its right to bring any claim against Stripe arising from Stripe sharing information about User Group with Payment Method Providers and Payment Method Acquirers, including any inclusion on a terminated merchant list that results from this sharing. Stripe may periodically review User’s Stripe Account information to verify that User is eligible to use the Stripe Payments Services.
Qualifications & exceptions
Sharing with Providers and Acquirers is 'as Stripe believes necessary' for the listed purposes.
Financial Providers may themselves use and share the data for the listed Dispute, compliance and legal purposes.
The waiver covers claims against Stripe from the sharing, including terminated-merchant-list consequences.
Not stated here
What Protected Data covers is defined in the General Terms, not supplied.
Which terminated merchant lists are meant is not stated.
Account & Service Control · Procedure
Describe each charge accurately, be contactable, deal fairly, name Stripe as processor, meet consumer disclosure Law
When using the Stripe Payments Services, the User must, towards Customers: accurately communicate and not misrepresent the nature, amount and currency of each Transaction before submitting it; provide a meaningful way to contact the User if goods or services are not provided as described; not sell in a way that is unfair or deceptive, exposes Customers to unreasonable risks or fails to disclose material purchase terms in advance; inform Customers that Stripe and, if applicable, its Affiliates process Transactions for the User; and, when collecting authorizations electronically, ensure Customers consent to electronic signatures and electronic delivery of communications in accordance with Law. With consumer Customers, the User must provide legally required disclosures and must not engage in unfair, deceptive or abusive acts or practices.
Supporting quotations
3.7 Customer Communication.
When using the Stripe Payments Services User must, with respect to Customers (a) accurately communicate and not misrepresent the nature, amount and currency of each Transaction prior to submitting it for processing; (b) provide a meaningful way to contact User in the event that User’s goods or services are not provided as described; (c) not use the Stripe Payments Services to sell goods or services in a manner that is unfair or deceptive, exposes Customers to unreasonable risks, or does not disclose material terms of a purchase in advance; (d) inform Customers that Stripe and, if applicable, its Affiliates, process Transactions for User; and (e) if User is collecting authorizations electronically, ensure that Customers consent to electronic signatures and delivery of communications in accordance with Law.
If User engages in Transactions with Customers who are consumers, User must provide the disclosures Law requires, and must not engage in unfair, deceptive, or abusive acts or practices.
Qualifications & exceptions
The consumer-disclosure and UDAAP-style duty applies to Transactions with Customers who are consumers.
Not stated here
Which Law's disclosure requirements apply depends on the User's and Customers' jurisdictions, not stated here.
Legal Rights & Agreement Rules · Procedure
Network-imposed duties: own your agents’ acts, do not bind providers, keep data quality, fair refunds, respect Marks
As required by the Payment Method Rules: each party is responsible, as between them, for the acts and omissions of its employees, contractors and agents; the User cannot bind a Payment Method Provider to any contract or obligation unless the Provider agrees, and must not claim it can; the User must meet the Rules' data quality requirements for Transaction data and comply with the Provider's technical specifications; and the User must process the Transaction data it collects promptly, accurately and completely. The User must maintain and make available to Customers a fair and neutral refund and exchange policy and clearly explain how Customers get a Refund, a User-initiated full or partial return of funds for a processed Transaction. Payment Method Providers keep all IP Rights in their Marks; the User must not contest them, may use the Marks only consistently with the Payment Method Rules, and must promptly follow Stripe's instructions on their use or presentation.
Supporting quotations
3.8 Requirements Imposed by Payment Method Rules.
As required by the Payment Method Rules (a) as between the parties, each party is responsible for the acts and omissions of its employees, contractors, and agents; (b) unless a Payment Method Provider agrees otherwise, User cannot bind a Payment Method Provider to any contract or obligation, and User must not represent that User can do so; (c) User will meet data quality requirements for relevant categories of Transaction data (as described in the Payment Method Rules) and in respect of that data, User must comply with all technical specifications mandated by the relevant Payment Method Provider; and (d) User must ensure that Transaction data that User collects is processed promptly, accurately and completely.
User must maintain and make available to Customers a fair and neutral refund and exchange policy, and clearly explain the process by which Customers can receive a Refund. Payment Method Providers retain all IP Rights in their Marks, and User must not contest any Payment Method Provider’s IP Rights in their Marks. User may only use Payment Method Providers’ Marks in a manner consistent with the Payment Method Rules, and User must promptly comply with all instructions from Stripe regarding use or presentation of Payment Method Providers’ Marks.
“Refund” means an instruction User initiates to provide a full or partial return of funds to a Customer for a processed Transaction.
Qualifications & exceptions
These duties are stated as requirements of the Payment Method Rules.
A Provider may agree to let the User bind it; otherwise the User cannot.
Not stated here
The data quality requirements and technical specifications are in the Payment Method Rules, not supplied.
Charges & Financial Obligations · Restriction or exception
You alone bear all losses, yours and Stripe’s, from erroneous or fraudulent Transactions and account misuse
The User is solely responsible for all losses that the User and the Stripe Parties incur because of erroneous and fraudulent Transactions connected with the User's use of the Services. This includes losses resulting from lost or stolen payment credentials or account details used to buy from the User, from changes to the User Bank Accounts, and from unauthorized use of, access to or modification of the User's Stripe Account.
Supporting quotations
3.9 User Responsibility for Transactions.
User is solely responsible for all losses User and the Stripe Parties incur due to erroneous and fraudulent Transactions that occur in connection with User’s use of the Services, including as a result of (a) lost or stolen payment credentials or the details of any accounts that are used to purchase goods or services from User; (b) any changes to the User Bank Accounts; and (c) any unauthorized use of, or access or modification to, User’s Stripe Account.
Qualifications & exceptions
Covers losses of the Stripe Parties as well as the User's own.
No exception for losses caused by Stripe is stated in this clause; whether the General Terms limit this is not known from this source.
Not stated here
The General Terms' liability provisions, which may interact with this clause, are not supplied.
Charges & Financial Obligations · Procedure
You authorize settlement of your funds; submit only Customer-authorized charges after delivery, except prepayments
To let Stripe process Transactions, the User authorizes and directs Stripe, its Affiliates, Payment Method Providers and Payment Method Acquirers to receive and settle, as applicable, the settlement funds owed to the User through the Stripe Payments Services. The User may submit only Transactions that Customers have authorized, and only after the goods have shipped or the services have been provided. The exception is where the Customer has authorized a partial or full prepayment for goods or services to be provided later, or the User has obtained the Customer's consent, in which case the Transaction may be submitted before delivery.
Supporting quotations
4. Processing Transactions.
4.1 Payment Authorization Requests.
To enable Stripe to process Transactions for User, User authorizes and directs Stripe, its Affiliates, Payment Method Providers, and Payment Method Acquirers to receive and settle, as applicable, settlement funds owed to User through User’s use of the Stripe Payments Services. User may only submit Transactions that Customers authorize, and only after the applicable goods have been shipped or services provided to the Customer; except, User may submit a Transaction before goods have been shipped or services have been provided to the Customer where the Customer has authorized a Transaction for a partial or full prepayment for goods or services to be provided at a future time, or User has obtained the Customer’s consent.
Qualifications & exceptions
Submission before shipment or performance is allowed only with Customer-authorized prepayment or the Customer's consent.
Charges & Financial Obligations · Restriction or exception
Do not run fraudulent, declined, invalid or duplicate charges; Stripe may refuse, condition or suspend risky ones
The User must not proceed with a Transaction if it knows or should have known the Transaction was fraudulent, unauthorized by the Customer or illegal in the User's or Customer's jurisdiction, if it receives a response declining authorization, or if the Customer's ability to use the Payment Method has expired or is no longer valid. The User must not submit a Transaction that duplicates one already under Dispute or previously disputed and resolved in the User's favor. Stripe may refuse to process, or condition or suspend, any Transaction it believes may violate the Agreement or another agreement with Stripe, is unauthorized, fraudulent or illegal, or exposes or is likely to expose Stripe, the User or others to unacceptable risk.
Supporting quotations
User must not proceed with a Transaction if (i) User knows or should have known that the Transaction was fraudulent, not authorized by the Customer, or illegal in User or User’s Customer’s jurisdiction; (ii) User receives a response declining to authorize the Transaction; or (iii) the Customer’s ability to use a Payment Method has expired or is no longer valid. User must not submit any Transaction that duplicates a Transaction that is already subject to a Dispute, or was previously disputed and subsequently resolved in User’s favor.
Stripe may refuse to process, or condition or suspend any Transaction that Stripe believes (x) may violate this Agreement or other agreement User has with Stripe (if any); (y) is unauthorized, fraudulent or illegal; or (z) exposes, or is likely to expose, Stripe, User or others to unacceptable risk.
Qualifications & exceptions
The User's duty is triggered by actual or constructive knowledge ('knows or should have known').
Stripe's refusal right rests on its belief about violation, illegality or unacceptable risk.
Not stated here
What Stripe treats as 'unacceptable risk' is not defined.
Charges & Financial Obligations · Company practice
Stripe holds your settlement funds as agent in pooled accounts; once it has the money, your recourse is Stripe only
The User appoints Stripe as its agent for the limited purpose of directing, receiving, holding and settling funds under the Agreement. All settlement funds Stripe receives for Transactions are combined with other users' funds in one or more Pooled Accounts at Financial Providers. Once Stripe receives a Transaction's funds on the User's behalf, the Customer owes the User nothing further for that Transaction, whether or not and whenever Stripe settles the funds to the User; if Stripe fails to settle funds due, the User's recourse is against Stripe only, not the Customer. Stripe will promptly update the User's Stripe Account balance to reflect processed Transactions. The User has no right to earnings on Pooled Account funds, cannot draw from a Pooled Account and cannot direct transactions into or out of one.
Supporting quotations
4.2 Pooled Accounts.
User appoints Stripe as User’s agent for the limited purpose of directing, receiving, holding and settling funds under this Agreement. All settlement funds Stripe receives for Transactions are combined with settlement funds for other users and held in one or more Pooled Accounts at one or more Financial Providers. Once Stripe receives funds for a Transaction on User’s behalf, the relevant Customer has no further obligation to make payments to User with respect to that Transaction, regardless of whether and when Stripe settles those funds to User. If Stripe does not settle funds due to User under this Agreement, User will have recourse only against Stripe and not the relevant Customer.
Stripe will promptly update User’s Stripe Account balance to reflect processed Transactions. User has no rights to earnings generated by funds held in any Pooled Account and is not entitled to draw funds from any Pooled Account and has no rights to direct transactions into and out of any Pooled Accounts.
“Pooled Account” means a pooled account to which Transaction settlement funds are credited.
Qualifications & exceptions
Stripe's agency is for the limited purpose of directing, receiving, holding and settling funds.
Regional Terms vary this for some countries; for example the United States Regional Term adds SPC as a second agent.
Not stated here
The Financial Providers holding the Pooled Accounts are not named.
Charges & Financial Obligations · Company practice
Payouts are net of Fees, Disputes, Refunds and Reversals, on your schedule, to a bank, Financial Account or wallet
Stripe transfers Transaction settlement funds from the Pooled Account to the User net of Fees, Disputes, Refunds, Reversals and other amounts owed to Stripe, using the applicable settlement method, unless a Payout Delay affects the transfer or Stripe exercises a right under the Agreement to withhold or delay it. Settlement to a User Bank Account follows the Payout Schedule the User selects in the Stripe Dashboard, but Stripe may impose an additional holding period before the first settlement. Settlement to a Financial Account means the User is using the Stripe Treasury Services under the Stripe Treasury Terms. Settlement in Stablecoin to a Stablecoin Partner Wallet is performed solely by the Stablecoin Partner, and using a Service that settles in Stablecoin counts as acceptance of the Stablecoin Partner Terms, which are Financial Provider Terms. A Payout Delay includes provider or network unavailability, incorrect information given to Stripe, the User's own technology, and a Financial Provider's delay or failure to settle to Stripe.
Supporting quotations
4.3 Transaction Settlement Funds.
Stripe will transfer settlement funds for Transactions, net of Fees, Disputes, Refunds, Reversals and other amounts owed to Stripe, from the applicable Pooled Account to User in accordance with the applicable settlement method as follows, unless a Payout Delay occurs and affects the transfer initiation, or Stripe exercises a right under this Agreement to withhold or delay the transfer:
Where Stripe settles funds to a User Bank Account, Stripe will do so in accordance with the Payout Schedule. However, Stripe may impose an additional holding period before making the initial settlement to a User Bank Account.
Where Stripe settles funds to User's Financial Account, User will be using Stripe Treasury Services subject to the Stripe Treasury Terms.
Where funds are settled in Stablecoin to a Stablecoin Partner Wallet, that settlement is performed solely by the applicable Stablecoin Partner. User’s use of a Service that involves settlement in Stablecoin constitutes User’s acceptance of the applicable Stablecoin Partner Terms, which are Financial Provider Terms for the purposes of this Agreement.
“Payout Delay” means a delay to the Payout Schedule caused by (a) the unavailability of a Financial Provider, Governmental Authority, telecommunications provider, or internet service provider; (b) incorrect information, such as a bank account number, provided to Stripe; (c) User’s equipment, software, or other technology; (d) a delay or failure of a Financial Provider to settle a Transaction to Stripe
“Payout Schedule” means the schedule that User selects in the Stripe Dashboard (e.g. daily, weekly, monthly) to pay out Transaction settlement funds to a User Bank Account after those funds become available in User’s Stripe Account based on the Payout Speed.
“Financial Account” means the Stripe Account that Stripe provides to User as part of the Stripe Treasury Services.
“Stablecoin Partner” means an entity, which may be a Stripe Affiliate or a third party, that provides Stablecoin-related services to User, including the exchange, custody, transmission, or payout of Stablecoin, under the applicable Stablecoin Partner Terms.
“Stablecoin Partner Terms” means the terms that govern the Stablecoin Partner's provision, and User's access to and use of, the Stablecoin Partner Services, and which may be updated from time to time.
“Stablecoin Partner Wallet” means the account or wallet that the Stablecoin Partner maintains for User in connection with the Stablecoin Partner Services, through which User may hold, exchange, and transmit Stablecoin.
Qualifications & exceptions
Payouts are net of Fees, Disputes, Refunds, Reversals and other amounts owed to Stripe.
Transfers can be delayed by a Payout Delay or by Stripe exercising a contractual right to withhold or delay.
An additional holding period may apply before the initial settlement to a User Bank Account.
Stablecoin settlement is performed by the Stablecoin Partner, not Stripe, and accepting it means accepting the Stablecoin Partner Terms.
Not stated here
The Stripe Treasury Terms are a later section of this document; the Stablecoin Partner Terms are external and not supplied.
The length of any initial holding period is not stated.
Charges & Financial Obligations · Company practice
Stripe may let you send funds owed to you to a third party; doing so fully discharges its settlement duty
Stripe may offer the User the ability to send funds owed to it to a third party on the User's instructions, including sending all or part of its positive Stripe Account balance to the recipient's Stripe account or bank account, instead of settling to a User Bank Account, Financial Account or Stablecoin Partner Wallet. If Stripe or an Affiliate sends funds to a third-party recipient as this section contemplates, including through a payment intermediary acting for the User, the settlement obligations of Stripe, its Affiliate and the Payment Method Providers and Acquirers to the User are satisfied.
Supporting quotations
4.4 Sending Funds to Third-Party Recipients.
Stripe may offer User the ability to send to a third party funds owed to User as User instructs Stripe (including by sending all or part of the positive balance in User’s Stripe Account to that third-party recipient’s Stripe account or bank account), instead of settling funds to a User Bank Account, or Financial Account or Stablecoin Partner Wallet. If Stripe or an applicable Affiliate sends funds to a third-party recipient which may include the use of a payment intermediary operating on User’s behalf, as this Section 4.4 contemplates, then Stripe’s or its Affiliate’s obligations (and all applicable Payment Method Provider and Payment Method Acquirer obligations) to settle those funds to User are satisfied.
Qualifications & exceptions
The feature is offered at Stripe's option ('may offer').
Once funds are sent to the third party as instructed, settlement obligations to the User are treated as fully met.
Not stated here
Any fees or eligibility conditions for this feature are not stated here.
Charges & Financial Obligations · Restriction or exception
Stripe is not responsible for fees charged by the banks, recipients or Stablecoin Partners that receive your funds
Stripe is not responsible for fees imposed by third parties to which it transfers funds, including the banks holding the User Bank Accounts, Financial Accounts and third-party recipient accounts, and Stablecoin Partners.
Supporting quotations
4.5 Settlement Fees.
Stripe is not responsible for any fees imposed by third parties to which Stripe transfers funds, including (i) the banks that hold the User Bank Accounts, Financial Accounts, and the third-party recipient accounts; or (ii) Stablecoin Partners.
Not stated here
The fees those third parties charge are set outside this Agreement.
Charges & Financial Obligations · Procedure
Before the first recurring or subscription charge, tell Customers it is ongoing and how to cancel
If the User uses the Services to submit recurring or subscription Transactions, then before submitting the initial Transaction it must inform each Customer that the Transactions will occur on an ongoing basis and explain how the Customer can cancel the recurring billing or subscription.
Supporting quotations
4.6 Subscriptions and Invoicing.
If User uses the Services to submit recurring or subscription Transactions, then before submitting the initial Transaction, User must (a) inform each Customer that the relevant Transactions will occur on an ongoing basis; and (b) explain the method for canceling the Customer’s recurring billing or subscription.
Qualifications & exceptions
Both disclosures must be made before the initial Transaction is submitted.
Charges & Financial Obligations · Procedure
Card-not-present, merchant-initiated or stored-method charges may need mandates and disclosures; keep proof
If the User uses the Stripe Payments Services for Transactions where the Customer is not present, including MOTO Transactions or Merchant Initiated Transactions, or to store a Customer's Payment Method for future use, Law and the Payment Method Rules may require it to obtain the Customer's authorization (a mandate or agreement) and make disclosures, such as when and in what circumstances the Payment Method will be charged, how the amount is determined and how future payments can be canceled. The User must retain, and give Stripe on request, records showing it obtained any required authorizations in compliance with Law and the Payment Method Rules and that it submitted as MOTO or Merchant Initiated Transactions only those it determined were eligible.
Supporting quotations
4.7 Customer Authorizations.
If User uses the Stripe Payments Services for certain Transactions where the Customer is not present, including MOTO Transactions or Merchant Initiated Transactions, or to store a Customer’s Payment Method for future use, User may be required by Law and Payment Method Rules to obtain the Customer’s authorization (also known as a mandate or agreement for the provision of products or services) and make certain disclosures to the Customer.
User must retain, and provide to Stripe upon request, records demonstrating that User has (a) obtained any required Customer authorizations in compliance with Law and Payment Method Rules; and (b) only submitted Transactions as MOTO Transactions or Merchant Initiated Transactions that User has determined are eligible.
Qualifications & exceptions
The authorization and disclosure duties arise where Law and the Payment Method Rules require them ('may be required').
The record-keeping and production duty is unconditional once such Transactions are used.
Not stated here
MOTO Transactions and Merchant Initiated Transactions are capitalized terms defined elsewhere in these Payments Terms.
Which Law and Rules apply depends on the Payment Method and jurisdiction.
Charges & Financial Obligations · Procedure
You must reconcile your Transaction history and report errors within 60 days; EEA and Australia get 13 months
As between the parties, and unless Law requires otherwise, the User is responsible for reviewing its Transaction history for accuracy and completeness and reconciling it with the transfers from the Pooled Accounts to its User Bank Accounts, Financial Accounts and Stablecoin Partner Wallet. If the User finds an error, Stripe will reasonably cooperate to investigate and help correct it, provided the User notifies Stripe within 60 days (or longer if Law requires) after the error appears in the Transaction history. Stripe may correct errors by crediting or debiting the User Bank Accounts and Financial Accounts. The Regional Terms vary this: for the European Economic Area the notice window is 13 months; for Australia and New Zealand the reconciliation duty applies monthly, the User must notify Stripe as soon as possible, and the window is 13 months.
Supporting quotations
As between the parties, and except as otherwise required by Law, User is responsible for reviewing its Transaction history for accuracy and completeness and reconciling its Transaction history with the history of transfers from the Pooled Accounts to the User Bank Accounts, Financial Accounts, and Stablecoin Partner Wallet, as applicable. If User finds an error when User reconciles its Transaction history, Stripe will reasonably cooperate with User to investigate and help correct that error as long as User notifies Stripe of the error within 60 days (or longer time period if Law requires) after the error appears in User’s Transaction history. Stripe may correct any errors in User’s Transaction history by crediting or debiting the User Bank Accounts and Financial Accounts, as applicable.
Deviating from Section 5.1 (Reconciliation and Responsibility), if User finds an error when User reconciles User’s Transaction history, Stripe will reasonably cooperate with User to investigate and help correct that error as long as User notifies Stripe of the error within 13 months after the error appears in User’s Transaction history.
Deviating from Section 5.1 (Reconciliation and Responsibility), User’s obligation to review User’s Transaction history for accuracy and completeness and for reconciling it with the history of transfers from the Pooled Accounts to the User Bank Accounts and Financial Accounts applies on a monthly basis. User must notify Stripe as soon as possible if User finds an error. Stripe will reasonably cooperate with User to investigate and help correct the error as long as User notifies Stripe of the error within 13 months after the error appears in User’s Transaction history.
Deviating from Section 5.1 (Reconciliation and Responsibility), User’s obligation to review User’s Transaction history for accuracy and completeness and for reconciling it with the history of transfers from the Pooled Accounts to the User Bank Accounts and Financial Accounts, as applicable, apply on a monthly basis. User must notify Stripe as soon as possible if User finds an error.
Qualifications & exceptions
The 60-day window runs from when the error appears in the Transaction history and is extended where Law requires.
Regional Terms replace the window with 13 months for the EEA, Australia and New Zealand, and set a monthly reconciliation duty for Australia and New Zealand.
Not stated here
Whether other Regional Terms also vary this clause is settled in those sections.
Charges & Financial Obligations · Restriction or exception
You owe Stripe the full amount of every Dispute, Refund and Reversal, whatever the reason, until a Dispute goes your way
Overriding anything else in the Agreement, the User is liable to Stripe for the full amount of all Disputes (unless and until a Dispute is finally resolved in the User's favor under the applicable Payment Method Rules and as the Documentation describes) and related costs, and for all Refunds and Reversals, a Reversal being the reversal of the settlement of funds for a Transaction. This applies regardless of the reason or timing and whether or not the User uses the Stripe Payments Services to manage its Disputes, Refunds or Reversals.
Supporting quotations
5.2 Disputes; Refunds; Reversals.
Notwithstanding anything to the contrary in this Agreement, User is liable to Stripe for the full amount of all Disputes (unless and until a Dispute is resolved to final disposition in User’s favor according to applicable Payment Method Rules and as described in the Documentation) and other related costs, Refunds and Reversals regardless of the reason, timing or whether User uses the Stripe Payments Services to manage its Disputes, Refunds or Reversals.
“Reversal” means the reversal of the settlement of funds for a Transaction.
Qualifications & exceptions
The clause applies 'notwithstanding anything to the contrary in this Agreement'.
Liability for a Dispute lifts only when it is resolved to final disposition in the User's favor.
Charges & Financial Obligations · Company practice
Stripe may hold funds for likely or actual Disputes; providers share your evidence; you own responses and automation
Stripe may delay or withhold paying out a Transaction amount if it reasonably believes a Dispute is likely for that Transaction, and may withhold amounts under an actual Dispute until the Payment Method Provider resolves it. Payment Method Providers and other Financial Providers may access and share data and evidence the User provides, following their standard Dispute-management practices. If the User uses the Stripe Payments Services to automate parts of Dispute management, it authorizes Stripe to interact with Financial Providers on its behalf, and acknowledges Stripe cannot guarantee and takes no responsibility for the outcome. The User remains responsible for every response submitted in a Dispute, including the accuracy of its content and evidence, and is solely responsible for its use of Stripe's Dispute-management solutions, including third-party-powered ones, and for all decisions, actions and default or custom rules it uses with them.
Supporting quotations
(a) Disputes.
Stripe may delay or withhold paying out a Transaction amount from funds owed to User if Stripe reasonably believes that a Dispute is likely to occur with respect to that Transaction. Stripe may delay or withhold paying out amounts subject to an actual Dispute until the Payment Method Provider resolves the Dispute.
Payment Method Providers and other Financial Providers may access and share data and evidence provided by User or on User’s behalf in accordance with that Financial Provider’s standard Dispute-management practices.
If User uses the Stripe Payments Services to automate certain aspects of a Dispute management process, User authorizes Stripe to interact with relevant Financial Providers on User’s behalf with respect to the Dispute. User acknowledges that Stripe cannot guarantee, and takes no responsibility for, a successful outcome of a Dispute.
User remains responsible for all responses submitted in connection with a Dispute including the accuracy of all content and evidence submitted.
User is solely responsible for its use of Stripe’s Dispute management solutions (including those powered by third parties), and all decisions User makes, actions User takes, and all rules (default or custom) User uses in connection with Stripe’s Dispute-management solutions.
Qualifications & exceptions
Withholding for a likely Dispute requires Stripe's reasonable belief; withholding for an actual Dispute lasts until the Provider resolves it.
Stripe disclaims responsibility for Dispute outcomes even when it interacts with Financial Providers on the User's behalf.
Not stated here
How long a 'likely Dispute' hold may last is not stated.
Charges & Financial Obligations · Company practice
Stripe may refuse or delay a Refund if you are insolvent, it would make your balance negative, or it sees liability risk
Stripe may refuse to act on a Refund instruction, or delay executing it, if the User is the subject of an Insolvency Event, if the Refund would cause a negative balance in the User's Stripe Account, or if Stripe believes there is a risk the User will not meet its liabilities under the Agreement.
Supporting quotations
Stripe may refuse to act upon a Refund instruction, or delay executing the instruction, if User is the subject of an Insolvency Event, if it would cause a negative balance in User’s Stripe Account, or if Stripe believes that there is a risk User will not meet its liabilities under this Agreement.
Qualifications & exceptions
Three triggers: an Insolvency Event, a resulting negative balance, or Stripe's belief in a risk of unmet liabilities.
Charges & Financial Obligations · Company practice
Stripe may reverse a settlement for invalidated, erroneous, unauthorized or violating payments, or on provider demand
Without limiting its remedies under Sections 5.3 to 5.5 of these Payments Terms, Stripe may initiate a Reversal if the Payment Method Provider invalidates the Transaction, the User received funds in error for any reason, the User was not authorized to accept the Transaction, the User received funds related to activities that violate the Agreement, Law or Financial Provider Terms, or a Payment Method Provider or Payment Method Acquirer requires Stripe to reverse under the applicable Financial Provider Terms.
Supporting quotations
Without limiting Stripe’s rights under Sections 5.3 - 5.5 of these Stripe Payments Terms, Stripe may initiate a Reversal if:
the Payment Method Provider invalidates the Transaction
User receives funds in error for any reason
User was not authorized to accept the Transaction
User receives funds related to activities that violate this Agreement, Law or Financial Provider Terms
a Payment Method Provider or Payment Method Acquirer requires Stripe to do so under the applicable Financial Provider Terms
Qualifications & exceptions
These triggers are in addition to Stripe's general remedies in Sections 5.3 to 5.5.
Account & Service Control · Company practice
Thirteen specific triggers let Stripe use its Section 5.5 remedies, from excessive Disputes to likely insolvency
Without limiting its other rights, Stripe may use any or all of the remedies in Section 5.5 of these Payments Terms if it reasonably determines that a User Entity: has incurred or is likely to incur excessive Disputes, Refunds or Reversals; submitted Transactions for goods or services not immediately deliverable without Stripe's prior consent; has a negative Stripe Account balance; has had or is likely to have a change Stripe considers material in the time between charge and fulfillment; is or is likely to become subject to an Insolvency Event; has had or is likely to have a deterioration of business or financial condition Stripe considers material; has breached or is likely to breach, or cause Stripe to breach, the Agreement, another Stripe services agreement or applicable Financial Provider Terms; has violated or is likely to violate Law or Financial Provider Terms, or cause Stripe to; has had or is likely to have a Change of Control; has initiated fraudulent, suspicious or criminal Transactions or actions, itself or through its people; has changed its business model without Stripe's prior consent, increasing Stripe's risk; or has acted or done business in a way that presents an unacceptable risk. Most triggers include anticipated events ('is likely to').
Supporting quotations
5.3 Stripe Remedies – Specific Triggers.
Without limiting Stripe’s other rights or remedies under this Agreement, Stripe may exercise any or all of the remedies stated in Section 5.5 of these Stripe Payments Terms if Stripe reasonably determines that a User Entity:
has incurred or is likely to incur excessive Disputes, Refunds or Reversals
has submitted one or more Transactions for goods or services not immediately deliverable to the Customer without first obtaining Stripe’s consent
has a negative Stripe Account balance
has experienced or is likely to experience a change in the average time between the initial charge and fulfillment of Customer orders that Stripe considers to be material
is or is likely to become the subject of an Insolvency Event
has experienced or is likely to experience a deterioration of its business or financial condition that Stripe considers to be material
has breached or is likely to breach, or has caused or is likely to cause Stripe to breach, this Agreement (or any other Stripe services agreement with a Stripe Entity) or the Financial Provider Terms applicable to the User Entity’s use of the Services
has violated or is likely to violate Law or Financial Provider Terms
has caused or is likely to cause Stripe to violate Law or Financial Provider Terms
has experienced or is likely to experience a Change of Control
has, either itself or by way of its employees, agents, directors or contractors, initiated Transactions or undertaken any other action that is or is likely to be fraudulent, suspicious or involve criminal activity
has, without Stripe’s prior consent, changed its business model (including services supplied by a User Entity to its customers), exposing Stripe to increased risk
has acted in a manner or engaged in business, trading practice or other activity that presents an unacceptable risk
Qualifications & exceptions
The standard is Stripe's reasonable determination.
Triggers apply to any User Entity, not only the contracting User.
Most triggers are met by a likely future event, not only an actual one.
Not stated here
The remedies themselves are in Section 5.5, analyzed in the next packet.
What Stripe considers 'material' or an 'unacceptable risk' is not defined.
Account & Service Control · Company practice
Stripe may also use its remedies if it reasonably expects post-termination losses from a User Entity, or Law requires
Beyond the thirteen specific triggers, Stripe may exercise any or all of the Section 5.5 remedies if it reasonably determines that it may incur losses from credit, fraud, criminal activity or other risks associated with a User Entity after these Payments Terms terminate, or if Law requires. This is without limiting Stripe's other rights or remedies.
Supporting quotations
5.4 Stripe Remedies – General Trigger.
Without limiting Stripe’s other rights or remedies under this Agreement, Stripe may exercise any or all of the remedies stated in Section 5.5 of these Stripe Payments Terms if (a) Stripe reasonably determines that Stripe may incur losses resulting from credit, fraud, criminal activity or other risks associated with a User Entity after these Stripe Payments Terms terminate; or (b) Law requires.
Qualifications & exceptions
The risk trigger looks to losses that may arise after termination and applies to any User Entity.
The standard is Stripe's reasonable determination, or a legal requirement.
Charges & Financial Obligations · Company practice
When triggered, Stripe may reverse payments, hold payouts, take a Reserve without notice, suspend you and refuse refunds
If a triggering event under Section 5.3 or 5.4 of these Payments Terms, or under any other provision of the Agreement that refers to these remedies, has occurred, Stripe may, without limiting its other rights: initiate Reversals; change the Payout Schedule or delay or cancel payouts to the User Bank Accounts, Financial Account or Stablecoin Partner Wallet; establish, fund, use and apply a Reserve, including enforcing or drawing on any security interest or lien it holds over the Reserve without demand, legal process or notice of any kind, by applying Reserve funds to liabilities the User owes any Stripe Entity; suspend or terminate the User's ability to accept or process Transactions; manage Disputes that Stripe believes present an unacceptable risk to it; and refuse to process Transactions or act on Refund instructions.
Supporting quotations
5.5 Stripe Remedies – Scope.
Without limiting Stripe’s other rights or remedies under this Agreement, if a triggering event in Sections 5.3 or 5.4 of these Stripe Payments Terms (or any other provision of this Agreement that refers to these remedies) has occurred, then Stripe may:
initiate Reversals
change the Payout Schedule or delay or cancel the payout of funds to the User Bank Accounts, Financial Account, or Stablecoin Partner Wallet
establish, fund, use, and apply a Reserve, which may include enforcing or drawing down upon, without demand, legal process, or notice of any kind, any security interest or lien held by Stripe in respect of the Reserve, by applying the Reserve funds toward settlement of any liabilities owed by User to any Stripe Entity
suspend or terminate User’s ability to accept or process Transactions
manage Disputes that Stripe believes present an unacceptable risk to Stripe
refuse to (i) process Transactions, and (ii) act upon Refund instructions
Qualifications & exceptions
Available only after a triggering event under Section 5.3, 5.4 or another provision pointing to these remedies.
Reserve enforcement may happen 'without demand, legal process, or notice of any kind'.
Other sets of Service Terms (for example the Stripe Connect Terms) also point to these remedies.
Not stated here
Whether and how Stripe tells the User which remedy it has applied is not stated here.
Charges & Financial Obligations · Company practice
Multi-currency settlement needs an account per currency; rates fix per Transaction, Refunds use the rate at refund time
Stripe may offer Multi-Currency Processing, which lets funds settle to a User Bank Account or Financial Account in a currency different from the one the Customer paid in. To use it, the User must give Stripe a valid bank account or Financial Account for each settlement currency it requests, from the list of available settlement currencies in the Documentation; each counts as a User Bank Account or Financial Account under the Agreement. Stripe identifies the applicable conversion rate at the time of each Transaction. For a Refund, the rate used is the one in effect at the time of the Refund, not the original Transaction's rate.
Supporting quotations
6. Multi-Currency Processing.
Stripe may offer Multi-Currency Processing. To use Multi-Currency Processing, User must provide to Stripe a valid bank account or Financial Account for each currency for which User requests settlement, based on the list of available settlement currencies stated in the Documentation. Each of these bank accounts is a User Bank Account or Financial Account for the purposes of this Agreement. If User uses Multi-Currency Processing, Stripe will identify at the time of each applicable Transaction the conversion rate that will apply to the Transaction. In the event of a Refund, the conversion rate that will be used to calculate the Refund will be the rate in effect at the time of the Refund.
“Multi-Currency Processing” means the ability to have funds settled to a User Bank Account or Financial Account in a currency different from the one in which User accepted payment from a Customer.
Qualifications & exceptions
Offered at Stripe's option ('may offer') and limited to the settlement currencies listed in the Documentation.
A Refund is converted at the rate in effect when the Refund is made, which may differ from the rate at the original Transaction.
Not stated here
How Stripe sets the conversion rate, and any conversion fee, is not stated here.
Account & Service Control · Procedure
After these terms end you must finish existing Transactions, take no new ones and remove Stripe and provider Marks
After these Payments Terms terminate, the User must fulfill its obligations for existing Transactions, must not accept new Transactions through the Services, and must remove all Marks of the Stripe Entities and Financial Providers from its website unless a separate license with a Financial Provider permits them. Stripe will complete Transactions initiated before termination as long as it would have completed them had the terms still been in force; for example, it will not complete a Transaction a Financial Provider prohibits. Termination does not affect the User's responsibility for Transactions under Section 3 of these Payments Terms.
Supporting quotations
7. Post-Termination Obligations.
7.1 Completion of Transactions.
Following termination of these Stripe Payments Terms, User must fulfill User’s obligations related to existing Transactions and must not accept new Transactions via the Services, and must remove all Marks of the Stripe Entities and Financial Providers from User’s website (unless permitted under a separate license with a Financial Provider). Stripe will complete Transactions initiated before termination as long as Stripe would have completed those Transactions were these Stripe Payments Terms still in place (e.g., Stripe will not complete a Transaction if a Financial Provider prohibits Stripe from doing so). Termination does not affect User’s responsibility for Transactions described in Section 3 of these Stripe Payments Terms.
Qualifications & exceptions
Marks may stay only under a separate license with a Financial Provider.
Stripe's completion of pre-termination Transactions is conditional on it having been able to complete them under the terms.
Retention & Deletion · User right or choice
If the terms end other than for your breach, you have 30 days to ask Stripe to send card details to a new processor
If these Payments Terms terminate for reasons other than the User's breach, the User may, within 30 days after the termination date, ask Stripe in writing to provide all relevant Payment Method Account Details to an alternative PCI-DSS Level 1-certified payment processor the User identifies. Stripe will provide the details the User is entitled to receive to that processor to the extent commercially reasonable. Stripe may delay or refuse the request if it believes the named processor lacks sufficient systems or controls to protect the details, that their integrity may be compromised, or that Law or Financial Provider Terms do not allow the transfer.
Supporting quotations
7.2 Provision of Payment Method Account Details.
If these Stripe Payments Terms terminate for reasons other than User’s breach, then within 30 days after the termination date, User may request in writing that Stripe provide all relevant Payment Method Account Details to an alternative PCI-DSS Level 1-certified payment processor that User identifies to Stripe. Stripe will provide the Payment Method Account Details that User is entitled to receive to the named payment processor to the extent commercially reasonable.
Stripe may delay or refuse any request if Stripe believes the payment processor User has identified does not have systems or controls in place that are sufficient to protect Payment Method Account Details, that the integrity of Payment Method Account Details may be compromised, or that Law or Financial Provider Terms do not allow Stripe to provide the Payment Method Account Details.
Qualifications & exceptions
Not available where termination was for the User's breach.
The request must be in writing within 30 days after termination and name a PCI-DSS Level 1-certified processor.
Stripe's duty is limited to details the User is entitled to receive and to what is commercially reasonable.
Not stated here
Which details the User is 'entitled to receive' is not spelled out here.
Account & Service Control · Procedure
Tell Stripe at once if your charge-to-fulfillment time changes materially; supply policy and fulfillment data on request
The User must immediately notify Stripe and provide updated User Information if it experiences or anticipates a material change in the average time between the initial charge and fulfillment of Customer orders. On request, the User must promptly give Stripe information about Transactions and Disputes, including its refund and shipping policies, data on captured but unfulfilled charges, data on the time between charge capture and fulfillment, and any other information Stripe reasonably requests.
Supporting quotations
8. User Information Updates.
User must immediately notify Stripe, and provide to Stripe updated User Information, if User experiences or anticipates experiencing a material change in the average time between the initial charge and fulfillment of Customer orders. Upon request, User must promptly provide to Stripe information related to Transactions and Disputes, including (a) refund and shipping policies (if applicable); (b) data on captured but unfulfilled charges; (c) data on the time between charge capture and fulfillment of Customer orders; and (d) any other information Stripe reasonably requests.
Qualifications & exceptions
The notice duty covers anticipated as well as actual changes.
Stripe's information requests must be reasonable.
Security & Safeguards · Restriction or exception
If you store card Account Data you must be PCI-compliant and prove it; vet third parties; never keep security codes
If the User chooses to store or hold 'Account Data' as defined in the PCI Standards, such as card numbers or expiration dates, it must maintain a PCI-compliant system and give Stripe evidence of compliance on request. If the User does not comply, or Stripe, a Payment Method Provider or a Payment Method Acquirer cannot verify compliance, Stripe may suspend the User's Stripe Account or terminate the Agreement in whole or in part. Before using a third-party service provider to store or transmit Payment Method Account Details, the User must verify the provider holds sufficient PCI certifications and notify Stripe of the intention to share; it must not share any details until then. The User must never store or hold 'Sensitive Authentication Data', including the card verification value. The India Regional Term goes further: the User must ensure its infrastructure complies with the PCI Standards and provide evidence of compliance, without the 'if User elects to store' condition.
Supporting quotations
If User elects to store or hold "Account Data," as defined in the PCI Standards (including Customer card account number or expiration date), User must maintain a system that complies with the PCI Standards and upon Stripe’s request, User must provide to Stripe evidence of User’s compliance. If User does not comply with the PCI Standards, or if Stripe or any Payment Method Provider or Payment Method Acquirer is unable to verify User’s compliance with the PCI Standards, Stripe may suspend User’s Stripe Account or terminate this Agreement, in whole or in part.
User must not share any Payment Method Account Details with the service provider until User verifies that the third party holds sufficient certifications under the PCI Standards, and must
Further, User agrees to never store or hold any "Sensitive Authentication Data," as defined by the PCI Standards (including the card verification value or similar security code), at any time.
User must ensure that its infrastructure is compliant with the PCI Standards, as applicable. User must maintain a system that complies with the PCI Standards. User must provide to Stripe evidence of User’s compliance.
Qualifications & exceptions
The general duty is conditional on the User electing to store or hold Account Data; the India Regional Term makes it unconditional.
Suspension or termination follows non-compliance or an inability to verify compliance.
The ban on storing Sensitive Authentication Data applies at any time.
Not stated here
The PCI Standards are external documents referenced via the PCI Council website, not supplied.
Account & Service Control · Restriction or exception
Use payment methods only for genuine, unencumbered sales, and make your card-data providers meet the PCI Standards
The User may use the Payment Methods and Stripe Payments Services only for bona fide commercial transactions with Customers, which must be free of liens, claims and encumbrances other than ordinary sales taxes. The User must comply with the PCI Standards to the extent they apply, and must ensure its third-party service providers that store, access or transmit Payment Method Account Details do too.
Supporting quotations
10. Additional Obligations.
User must only use the Payment Methods and Stripe Payments Services for bona fide commercial transactions (which must be free of liens, claims, and encumbrances other than ordinary sales taxes) with Customers. User must, and will ensure that User’s third-party service providers that store, access or transmit Payment Method Account Details, comply with the PCI Standards, to the extent they apply.
Qualifications & exceptions
PCI compliance duties apply 'to the extent they apply' and extend to the User's third-party providers handling Payment Method Account Details.
Charges & Financial Obligations · Restriction or exception
You cover all of Stripe’s fraud-Transaction losses without the General Terms’ liability caps, plus provider audit costs
As between the parties, the User is responsible for all losses, damages and costs Stripe and its Affiliates incur from fraudulent Transactions, and the limitations on liability in Sections 8.3 and 8.4 of the General Terms do not apply to that responsibility. The User also bears the costs of any Financial Provider-initiated audit or forensic investigation arising from or relating to its use of the Stripe Payments Services.
Supporting quotations
11. Fraudulent Transactions.
As between the parties, User is responsible for all (a) losses, damages, and costs Stripe and its Affiliates incur due to fraudulent Transactions, and the limitations on liability in Sections 8.3 and 8.4 of the General Terms do not apply; and (b) costs associated with any Financial Provider-initiated audit or forensic investigation arising out of or relating to User’s use of the Stripe Payments Services.
Qualifications & exceptions
The General Terms' liability limitations (Sections 8.3 and 8.4) are expressly switched off for fraud losses.
Audit and forensic investigation costs are covered when a Financial Provider initiates them.
Not stated here
The content of Sections 8.3 and 8.4 of the General Terms is unknown; the General Terms are not supplied.
Charges & Financial Obligations · Restriction or exception
If Stripe fails to pay out funds it received and owes you, its liability is limited to that amount, not the general cap
The limitation of liability in Section 8.4 of the General Terms does not apply to claims by the User or its Affiliates against the Stripe Parties for failing to transfer settlement funds the Stripe Parties received and owe to the User in connection with the Stripe Payments Services. For those claims, the Stripe Parties' liability is instead limited to the amount they received and owe but failed to transfer.
Supporting quotations
12. Liability for Failure to Transfer Funds.
The limitation of liability in Section 8.4 of the General Terms will not apply to claims User or User’s Affiliates make against the Stripe Parties for failing to transfer any settlement funds the Stripe Parties receive and owe to User in connection with the Stripe Payments Services. For these claims, the Stripe Parties’ liability is limited to the amount that the Stripe Parties have received and owe, but failed to transfer, to User.
Qualifications & exceptions
Applies only to claims for failure to transfer settlement funds actually received and owed.
The replacement cap is the unpaid amount itself; consequential losses are not mentioned.
Not stated here
The content of Section 8.4 of the General Terms is unknown; the General Terms are not supplied.
Charges & Financial Obligations · Restriction or exception
Force majeure under the General Terms never excuses your Dispute, Refund and Reversal liabilities
Nothing in Section 11.13 of the General Terms, the force majeure clause, excuses the User's liabilities and obligations for Disputes, Refunds and Reversals. Those remain payable even during events that might otherwise suspend performance.
Supporting quotations
13. Force Majeure.
Nothing in Section 11.13 of the General Terms will excuse User’s liabilities and obligations with respect to Disputes, Refunds, and Reversals.
Qualifications & exceptions
Carves Disputes, Refunds and Reversals out of whatever relief Section 11.13 of the General Terms provides.
Not stated here
The content of Section 11.13 of the General Terms is unknown; the General Terms are not supplied.
Legal Rights & Agreement Rules · Context
Payments Terms definitions: Acquirer Terms, Card Network and Rules, Dispute, MOTO and Merchant Initiated, Payout Delay
Section 14 defines the terms used in the Payments Terms. 'Acquirer Disclosure' is information on applicable Payment Method Acquirers on the Stripe Legal Page; 'Acquirer Terms' are the acquirer's own terms there. 'Card Network' includes the Visa, Mastercard, American Express and Discover networks; 'Card Network Rules' are the Payment Method Rules a Card Network publishes. A 'Dispute' is a Customer-initiated instruction to reverse or invalidate a processed Transaction, including chargebacks. 'Financial Account' is the Stripe Account provided under the Stripe Treasury Services. A 'Merchant Initiated Transaction' is one the User initiates under a Customer's standing authorization (mandate) without further Customer action; a 'MOTO Transaction' is one initiated by mail order or telephone. 'Multi-Currency Processing' is settlement in a currency other than the payment currency. 'Payment Method Account Details' are the Customer account details the PCI Standards protect, including name, card number, expiration date and security code. 'Payment Method Terms' are the terms on the Stripe Website described as such. A 'Payout Delay' is a delay to the Payout Schedule caused by provider or network unavailability, incorrect information given to Stripe, the User's technology, a Financial Provider's settlement delay or failure (including insolvency), or a Force Majeure Event.
Supporting quotations
14. Definitions.
“Acquirer Disclosure” means information on applicable Payment Method Acquirers, which is accessible from the Stripe Legal Page.
“Acquirer Terms” means the terms that a Payment Method Acquirer has specified that apply to that Payment Method Acquirer’s services, located on or accessible from the Stripe Legal Page.
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
“Card Network Rules” means the Payment Method Rules published by a Card Network.
“Dispute” means an instruction a Customer initiates to reverse or invalidate a processed Transaction (including “chargebacks” and “disputes” as those terms may be used by Payment Method Providers).
“Financial Account” means the Stripe Account that Stripe provides to User as part of the Stripe Treasury Services.
“Merchant Initiated Transaction” means a Transaction or a series of Transactions that User initiates according to an authorization (i.e., mandate) that User receives from a Customer that authorizes User to initiate the Transaction(s) on the agreed terms, without requiring the Customer to take any further action to trigger their initiation by User.
“MOTO Transaction” means a Transaction that User initiates through a mail order or over the telephone.
“Multi-Currency Processing” means the ability to have funds settled to a User Bank Account or Financial Account in a currency different from the one in which User accepted payment from a Customer.
“Payment Method Account Details” means the Payment Method account details for a Customer that the PCI Standards require to be protected, which may include the Customer’s name, and with respect to credit and debit cards, the Customer’s account number, card expiration date, and card verification value or similar security code.
“Payment Method Terms” means terms that apply to User’s acceptance and use of a Payment Method, located on or accessible from the Stripe Website, including on the Stripe Legal Page, and which as of the Effective Date are described on that page as “Payment Method Terms.”
“Payout Delay” means a delay to the Payout Schedule caused by (a) the unavailability of a Financial Provider, Governmental Authority, telecommunications provider, or internet service provider; (b) incorrect information, such as a bank account number, provided to Stripe; (c) User’s equipment, software, or other technology; (d) a delay or failure of a Financial Provider to settle a Transaction to Stripe, including as a result of a Financial Provider’s default, insolvency, or bankruptcy; or (e) a Force Majeure Event.
Qualifications & exceptions
The definitions continue in the next packet (Payout Schedule onward).
Legal Rights & Agreement Rules · Context
Payments Terms definitions: Payout Schedule and Speed, Pooled Account, Refund, Reversal and Stablecoin Partner terms
The remaining Section 14 definitions: the 'Payout Schedule' is the cadence (daily, weekly, monthly) the User selects in the Stripe Dashboard for paying settlement funds to a User Bank Account once they are available; 'Payout Speed' is the number of days after a Transaction until its funds become available in the Stripe Account, as stated in the Documentation. A 'Pooled Account' receives Transaction settlement funds for many users. A 'Refund' is a User-initiated full or partial return of funds for a processed Transaction; a 'Reversal' is the reversal of a Transaction's settlement. A 'Stablecoin Partner' is a Stripe Affiliate or third party providing Stablecoin exchange, custody, transmission or payout services under its own 'Stablecoin Partner Terms', which may be updated from time to time, and a 'Stablecoin Partner Wallet' is the account or wallet it maintains for the User to hold, exchange and transmit Stablecoin.
Supporting quotations
“Payout Schedule” means the schedule that User selects in the Stripe Dashboard (e.g. daily, weekly, monthly) to pay out Transaction settlement funds to a User Bank Account after those funds become available in User’s Stripe Account based on the Payout Speed.
"Payout Speed" means the number of days following the Transaction that it takes for the Transaction settlement funds to become available in User’s Stripe Account as stated in the Documentation.
“Pooled Account” means a pooled account to which Transaction settlement funds are credited.
“Refund” means an instruction User initiates to provide a full or partial return of funds to a Customer for a processed Transaction.
“Reversal” means the reversal of the settlement of funds for a Transaction.
“Stablecoin Partner” means an entity, which may be a Stripe Affiliate or a third party, that provides Stablecoin-related services to User, including the exchange, custody, transmission, or payout of Stablecoin, under the applicable Stablecoin Partner Terms.
“Stablecoin Partner Terms” means the terms that govern the Stablecoin Partner's provision, and User's access to and use of, the Stablecoin Partner Services, and which may be updated from time to time.
“Stablecoin Partner Wallet” means the account or wallet that the Stablecoin Partner maintains for User in connection with the Stablecoin Partner Services, through which User may hold, exchange, and transmit Stablecoin.
Qualifications & exceptions
Payout Speed is set by the Documentation, not by the User; the Payout Schedule is the User's selection.
Stablecoin Partner Terms may be updated from time to time.
Legal Rights & Agreement Rules · Restriction or exception
The Payments Regional Terms apply by country or region and override the Payments Terms where they conflict
Section 15 sets out Regional Terms for listed countries and regions. Where a Regional Term conflicts with the main Stripe Payments Terms, the Regional Term prevails. Which Regional Terms apply depends on the User's Stripe Account Country, as Section 1 states.
Supporting quotations
15. Regional Terms.
The following Regional Terms apply for the countries or regions below. If there is a conflict between the Stripe Payments Terms and the Regional Terms, the Regional Terms prevail.
Qualifications & exceptions
Regional Terms prevail only to the extent of a conflict with the Payments Terms.
Charges & Financial Obligations · Restriction or exception
United States: Stripe and its affiliate SPC are both your agents for pooled settlement funds, replacing Section 4.2
For Users in the United States, Section 4.2 (Pooled Accounts) is replaced. The User appoints both Stripe and its Affiliate Stripe Payments Company (SPC) as agents for the limited purpose of directing, receiving, holding and settling funds. Settlement funds Stripe or SPC receives are pooled with other users' funds at Financial Providers. Once Stripe or SPC receives a Transaction's funds on the User's behalf, the Customer owes nothing further, and if funds are not settled the User's recourse is against Stripe or SPC, as applicable, not the Customer. Stripe will promptly update the account balance. The User has no rights to Pooled Account earnings, cannot draw from a Pooled Account and cannot direct transactions in or out of one.
Supporting quotations
United States.
The following Regional Terms apply for Users in the United States.
15.1 Pooled Accounts.
Section 4.2 (Pooled Accounts) is replaced with the following:
User appoints Stripe and Stripe’s Affiliate, SPC, as User’s agents for the limited purpose of directing, receiving, holding and settling funds under this Agreement. All settlement funds Stripe or, as applicable, SPC receives for Transactions are combined with settlement funds for other users and held in one or more Pooled Accounts at one or more Financial Providers.
If Stripe or SPC (as applicable) does not settle funds due to User under this Agreement, User will have recourse only against Stripe or SPC (as applicable) and not the relevant Customer.
Qualifications & exceptions
Applies to Users in the United States and replaces Section 4.2 entirely.
Recourse for unsettled funds lies against whichever of Stripe or SPC holds them.
Account & Service Control · Restriction or exception
EEA card rules: never pose as a network member, no harmful site content, track PIN devices, one name in authentications
For Users in the European Economic Area, additional card Transaction rules apply. The User must not misrepresent itself as a member of any Card Network. Its site and establishment must not contain libelous, defamatory, obscene, pornographic or profane material or instructions that may cause harm to individuals. The User must manage PIN entry device assets, recording each device's stock and serial numbers and location and performing basic electronic and physical identification and authentication of each device. For intra-EEA and intra-country Transactions in the EEA, the User must use the same name in the authentication messages it submits.
Supporting quotations
European Economic Area.
The following Regional Terms apply for Users in the European Economic Area.
15.1 Card Transactions.
15.1.1 Location and Identification.
In addition to the further requirements related to location and identification, User must not misrepresent itself as being a member of any Card Network.
15.1.2 Harmful Material.
User’s site and establishment (if applicable) must not contain libelous, defamatory, obscene, pornographic or profane material or any instructions that may cause harm to individuals.
15.1.3 PIN Entry Device Asset Management.
User must appropriately manage PIN entry device assets, including by (i) recording the stock and serial numbers of each PIN entry device; (ii) recording the location of each PIN entry device; and (iii) undertaking basic electronic and physical identification and authentication of each PIN entry device.
15.1.4 Intra-EEA and Intra-country Transactions.
User must use the same name in authentication messages User submits for intra-EEA Transactions and intra-country Transactions in the EEA.
Qualifications & exceptions
Applies to Users in the European Economic Area, in addition to the general location and identification requirements.
PIN entry device duties apply where the User has such devices.
Charges & Financial Obligations · Restriction or exception
EEA: you have 13 months, not 60 days, to report a Transaction history error for Stripe to help correct
For Users in the European Economic Area, deviating from Section 5.1, if the User finds an error when reconciling its Transaction history, Stripe will reasonably cooperate to investigate and help correct it as long as the User notifies Stripe within 13 months after the error appears in the Transaction history, replacing the general 60-day window.
Supporting quotations
15.2 Notice Period for Error Reconciliation.
Deviating from Section 5.1 (Reconciliation and Responsibility), if User finds an error when User reconciles User’s Transaction history, Stripe will reasonably cooperate with User to investigate and help correct that error as long as User notifies Stripe of the error within 13 months after the error appears in User’s Transaction history.
Qualifications & exceptions
Applies to Users in the European Economic Area and replaces the 60-day window of Section 5.1.
Account & Service Control · Procedure
EEA: you must make customer service information, including email and telephone contact instructions, readily available
For Users in the European Economic Area, as an additional requirement imposed by the Payment Method Rules, the User must make customer service information readily available to its Customers, including clear instructions on how Customers can contact it by email and telephone.
Supporting quotations
15.3 Additional Customer Service Information Requirements Imposed by Payment Method Rules.
User must make customer service information readily available to User’s Customers, including clear instructions on how User’s Customers can contact User by email and telephone.
Qualifications & exceptions
Applies to Users in the European Economic Area; both email and telephone contact instructions are required.
Account & Service Control · Restriction or exception
UK, Switzerland, Gibraltar card rules: never pose as a network member, no harmful site content, manage PIN devices
For Users in the United Kingdom, Switzerland and Gibraltar, the same additional card Transaction rules as the EEA apply: the User must not misrepresent itself as a member of any Card Network, and its site and establishment must not contain libelous, defamatory, obscene, pornographic or profane material or instructions that may cause harm to individuals. A PIN entry device asset-management duty follows under heading 15.1.3; its text is in the next packet.
Supporting quotations
United Kingdom, Switzerland, Gibraltar.
The following Regional Terms apply for Users in the United Kingdom, Switzerland and Gibraltar.
15.1 Card Transactions.
15.1.1 Location and Identification.
In addition to the further requirements related to location and identification, User must not misrepresent itself as being a member of any Card Network.
15.1.2 Harmful Material.
User’s site and establishment (if applicable) must not contain libelous, defamatory, obscene, pornographic or profane material or any instructions that may cause harm to individuals.
15.1.3 PIN Entry Device Asset Management.
Qualifications & exceptions
Applies to Users in the United Kingdom, Switzerland and Gibraltar, in addition to the general location and identification requirements.
Account & Service Control · Restriction or exception
UK, Switzerland, Gibraltar: manage PIN devices, 13 months to report reconciliation errors, publish email and phone
For Users in the United Kingdom, Switzerland and Gibraltar, the User must manage PIN entry device assets by recording each device's stock and serial numbers and location and performing basic electronic and physical identification and authentication. Deviating from Section 5.1, the window for notifying Stripe of a Transaction history error so that Stripe will help correct it is 13 months after the error appears, not 60 days. As an additional Payment Method Rules requirement, the User must make customer service information readily available, including clear email and telephone contact instructions.
Supporting quotations
User must appropriately manage PIN entry device assets, including by (i) recording the stock and serial numbers of each PIN entry device; (ii) recording the location of each PIN entry device; and (iii) undertaking basic electronic and physical identification and authentication of each PIN entry device.
15.2 Notice Period for Error Reconciliation.
Deviating from Section 5.1 (Reconciliation and Responsibility), if User finds an error when User reconciles User’s Transaction history, Stripe will reasonably cooperate with User to investigate and help correct that error as long as User notifies Stripe of the error within 13 months after the error appears in User’s Transaction history.
15.3 Additional Customer Service Information Requirements Imposed by Payment Method Rules.
User must make customer service information readily available to User’s Customers, including clear instructions on how User’s Customers can contact User by email and telephone.
Qualifications & exceptions
Applies to Users in the United Kingdom, Switzerland and Gibraltar.
The 13-month window replaces the general 60-day window of Section 5.1.
Charges & Financial Obligations · Restriction or exception
Australia: no liability for fraud, Dispute, Refund or Reversal losses caused by Stripe’s own fault
For Users in Australia, the User's sole responsibility for erroneous and fraudulent Transactions (Section 3.9), its responsibility for Disputes, related costs, Refunds and Reversals (Section 5.2), and its responsibility under Section 11 (Fraudulent Transactions) do not apply to the extent the losses, damages and costs arise from the fraud, wilful misconduct or negligent acts or omissions of Stripe or its Affiliates. This carve-out is absent from the general clauses.
Supporting quotations
Australia.
The following Regional Terms apply for Users in Australia.
15.1 Responsibility for Transactions, Disputes, Refunds and Reversals.
User’s sole responsibility for erroneous and fraudulent Transactions in Section 3.9 (User Responsibility for Transactions), User’s responsibility for Disputes and other related costs, Refunds and Reversals in Section 5.2 (Disputes; Refunds; Reversals), and User’s responsibility in Section 11 (Fraudulent Transactions) do not apply to the extent any losses, damages and costs arise out of the fraud, wilful misconduct or negligent acts or omissions of Stripe or its Affiliates.
Qualifications & exceptions
Applies to Users in Australia.
The carve-out operates 'to the extent' the loss arises from Stripe's or its Affiliates' fraud, wilful misconduct or negligence.
Charges & Financial Obligations · Procedure
Australia: reconcile monthly, report errors as soon as possible, and keep a 13-month window for Stripe's help
For Users in Australia, deviating from Section 5.1, the duty to review the Transaction history for accuracy and completeness and reconcile it with transfers from the Pooled Accounts to User Bank Accounts and Financial Accounts applies monthly. The User must notify Stripe as soon as possible on finding an error, and Stripe will reasonably cooperate to investigate and help correct it if notified within 13 months after the error appears.
Supporting quotations
15.2 Reconciliation.
Deviating from Section 5.1 (Reconciliation and Responsibility), User’s obligation to review User’s Transaction history for accuracy and completeness and for reconciling it with the history of transfers from the Pooled Accounts to the User Bank Accounts and Financial Accounts applies on a monthly basis. User must notify Stripe as soon as possible if User finds an error. Stripe will reasonably cooperate with User to investigate and help correct the error as long as User notifies Stripe of the error within 13 months after the error appears in User’s Transaction history.
Qualifications & exceptions
Applies to Users in Australia; replaces the 60-day window of Section 5.1 with 13 months and sets a monthly reconciliation cadence.
Sharing & Disclosure · Restriction or exception
Australia: the waiver of claims over Stripe sharing your information with payment providers does not apply
For Users in Australia, the Section 3.6 waiver of the User's right to bring any claim against Stripe arising from Stripe sharing information about the User Group with Payment Method Providers and Payment Method Acquirers does not apply. The sharing itself remains permitted under Section 3.6.
Supporting quotations
15.3 Data Sharing.
The waiver in Section 3.6 (Data Sharing) of User’s right to bring any claim against Stripe arising from Stripe sharing information about User Group with Payment Method Providers and Payment Method Acquirers does not apply.
Qualifications & exceptions
Applies to Users in Australia; only the claim waiver is switched off, not the sharing permission.
Legal Rights & Agreement Rules · Context
Brazil: Stripe itself, not an Affiliate or Financial Provider, is the Payment Method Acquirer
For Users in Brazil, for the avoidance of doubt, Stripe is the Payment Method Acquirer, not a Stripe Affiliate or a Financial Provider. This fixes which entity plays the acquirer role described in Sections 3.2 and 3.3 of the Payments Terms.
Supporting quotations
Brazil.
The following Regional Terms apply for Users in Brazil.
15.1 Stripe as the Payment Method Acquirer.
For the avoidance of doubt, Stripe is the Payment Method Acquirer in Brazil, not a Stripe Affiliate or Financial Provider.
Qualifications & exceptions
Applies to Users in Brazil.
Account & Service Control · Procedure
Brazil: your name and URL may appear on Customers’ bank statements, so the descriptor must clearly identify you
For Users in Brazil, when using the Stripe Payment Services, the User's name (or the name used to identify it) and URL may appear on Customers' bank statements. To minimize confusion and avoid disputes, the text the User gives Stripe for this purpose must let Customers clearly identify the User and accurately describe its business or activities.
Supporting quotations
15.2 User Identification Information in Bank Statements.
When using Stripe Payment Services, User’s name (or the name used to identify User) and URL may appear on Customers’ bank statements. To minimize confusion and avoid potential disputes, the text User provides to Stripe for this purpose must clearly allow Customers to identify User and accurately describe User’s business or activities.
Qualifications & exceptions
Applies to Users in Brazil.
Charges & Financial Obligations · Restriction or exception
Brazil: Stripe may add a holding period before your first settlement only to the extent Law permits
For Users in Brazil, for the avoidance of doubt, when transferring settlement funds Stripe may impose an additional holding period before the initial settlement to a User Bank Account, Financial Account or Stablecoin Partner Wallet only to the extent Law permits. This qualifies the general Section 4.3(a) right to impose an initial holding period.
Supporting quotations
15.3 Transaction Settlement Funds.
For the avoidance of doubt, when transferring settlement funds for Transactions, Stripe may only impose an additional holding period before making the initial settlement to a User Bank Account, Financial Account, or Stablecoin Partner Wallet, as applicable, to the extent Law permits.
Qualifications & exceptions
Applies to Users in Brazil; limits the Section 4.3 initial holding period to what Law permits.
Charges & Financial Obligations · Context
Canada: the key-elements summary, cost-per-transaction and fee disclosures live on a linked disclosures site
For Users in Canada, the Summary of Key Elements of the Agreement, the Cost Per Transaction Disclosure and the Disclosure of Fees are on Stripe's Required Regulatory Disclosures site. Additional fees and pricing information are on the Stripe Pricing Page, in the Agreement and in the Stripe Dashboard. These pages are linked but not supplied.
Supporting quotations
Canada.
The following Regional Terms apply for Users in Canada.
15.1 Required Regulatory Disclosures.
The Summary of Key Elements of the Agreement, Cost Per Transaction Disclosure and Disclosure of Fees can be found on
Qualifications & exceptions
Applies to Users in Canada.
Not stated here
The disclosures and pricing pages are external and not supplied; the amounts are not stated here.
Charges & Financial Obligations · Restriction or exception
Hong Kong: local American Express terms apply, Stripe is no fiduciary over pooled funds, third-party sends follow Law
For Users in Hong Kong, the country-specific Terms and Conditions for American Express Card Acceptance apply instead of the American Express Merchant Operating Guide linked in Section 3.4(a). As holder of the Pooled Accounts under Section 4.2, Stripe does not act as a fiduciary or trustee. And Stripe will offer the Section 4.4 ability to send funds to a third party only to the extent Law permits.
Supporting quotations
Hong Kong.
The following Regional Terms apply for Users in Hong Kong.
15.1 Card Network Rules.
Instead of the version of the American Express Merchant Operating Guide linked to in Section 3.4(a) (Card Network Rules), these country-specific
15.2 No Fiduciary or Trustee.
As a holder of Pooled Accounts as described in Section 4.2 (Pooled Accounts), Stripe does not act as a fiduciary nor trustee.
15.3 Sending Funds to Third-Party Recipients.
For the avoidance of doubt, Stripe will only offer User the ability to send funds to a third party as described in Section 4.4 (Sending Funds to Third-Party Recipients) to the extent this is permitted by Law.
Qualifications & exceptions
Applies to Users in Hong Kong.
The Hong Kong American Express terms are linked, not supplied.
Legal Rights & Agreement Rules · Context
India: you agree Stripe acts only as a payment facilitator and is not a bank or non-banking financial company
For Users in India, the User expressly agrees and acknowledges that Stripe acts, and will at all times act, only as a payment facilitator for Transactions between the User and its Customers. Stripe is not, and will not be characterized as, a banking company under the Banking Regulation Act, 1949 or a non-banking financial company under the Reserve Bank of India Act, 1934.
Supporting quotations
India.
The following Regional Terms apply for Users in India.
15.1 Stripe acting as Payment Facilitator.
User expressly agrees and acknowledges that Stripe acts and will act (at all times) only as a payment facilitator with respect to the Transactions between User and User’s Customers. Stripe is not and will not be characterized as: (i) a banking company as defined under the Banking Regulation Act, 1949 or (ii) a non-banking financial company as defined by the Reserve Bank of India Act, 1934.
Qualifications & exceptions
Applies to Users in India.
The Indian statutes are cited by name; their text is not supplied.
Account & Service Control · Restriction or exception
India: use the Payment Services only for selling goods and services, not for donations or charitable payments
For Users in India, the User may use the Stripe Payment Services only for Transactions for the provision of goods and services to its Customers. Processing donations or payments for charitable services is excluded, which narrows the general terms that elsewhere contemplate accepting donations.
Supporting quotations
15.2 Processing Transactions for Provision of Goods and Services.
User may only use the Stripe Payment Services in connection with Transactions for the provision of goods and services to User’s Customers. This does not include processing of donations or payments for charitable services.
Qualifications & exceptions
Applies to Users in India.
Donations and charitable payments are expressly excluded.
Account & Service Control · Procedure
India: your website must clearly show your terms and conditions and the timeline for returns and refunds
For Users in India, the User must ensure its website clearly indicates the terms and conditions for the goods or services it provides to Customers and the timeline for processing returns and refunds.
Supporting quotations
15.3 Terms and Conditions for User’s own Goods or Services.
User will ensure that User’s website clearly indicates the terms and conditions for the goods or services that User provides to its Customers, and the timeline for processing returns and refunds.
Qualifications & exceptions
Applies to Users in India.
Charges & Financial Obligations · Company practice
India: merchant discount rate charges are billed separately from the Fees under Law, and Stripe may waive them
For Users in India, the Fees do not include amounts for the merchant discount rate (MDR Charges), which are charged in accordance with applicable Law and separately from the Fees. The Stripe Pricing Page describes the MDR Charges, and Stripe reserves the right to waive any that are imposed.
Supporting quotations
15.4 Merchant Discount Rate Charges.
The Fees do not include any amounts towards the merchant discount rate ("MDR Charge(s)"), which will be charged in accordance with applicable Law and separate from the Fees. The Stripe Pricing Page describes the details of the MDR Charges. Stripe reserves the right to waive any such MDR Charges which are imposed.
Qualifications & exceptions
Applies to Users in India.
Waiver is at Stripe's discretion.
Not stated here
The MDR Charge amounts are on the Stripe Pricing Page, not supplied.
Legal Rights & Agreement Rules · User right or choice
India: complaints about the Payment Services go through the channels in Stripe's board-approved Complaints Policy
For Users in India, a User with a complaint about the Stripe Payment Services may contact Stripe through the channels named in Stripe's board-approved Complaints Policy on handling Customer complaints. The policy is linked but not supplied.
Supporting quotations
15.5 Complaints Policy.
If User has a complaint about the Stripe Payment Services, User may contact Stripe through the appropriate channels mentioned in Stripe’s board-approved
Qualifications & exceptions
Applies to Users in India.
Not stated here
The Complaints Policy's channels and timelines are not in this text.
Legal Rights & Agreement Rules · Restriction or exception
India: you and your providers must follow all relevant Laws, including the RBI payment-data storage circular
For Users in India, the User must comply, and ensure any third-party service provider it engages complies, with all Laws relevant to its use of the Services, whether or not those Laws apply directly to the User or its providers. This expressly includes the Reserve Bank of India's circular of April 6, 2018 on 'Storage of Payment System Data' and any directions issued in connection with it.
Supporting quotations
15.6 Compliance with Law and Reserve Bank of India’s Requirements.
User will comply, and will ensure that third-party service provider User engages will comply, with all Laws that may be relevant to User’s use of the Services, whether or not those Laws are directly applicable to User or User’s third-party service providers, including compliance with the circular dated April 6, 2018 on ‘Storage of Payment System Data’ issued by the Reserve Bank of India, and any directions or instructions issued in connection with the circular.
Qualifications & exceptions
Applies to Users in India.
The duty reaches Laws not directly applicable to the User or its providers.
The RBI circular is cited by name and date; its text is not supplied.
Data Access & Collection · Restriction or exception
India: you must get explicit Customer consent to tokenize card data, and may not exceed RBI monetary limits
For Users in India, the User is responsible for obtaining explicit consent from its Customers to tokenize their card data in accordance with Law, where applicable. The User may not use the Services for a value above the monetary limits the Reserve Bank of India specifies from time to time, if applicable.
Supporting quotations
15.7 Tokenization of Customer Card Data.
User is responsible for obtaining explicit consent from User’s Customers to tokenize Customer card data in accordance with Law, if applicable.
15.8 Monetary Limits.
User may not use the Services for a value above the monetary limits specified by the Reserve Bank of India from time to time, if applicable.
Qualifications & exceptions
Applies to Users in India; both duties are qualified by 'if applicable'.
Monetary limits are set by the Reserve Bank of India and may change.
Not stated here
The current RBI limits are not stated.
Charges & Financial Obligations · Company practice
India: payout speed depends on domestic or cross-border type; providers or your bank may delay settlement for any reason
For Users in India, the Payout Speed may differ between domestic and cross-border transaction types and is stated in the Documentation. Stripe will settle funds to the User Bank Account or Financial Account according to the Payout Speed for that type. However, a Payment Method Provider, a Payment Method Acquirer or the financial institution holding the User's account may delay settlement for any reason.
Supporting quotations
15.9 Payout Speed.
The Payout Speed might differ depending on domestic or cross-border transaction type and is stated in the Documentation. Stripe will settle funds to the User Bank Account or Financial Account according to the Payout Speed applicable to that transaction type. However, a Payment Method Provider, a Payment Method Acquirer, or the financial institution holding the User Bank Account or Financial Account, may delay settlement for any reason.
Qualifications & exceptions
Applies to Users in India.
Third-party delays need no reason.
Not stated here
The Payout Speeds themselves are in the Documentation, not supplied.
Use & Processing · Company practice
India: Stripe may serve you from systems abroad; tell Customers their data may leave India and get their consents
For Users in India, Stripe will provide the Services from systems located in India or in other countries, to the extent applicable Law permits, and will provide Payment Processing Services in compliance with the RBI circular of April 6, 2018 on 'Storage of Payment System Data'. The User must disclose to its Customers that Data may be transferred, processed and stored outside India in compliance with Law and, as set out in Stripe's Privacy Policy, may be disclosed as Laws require, and must obtain from Customers all consents applicable Laws require for this.
Supporting quotations
15.10 Provision of Services from Systems located outside of India.
Stripe will provide the Services from systems located within India or other countries outside of India (to the extent permissible under applicable Law). Without limiting the generality of the prior sentence, Stripe will provide Payment Processing Services in compliance with circular dated April 6, 2018 on ‘Storage of Payment System Data’ issued by the Reserve Bank of India. It is User’s obligation to disclose to User’s Customers that Data may be transferred, processed and stored outside of India (in compliance with applicable Law) and, as set forth in Stripe’s Privacy Policy, may be subject to disclosure as required by applicable Laws, and to obtain from User’s Customers all necessary consents under applicable Laws in relation to the foregoing.
Qualifications & exceptions
Applies to Users in India.
Cross-border provision is limited to what applicable Law permits.
Stripe's Privacy Policy is referenced but not supplied.
Not stated here
Which countries' systems are used is not stated.
Charges & Financial Obligations · Restriction or exception
India: refund to the original method, store no card data beyond what Law allows, show extra charges before payment
For Users in India, all Refunds must go to the original method of payment unless the Customer specifically agrees to a credit to another mode belonging to the same Customer, or Law requires otherwise. The User must not store Customers' card and related data except to the extent applicable Law permits. Any charges other than the price of the goods, services or investment amount must be distinctly displayed to the payer before the transaction.
Supporting quotations
15.11 Refunds.
All Refunds must be made to the original method of payment unless specifically agreed by the User’s Customer to credit to an alternate mode belonging to the same Customer or as required under Law.
15.12 Storage of Card Data.
User must not store Customers’ card and related data, except to the extent applicable Law permits.
15.13 Disclosure of Charges.
User must ensure that any charges, other than the price of goods, services or investment amount, are distinctly displayed to the payer prior to the transaction.
Qualifications & exceptions
Applies to Users in India.
Refunds to another mode require the same Customer's specific agreement or a legal requirement.
Card data storage is allowed only to the extent applicable Law permits.
Security & Safeguards · Restriction or exception
India: your infrastructure must meet the PCI Standards and you must prove it, or Stripe may suspend or terminate
For Users in India, the User must ensure its infrastructure complies with the PCI Standards as applicable, maintain a PCI-compliant system and give Stripe evidence of compliance. If the User does not comply, or Stripe, a Payment Method Provider or a Payment Method Acquirer cannot verify compliance, Stripe may suspend the User's Stripe Account or terminate the Agreement in whole or in part. Unlike the general Section 9, this duty is not conditioned on the User electing to store Account Data.
Supporting quotations
15.14 PCI Standards Compliance.
User must ensure that its infrastructure is compliant with the PCI Standards, as applicable. User must maintain a system that complies with the PCI Standards. User must provide to Stripe evidence of User’s compliance. If User does not comply with the PCI Standards, or if Stripe or any Payment Method Provider or Payment Method Acquirer is unable to verify User’s compliance with the PCI Standards, Stripe may suspend User’s Stripe Account or terminate this Agreement, in whole or in part.
Qualifications & exceptions
Applies to Users in India and is unconditional, unlike the general Section 9 which applies only if the User elects to store Account Data.
Sharing & Disclosure · Restriction or exception
India: accepting American Express means following its Terms and Data Security Policy and sharing your data with Amex
For Users in India who elect to accept American Express cards, the following Payment Method Terms apply: the User will comply with American Express' Terms and Conditions and Data Security Policy, including obligations on disputes, transaction processing, authorization, submission, prohibited uses and transactions, and protecting Customer information. The User consents to Stripe disclosing its Transaction data, merchant data, personal information and other information to American Express, and to American Express using it to perform its obligations, operate its business, perform analytics, create reports and for any other lawful business purpose. A further term on displaying American Express trademarks follows in the next packet.
Supporting quotations
15.15 American Express Payment Method Terms.
User agrees to the following Payment Method Terms if User elects to accept payments using American Express cards in India:
including User’s obligations concerning disputes, transaction processing, authorization, submission, prohibited uses and transactions, and protecting Customer information.
User consents to Stripe’s disclosure of User’s Transaction data, merchant data, personal information, and other information to American Express and to American Express' use of such information to perform its obligations, operate its business, perform analytics or create reports and any other lawful business purpose.
Qualifications & exceptions
Applies to Users in India who elect to accept American Express cards.
American Express's permitted uses of the shared data are broad, ending in 'any other lawful business purpose'.
Not stated here
The American Express Terms and Conditions and Data Security Policy are linked external documents, not supplied.
Account & Service Control · Restriction or exception
India Amex terms: show Amex marks equally, no higher surcharge, no discouraging, equal refunds, give contact details
Users in India who accept American Express cards must display the American Express trademarks Stripe provides with at least equal representation to other payment methods they offer, through Stripe or otherwise. They must 'warmly welcome' American Express cards: either no surcharge for American Express, or a surcharge no greater than the lowest surcharge for any other credit card they accept. They must not discourage Customers from using American Express or disparage the brand; their site and establishment must not contain libelous, defamatory, obscene, pornographic or profane material or harmful instructions; their refund policy for American Express must be at least as favorable to Customers as for other payment methods; and they must provide contact information, including email and phone, that lets Customers access their Transaction information.
Supporting quotations
User will display American Express trademarks that Stripe may provide User from time to time and give them at least equal representation with other payment methods User offers, whether through Stripe or otherwise.
User will "warmly welcome" American Express cards meaning that either User will not surcharge User’s Customers for use of American Express cards, or if User does, that such surcharge will be no greater than the lowest surcharge for any other credit card User accepts.
User will not discourage Customers from using American Express cards or disparage the American Express brand.
User’s site and establishment (if applicable) must not contain libelous, defamatory, obscene, pornographic or profane material or any instructions that may cause harm to individuals.
User’s refund policy for use of American Express cards must be at least as favorable to User’s Customers as the refund policy for other payment methods User accepts.
User will provide User’s contact information (including email and phone) that will allow User’s Customers to access their Transaction information.
Qualifications & exceptions
Applies to Users in India who elect to accept American Express cards.
A surcharge on American Express is allowed only if no greater than the lowest surcharge on any other accepted credit card.
Legal Rights & Agreement Rules · Restriction or exception
India Amex terms: Amex excludes indirect damages and carrier or bank delays, owes you nothing, and can enforce on you
Under the India American Express terms, American Express's liability for the User's acceptance of its cards excludes indirect, consequential, exemplary, punitive or special damages, even if American Express was warned they might occur, and American Express is not responsible for damages from delays or problems caused by telecommunications carriers or the banking system. The Payment Terms give the User no rights against American Express, while American Express is an intended third-party beneficiary entitled to enforce the Payment Terms and its own Terms and Conditions against the User.
Supporting quotations
American Express' liability in connection with User’s acceptance of American Express cards will not include indirect or consequential, exemplary, punitive or special damages, even if American Express has been advised of the possibility of such damages in advance. American Express will not be responsible for damages arising from delays or problems caused by telecommunications carriers or the banking system.
These Payment Terms do not give User any rights against American Express. American Express is an intended third-party beneficiary of these Payment Terms and is entitled to enforce these Payment Terms and its Terms and Conditions against User.
Qualifications & exceptions
Applies to Users in India who elect to accept American Express cards.
Rights run one way: American Express can enforce against the User, but the User gains no rights against American Express.
Legal Rights & Agreement Rules · Context
Indonesia: a Refund you instruct is not money transmission carried out by Stripe on your behalf
For Users in Indonesia, the User agrees and understands that any return of funds to a Customer for a Refund, made on the User's instruction, is not a money transmission carried out by Stripe on the User's behalf.
Supporting quotations
Indonesia.
The following Regional Terms apply for Users in Indonesia.
15.1 Refunds.
User agrees and understands that any return of funds to a Customer for a Refund pursuant to an instruction from User is not a money transmission carried out by Stripe on User’s behalf.
Qualifications & exceptions
Applies to Users in Indonesia.
Charges & Financial Obligations · Restriction or exception
Malaysia: no BNM-regulated banking or remittance; you bear fraud losses unless a rule like 3-D Secure protects you
For Users in Malaysia, Stripe does not offer banking or remittance services regulated by Bank Negara Malaysia. The Payment Method Rules describe situations, such as a Transaction that fully complies with the 3-D Secure specification, in which the User is not held liable for unauthorized Transactions; outside those situations the User is solely responsible for fraudulent Transactions under Sections 3.9 and 11 of the Payments Terms.
Supporting quotations
Malaysia.
The following Regional Terms apply for Users in Malaysia.
15.1 No Banking or Remittance Services.
Stripe does not offer banking or remittance services regulated by Bank Negara Malaysia.
15.2 Fraudulent Transactions.
However, if User does not fall within such a situation, User is solely responsible for fraudulent Transactions as described in Section 3.9 (User Responsibility for Transactions) and Section 11 (Fraudulent Transactions).
Qualifications & exceptions
Applies to Users in Malaysia.
Relief from fraud liability depends on falling within a situation the Payment Method Rules describe, such as full 3-D Secure compliance.
Not stated here
The Payment Method Rules and the 3-D Secure specification are external, not supplied.
Charges & Financial Obligations · Restriction or exception
Mexico: Stripe is your non-exclusive agent under the Commercial Code, and third-party fund sending is not offered
For Users in Mexico, for the avoidance of doubt, the User appoints Stripe as a non-exclusive agent as specified in Section 4.2 (Pooled Accounts), and Stripe unconditionally accepts the appointment as described under the Mexican Commercial Code. Stripe will not offer Mexican Users the Section 4.4 ability to send funds to a third party.
Supporting quotations
Mexico.
The following Regional Terms apply for Users in Mexico.
15.1 Appointment as non-exclusive Agent.
For the avoidance of doubt, User appoints Stripe as a non-exclusive agent as further specified in Section 4.2 (Pooled Accounts), and Stripe unconditionally accepts the appointment as described under the Mexican Commercial Code.
15.2 Sending Funds to Third-Party Recipients.
For the avoidance of doubt, Stripe will not offer User the ability to send funds to a third party as described in Section 4.4 (Sending Funds to Third-Party Recipients).
Qualifications & exceptions
Applies to Users in Mexico.
The agency is non-exclusive; the third-party sending feature is unavailable.
Not stated here
The Mexican Commercial Code is cited by name; its text is not supplied.
Charges & Financial Obligations · Restriction or exception
Mexico: Customers may choose installments at the same total with no interest; PCI Standards include IFAI guidelines
For Users in Mexico who elect to offer installment payments, the Customer decides whether to pay in one installment or several. If the Customer chooses multiple installments, the User must charge the same total it would have charged for a single payment and may not charge interest on the installments. The definition of PCI Standards also includes the Mexican PCI guidelines issued by the Federal Institute of Access to Information (IFAI).
Supporting quotations
15.3 Installments Payments.
If User elects to offer to User’s Customers payment in installments, User’s Customer may decide whether payment will be carried out in one single installment or in multiple installments. If User’s Customer selects payment in multiple installments, User agrees to charge User’s Customer the same total amount that would be charged if payment was carried out in one single installment, and User will not charge User’s Customer any interest costs on installment payments.
15.4 PCI Standards.
The definition of PCI Standards also includes the guidelines in Mexico for PCI issued by the Federal Institute of Access to Information (Instituto Federal de Acceso a la Información or IFAI).
Qualifications & exceptions
Applies to Users in Mexico; the installment rules apply only if the User elects to offer installments.
Not stated here
The IFAI guidelines are cited by name; their text is not supplied.
Charges & Financial Obligations · Restriction or exception
New Zealand: no liability for fraud, Dispute, Refund or Reversal losses caused by Stripe's own fault
For Users in New Zealand, as for Australia, the User's sole responsibility for erroneous and fraudulent Transactions (Section 3.9), for Disputes, related costs, Refunds and Reversals (Section 5.2) and under Section 11 (Fraudulent Transactions) does not apply to the extent the losses, damages and costs arise from the fraud, wilful misconduct or negligent acts or omissions of Stripe or its Affiliates.
Supporting quotations
New Zealand.
The following Regional Terms apply for Users in New Zealand.
15.1 Responsibility for Transactions, Disputes, Refunds and Reversals.
User’s sole responsibility for erroneous and fraudulent Transactions in Section 3.9 (User Responsibility for Transactions), User’s responsibility for Disputes and other related costs, Refunds and Reversals in Section 5.2 (Disputes; Refunds; Reversals), and User’s responsibility in Section 11 (Fraudulent Transactions) do not apply to the extent any losses, damages and costs arise out of the fraud, wilful misconduct or negligent acts or omissions of Stripe or its Affiliates.
Qualifications & exceptions
Applies to Users in New Zealand.
Operates 'to the extent' the loss arises from Stripe's or its Affiliates' fraud, wilful misconduct or negligence.
Charges & Financial Obligations · Procedure
New Zealand: reconcile monthly, report errors as soon as possible, and keep a 13-month window for Stripe's help
For Users in New Zealand, deviating from Section 5.1, the duty to review and reconcile the Transaction history applies monthly; the User must notify Stripe as soon as possible on finding an error, and Stripe will reasonably cooperate to investigate and help correct it if notified within 13 months after the error appears.
Supporting quotations
15.2 Reconciliation.
Deviating from Section 5.1 (Reconciliation and Responsibility), User’s obligation to review User’s Transaction history for accuracy and completeness and for reconciling it with the history of transfers from the Pooled Accounts to the User Bank Accounts and Financial Accounts, as applicable, apply on a monthly basis. User must notify Stripe as soon as possible if User finds an error. Stripe will reasonably cooperate with User to investigate and help correct the error as long as User notifies Stripe of the error within 13 months after the error appears in User’s Transaction history.
Qualifications & exceptions
Applies to Users in New Zealand; replaces the 60-day window with 13 months and sets a monthly cadence.
Sharing & Disclosure · Restriction or exception
New Zealand: the waiver of claims over Stripe sharing your information with payment providers does not apply
For Users in New Zealand, the Section 3.6 waiver of the User's right to bring any claim against Stripe arising from Stripe sharing information about the User Group with Payment Method Providers and Payment Method Acquirers does not apply. The sharing permission itself is unchanged.
Supporting quotations
The waiver in Section 3.6 (Data Sharing) of User’s right to bring any claim against Stripe arising from Stripe sharing information about User Group with Payment Method Providers and Payment Method Acquirers does not apply.
Qualifications & exceptions
Applies to Users in New Zealand; only the claim waiver is switched off.
Account & Service Control · Restriction or exception
Japan: local American Express terms apply; individuals or sole proprietors may give their address on request instead
For Users in Japan, country-specific American Express Terms and Conditions replace the American Express Merchant Operating Guide linked in Section 3.4(a). Section 3.4(b) on location and identification is replaced with a version that keeps the same rules, acceptance only where Stripe and the Card Network authorize, prominent disclosure of name, address and country before card details are requested, clarity that the User is responsible, and no acting as a payment facilitator or reseller, with one exception: a User who is an individual or sole proprietor may choose to disclose its address to Customers promptly on request rather than up front.
Supporting quotations
Japan.
The following Regional Terms apply for Users in Japan.
15.1 Card Network Rules.
Instead of the version of the American Express Merchant Operating Guide linked to in Section 3.4(a) (Card Network Rules), these country-specific
15.2 Card Transactions: Location and Identification.
Section 3.4(b) (Location and Identification) is replaced with the following:
User must prominently and clearly disclose User’s name, address, and country location to Customers before Customers are prompted to provide payment card information, except that User may choose to disclose User’s address to Customers promptly upon request if User is an individual or sole proprietor.
Qualifications & exceptions
Applies to Users in Japan.
The address-on-request option is available only to individuals and sole proprietors.
The Japanese American Express terms are linked, not supplied.
Charges & Financial Obligations · Restriction or exception
Japan: Stripe may pay out faster than your schedule when Law requires; recurring charges need all legal disclosures
For Users in Japan, in addition to Section 4.3 and for the avoidance of doubt, Stripe may transfer settlement funds faster than the Payout Schedule states if Law requires it. For recurring or subscription Transactions, in addition to the Section 4.6 requirements, the User must disclose to Customers all information about those Transactions that Law requires before submitting the initial Transaction.
Supporting quotations
15.3 Shorter Settlement Period Required by Law.
In addition to Section 4.3 (Transaction Settlement Funds) and for the avoidance of doubt, Stripe may also transfer settlement funds faster than as stated in the Payout Schedule if required by Law.
15.4 Recurring or Subscription Transactions.
In addition to the further requirements in Section 4.6 (Subscriptions and Invoicing) for recurring or subscription Transactions, User must disclose all information about the relevant Transactions to Customers as Law requires before submitting the initial Transaction.
Qualifications & exceptions
Applies to Users in Japan.
Faster settlement is a legal override of the Payout Schedule, not a User option.
Not stated here
Which Law requires faster settlement or the recurring-payment disclosures is not named.
Charges & Financial Obligations · Company practice
Japan: for methods without native refunds, Stripe returns funds and debits you, unasked after 90 days or on triggers
For Users in Japan, where a Payment Method has no native Refund or Reversal function, such as Japan Bank Transfers or Konbini, Stripe processes Refunds and Reversals by returning funds to the Customer and then deducting the amount from the User's Stripe Account (a Non-Native Refund). Either the User or Stripe may initiate one, but the User always bears the obligation to return the funds. A User-initiated Non-Native Refund requires an instruction to Stripe, and the User is solely liable for errors in it. Stripe may initiate one with or without the User's approval if a Customer asks Stripe or the Payment Method Provider for a refund because the Transaction was unauthorized, fraudulent or in error; if Law or a court order requires; if the User keeps settlement funds in its Stripe Account for more than 90 days without Stripe's approval; if Stripe reasonably determines a Section 5.3 specific trigger has occurred; or if a Section 5.2(c) Reversal event occurs. If Stripe lacks the information to process a Non-Native Refund, the User must promptly supply it on request or immediately return the funds to the Customer itself.
Supporting quotations
15.5 Non-Native Refunds and Reversals.
For Payment Methods that do not have a native Refund or Reversal functionality, such as Japan Bank Transfers or Konbini, Stripe will process Refunds and Reversals to return funds to Customers and subsequently deduct a corresponding amount from User’s Stripe Account (“Non-Native Refund”). A Non-Native Refund may be initiated by User or Stripe but, in each case, User incurs the obligation to return the funds to User’s Customers. If User wishes to initiate a Non-Native Refund, User must instruct Stripe to process the Non-Native Refund and User is solely liable for any errors in that Non-Native Refund.
Stripe may also initiate a Non-Native Refund with or without User’s approval, if:
a Customer requests a Non-Native Refund from Stripe or a Payment Method Provider because the Transaction was unauthorized, fraudulent or in error
required by Law or court order
User retains settlement funds in User’s Stripe Account for more than 90 days, unless otherwise approved by Stripe
Stripe reasonably determines that any of the specific triggers under Section 5.3 (Stripe Remedies – Specific Triggers) has occurred
any of the events that would give rise to Stripe’s ability to initiate a Reversal under Section 5.2(c) (Reversals) occurs
Where Stripe does not have the information required to process a Non-Native Refund, User must either promptly provide Stripe with this information upon Stripe’s request or User must immediately return the relevant funds to the Customer.
Qualifications & exceptions
Applies to Users in Japan and to Payment Methods without native Refund or Reversal functionality.
Stripe's unilateral refund right includes a 90-day retention trigger that Stripe can waive by approval.
The User's obligation to return funds applies whether Stripe or the User initiates the refund.
Not stated here
Which other Payment Methods count as lacking native refund functionality is not listed.
Legal Rights & Agreement Rules · Restriction or exception
Singapore: country-specific American Express card acceptance terms replace the Merchant Operating Guide
For Users in Singapore, the country-specific Terms and Conditions for American Express Card Acceptance apply instead of the American Express Merchant Operating Guide linked in Section 3.4(a). The Singapore terms are linked but not supplied.
Supporting quotations
Singapore.
The following Regional Terms apply for Users in Singapore.
15.1 Card Network Rules.
Instead of the version of the American Express Merchant Operating Guide linked to in Section 3.4(a) (Card Network Rules), these country-specific
Qualifications & exceptions
Applies to Users in Singapore and only to American Express acceptance.
Not stated here
The Singapore American Express terms are external and not supplied.
Charges & Financial Obligations · Restriction or exception
UAE: Network International acquires Visa and Mastercard, binds you to its terms, is named to Customers and is co-agent
For Users in the United Arab Emirates, Network International, LLC is the Payment Method Acquirer for Visa and Mastercard Transactions. Submitting Visa or Mastercard Charges through the Stripe Services counts as agreement to the Network International Financial Services Terms (linked, not supplied), and under the Payment Method Rules Visa and Mastercard may enforce the Agreement directly against the User; the American Express conversion clause (Section 3.5) does not apply. Deviating from Section 3.7(d), the User must tell Customers that Stripe, its Affiliates where applicable, and Network International, LLC process its Transactions. Deviating from Section 4.2, the User appoints both Stripe and Network International, LLC as its agent for pooled settlement funds, so references to Stripe in that section mean Stripe or Network International as applicable.
Supporting quotations
United Arab Emirates.
The following Regional Terms apply for Users in the United Arab Emirates.
15.1 Network International, LLC as Payment Method Acquirer.
The Payment Method Acquirer for Visa and Mastercard Transactions is Network International, LLC. By using the Stripe Services to submit Visa or Mastercard Charges, User agrees to the Network International Financial Services Terms
In addition, pursuant to the applicable Payment Method Rules, Visa and Mastercard may enforce the terms of this Agreement directly against User. Section 3.5 (American Express Conversion – Only Applicable to the American Express Card Network) does not apply.
15.2 Customer Communications.
Deviating from Section 3.7 (d) (Customer Communications), User must inform Customers that Stripe and, if applicable, its Affiliates, and Network International, LLC process Transactions for User.
15.3 Appointment as Agent.
Deviating from Section 4.2 (Pooled Accounts), User appoints Stripe and Network International, LLC as User’s agent as further specified in that Section, and accordingly, any reference to Stripe in that section is a reference to Stripe or Network International, LLC (as applicable).
Qualifications & exceptions
Applies to Users in the United Arab Emirates.
Agreement to the Network International terms arises by submitting Visa or Mastercard Charges.
Section 3.5 (American Express conversion) does not apply.
Not stated here
The Network International Financial Services Terms are external and not supplied.
Which entity acquires non-Visa, non-Mastercard Payment Methods in the UAE is not stated.
Legal Rights & Agreement Rules · Context
The Adaptive Pricing Terms govern local-currency pricing, with the Financial Services Terms incorporated
The Stripe Adaptive Pricing Terms, last modified November 18, 2025, supplement the General Terms and incorporate the Stripe Financial Services Terms by reference; together they govern the Stripe Adaptive Pricing Services, which let the User present the price of its goods and services in a Customer's local currency using Stripe's Currency Exchange Rate, as described in the Documentation. Undefined capitalized terms take their meaning from the General Terms (not supplied) or the Financial Services Terms.
Supporting quotations
Stripe Adaptive Pricing
Last modified: November 18, 2025
1. Stripe Adaptive Pricing Services.
These terms (“Stripe Adaptive Pricing Terms”) supplement the General Terms and, together with the Stripe Financial Services Terms which are incorporated into these Stripe Adaptive Pricing Terms by this reference, govern the use of the Stripe Adaptive Pricing Services.
“Stripe Adaptive Pricing Services” means the Services that enable User to present the price of its goods and services in a Customer’s local currency using the Currency Exchange Rate, as described in the Documentation.
Qualifications & exceptions
The Financial Services Terms are incorporated by reference, so their Reserve, security interest and regional rules apply to this Service.
No Regional Terms section exists in these terms.
Not stated here
The Documentation describing the Service is not supplied.
Charges & Financial Obligations · Procedure
Tell Customers the local-currency service may include a markup and extra network fees, and offer them a currency choice
When using the Stripe Adaptive Pricing Services, the User must inform each Customer that, as between the User and Stripe, the User is providing a service letting the Customer pay in its local currency; that the service may include a markup on the prevailing exchange rate; and that a Card Network may impose additional transaction fees on purchases from foreign merchants even if the Customer pays in local currency. The User must also present each Customer with the option of paying in either the Integration Currency, the currency in which the User originally prices its goods, or the Customer's local currency as Stripe determines it.
Supporting quotations
2. Use of the Stripe Adaptive Pricing Services.
2.1 User Obligations. When using the Stripe Adaptive Pricing Services, User must:
inform each Customer that (i) as between User and Stripe, User is providing Customer a service that enables Customer to remit payment in Customer’s local currency, (ii) this service may include a markup on the prevailing currency exchange rate, and (iii) a Card Network may impose additional transaction fees on Customer’s purchases from foreign merchants, even if Customer chooses to pay in its local currency
present each Customer with the option of paying in either the Integration Currency, or in the Customer’s local currency, as determined by Stripe.
“Integration Currency” means the currency in which a User originally prices its goods and services.
Qualifications & exceptions
The disclosures frame the User, not Stripe, as the provider of the local-currency service to the Customer.
The local currency offered is 'as determined by Stripe'.
Account & Service Control · Restriction or exception
Adaptive Pricing works only on Stripe-processed Transactions and only to accept payment for your own goods and services
The User may use the Stripe Adaptive Pricing Services only in connection with Transactions Stripe processes through the Stripe Payments Services, and only for accepting a Customer's payment for goods and services the User provides to Customers.
Supporting quotations
2.2 Services Restrictions. User may only use the Stripe Adaptive Pricing Services in connection with:
Transactions that Stripe processes via the Stripe Payments Services
accepting a Customer’s payment for goods and services that User provides to Customers
Qualifications & exceptions
Both conditions must hold: Stripe-processed Transactions and payment for the User's own goods and services.
Charges & Financial Obligations · Company practice
Stripe alone sets the exchange rate, may add a markup, may use another rate on settlement or refunds, may cut currencies
Stripe determines the Currency Exchange Rate for each Transaction in its sole discretion and may include its own markup in it. For any individual Transaction, Stripe may apply a different rate when it settles the resulting funds into the User's Stripe Account or when issuing Refunds. Stripe may add or remove supported currencies, and enable or disable interoperability of Adaptive Pricing with other Services, at any time in its sole discretion without notice to the User.
Supporting quotations
3. Stripe’s Rights.
Stripe will determine the Currency Exchange Rate for each Transaction in its sole discretion. Stripe may include its own markup within the Currency Exchange Rate. With respect to any individual Transaction, Stripe may apply a different exchange rate than the Currency Exchange Rate when Stripe settles the resulting funds into User’s Stripe Account, or when issuing Refunds.
Stripe may add or remove supported currencies at any time in its sole discretion without notice to User.
Stripe may enable or disable the interoperability of the Stripe Adaptive Pricing Services with other Services at any time in its sole discretion without notice to User.
“Currency Exchange Rate” means the Stripe-determined currency exchange rate applied during a Customer transaction to convert the prices of goods and services into Customer’s local currency.
Qualifications & exceptions
Rate setting, currency support and interoperability are all at Stripe's sole discretion.
No notice is required for currency or interoperability changes.
The settlement or Refund rate may differ from the rate shown to the Customer.
Not stated here
The size of Stripe's markup is not stated.
Legal Rights & Agreement Rules · Restriction or exception
Local-currency totals are higher, your manual prices override it, it is not foreign exchange, partner fees are yours
The User acknowledges that the Currency Exchange Rate is applied to Integration Currency prices to compute the local-currency price, so a Customer paying in local currency pays more in total than one paying in the Integration Currency. The User's configuration of the Stripe Payment Services can affect the Service: if the User manually sets prices in a particular alternative currency, Adaptive Pricing does not apply to those prices and the manual prices prevail. The Stripe Adaptive Pricing Services do not supply foreign currency and are not a foreign currency exchange or similar service. The User is fully responsible for, and Stripe disclaims liability for, additional fees a Financial Services Partner may charge the User or a Customer in relation to the Service.
Supporting quotations
4. Disclaimers.
If User uses the Stripe Adaptive Pricing Services, User acknowledges that the Currency Exchange Rate will be applied to the Integration Currency prices of goods and services to calculate the corresponding Customer local currency price, and the total amount a Customer pays in their local currency will be higher than if they pay in the Integration Currency.
User’s use and configuration of the Stripe Payment Services may affect the operation of the Stripe Adaptive Pricing Services. For example, if User manually sets prices for User’s goods and services in a particular alternative currency, the Stripe Adaptive Pricing Services will not apply to determine the price of those goods and services in that particular currency, and User’s manually-set prices will prevail.
The Stripe Adaptive Pricing Services do not provide a supply of foreign currencies, and are not a foreign currency exchange or similar service.
User is fully responsible for, and Stripe disclaims all liability with respect to, additional fees a Financial Services Partner may charge User or a Customer in relation to the Stripe Adaptive Pricing Services.
Qualifications & exceptions
Manually set alternative-currency prices take precedence over Adaptive Pricing for that currency.
Stripe disclaims liability for Financial Services Partner fees to either the User or the Customer.
Not stated here
'Financial Services Partner' is a capitalized term not defined in these terms; its definition presumably sits in the General Terms, not supplied.
Legal Rights & Agreement Rules · Context
Adaptive Pricing definitions: Card Network, Currency Exchange Rate, Integration Currency, Refund and the Services
Section 5 defines the terms used in these Adaptive Pricing Terms: 'Card Network' (including Visa, Mastercard, American Express and Discover), 'Currency Exchange Rate' (the Stripe-determined rate applied during a Customer transaction to convert prices into the Customer's local currency), 'Integration Currency' (the currency in which the User originally prices its goods and services), 'Refund' (a User-initiated full or partial return of funds for a processed Transaction) and 'Stripe Adaptive Pricing Services' (the Services that present prices in a Customer's local currency using the Currency Exchange Rate). A 'Back to Top' link closes the section.
Supporting quotations
5. Definitions.
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
“Currency Exchange Rate” means the Stripe-determined currency exchange rate applied during a Customer transaction to convert the prices of goods and services into Customer’s local currency.
“Integration Currency” means the currency in which a User originally prices its goods and services.
“Refund” means an instruction User initiates to provide a full or partial return of funds to a Customer for a processed Transaction.
“Stripe Adaptive Pricing Services” means the Services that enable User to present the price of its goods and services in a Customer’s local currency using the Currency Exchange Rate, as described in the Documentation.
Legal Rights & Agreement Rules · Context
The Agentic Commerce Agent Terms (Preview) govern APIs that let AI agents buy for customers; Radar Terms may apply
The Agentic Commerce Agent Terms, last modified April 20, 2026 and labeled Preview in the index, supplement the General Terms and, where applicable to the User, the Stripe Radar Terms, and govern use of the Agentic Commerce Agent Services: the Services, including APIs and related infrastructure, that enable the Agentic Interface, as described in the Documentation. Undefined capitalized terms take their meaning from the General Terms, the Stripe Radar Terms, the Stripe Connect Infrastructure Terms, the Stripe Payments Terms and the Stripe Orchestrated Services Terms.
Supporting quotations
Stripe Agentic Commerce Agent Services (Preview)
Last modified: April 20, 2026
1. Stripe Agentic Commerce Agent Services.
These terms ("Agentic Commerce Agent Terms") supplement the General Terms, and if applicable to User, the Stripe Radar Terms, and govern User's use of the Agentic Commerce Agent Services. Capitalized terms not defined in these Agentic Commerce Agent Terms have the meanings given to them in the General Terms, the Stripe Radar Terms, the Stripe Connect Infrastructure Terms, the Stripe Payments Terms and the Stripe Orchestrated Services Terms.
"Agentic Commerce Agent Services" means the Services, including the provision of APIs and related infrastructure, that enable the Agentic Interface, as described in the Documentation.
Qualifications & exceptions
The Radar Terms apply only 'if applicable to User'.
Definitions may come from five other sets of terms; the General Terms are not supplied.
Not stated here
What Preview status entails for this Service is not stated in these terms.
Account & Service Control · Procedure
Integrate per the Documentation, use Stripe Elements for agent purchases, follow the rules, and help resolve disputes
The User must integrate the Stripe API and use the Agentic Commerce Agent Services, including Stripe Elements (Stripe's pre-built UI components for payment flows), in accordance with the Documentation, the Agreement and any technical specifications Stripe provides or publishes, and must use Stripe Elements to facilitate Agentic Transactions. It must use the Services in accordance with Law, the Payment Method Requirements (including those on collecting consents from and giving disclosures to Agentic Customers under Section 4.1) and any obligations owed to Agentic Sellers. It must reasonably cooperate with Stripe and any Agentic Seller, including by supplying the information and evidence needed to resolve Agentic Disputes, Agentic Refunds and Agentic Customers' product liability claims, such as transaction logs and Agentic Customer Information.
Supporting quotations
2. User Obligations.
User must integrate the Stripe API and use the Agentic Commerce Agent Services, including Stripe Elements, in accordance with the Documentation, this Agreement and any technical specifications that Stripe provides to User or publishes.
User must use Stripe Elements to facilitate Agentic Transactions.
User must use the Agentic Commerce Agent Services in accordance with Law, Payment Method Requirements (including those relating to User's collection of consents from Agentic Customers and its provision of disclosures to Agentic Customers under Section 4.1 of these Agentic Commerce Agent Terms) and any obligations owed to Agentic Sellers.
User must reasonably cooperate with Stripe and any Agentic Seller, including to provide all necessary information and evidence to resolve Agentic Disputes, Agentic Refunds, and Agentic Customers' product liability claims, including transaction logs and relevant Agentic Customer Information.
“Stripe Elements” means Stripe's pre-built UI components for creating payment flows.
Qualifications & exceptions
Use of Stripe Elements for Agentic Transactions is mandatory.
Cooperation extends to Agentic Sellers, not only Stripe.
Not stated here
The Documentation and technical specifications are not supplied.
Security & Safeguards · Procedure
You and your providers handling Agentic Payment Account Details must meet the PCI Standards and prove it on request
The User must comply with the PCI Standards and ensure that its service providers that store, access or transmit Agentic Payment Account Details do so too. On Stripe's request, the User must provide evidence of its compliance. Agentic Payment Account Details are the Agentic Customer's payment method details the PCI Standards protect, such as name, card number, expiration date and security code.
Supporting quotations
User must, and must ensure that User’s service providers that store, access, or transmit Agentic Payment Account Details, comply with the PCI Standards. Upon Stripe’s request, User must provide to Stripe evidence of User’s compliance.
"Agentic Payment Account Details" means the Agentic Payment Method account details for an Agentic Customer that PCI Standards require to be protected, which may include the Agentic Customer's name, and with respect to credit and debit cards, the Agentic Customer's account number, card expiration date, and card verification value or similar security code.
Qualifications & exceptions
The duty extends to the User's service providers that handle the details.
Legal Rights & Agreement Rules · Restriction or exception
Network requirements bind you; Stripe may amend these terms for them, you secure waivers, networks may enforce directly
The User must ensure its use of the Agentic Commerce Agent Services complies with all applicable Payment Method Requirements, the Agentic Payment Method Providers' public rules plus the Stripe Website terms on accepting an Agentic Payment Method, including requirements on payment method presentment, use of payment method Marks, and the privacy, protection, collection, use, storage and disclosure of data. Stripe may amend these terms or add terms to reflect requirements an Agentic Payment Method Provider (such as Visa) imposes, giving reasonable prior written notice except where the Provider requires immediate implementation, in which case notice follows as soon as reasonably practicable. If the User's use needs a waiver from a Provider, the User must obtain it, keep it effective during the Term and evidence it on request. The User must give Providers the information, cooperation and assistance they reasonably request, within the time Stripe or the Provider specifies, and a Provider may enforce these terms directly against the User for its own payment methods.
Supporting quotations
User must ensure that its use of the Agentic Commerce Agent Services complies with all applicable Payment Method Requirements, including requirements related to Agentic Payment Method presentment, use of Agentic Payment Method Marks, and the privacy, protection, collection, use, storage, and disclosure of data. Stripe may amend these Agentic Commerce Agent Terms, or introduce additional terms applicable to User, to reflect requirements imposed on Stripe or User by an Agentic Payment Method Provider. Stripe will provide User with reasonable prior written notice of any amendment under this Section, except where the Agentic Payment Method Provider requires immediate implementation, in which case Stripe will notify User as soon as reasonably practicable.
Where User’s use of the Agentic Commerce Agent Services requires a waiver from an Agentic Payment Method Provider from any applicable Payment Method Requirements, User must obtain that waiver, ensure that it remains effective during the Term, and provide evidence of it to Stripe upon request.
An Agentic Payment Method Provider may enforce the terms of these Agentic Commerce Agent Terms directly against User with respect to that Agentic Payment Method Provider's Agentic Payment Method(s).
“Payment Method Requirements” means: (a) the publicly available guidelines, bylaws, rules, and regulations an Agentic Payment Method Provider imposes that describe how an Agentic Payment Method may be accepted and used; and (b) terms that apply to the acceptance and use of an Agentic Payment Method, located on or accessible from the Stripe Website, including on the Stripe Legal Page
"Agentic Payment Method Provider" means the provider of an Agentic Payment Method (e.g., Visa Inc.).
Qualifications & exceptions
Stripe's amendment right is limited to reflecting Agentic Payment Method Provider requirements.
Prior notice of amendments can be skipped where the Provider requires immediate implementation.
Not stated here
The Payment Method Requirements are external documents, not supplied.
Use & Processing · Procedure
You must meet network data-quality rules and keep collected data accurate; Stripe may set criteria for trusted agents
As the Payment Method Requirements require and to the extent applicable, the User must meet data quality requirements for the relevant categories of Agentic Transaction data, comply with the Agentic Payment Method Provider's technical specifications for that data, and ensure Agentic Payment Account Details and other information it collects through the Service are accurate and complete. Stripe may develop a framework for identifying trusted agents; to qualify, the User must comply with the trusted-agent criteria Stripe provides or publishes.
Supporting quotations
As required by the Payment Method Requirements and to the extent applicable to User's performance under these Agentic Commerce Agent Terms, User must: (a) meet data quality requirements for relevant categories of Agentic Transaction data (as described in the Payment Method Requirements); (b) comply with all technical specifications mandated by the relevant Agentic Payment Method Provider with respect to Agentic Transaction data; and (c) ensure that Agentic Payment Account Details, and any other information that User collects in connection with the Agentic Commerce Agent Services, is accurate and complete.
Stripe may develop a framework for identifying trusted agents. To qualify as a trusted agent, User must comply with the criteria for trusted agents that Stripe provides to User or publishes.
Qualifications & exceptions
Data quality duties apply 'to the extent applicable to User's performance'.
The trusted-agent framework is optional for Stripe ('may develop'); the criteria are not in these terms.
Not stated here
What benefits or consequences attach to trusted-agent status is not stated.
Use & Processing · Restriction or exception
No training AI on catalog, personal, Radar, payment or transaction data, no profiling, no reuse of catalog data
The User must not use Agentic Catalog Data, Personal Data, Stripe Radar Data, Agentic Payment Account Details or Agentic Transaction data, even aggregated, to create, improve, train or enhance its own or any third party's machine learning or AI models, tools, technology, systems, modules or algorithms. It must not process Personal Data to evaluate, analyze or predict the characteristics or behavior of data subjects (Profiling), including behavioral profiles, predictive models or look-alike audiences, and must not subject data subjects to automated decision-making or Profiling with legal or similarly significant effects. Agentic Catalog Data, the information about an Agentic Seller's goods or services such as descriptions, pricing, images and availability, may be used only in connection with the User's use of the Service under these terms.
Supporting quotations
3. Services Restrictions.
User must not use Agentic Catalog Data, Personal Data, Stripe Radar Data, Agentic Payment Account Details, or Agentic Transaction data (including aggregated data) to create, improve, train, or enhance User Systems or any third party's machine learning or artificial intelligence models, tools, technology, systems, modules, or algorithms.
User must not process Personal Data for the purpose of evaluating, analyzing, or predicting the characteristics or behavior of data subjects ("Profiling"). This includes the creation of behavioral profiles, predictive models, or "look-alike" audiences. User must not subject data subjects to any automated decision-making or Profiling that produces legal or similarly significant effects.
User must not use Agentic Catalog Data received via Stripe for any purpose other than in connection with User's use of the Agentic Commerce Agent Services in accordance with these Agentic Commerce Agent Terms.
"Agentic Catalog Data" means information about an Agentic Seller’s goods or services, including but not limited to descriptions, disclaimers, links to terms or policies, product variants, images, pricing, availability and any additional data used to facilitate a sale to Agentic Customers.
Qualifications & exceptions
The training ban covers aggregated data and third-party models as well as the User's own.
Profiling is banned for any purpose, and automated decision-making with legal or similarly significant effects is banned.
Not stated here
Personal Data is a capitalized term defined elsewhere in the Agreement, not in this packet.
Use & Processing · Restriction or exception
Stripe may give you and sellers Radar fraud data, usable only to manage fraud on agent transactions; Radar Terms prevail
Stripe may provide the User and, where applicable, Agentic Sellers with Stripe Radar Data for the purpose of managing transaction fraud on Agentic Transactions. The User must use any Stripe Radar Data solely for that purpose and in accordance with the Stripe Radar Terms. If these Agentic Commerce Agent Terms conflict with the Stripe Radar Terms, the Radar Terms prevail.
Supporting quotations
Stripe may provide User and Agentic Sellers (if applicable) Stripe Radar Data for the purpose of managing transaction fraud on Agentic Transactions. User must use any Stripe Radar Data: (a) solely for the purpose stated in this Section 3.4; and (b) in accordance with the Stripe Radar Terms. If there is a conflict between the terms of these Agentic Commerce Agent Terms and the Stripe Radar Terms, the Stripe Radar Terms prevail.
Qualifications & exceptions
Provision of Radar Data is at Stripe's option ('may provide').
The purpose limit is strict: solely managing transaction fraud on Agentic Transactions.
The Stripe Radar Terms prevail over these terms on conflict.
Not stated here
The Stripe Radar Terms are a later section of this document, analyzed in its own packets.
Sharing & Disclosure · Procedure
You, not Stripe, must get verifiable consents letting Stripe use, store and share personal and payment data with sellers
The User, not Stripe, must obtain valid and verifiable consents from Agentic Customers and give them the disclosures and notices Law and the Payment Method Requirements require. The consents must authorize Stripe to lawfully use, store and share Personal Data and Agentic Payment Account Details with Agentic Sellers and, where applicable, Stripe Connect Platforms in order to complete Agentic Transactions, save and reuse payment details for future transactions, provide services to Agentic Sellers, and carry out other data sharing or activities needed to comply with these terms.
Supporting quotations
4. Disclosures, Information-Sharing and User Agreements.
User, and not Stripe, must obtain valid and verifiable consents from, and provide necessary disclosures and notices to, Agentic Customers, as required by Law and applicable Payment Method Requirements. These consents must authorize Stripe to lawfully use, store, and share Personal Data and Agentic Payment Account Details with Agentic Sellers and Stripe Connect Platforms (as applicable) to: (a) complete Agentic Transactions; (b) save and reuse Agentic Payment Account Details for future transactions; (c) provide services to Agentic Sellers; and (d) facilitate other data sharing or activities necessary to comply with these Agentic Commerce Agent Terms.
"Agentic Customer" means an entity or individual, whether acting for itself or through an AI agent, who provides Authority or initiates a request to purchase goods or services via an Agentic Interface.
Qualifications & exceptions
Responsibility for consents and disclosures sits with the User alone.
The consents must cover reuse of saved payment details for future transactions as well as the current one.
Not stated here
What Law and Payment Method Requirements demand of the consents depends on jurisdiction and network; not stated here.
Retention & Deletion · Procedure
Keep auditable records of consents, disclosures and each agent’s Authority, update your agreements, report to sellers
The User must retain auditable records of all Agentic Customer consents obtained and disclosures provided under Section 4.1, make any updates to its User Agreement (including its Privacy Policy) these terms require, and retain auditable records of its Authority, the express scope of permission an Agentic Customer gives an AI agent including spending limits, merchant restrictions and time bounds, at the time of each Agentic Transaction. On Stripe's written request, the User must promptly provide documentation and evidence of compliance. Where the Documentation or the User's agreements with Agentic Sellers or Customers require, the User must give each Agentic Seller usage reports, performance data and other relevant information about that seller's Agentic Transactions.
Supporting quotations
User must: (a) retain auditable records of all Agentic Customer consents obtained, and disclosures provided under Section 4.1 of these Agentic Commerce Agent Terms; (b) make all necessary updates to its User Agreement (including its Privacy Policy) that may be required for the purposes of these Agentic Commerce Agent Terms, and (c) retain auditable records of User’s Authority at the time of each Agentic Transaction.
At Stripe's written request, User must promptly provide Stripe with documentation and evidence to verify User's compliance with this Section 4.2.
User must provide to the Agentic Seller usage reports, performance data, and other relevant information about that Agentic Seller's Agentic Transactions where required by the Documentation or User’s agreements with Agentic Sellers or Agentic Customers.
“Authority” means the express scope of authority an Agentic Customer grants to any AI agent operating within the Agentic Interface to initiate Agentic Transactions on Agentic Customer's behalf including any applicable spending limits, merchant restrictions, or time-bound parameters.
Qualifications & exceptions
Authority records must be captured at the time of each Agentic Transaction.
Seller reporting applies only where the Documentation or the User's agreements require it.
Not stated here
No retention period for the records is stated.
Legal Rights & Agreement Rules · Procedure
Your customer agreement must explain the agent’s Authority and say the seller, not Stripe, owns fulfillment and claims
The User must have a User Agreement (its agreements with each Agentic Customer) governing Agentic Transactions. It must explain the User's Authority and include at least these acknowledgements: the User may display Agentic Catalog Data on its Agentic Interface where applicable; Agentic Transactions are subject to the Agentic Seller's terms and Privacy Policy; the User may share payment details and transaction data with Agentic Sellers, Stripe and, as applicable, Stripe Connect Platforms and the sellers' other service providers to process transactions; the Agentic Seller is the seller of record; the seller is responsible for fulfillment and post-fulfillment duties such as shipping, returns, refunds and exchanges; and the seller alone answers for claims about its goods, which customers must raise with the seller, not Stripe. The User remains solely responsible for ensuring its User Agreement and interface disclosures accurately reflect every party's role and comply with these terms, Laws and the Payment Method Requirements.
Supporting quotations
User must have a User Agreement to govern Agentic Transactions. The User Agreement must explain User’s Authority and include, at a minimum, an acknowledgement that: (a) if applicable, User may display the Agentic Catalog Data on the Agentic Interface; (b) Agentic Transactions are subject to the Agentic Seller's terms and conditions and Privacy Policy; (c) User may share Agentic Payment Details and Agentic Transaction Data with other parties in order to process Agentic Transactions, including with Agentic Sellers, Stripe, and, as applicable, Stripe Connect Platforms and Agentic Sellers’ other service providers; (d) an Agentic Seller is the seller of record for all Agentic Transactions; (e) an Agentic Seller is responsible for all order fulfillment and post-fulfillment obligations, including shipping, processing returns, issuing refunds, and facilitating exchanges; and (f) an Agentic Seller is solely responsible for Agentic Customers' claims relating to Agentic Seller's goods and services, and Agentic Customers must raise claims, disputes or questions about the goods or services directly with the Agentic Seller (and not against Stripe).
User remains solely responsible for ensuring its User Agreement and Agentic Interface disclosures fully and accurately reflect the roles and responsibilities of all parties involved in an Agentic Transaction and comply with these Agentic Commerce Agent Terms, Laws, and Payment Method Requirements.
“User Agreement” means, as to each Agentic Customer, collectively, the agreements that User has with that Agentic Customer.
Qualifications & exceptions
The listed acknowledgements are a minimum; the User remains responsible for the overall accuracy of its disclosures.
Charges & Financial Obligations · Company practice
Sellers decide whether to submit; Stripe may refuse risky transactions or drop sellers without liability; tokens
Agentic Sellers (third-party sellers offering goods to Agentic Customers) may process Agentic Transactions through the Stripe Payments Services or route the data to another payment provider through the Stripe Orchestrated Services; where they use Stripe Payments, completion depends on the seller choosing to submit the transaction, and Stripe is not responsible for ensuring a seller submits. Stripe and its Affiliates may decline, cancel or refuse to facilitate any Agentic Transaction Stripe reasonably believes is unauthorized, fraudulent, illegal or exposes Stripe, the User, sellers, payment methods or customers to unacceptable risk, without liability to the User. Stripe is not liable, and not in breach, if it or an Affiliate refuses to onboard or stops serving any Agentic Seller. Where Agentic Payment Method Providers request it, the User authorizes Stripe to provision Agentic Tokens on its behalf, which may involve submitting Agentic Customer and seller information to the Provider, to share the tokens with sellers, Providers and Stripe Connect Platforms, and to use them as reasonably necessary to facilitate transactions.
Supporting quotations
5. Stripe's Rights.
Where the Agentic Seller uses the Stripe Payments Services, completion of the Agentic Transaction by Stripe is subject to the Agentic Seller, at its discretion, submitting the transaction and directing Stripe to process the payment. In either case, Stripe is not responsible for ensuring that an Agentic Seller submits a transaction for payment processing.
Stripe and its Affiliates may decline, cancel, or refuse to facilitate any Agentic Transaction that Stripe reasonably believes is unauthorized, fraudulent, illegal, or exposes Stripe, User, Agentic Sellers, Agentic Payment Methods or Agentic Customers to unacceptable risk. Stripe is not liable to User for this refusal.
Stripe is not liable to User, nor will Stripe be in breach of this Agreement, if Stripe or any Affiliate refuses to onboard or discontinues the provision of Stripe services or Stripe Technology to any Agentic Seller.
Agentic Payment Method Providers may request that Stripe provision Agentic Tokens for use in initiating Agentic Transactions, and User authorizes Stripe to: (a) provision Agentic Tokens on User's behalf, which may involve submitting information (including Agentic Customer Information and Agentic Seller information) to the Agentic Payment Method Provider; (b) share Agentic Tokens with Agentic Sellers, Agentic Payment Method Providers, and if applicable Stripe Connect Platforms; and (c) otherwise use those Agentic Tokens as reasonably necessary to facilitate Agentic Transactions.
"Agentic Seller" means a third party seller of goods or services that has made its goods or services available for purchase by Agentic Customers.
Qualifications & exceptions
Refusal requires Stripe's reasonable belief in unauthorized, fraudulent, illegal or unacceptably risky activity.
Stripe bears no liability for refused transactions or for refusing or discontinuing a seller.
Token provisioning may involve submitting Agentic Customer Information to the Payment Method Provider.
Not stated here
What an Agentic Token is technically is not defined in this packet.
Content & IP Rights · Permission or license
Display seller catalog data accurately and with permission under a revocable license; Stripe disclaims its accuracy
If the User receives Agentic Catalog Data, it must display it accurately, completely, in a timely manner and without violating Law, and must hold all rights, consents and authorizations from Agentic Sellers or third parties needed to receive and display it in its Agentic Interface. Stripe grants the User a non-exclusive, non-transferable, non-sublicensable, royalty-free and revocable license to display Agentic Catalog Data provided via Stripe on behalf of any Agentic Seller, solely as necessary to perform the User's obligations under these terms. Because the data comes from sellers or their agents, the Stripe Parties disclaim liability for claims about its accuracy, quality, currentness or completeness, or about other order-related data, unless Stripe caused a material defect.
Supporting quotations
If User receives Agentic Catalog Data, User must: (a) ensure that Agentic Catalog Data is displayed accurately, completely, in a timely manner, and does not violate Law; and (b) ensure that it has all necessary rights, consents, and authorizations from Agentic Sellers or third parties to receive and display the Agentic Catalog Data in the Agentic Interface.
Stripe grants to User a non-exclusive, non-transferable, non-sublicensable, royalty-free, revocable license to display Agentic Catalog Data provided via Stripe to User on behalf of any Agentic Seller solely as necessary to perform User's obligations under these Agentic Commerce Agent Terms.
Agentic Catalog Data is provided by Agentic Sellers or third parties acting on the Agentic Seller's behalf. Stripe Parties disclaim all liability with respect to any claim relating to the accuracy, quality, currentness, or completeness of the Agentic Catalog Data or other order-related data for Agentic Transactions, unless a material defect in the accuracy, quality, currentness, or completeness of the Agentic Catalog Data is caused by Stripe.
Qualifications & exceptions
The display license is revocable and limited to what is necessary to perform the User's obligations.
Stripe's disclaimer gives way where Stripe itself caused a material defect in the catalog data.
Content & IP Rights · Permission or license
You license Stripe and its Affiliates to access your systems during the Term, only as needed to deliver the Services
Subject to these terms, the User grants Stripe and its Affiliates a worldwide, non-exclusive, non-transferable (except with a permitted assignment), non-sublicensable, royalty-free license during the Term to access and use any aspects of the User Systems necessary to enable the Services. Stripe's access and use must be solely as necessary to make the Services and related Stripe Technology available to the User and Agentic Sellers under these terms, and must comply with these terms.
Supporting quotations
7. License to User Systems.
Subject to these Agentic Commerce Agent Terms, User grants to Stripe and its Affiliates a worldwide, non-exclusive, non-transferable (except in connection with a permitted assignment), non-sublicensable, royalty-free license during the Term to access and use any aspects of the User Systems necessary to enable the Services, as long as Stripe's access and use is: (a) solely as necessary to make the Services and related Stripe Technology available to User and Agentic Sellers under these Agentic Commerce Agent Terms; and (b) in compliance with these Agentic Commerce Agent Terms.
Qualifications & exceptions
Limited to the Term and to access necessary to enable the Services for the User and Agentic Sellers.
Transferable only in connection with a permitted assignment.
Not stated here
'User Systems' is a capitalized term whose definition is not in this packet.
Legal Rights & Agreement Rules · Restriction or exception
You answer for your interface, AI output and Authority, for disputes and refunds, and for agent purchases without intent
The User remains fully responsible for, and the Stripe Parties disclaim liability for, any claim by anyone, including Agentic Sellers and Agentic Customers, relating to the Agentic Interface, the User Systems (including any output or bias) or the User's Authority. Stripe is not responsible for Agentic Disputes, Agentic Refunds or other transaction-related Losses. The User must manage transaction fraud on Agentic Transactions on its interface, and, as between Stripe and the User, is responsible for an Unauthorized Agentic Transaction: one where the User failed to procure appropriate consents; one the customer did not authorize, that exceeded the User's Authority, or that was caused by bugs, hallucinations or misinterpretations; or one that the interface, User Systems or an AI agent generated without the customer manifesting, or the User receiving, an intent to purchase, whether through error, malfunction, unauthorized action or the agent acting beyond its authority.
Supporting quotations
8. Liability for Use of Agentic Commerce Agent Services.
User remains fully responsible for, and Stripe Parties disclaim all liability with respect to any claim made by any person or entity, including Agentic Sellers and Agentic Customers relating to the Agentic Interface, User Systems (including any output or bias) or User’s Authority.
Stripe is not responsible for, and Stripe Parties disclaim all liability with respect to, Agentic Disputes, Agentic Refunds, or other Agentic Transaction-related Losses.
User will manage transaction fraud on Agentic Transactions on the Agentic Interface. As between Stripe and User, User is responsible for unauthorized Agentic Transactions, if: (a) User fails to procure appropriate consents from the relevant Agentic Customer in accordance with these Agentic Commerce Agent Terms; (b) the Agentic Transaction was not authorized by the Agentic Customer, exceeded User’s Authority, or was caused by bugs, hallucinations or misinterpretations; or (c) the Agentic Interface, User Systems, or any AI agent operating within or on behalf of the Agentic Interface or User Systems, generates or initiates a transaction without an Agentic Customer manifesting, or User receiving, the Agentic Customer's intent to purchase whether due to error, malfunction, unauthorized action, or the agent acting without requisite authority or outside the scope of its permitted authority (each an "Unauthorized Agentic Transaction”).
Qualifications & exceptions
Responsibility for AI 'output or bias', 'hallucinations' and agents acting beyond authority sits with the User.
The allocation is 'as between Stripe and User'; it does not itself settle positions with customers or sellers.
Legal Rights & Agreement Rules · Restriction or exception
Defend and indemnify the Stripe Parties for unauthorized agent transactions and alleged hacking or terms breaches
The User must defend the Stripe Parties against any Claim, and indemnify them against all Losses, arising out of or relating to an Unauthorized Agentic Transaction, or to any allegation that the User had unauthorized access to a third party's computer system or violated a third party's terms of service.
Supporting quotations
User will defend the Stripe Parties against any Claim and indemnify the Stripe Parties against all Losses arising out of or relating to: (a) an Unauthorized Agentic Transaction; or (b) any allegation that User had unauthorized access to a third party's computer system or violated any third party's terms of service.
Qualifications & exceptions
The indemnity is triggered by an allegation of unauthorized access or terms-of-service violation, not only a finding.
Not stated here
Claim and Losses are capitalized terms defined in the General Terms, not supplied.
Section 9 defines the terms of the Agentic Commerce Agent Terms. 'Authority' is the express scope of permission an Agentic Customer gives an AI agent, including spending limits, merchant restrictions and time bounds. 'Agentic Catalog Data' is information about a seller's goods such as descriptions, pricing, images and availability. The 'Agentic Commerce Agent Services' are the APIs and infrastructure enabling the Agentic Interface. An 'Agentic Customer' is a person or entity, acting itself or through an AI agent, who gives Authority or asks to buy through an Agentic Interface. 'Agentic Customer Information' includes payment details, shipping and billing names, emails, phone numbers and addresses, and any limits the customer placed on the User's Authority. An 'Agentic Dispute' is a customer-initiated reversal of a processed Agentic Transaction, including chargebacks. The 'Agentic Interface' is the User's own agentic interface through which customers transact. Further definitions follow in the next packet.
Supporting quotations
9. Definitions.
“Authority” means the express scope of authority an Agentic Customer grants to any AI agent operating within the Agentic Interface to initiate Agentic Transactions on Agentic Customer's behalf including any applicable spending limits, merchant restrictions, or time-bound parameters.
"Agentic Catalog Data" means information about an Agentic Seller’s goods or services, including but not limited to descriptions, disclaimers, links to terms or policies, product variants, images, pricing, availability and any additional data used to facilitate a sale to Agentic Customers.
"Agentic Commerce Agent Services" means the Services, including the provision of APIs and related infrastructure, that enable the Agentic Interface, as described in the Documentation.
"Agentic Customer" means an entity or individual, whether acting for itself or through an AI agent, who provides Authority or initiates a request to purchase goods or services via an Agentic Interface.
"Agentic Customer Information" means any information related to an Agentic Customer, including Agentic Payment Account Details, shipping information (name, email address, phone number, and address of the recipient), billing information (name, email address, phone number, and address of the Agentic Customer), and any information related to any restrictions, conditions, or limitations the Agentic Customer has placed on User’s Authority to act on behalf of the Agentic Customer.
"Agentic Disputes" means an instruction an Agentic Customer initiates to reverse or invalidate a processed Agentic Transaction (including "chargebacks" and "disputes" as those terms may be used by Agentic Payment Method Providers).
"Agentic Interface" means User's agentic interface that enables Agentic Customers to make an Agentic Transaction.
Qualifications & exceptions
Agentic Customer Information expressly includes shipping and billing contact details and the limits placed on the agent's Authority.
Legal Rights & Agreement Rules · Context
Agent terms definitions: payment details, methods, providers, Refunds, Seller, Token, Transaction, PCI, User System
The remaining Section 9 definitions: 'Agentic Payment Account Details' are the customer's payment method details the PCI Standards protect (name, card number, expiration date, security code). An 'Agentic Payment Method' is any payment method offered at the point of purchase in the Agentic Interface, and its 'Agentic Payment Method Provider' is its provider, such as Visa. 'Agentic Refunds' are seller-initiated full or partial returns of funds. An 'Agentic Seller' is a third-party seller offering goods to Agentic Customers. An 'Agentic Token' is a payment credential a Provider issues for a seller to initiate transactions via the User, plus related data such as cryptograms. An 'Agentic Transaction' is a customer-initiated purchase from an Agentic Seller. 'Payment Method Requirements' are the Provider's public rules plus the Stripe Website's Payment Method Terms. 'PCI-DSS' and 'PCI Standards' are the card industry security standards including PCI-SSF and successors. 'Stripe Elements' are Stripe's pre-built payment UI components. The 'User Agreement' is the User's agreements with each customer. A 'User System' is any User software, hardware, AI model, tool, technology or algorithm the User uses or makes available for these activities. A 'Back to Top' link closes the section.
Supporting quotations
"Agentic Payment Account Details" means the Agentic Payment Method account details for an Agentic Customer that PCI Standards require to be protected
"Agentic Payment Method" means any payment method available to Agentic Customers at the point of purchase in the Agentic Interface.
"Agentic Payment Method Provider" means the provider of an Agentic Payment Method (e.g., Visa Inc.).
"Agentic Refunds" means an instruction an Agentic Seller initiates to provide a full or partial return of funds to an Agentic Customer for a processed Agentic Transaction.
"Agentic Seller" means a third party seller of goods or services that has made its goods or services available for purchase by Agentic Customers.
"Agentic Token" means a payment credential issued by an Agentic Payment Method Provider corresponding to an Agentic Payment Method, specifically for use by an Agentic Seller to initiate Agentic Transactions via User, and any other data related to that payment credential (e.g., cryptograms).
"Agentic Transaction" means a transaction between an Agentic Customer and an Agentic Seller that is initiated by an Agentic Customer for the purchase of goods or services offered by an Agentic Seller.
“Payment Method Requirements” means: (a) the publicly available guidelines, bylaws, rules, and regulations an Agentic Payment Method Provider imposes that describe how an Agentic Payment Method may be accepted and used
"PCI-DSS" means the Payment Card Industry Data Security Standards.
"PCI Standards" means PCI-DSS and Payment Card Industry Software Security Framework (PCI-SSF), including successor standards (if any).
“Stripe Elements” means Stripe's pre-built UI components for creating payment flows.
“User Agreement” means, as to each Agentic Customer, collectively, the agreements that User has with that Agentic Customer.
“User System” means any User software, hardware, system, artificial intelligence model, tool, technology or algorithm (a) used by User, or (b) made available by User in connection with the activities contemplated under these Agentic Commerce Agent Service Terms.
Qualifications & exceptions
'User System' expressly includes the User's artificial intelligence models, which matters for the liability and no-training clauses.
Legal Rights & Agreement Rules · Context
The Agentic Commerce Seller Terms (Preview) govern selling to customers who buy through AI agents, on top of other terms
The Agentic Commerce Seller Terms, last modified September 28, 2026 and labeled Preview in the index, supplement the General Terms and the Stripe Financial Services Terms and, where applicable to the User and its Integration, the Stripe Payments Terms, Stripe Connect Terms, Stripe Radar Terms and Stripe Orchestrated Services Terms. They govern the Stripe Agentic Commerce Seller Services: the Services, including Shared Payment Tokens and other Stripe Technology, that let the User offer goods to AC Customers and enable checkout and payment processing for AC Transactions. Undefined capitalized terms take their meaning from the Agreement.
Supporting quotations
Stripe Agentic Commerce Seller Services (Preview)
Last modified: September 28, 2026
1. Stripe Agentic Commerce Seller Services.
These terms (“Agentic Commerce Seller Terms”) supplement the General Terms, the Stripe Financial Services Terms, and if applicable to User and its Integration, the Stripe Payments Terms, the Stripe Connect Terms, the Stripe Radar Terms, and the Stripe Orchestrated Services Terms, and govern User’s use of Stripe Agentic Commerce Seller Services.
“Stripe Agentic Commerce Seller Services” means the Services, including Shared Payment Tokens and other Stripe Technology, as described in the Documentation, that enable User to offer goods or services to AC Customers and enable checkout and payment processing for AC Transactions.
Qualifications & exceptions
Which of the Payments, Connect, Radar and Orchestrated Services Terms also apply depends on the User's Integration.
Not stated here
What Preview status entails for this Service is not stated in these terms.
Charges & Financial Obligations · Context
Agent-initiated sales run through Stripe Payments under the Payments Terms, or other processors under Orchestrated Terms
Stripe makes the Stripe Payments Services available for AC Transactions the User submits, and the Stripe Payments Terms apply when the User processes AC Transactions that way. Certain Integrations require use of the Stripe Payments Services, as the Documentation describes. If the User instead processes AC Transactions with third-party payment service providers, the Stripe Orchestrated Services Terms apply.
Supporting quotations
2. Processing AC Transactions.
Stripe will make Stripe Payments Services available for AC Transactions submitted by User to Stripe. The Stripe Payments Terms apply to AC Transactions when User uses Stripe Payments Services to process AC Transactions. Certain Integrations require the use of Stripe Payments Services, as described in the Documentation. The Stripe Orchestrated Services Terms apply if User processes AC Transactions with third party payment services providers.
Qualifications & exceptions
Some Integrations mandate Stripe Payments; the Documentation says which.
Not stated here
The Documentation is not supplied.
Account & Service Control · Restriction or exception
You may need a Stripe profile; you, not Stripe or the agent platform, fulfill orders, issue receipts, are the merchant
To use the Service, the User and each Participating Seller that is a Connected Account may be required to create a Stripe profile with complete and accurate business information Stripe reasonably requires and keep it current. The User, itself or through its Participating Sellers, and not Stripe, is responsible for fulfilling orders from AC Transactions (customer-initiated purchases through an AC Interface), giving the AC Customer an itemized receipt, and handling customer service including warranty claims, returns, exchanges, disputes, refunds and reversals. The User or Participating Seller, not Stripe or the AC Interface Provider, is the merchant of record, and neither Stripe nor the AC Interface Provider ever takes title to goods sold through the AC Interface. An AC Customer is a Customer under the Agreement and a Data Subject under the Data Processing Agreement.
Supporting quotations
3. User Obligations.
To use the Stripe Agentic Commerce Seller Services, User and each Participating Seller (if applicable and if a Connected Account) may be required to (a) create a Stripe profile that provides complete and accurate business information that Stripe reasonably requires to provide the Stripe Agentic Commerce Seller Services; and (b) maintain that Stripe profile and keep all information provided current.
User (whether itself or through its Participating Sellers), and not Stripe, is responsible for (a) fulfilling AC Customer orders from AC Transactions; (b) providing AC Customer with an itemized receipt for the AC Transaction; and (c) addressing any customer-service-related issues for AC Transactions, including warranty claims, returns, exchanges, disputes, refunds, and reversals.
User or Participating Seller (if applicable), and not Stripe or the AC Interface Provider, is the “merchant of record” for AC Transactions. Stripe and AC Interface Provider will not, at any time, take title to any goods sold via the AC Interface.
“AC Customer” means an individual or entity, whether acting for itself or through an AI agent, who initiates a request to purchase goods or services from User or a Participating Seller (if applicable) via an AC Interface enabled by Stripe Agentic Commerce Seller Services. An “AC Customer” is a “Customer” under the Agreement and “Data Subject” under the Data Processing Agreement.
“AC Transaction” means a transaction between an AC Customer and User or Participating Seller (if applicable), that is initiated by an AC Customer for the purchase of goods or services offered by the User or Participating Seller.
Qualifications & exceptions
The profile requirement is 'may be required', at Stripe's determination.
Merchant-of-record status sits with the User or Participating Seller for every AC Transaction.
Not stated here
The Data Processing Agreement is referenced but not supplied.
Use & Processing · Restriction or exception
You and your sellers manage fraud on agent sales; Radar scores Stripe shares are Stripe Radar Data under the Radar Terms
The User and any Participating Sellers will manage transaction fraud on AC Transactions. The User may use Stripe Radar Data it receives from Stripe, if any, for that purpose in accordance with the Stripe Radar Terms. Any Radar Scores and other fraud signals shared with the User about the User, Participating Sellers or AC Transactions constitute Stripe Radar Data.
Supporting quotations
User and Participating Sellers (if applicable) will manage transaction fraud on AC Transactions. User may use Stripe Radar Data received from Stripe (if any) for that purpose in accordance with the Stripe Radar Terms. Any Radar Scores and other fraud signals shared with User relating to User, Participating Sellers (if applicable), or AC Transactions, constitute Stripe Radar Data.
Qualifications & exceptions
Radar Data may be used for fraud management only, and only under the Stripe Radar Terms.
Not stated here
Whether Stripe shares Radar Data with a particular User is not promised ('if any').
Use & Processing · Restriction or exception
You let the agent platform create Shared Payment Tokens and start checkouts; token data is for post-sale contact only
By using the Service for AC Transactions, the User authorizes the AC Interface Provider (the entity running the agentic interface) to create a Shared Payment Token, a limited reference to a payment method shared with the User or its Participating Sellers to facilitate AC Transactions, and, for certain Integrations, to initiate a checkout session on the User's behalf. The User must not access or use payment data received via a Shared Payment Token except as necessary for post-transaction customer engagement, must not try to use a token for more than one authorization unless the Documentation expressly permits, and must not try to use expired or revoked tokens. Where the Documentation requires, the User must report token usage through the Payment Records API.
Supporting quotations
By using the Stripe Agentic Commerce Seller Services in connection with AC Transactions, User authorizes AC Interface Provider to (a) create a Shared Payment Token to facilitate User’s or its Participating Seller’s AC Transactions; and (b) for certain Integrations, initiate a checkout session on User’s behalf. User must not (x) access or use any payment data received via a Shared Payment Token except as necessary for post-transaction customer engagement; (y) attempt to use a Shared Payment Token for more than one authorization (except as expressly permitted by the Documentation); or (z) attempt to use Shared Payment Tokens that are expired or revoked.
“Shared Payment Token” means a limited reference to a payment method that is created by an AC Interface Provider and shared with User or Participating Sellers to facilitate AC Transactions.
“AC Interface Provider” means the entity providing the AC Interface.
Qualifications & exceptions
Payment data from a Shared Payment Token may be used only as necessary for post-transaction customer engagement.
A token supports one authorization unless the Documentation expressly permits more.
Not stated here
Which Integrations allow the AC Interface Provider to initiate checkout sessions is in the Documentation, not supplied.
Legal Rights & Agreement Rules · Restriction or exception
Using the Service to accept a payment method accepts its Rules and Terms as Financial Provider Terms; you obtain waivers
Using the Stripe Agentic Commerce Seller Services to accept, or enable acceptance of, a Payment Method counts as the User's acceptance of the applicable Payment Method Rules and Payment Method Terms, which are Financial Provider Terms under the Agreement. Where the User's use of the Seller Services or Orchestrated Services requires a Payment Method Provider's waiver from any requirement, the User must obtain the waiver, keep it effective and give Stripe evidence of it on request.
Supporting quotations
Using Stripe Agentic Commerce Seller Services in connection with accepting or enabling the acceptance of a Payment Method constitutes User’s acceptance of the applicable Payment Method Rules and Payment Method Terms. Where User’s use of Agentic Commerce Seller Services or Orchestrated Services requires a Payment Method Provider’s waiver from any applicable requirements, User must obtain that waiver, ensure it remains effective, and provide evidence of it to Stripe upon request. Payment Method Rules and Payment Method Terms are Financial Provider Terms for purposes of this Agreement.
Qualifications & exceptions
As Financial Provider Terms, the Rules and Terms prevail over the Agreement where inconsistent (Financial Services Terms Section 2.4).
Not stated here
The Payment Method Rules and Terms are external, not supplied.
Account & Service Control · Restriction or exception
Connect platforms designate Participating Sellers; agent sales are Connect Activity and sellers carry your duties
Section 3.7 applies if the User is a Stripe Connect Platform and any of its Connected Accounts are Participating Sellers: merchants selling through the User's platform, or Connected Accounts the User designates to sell through the Service. The Stripe Connect Terms apply to the platform, and AC Transactions count as 'Activity' under them. The User designates Participating Sellers to the applicable AC Interface Providers and Stripe and enables them to offer goods to AC Customers through an AC Interface. Each Participating Seller that is a Connected Account is treated as a 'User' of the Seller Services, so the User's obligations under these terms also bind that Connected Account.
Supporting quotations
This section applies if User is a Stripe Connect Platform and any of User’s Connected Accounts are Participating Sellers. The Stripe Connect Terms apply to the Stripe Connect Platform and AC Transaction(s) are an “Activity”, under the Stripe Connect Terms.
User will designate Participating Sellers to applicable AC Interface Providers and Stripe, and enable Participating Sellers to make goods or services available for purchase to AC Customers via an AC Interface.
Each Participating Seller that is a Connected Account is considered a “User” of the Stripe Agentic Commerce Seller Services and the obligations of User under these Agentic Commerce Seller Terms also apply to the Connected Account.
“Participating Seller” means either (a) a merchant offering its goods and services to end customers through User’s platform and User is using Stripe Agentic Commerce Seller Services; or (b) a Connected Account designated by User, that is enabled to offer its goods or services to end customers using Stripe Agentic Commerce Seller Services.
Qualifications & exceptions
Applies only where the User is a Stripe Connect Platform with Connected Accounts acting as Participating Sellers.
Treating AC Transactions as Connect 'Activity' brings the platform's Connect liability for Connected Account activity into play.
Legal Rights & Agreement Rules · Procedure
If the agent platform shows disclosures for you, review its mock-ups of disclosures and checkout flows when offered
If the AC Interface Provider presents disclosures to AC Customers on the User's behalf, the User is responsible for reviewing the Provider's proposed disclosure mock-ups, to obtain the necessary consents from AC Customers, and any proposed checkout flow mock-ups, to the extent the Provider makes them available for review. Further allocation of responsibility for terms of service, privacy policies and disclosures follows in the next clause.
Supporting quotations
3.8 Terms of Service, Disclosures, and Consents.
If AC Interface Provider presents disclosures to AC Customers on behalf of User, User is responsible for reviewing mock ups of an AC Interface Provider’s proposed disclosures to obtain necessary consents from AC Customers and any mock ups of proposed checkout flows, to the extent mock ups are made available to User for review by the AC Interface Provider.
Qualifications & exceptions
The review duty applies only to the extent the AC Interface Provider makes mock-ups available.
Legal Rights & Agreement Rules · Restriction or exception
You or the agent platform, not Stripe, present your terms and privacy policy; Stripe relies on the platform for consents
Depending on the Integration, the User or the AC Interface Provider, and not Stripe, is responsible either for including the User's terms of service, privacy policy and disclosures in the Catalog Data, or for ensuring AC Customers are shown and accept any required terms, privacy policy and disclosures with an AC Transaction. Stripe is not responsible for obtaining, and relies on AC Interface Providers to obtain, all consents from AC Customers needed for Stripe to provide the Seller Services and facilitate AC Transactions.
Supporting quotations
User or AC Interface Provider (depending on the Integration), and not Stripe, is responsible for either (i) ensuring User’s terms of service, privacy policy and disclosures are included as part of the Catalog Data, or (ii) ensuring that AC Customers are presented with and accept any required terms of service, privacy policy and disclosures in connection with an AC Transaction
Stripe is not responsible for obtaining, and relies on AC Interface Providers to obtain, all necessary consents from AC Customers to enable Stripe to provide the Stripe Agentic Commerce Seller Services and facilitate AC Transactions.
Qualifications & exceptions
Which of the User or the AC Interface Provider carries the duty depends on the Integration.
Stripe disclaims responsibility for customer consents and relies on the AC Interface Provider.
Charges & Financial Obligations · Restriction or exception
You alone calculate, collect and remit sales, VAT, GST and similar taxes on agent-initiated sales
The User is solely responsible for calculating, collecting and remitting Indirect Taxes on AC Transactions. Indirect Taxes are transaction taxes and duties imposed by any Governmental Authority, including sales and use tax, VAT, GST and equivalents.
Supporting quotations
User is solely responsible for calculating, collecting, and remitting Indirect Taxes on AC Transactions.
“Indirect Taxes” means any applicable transaction taxes and duties imposed by any Governmental Authority, including sales and use tax, value-added tax (VAT), and goods and services tax (GST), or equivalent transaction taxes.
Content & IP Rights · Permission or license
Catalog data you supply must be accurate and lawful; you license Stripe and agent platforms to use and improve with it
Section 4 applies only to Integrations in which the User directly or indirectly provides Catalog Data to Stripe; an Integration without Catalog Data, such as Link's Agent Wallet, is outside it. Catalog Data is information about the User's or a Participating Seller's goods, such as descriptions, pricing, images and availability. The User must ensure Catalog Data and other information it gives Stripe or the AC Interface Provider is current, accurate, complete, not misleading, non-infringing and compliant with Law including advertising and consumer protection Law, and the User, not Stripe, is responsible for obtaining accurate data from AC Customers. The User must supply all necessary Catalog Data, directly or via a catalog service provider, and ensure Stripe has the rights to use, reproduce, display, retain and share it with the AC Interface Provider. The User grants Stripe a worldwide, royalty-free, non-exclusive, sublicensable license to do so in connection with providing, personalizing, customizing, developing and improving the Seller Services and related Services, sublicensable to AC Interface Providers and their affiliates for improving their AC Interfaces. Stripe commits that Catalog Data it passes to a Provider will be consistent with what it received from the User.
Supporting quotations
4. Catalog Data.
This Section 4 applies only to an Integration in respect of which User directly or indirectly provides Catalog Data to Stripe. An Integration that does not involve the provision of Catalog Data to Stripe, such as in connection with
4.1 Catalog Data and Order-related Data.
User must ensure that Catalog Data and any other information that User provides to Stripe or the AC Interface Provider in connection with the Stripe Agentic Commerce Seller Services is current, accurate, complete, not misleading, does not infringe or violate the rights of any third party, and complies with Law, including advertising and consumer protection Law. By using Stripe Agentic Commerce Seller Services to enable AC Transactions, User, and not Stripe, is responsible for obtaining current, accurate and complete data from AC Customers in connection with AC Transactions.
4.2 Catalog Data License.
User must provide (directly or indirectly through a third party product catalog service provider) all necessary Catalog Data to Stripe. User must ensure that Stripe has all necessary rights to use, reproduce, display, retain, and share with the AC Interface Provider Catalog Data in connection with the Stripe Agentic Commerce Seller Services.
User grants to Stripe a worldwide, royalty-free, non-exclusive, sublicensable license to use, reproduce, display, retain, and share with the AC Interface Provider Catalog Data in connection with providing, personalizing, customizing, developing, and improving the Stripe Agentic Commerce Seller Services and other related Services. User acknowledges that this license is sublicensable to AC Interface Providers and their affiliates for the purposes of providing, personalizing, customizing, developing and improving their AC Interfaces and related services.
Stripe will ensure that Catalog Data provided by Stripe to an AC Interface Provider on behalf of User is consistent with the Catalog Data received by Stripe from User.
“Catalog Data" means information about a User’s or Participating Seller’s (if applicable) goods or services, including but not limited to descriptions, disclaimers, links to terms or policies, product variants, images, pricing, availability and any additional data used to facilitate a sale to AC Customers.
“Integration” means the specific configuration, selection, and technical implementation of the Stripe Agentic Commerce Seller Services deployed by User, as described in the applicable Documentation.
Qualifications & exceptions
Applies only to Integrations where the User provides Catalog Data to Stripe.
The license covers 'developing and improving' Stripe's and the platforms' services, not only displaying the catalog.
The license is sublicensable to AC Interface Providers and their affiliates.
Not stated here
No term or termination for the Catalog Data license is stated in this clause.
Content & IP Rights · Permission or license
Where Stripe identifies you to customers or agent platforms, you license your and your sellers’ Marks for that use
Section 5 applies only where an Integration involves Stripe identifying the User or a Participating Seller to Customers or AC Interface Providers; where it does not, such as with Link's Agent Wallet, the section does not apply. In those Integrations the User grants Stripe, on its own behalf and for Participating Sellers, a worldwide, non-exclusive, sublicensable, royalty-free license during the Term to use the User's and Participating Sellers' Marks within AC Interfaces and in connection with AC Transactions as necessary to provide the Seller Services.
Supporting quotations
5. Limited License to Marks.
This Section 5 applies only where an Integration will involve Stripe identifying User (or a Participating Seller, if applicable) to Customers or AC Interface Providers in connection with the Stripe Agentic Commerce Seller Services.
User grants to Stripe (on behalf of itself and Participating Sellers, if applicable) a worldwide, non-exclusive, sublicensable, royalty-free license during the Term to use User’s and Participating Seller’s (if applicable) Marks within AC Interfaces and in connection with AC Transactions as necessary to provide the Stripe Agentic Commerce Seller Services.
Qualifications & exceptions
Applies only where Stripe identifies the User or a Participating Seller in the Integration.
Limited to the Term and to use necessary to provide the Seller Services; sublicensable.
Account & Service Control · Company practice
Stripe may refuse to onboard you or a seller it sees as too risky, and may decline any agent sale it thinks improper
Stripe may, at its discretion, refuse to onboard the User or any Participating Seller to the Seller Services if it believes they present an unacceptable risk to Stripe. It may also, at its discretion, decline, cancel, refuse to facilitate or otherwise refuse to provide the Services for any AC Transaction it believes may violate these terms, the Agreement or another agreement with Stripe, is unauthorized, fraudulent or illegal, violates Law or the Payment Method Rules, or exposes or is likely to expose Stripe to unacceptable risk.
Supporting quotations
6. Additional Stripe Rights.
Stripe may, at its discretion, refuse to onboard User or any Participating Seller to Stripe Agentic Commerce Seller Services if Stripe believes User or Participating Seller presents an unacceptable risk to Stripe. Stripe may also, at its discretion, decline, cancel, refuse to facilitate or otherwise provide Stripe Agentic Commerce Seller Services in conjunction with any AC Transaction that Stripe believes (a) may violate these Agentic Commerce Seller Terms, the Agreement, or any other agreement between Stripe and User or a Participating Seller; (b) is unauthorized, fraudulent or illegal; (c) violates Law or Payment Method Rules; or (d) exposes, or is likely to expose, Stripe to unacceptable risk.
Qualifications & exceptions
Both rights are discretionary and rest on Stripe's belief about risk or violation.
Not stated here
What Stripe treats as 'unacceptable risk' is not defined.
Legal Rights & Agreement Rules · Restriction or exception
The agent platform decides whether to list, surface or transact with you, may reject your catalog; its terms bind you
The User acknowledges that the AC Interface Provider may, at its discretion, choose whether to enable transactions between AC Customers and the User or its Participating Sellers, decline to feature or allow them to sell on its AC Interface, choose not to find, surface or recommend their goods, and reject the User's Catalog Data in whole or part if it violates the Provider's policies. Completion of an AC Transaction depends on the AC Interface enabling it, and the Provider controls the discoverability of the User's and sellers' goods. By electing to enable AC Transactions, the User agrees to the applicable AC Interface Provider's terms of service, provided either by Stripe or by the Provider.
Supporting quotations
7. AC Interface Provider Rights.
User acknowledges that AC Interface Provider may, at its discretion, (a) choose whether to enable transactions between AC Customers and User or Participating Sellers (if applicable), (b) decline to feature or allow User or Participating Seller (if applicable) to sell on its AC Interface, (c) not find, surface, or recommend User’s and Participating Sellers’ (if applicable) goods or services, and (d) reject User’s Catalog Data, in whole or in part, if it violates AC Interface Provider’s policies.
When User elects to enable AC Transactions, User agrees to the applicable AC Interface Provider terms of service, which are made available to User either by Stripe or by AC Interface Provider.
Qualifications & exceptions
All listing, surfacing and transaction-enablement decisions sit with the AC Interface Provider.
Enabling AC Transactions is acceptance of the AC Interface Provider's terms of service, which are not supplied here.
Not stated here
The AC Interface Providers' terms of service are external and not supplied.
Charges & Financial Obligations · Company practice
Fees for Payments, Radar and other Services on agent sales apply on top; Stripe may deduct the agent platform’s fees
In addition to the Fees for the Seller Services on the Stripe Pricing Page or agreed in writing, the Fees for any other Services used in relation to AC Transactions or as part of the Seller Services apply to the User, including Fees for the Stripe Payments Services and Stripe Radar Services. If the AC Interface Provider directs it, Stripe may deduct fees the User owes the Provider from AC Transactions processed through the Stripe Payments Services and remit them to the Provider.
Supporting quotations
In addition to Fees listed on the Stripe Pricing Page or otherwise agreed in writing for Stripe Agentic Commerce Seller Services, the Fees for any other Services used in relation to AC Transactions or as part of Stripe Agentic Commerce Seller Services will apply to User, including Fees for Stripe Payments Services and Stripe Radar Services. If directed by AC Interface Provider, Stripe may deduct fees payable by User to the AC Interface Provider from AC Transactions processed through the Stripe Payments Services and remit those fees to AC Interface Provider.
Qualifications & exceptions
Deduction of platform fees happens at the AC Interface Provider's direction, from Transactions processed through Stripe Payments.
Not stated here
The fee amounts are on the Stripe Pricing Page or in separate agreements, not supplied.
The User's fee arrangement with the AC Interface Provider is outside this document.
Legal Rights & Agreement Rules · Restriction or exception
You remain liable for product, injury and consumer claims on agent sales and for catalog data accuracy; Stripe disclaims
The User remains fully responsible for, and the Stripe Parties disclaim all liability for, any claim related to the goods or services sold in an AC Transaction, including product warranty, product liability, product defect, property damage, personal injury and consumer protection claims, and any claim about the accuracy, quality, currentness or completeness of the Catalog Data or other order-related data such as tax information.
Supporting quotations
9. Stripe Disclaimers.
User remains fully responsible for, and Stripe Parties disclaim all liability with respect to (a) any claim, including product warranty, product liability, product defect, property damage, personal injury, or consumer protection claims, related to the goods or services sold as part of an AC Transaction; (b) any claim related to the accuracy, quality, currentness, or completeness of the Catalog Data or other order-related data (e.g. tax information) for AC Transactions.
Qualifications & exceptions
Unlike the agent-side disclaimer, no exception is stated for defects Stripe itself causes.
As written here, the catalog-data disclaimer states no exception for defects Stripe itself causes; the agent-side Agentic Catalog Data disclaimer does.
Legal Rights & Agreement Rules · Restriction or exception
For the Seller Services these terms beat the Payments, Financial Services, Orchestrated and Connect Terms; Radar wins
If these Agentic Commerce Seller Terms conflict with the Stripe Payments Terms, Stripe Financial Services Terms, Stripe Orchestrated Services Terms or Stripe Connect Terms, to the extent those apply to the User and its Integration, these terms prevail for the Seller Services. If they conflict with the Stripe Radar Terms, the Radar Terms prevail.
Supporting quotations
10. Conflicts.
In the event of a conflict between these Agentic Commerce Seller Terms and the Stripe Payments Terms, Stripe Financial Services Terms, Stripe Orchestrated Services Terms, or Stripe Connect Terms, to the extent such terms apply to User and its Integration, the provisions of these Agentic Commerce Seller Terms will prevail for the Stripe Agentic Commerce Seller Services. In the event of a conflict between these Agentic Commerce Seller Terms and the Stripe Radar Terms, the provisions of the Stripe Radar Terms will prevail.
Qualifications & exceptions
Precedence over the four named sets of terms is limited to the Seller Services.
The Stripe Radar Terms override these terms on conflict.
Section 11 defines the Seller Terms' vocabulary. An 'AC Customer' is a person or entity, acting itself or through an AI agent, who asks to buy from the User or a Participating Seller via an AC Interface, and is a Customer under the Agreement and a Data Subject under the Data Processing Agreement. An 'AC Interface' is an agentic interface through which end users ask to buy from third-party sellers; its 'AC Interface Provider' is the entity running it. An 'AC Transaction' is a customer-initiated purchase from the User or a Participating Seller. 'Catalog Data' is information about goods such as descriptions, pricing, images and availability. 'Indirect Taxes' are sales, VAT, GST and similar transaction taxes. An 'Integration' is the User's specific configuration and implementation of the Seller Services. A 'Participating Seller' is a merchant selling through the User's platform, or a Connected Account the User designates. A 'Shared Payment Token' is a limited payment-method reference the AC Interface Provider creates and shares. The 'Stripe Agentic Commerce Seller Services' are the Services, including Shared Payment Tokens, that let the User sell to AC Customers with checkout and payment processing. A 'Back to Top' link closes the section.
Supporting quotations
11. Definitions.
“AC Customer” means an individual or entity, whether acting for itself or through an AI agent, who initiates a request to purchase goods or services from User or a Participating Seller (if applicable) via an AC Interface enabled by Stripe Agentic Commerce Seller Services.
“AC Interface” means an agentic interface that enables end users to initiate a request to purchase goods or services from third party sellers.
“AC Interface Provider” means the entity providing the AC Interface.
“AC Transaction” means a transaction between an AC Customer and User or Participating Seller (if applicable), that is initiated by an AC Customer for the purchase of goods or services offered by the User or Participating Seller.
“Catalog Data" means information about a User’s or Participating Seller’s (if applicable) goods or services
“Indirect Taxes” means any applicable transaction taxes and duties imposed by any Governmental Authority, including sales and use tax, value-added tax (VAT), and goods and services tax (GST), or equivalent transaction taxes.
“Integration” means the specific configuration, selection, and technical implementation of the Stripe Agentic Commerce Seller Services deployed by User, as described in the applicable Documentation.
“Participating Seller” means either (a) a merchant offering its goods and services to end customers through User’s platform and User is using Stripe Agentic Commerce Seller Services; or (b) a Connected Account designated by User, that is enabled to offer its goods or services to end customers using Stripe Agentic Commerce Seller Services.
“Shared Payment Token” means a limited reference to a payment method that is created by an AC Interface Provider and shared with User or Participating Sellers to facilitate AC Transactions.
“Stripe Agentic Commerce Seller Services” means the Services, including Shared Payment Tokens and other Stripe Technology, as described in the Documentation, that enable User to offer goods or services to AC Customers and enable checkout and payment processing for AC Transactions.
Legal Rights & Agreement Rules · Context
The Atlas Terms govern Services for forming a business entity and accessing tools and third-party services
The Stripe Atlas Terms, last modified September 28, 2026, supplement the General Terms and govern the Stripe Atlas Services: the Services that let the User form a business entity and access tools, information, documentation and third-party services to establish, operate and fundraise for that entity. Undefined capitalized terms take their meaning from the General Terms, which are not supplied.
Supporting quotations
Stripe Atlas Services
Last modified: September 28, 2026
1. Stripe Atlas Services.
These terms (“Stripe Atlas Terms”) supplement the General Terms and govern User’s use of the Stripe Atlas Services. Capitalized terms that are not defined in these Stripe Atlas Terms have the same meanings given to them in the General Terms.
“Stripe Atlas Services” means the Services that enable User to form a business entity and access tools, information, documentation, and third-party services to establish, operate, and Fundraise for that entity.
Qualifications & exceptions
Unlike most Service Terms, Atlas does not incorporate the Financial Services Terms.
Account & Service Control · Restriction or exception
Atlas relies on what you tell Stripe; inaccurate information can block the Service or make documents wrong
The User acknowledges that the Stripe Atlas Services rely on the accuracy and completeness of the information it provides and that it is solely responsible for that accuracy and completeness. Inaccurate or incomplete information may prevent Stripe from providing some or all of the Atlas Services and may cause the documents prepared through them to be inaccurate or incomplete.
Supporting quotations
2. User Information.
User acknowledges that the Stripe Atlas Services rely on the accuracy and completeness of information User provides to Stripe, and User is solely responsible for the accuracy and completeness of all information. Inaccurate or incomplete information may: (a) result in Stripe not being able to provide some or all of the Stripe Atlas Services; and (b) cause the documents in connection with the Stripe Atlas Services to be inaccurate or incomplete.
Legal Rights & Agreement Rules · Permission or license
Using Atlas is consent to do business electronically and to let Stripe apply your e-signature to its documents
By using the Stripe Atlas Services, the User consents to doing business electronically. Because the Services involve processing various legal documents, the User acknowledges it will be legally bound by them and authorizes Stripe to automatically apply the User's electronic signature to all documents necessary to provide the Services.
Supporting quotations
3.1 Doing Business Electronically.
By using the Stripe Atlas Services, User consents to doing business electronically.
3.2 Electronic Signature.
The Stripe Atlas Services include processing various legal documents for User. User acknowledges that it will be legally bound by these documents and authorizes Stripe to automatically apply User’s signature(s) electronically to all documents necessary to provide the Stripe Atlas Services.
Qualifications & exceptions
The signature authorization covers all documents necessary to provide the Atlas Services and is automatic.
Not stated here
Which documents are 'necessary' is not listed.
Account & Service Control · Permission or license
You authorize Stripe to use your information for an IRS tax ID and to appoint a Registered Agent; report agent changes
If the User uses the Atlas Services to obtain a tax identification number from the U.S. Internal Revenue Service, it authorizes Stripe to use the User Information for that purpose. The User also authorizes Stripe to designate a Registered Agent, a person or entity appointed to act as registered agent for the Company, and must inform Stripe of any independent action it takes regarding its Registered Agent, including changes and dissolutions.
Supporting quotations
3.3 Tax Identification Number.
If User uses the Stripe Atlas Services to obtain a tax identification number from the U.S. Internal Revenue Service, User authorizes Stripe to use the User Information for such purpose..
3.4 Registered Agent.
User authorizes Stripe to designate a Registered Agent. User must inform Stripe of any action related to its Registered Agent that it takes independently, including changes and dissolutions.
“Registered Agent” means a person or entity appointed to act as a registered agent on behalf of the Company.
Qualifications & exceptions
The tax-ID authorization applies only if the User uses Atlas to obtain an IRS tax identification number.
Legal Rights & Agreement Rules · Restriction or exception
If an AI Agent uses Atlas for you, you are solely responsible and its actions bind you as an electronic agent under UETA
If the User uses an AI Agent to access the Atlas Services, it is solely responsible for every action initiated by or through the agent. The User acknowledges that an AI Agent is an 'electronic agent' or equivalent under the Uniform Electronic Transactions Act and similar statutes, and that actions the agent initiates or completes are legally binding on the User. An AI Agent is any automated technology, including chains of systems the User may not control or see, that is capable of or used for acting independently or semi-independently.
Supporting quotations
3.5 AI Agent.
If User uses an AI Agent to access the Stripe Atlas Services, User is solely responsible for each action initiated by or through the AI Agent. User acknowledges that: (a) an AI Agent constitutes an "electronic agent" or equivalent concept as defined or recognized under the Uniform Electronic Transactions Act (UETA) and similar statutes; and (b) actions initiated or completed by an AI Agent are legally binding on User.
“AI Agent” means any software, computer or other automated technology, including any such technology that operates through, in conjunction with, or by invoking other automated systems, platforms, APIs or agents, whether or not User has direct control over or visibility into each intermediate system in the chain
Qualifications & exceptions
Covers agents operating through intermediate systems the User does not directly control or see.
UETA is cited by name; its text is not supplied.
Legal Rights & Agreement Rules · Restriction or exception
If you fundraise through Atlas, you alone handle securities compliance, investor eligibility and tax treatment
If the User uses the Atlas Services for a Fundraising (offering securities for sale, including preparing, executing, administering or receiving funds under a financing instrument), it must comply with all Laws relating to the Fundraising and ensure the information and materials it gives investors through the Services are accurate, complete and not misleading. The User is solely responsible for determining whether and on what basis a Fundraising may be made, including registration exemptions, investor eligibility or verification, required disclosures, notices, filings and recordkeeping; for ensuring each purchaser meets the eligibility requirements relied on, including confirming 'accredited investor' status under Regulation D of the Securities Act of 1933 where required; and for the tax characterization, reporting, filing, withholding and payment obligations arising from any Fundraising.
Supporting quotations
4 Fundraising.
4.1 Compliance.
If User uses the Stripe Atlas Services for a Fundraising, User must: (a) comply with all Laws relating to a Fundraising; and (b) ensure that information and materials it provides to investors through the Stripe Atlas Services are accurate, complete, and not misleading.
4.2 User Responsibilities.
User is solely responsible for:
determining whether, and on what basis, a Fundraising may be made, including the availability and satisfaction of any registration exemption, investor eligibility or verification requirements, required disclosures, notices, filings, and recordkeeping obligations.
ensuring that each purchaser satisfies the eligibility requirements on which User relies for its Fundraising, including, if required, confirming that a purchaser is an “accredited investor” (within the meaning of Regulation D under the Securities Act of 1933).
the tax characterization, reporting, filing, withholding, and payment obligations of User that arise from any Fundraising.
“Fundraising” means the offering for sale of securities, including preparing, executing, administering, or receiving funds in connection with any financing instrument.
Qualifications & exceptions
Applies when the User uses the Atlas Services for a Fundraising.
Regulation D and the Securities Act of 1933 are cited by name; their text is not supplied.
Sharing & Disclosure · Permission or license
Stripe may route you to third-party Providers and share data with them; agent and filing services follow LegalZoom terms
Stripe may enable or allow the User to access services from Providers, third parties serving the User in connection with the Atlas Services. The User authorizes Providers to deliver their services and interact with Government Authorities as needed, and authorizes Stripe to share the data necessary for that. The User acknowledges that its access to Registered Agent services and automated state and federal filing processing is subject to the LegalZoom Provider Terms, located at legalinc.com.
Supporting quotations
5. Providers.
Stripe may enable or allow User to access services provided to User by Providers. User authorizes: (a) Providers to deliver services and interact with Government Authorities as required to deliver the relevant services, and (b) Stripe to share data necessary to deliver the same. User acknowledges that its access to and use of Registered Agent services, and automated state and federal filing processing is subject to the LegalZoom Provider Terms.
“Provider” means a third party that provides services to User in connection with the Stripe Atlas Services.
“LegalZoom Provider Terms” means the terms located at
Qualifications & exceptions
Data sharing with Providers is limited to what is necessary to deliver the services.
The LegalZoom Provider Terms are an external document, linked but not supplied.
Not stated here
Which other Providers Stripe uses is not stated.
Legal Rights & Agreement Rules · Context
Stripe, Providers and Legal Partners give no legal, accounting or tax advice and create no privilege
The User acknowledges that Stripe is not a law firm, accounting firm, financial advisor or tax advisor, and that Stripe, Providers and Legal Partners give no legal, accounting, financial or tax advice in connection with the Atlas Services. Using the Services creates no attorney-client or other special relationship, and communications are not covered by work-product or attorney-client privilege. The User alone is responsible for all corporate, tax, securities and other legal reporting, payment and compliance for its personal and business activities, and all information, forms and materials provided through the Services are for informational and educational purposes only.
Supporting quotations
6. Acknowledgments, Disclaimer and Liability.
6.1 Acknowledgments.
User acknowledges and agrees that:
Stripe is not a law firm, an accounting firm, financial advisor or tax advisor. Stripe, Providers and Legal Partners do not provide legal, accounting, financial or tax advice of any kind whatsoever in connection with the Stripe Atlas Services.
Use of the Stripe Atlas Services and any information provided does not create an attorney-client relationship or any other special relationship and communications will not be subject to any work-product or attorney-client privilege.
User alone is responsible for all corporate, tax, securities and other legal reporting, payment and compliance aspects of its personal and business activities.
All information, forms, and materials provided through the Stripe Atlas Services are provided to User for informational and educational purposes only, and do not constitute legal, accounting, financial or tax advice.
Qualifications & exceptions
'Legal Partners' is a capitalized term used here without a definition in this packet.
Legal Rights & Agreement Rules · Restriction or exception
You, not Stripe, bear losses from late or misfiled filings, from not hiring a lawyer, and from bad information
The User remains fully liable, and Stripe is not liable, for any losses, damages, costs, fines, fees or penalties the User or anyone else suffers because a filing is delayed, misfiled or filed late, because the User retained or failed to consult or retain an attorney or other professional on any contract, document or legal matter, or because of inaccuracies in the information the User gave Stripe.
Supporting quotations
6.2. Disclaimer
User remains fully liable for, and Stripe is not liable for, any losses, damages, costs, fines, fees or penalties that User or any other person may suffer as a result of: (a) a filing being delayed, misfiled, or late filed; (b) User’s retention of, or its failure to consult or retain, an attorney or other professional with respect to any contract, document or legal matter; or (c) any inaccuracies in the information User provides to Stripe.
Qualifications & exceptions
Covers losses to third parties as well as the User ('or any other person').
The filing-delay exclusion is not conditioned on who caused the delay.
Legal Rights & Agreement Rules · Restriction or exception
Under Atlas, 'User' means each Founder and the Company, all jointly liable, and 'Stripe' means Stripe GEP, Inc.
For the Stripe Atlas Terms, references to the User include each Founder (the Company's directors, officers and initial equity holders) and the Company (the entity formed through Atlas), and references to Stripe mean Stripe GEP, Inc. Each Founder and the Company remain jointly and severally liable for all acts and omissions of each of them and for all losses, damages and costs arising out of or related to use of the Atlas Services.
Supporting quotations
For the purposes of these Stripe Atlas Terms: (i) references to User include each Founder and the Company; and (ii) references to Stripe mean Stripe GEP, Inc.
Each Founder and the Company remain jointly and severally liable for all: (i) acts and omissions of each of them; and (ii) losses, damages and costs, in each case arising out of or related to use of the Stripe Atlas Services.
“Company” means the entity formed using the Stripe Atlas Services.
“Founder” means each of the Company’s directors, officers and initial equity holders.
Qualifications & exceptions
Joint and several liability means Stripe may pursue any Founder or the Company for the whole amount.
The contracting Stripe entity for Atlas is Stripe GEP, Inc., not the entity named in the General Terms.
Section 7 defines the Atlas vocabulary. An 'AI Agent' is any automated technology, including chains of systems the User may not control or see, capable of or used for acting independently or semi-independently as the User's delegate, proxy, intermediary or agent in transactions. The 'Company' is the entity formed through Atlas; a 'Founder' is each of its directors, officers and initial equity holders. 'Fundraising' is offering securities for sale, including handling funds under a financing instrument. 'Legal Partners' are the legal or accounting firms partnering with Stripe to provide legal and educational information, templates and documents, including Cooley LLP. The 'LegalZoom Provider Terms' are the terms at legalinc.com governing that Provider's services. A 'Provider' is a third party serving the User in connection with Atlas. A 'Registered Agent' is the person or entity appointed as registered agent for the Company. The 'Stripe Atlas Services' let the User form an entity and access tools, documentation and third-party services to establish, operate and fundraise for it. A 'Back to Top' link closes the section.
Supporting quotations
7. Definitions.
that is capable of, designed for, or employed for the purpose of independently or semi-independently acting as User’s delegate, proxy, intermediary, or agent in any transactional activity, whether in a single transaction or across multiple ongoing transactions.
“Company” means the entity formed using the Stripe Atlas Services.
“Founder” means each of the Company’s directors, officers and initial equity holders.
“Fundraising” means the offering for sale of securities, including preparing, executing, administering, or receiving funds in connection with any financing instrument.
“Legal Partner" means the legal or accounting firms that partner with Stripe to provide legal and educational information, templates, documents and agreements, including Cooley LLP.
that govern Provider’s provision, and User's access to and use of Provider’s services.
“Provider” means a third party that provides services to User in connection with the Stripe Atlas Services.
“Registered Agent” means a person or entity appointed to act as a registered agent on behalf of the Company.
“Stripe Atlas Services” means the Services that enable User to form a business entity and access tools, information, documentation, and third-party services to establish, operate, and Fundraise for that entity.
Legal Rights & Agreement Rules · Context
The Billing Terms govern billing, revenue collection and subscriptions, including the Metronome usage-based services
The Stripe Billing Terms, last modified June 17, 2026, supplement the General Terms and govern the Stripe Billing Services: the Services for billing Customers, collecting revenue and managing subscriptions, including the Metronome-branded Stripe Metronome Services for metering usage events, configuring usage-based and flexible pricing, and managing usage-based contracts and commitments. Undefined capitalized terms take their meaning from the General Terms, not supplied.
Supporting quotations
Stripe Billing
Last modified: June 17, 2026
1. Stripe Billing Services.
These terms (“Stripe Billing Terms”) supplement the General Terms and govern the use of the Stripe Billing Services. Capitalized terms that are not defined in these Stripe Billing Terms have the same meanings given to them in the General Terms.
“Stripe Billing Services” means the Services that enable User to bill Customers for products and services, collect revenue, and manage subscriptions, including the Stripe Metronome Services.
“Stripe Metronome Services” means the Services that are Metronome-branded, including the Services that enable User to meter usage events, configure usage-based and flexible pricing models, and manage contracts and commitments for Customers based on usage or other consumption metrics.
Qualifications & exceptions
The Financial Services Terms are not incorporated into these terms.
Charges & Financial Obligations · Company practice
Billing can connect you to third-party and LLM services; Stripe may bill their fees, or you pay providers directly
Certain Billing features let the User access Third-Party Services, which include LLM Services: a large language model and related services from an LLM Provider the User selects and enables via Billing. Stripe may collect fees from the User for using Third-Party Services through Billing, including LLM Fees, the charges the LLM Provider bills Stripe at query and response time; the Agreement's fee-payment and collection provisions apply to them. If instead the User integrates directly with an LLM Provider or other Third-Party Service provider, or through another Third-Party Service, it is solely responsible for paying that provider directly. The User may need to create an account with the Third-Party Service provider.
Supporting quotations
2. Third-Party Services; LLM Services and Fees.
Certain features of the Stripe Billing Services allow User to access and use Third-Party Services. LLM Services are Third-Party Services. Stripe may collect fees (including LLM Fees) from User for User’s use of Third-Party Services via the Stripe Billing Services. User’s obligation to pay fees and Stripe’s rights to collect fees under this Agreement apply to those fees.
If User integrates directly with a Third-Party Service provider (including an LLM Provider), or uses another Third-Party Service through which to integrate with an LLM Provider, User is solely responsible for and must pay directly to the LLM Provider or Third-Party Service provider (as applicable) any fees for use of the Third-Party Services.
User may be required to create an account with a Third-Party Service provider to use Third-Party Services.
“LLM Fees” shall mean the fees charged by the LLM Provider to Stripe at the time of query and response for User’s use of the LLM Services.
“LLM Provider” means a third-party provider of an LLM that User selects and enables for use via the Stripe Billing Services.
“LLM Services” means an LLM and related services provided by an LLM Provider, which User accesses via the Stripe Billing Services.
Qualifications & exceptions
Stripe collects LLM Fees only when the LLM Service is used via the Billing Services; direct integrations are paid directly to the provider.
Not stated here
LLM Fee amounts are set by the LLM Provider and not stated here.
Account & Service Control · Procedure
Configure Billing lawfully, keep data accurate, settle disputes, warn of recurring charges, get consents for LLM data
The User is responsible for configuring the Billing Services for its needs and to comply with Law, for the accuracy of information it gives Stripe, and for resolving disputes with Customers about its use of Billing. To use Third-Party Services including LLM Services, the User must activate them by selecting the provider in the Stripe Dashboard or integrating via the Stripe API. Before the first recurring or subscription Transaction, the User must tell each Customer the charges are ongoing and explain how to cancel. If the User accesses Third-Party Services via Billing, it must give Customers the notices and obtain the rights and consents needed for Stripe to lawfully receive, handle, transmit and process Customer Personal Data, including data in LLM Data exchanged with an LLM Provider.
Supporting quotations
3. User’s Obligations.
User is responsible for configuring the Stripe Billing Services for its needs and to comply with Law.
User must (a) ensure the accuracy of information User provides to Stripe in connection with the Stripe Billing Services, and (b) resolve any disputes between User and Customers related to User’s use of the Stripe Billing Services.
To access Third-Party Services (including LLM Services) via the Stripe Billing Services, User must activate those services by selecting the relevant Third-Party Service provider (e.g., LLM Provider) in its Stripe Dashboard or by integrating via the Stripe API.
If User uses the Services to submit recurring or subscription Transactions, then before submitting the initial Transaction, User must (a) inform each Customer that the relevant Transactions will occur on an ongoing basis; and (b) explain the method for canceling the Customer’s recurring billing or subscription.
If User accesses Third-Party Services (including LLM Services) via the Stripe Billing Services, User must provide notices to, and obtain rights and consents from, Customers sufficient to permit Stripe to lawfully receive, handle, transmit and process Customer Personal Data, including as contained in LLM Data between User and an LLM Provider.
“LLM Data” means any data User directs Stripe to send to or receive from an LLM Provider in connection with User’s use of the Stripe Billing Services.
Qualifications & exceptions
The consent duty covers Customer Personal Data contained in LLM Data sent to or from an LLM Provider.
Account & Service Control · Restriction or exception
No gift cards, stored value or wallets via credits; no health data, ITAR activity, unlawful use or LLM-terms breaches
The User must not use the credits feature of Billing to sell gift cards, offer stored value, offer wallet functionality or enable purchases from third parties. It must not use Billing in ways the Documentation expressly prohibits, must not use it, or let its Connected Accounts use it, with Protected Health Information, must not use LLM Services in violation of the LLM Services' terms and policies, and must not use Billing for activities subject to the U.S. International Traffic in Arms Regulations (ITAR) or in a way that breaches or causes a breach of Law.
Supporting quotations
4. Services Restrictions.
User must not use the credits feature of the Stripe Billing Services to (a) sell gift cards; (b) offer stored value to User’s customers; (c) offer a wallet functionality; or (d) enable the purchase of products or services from third parties.
User must not use the Stripe Billing Services in ways expressly prohibited in the Documentation.
User must not, and must ensure that its Connected Accounts (if applicable) do not, use the Stripe Billing Services in connection with Protected Health Information.
User must not use LLM Services in violation of the LLM Services’ terms of service and policies.
User must not use the Stripe Billing Services (a) for activities that are subject to International Traffic in Arms Regulations (ITAR) maintained by the United States Department of State; or (b) in a manner that breaches, or causes the breach of Law.
Qualifications & exceptions
The Protected Health Information ban extends to the User's Connected Accounts where applicable.
ITAR is cited by name; its text is not supplied.
Not stated here
The Documentation's express prohibitions are not supplied.
Account & Service Control · Company practice
Stripe may suspend, restrict or remove any third-party or LLM service in Billing at its discretion, without notice
Stripe reserves the right, at its sole discretion, to suspend, restrict or remove the User's access to any Third-Party Service, including LLM Services, available through the Billing Services, with or without prior notice and without liability to the User.
Supporting quotations
Stripe reserves the right, at its sole discretion, to suspend, restrict, or remove User's access to any Third-Party Service (including LLM Services) available via the Stripe Billing Services, with or without prior notice and without liability to User.
Qualifications & exceptions
No reason, notice or compensation is required.
Legal Rights & Agreement Rules · Restriction or exception
You indemnify Stripe and its people for Losses from your material breach of an LLM Provider’s terms, within limits
Subject to the Limitations on Indemnity in the General Terms, the User will indemnify Stripe, its Affiliates and their directors, employees and agents for all Losses arising from the User's material breach of an LLM Provider's terms of service and policies.
Supporting quotations
5. Indemnification.
Subject to the Limitations on Indemnity in the General Terms, User will indemnify Stripe, its Affiliates, and their directors, employees, and agents for all Losses arising from User’s material breach of an LLM Provider’s terms of service and policies.
Qualifications & exceptions
Triggered by a material breach, not any breach.
Subject to the General Terms' Limitations on Indemnity, which are not supplied.
Section 6 defines the Billing vocabulary. A 'Connected Account' is a Platform User onboarded to a Stripe Connect Platform or a Payout Recipient. 'LLM' is a large language model; 'LLM Data' is data the User directs Stripe to send to or receive from an LLM Provider; 'LLM Fees' are the provider's charges to Stripe at query and response time; an 'LLM Provider' is the third-party LLM provider the User selects and enables; 'LLM Services' are the LLM and related services accessed via Billing. The 'Stripe Billing Services' cover billing, revenue collection and subscription management including the 'Stripe Metronome Services', the Metronome-branded usage-metering and usage-based pricing and contract services. A 'Back to Top' link closes the section.
Supporting quotations
6. Definitions.
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
“LLM” means large language model.
“LLM Data” means any data User directs Stripe to send to or receive from an LLM Provider in connection with User’s use of the Stripe Billing Services.
“LLM Fees” shall mean the fees charged by the LLM Provider to Stripe at the time of query and response for User’s use of the LLM Services.
“LLM Provider” means a third-party provider of an LLM that User selects and enables for use via the Stripe Billing Services.
“LLM Services” means an LLM and related services provided by an LLM Provider, which User accesses via the Stripe Billing Services.
“Stripe Billing Services” means the Services that enable User to bill Customers for products and services, collect revenue, and manage subscriptions, including the Stripe Metronome Services.
“Stripe Metronome Services” means the Services that are Metronome-branded, including the Services that enable User to meter usage events, configure usage-based and flexible pricing models, and manage contracts and commitments for Customers based on usage or other consumption metrics.
Legal Rights & Agreement Rules · Context
The Capital for Platforms Terms govern a platform’s role in marketing Stripe Capital Financing to its Connected Accounts
The Stripe Capital for Platforms Terms, last modified September 28, 2026, supplement the General Terms and incorporate the Stripe Financial Services Terms and Stripe Connect Infrastructure Terms by reference. They govern the Stripe Capital for Platforms Services: the Services Stripe provides to support joint efforts to market Stripe Capital Financing (a Stripe Capital Loan, Stripe Capital Advance or other commercial financing) to the User's Platform Users, Connected Accounts and Prospects, enabling Connected Accounts to obtain financing alongside the User's Platform Services. Undefined terms take their meaning from the General Terms, Financial Services Terms or Connect Infrastructure Terms.
Supporting quotations
Stripe Capital for Platforms
Last modified: September 28, 2026
1. Stripe Capital for Platforms.
These terms (“Stripe Capital for Platforms Terms”) supplement the General Terms and, together with the Stripe Financial Services Terms and Stripe Connect Infrastructure Terms each of which are incorporated into these Stripe Capital for Platforms Terms by this reference, govern the use of the Stripe Capital for Platforms Services.
The Stripe Capital for Platforms Services enable User’s Connected Accounts to obtain Stripe Capital Financing in conjunction with User’s Platform Services.
“Stripe Capital for Platforms Services” means the Services that Stripe provides to User in support of efforts between User and Stripe to market Stripe Capital Financing to Platform Users, Connected Accounts, and Prospects.
“Stripe Capital Financing” means a Stripe Capital Loan or Stripe Capital Advance, as applicable, or other form of commercial financing.
Qualifications & exceptions
These terms address the platform's marketing role; the financing itself is provided by a Capital Provider under separate Financing Terms.
Charges & Financial Obligations · Restriction or exception
Keep financing to business use and lawful purposes, report misuse at once, hold licenses, market only where approved
The User must ensure Prospects apply for, and Financing Recipients use, Stripe Capital Financing only in compliance with Law and only for their Business Purposes, never personal, family or household use, and must immediately notify Stripe on learning that a recipient has used proceeds otherwise or unlawfully. The User must maintain every regulatory license, registration, authorization, permit or waiver any Governmental Authority requires for its activities under these terms, and must conduct all financing-related marketing only in the Approved Territory, the Stripe-approved jurisdictions where its Connected Accounts may be eligible to become Prospects. A Stripe Capital Advance, a merchant cash advance or receivables-purchase agreement from a Capital Provider, is not intended to be and is not to be construed as a loan.
Supporting quotations
2. Stripe Capital Financing.
2.1 Nature and Use of Stripe Capital Financing.
User must ensure that Prospects only apply for, and Financing Recipients only use, Stripe Capital Financing in compliance with all Laws and only for their Business Purposes (and not for personal, family or household use). User must immediately notify Stripe if, at any time, User becomes aware that a Financing Recipient has used or is using the proceeds of a Stripe Capital Financing for any purpose other than Financing Recipient’s Business Purpose (and not for personal, family or household use) or in any manner that does not comply with all Laws.
User must maintain all regulatory licenses, registrations, authorizations, permits, and other permissions (or waivers) required by any Governmental Authority in connection with its activities and obligations under these terms. User must undertake all marketing financing-related activities in connection with the Stripe Capital for Platforms Services and these Stripe Capital for Platforms Terms only in the Approved Territory.
A Stripe Capital Advance is not intended to be, nor will it be construed as, a loan or any other lending transaction.
“Approved Territory” means a Stripe-approved jurisdiction or region in which User’s Connected Accounts may be eligible to become Prospects.
“Stripe Capital Advance” means a merchant cash advance agreement or a purchase of receivables agreement provided by a Capital Provider to a Prospect.
Qualifications & exceptions
Misuse of proceeds must be reported immediately.
Marketing is limited to the Approved Territory.
Not stated here
Which jurisdictions are Approved Territories is not listed.
Legal Rights & Agreement Rules · Context
Stripe itself is a Capital Provider only for Stripe Capital Advances and only in certain Approved Territories
The User acknowledges that Stripe is a Capital Provider, an entity that underwrites and provides Stripe Capital Financing, only in certain Approved Territories where it offers Stripe Capital Advances, and only with respect to those advances. Elsewhere, and for loans, the Capital Provider is another entity.
Supporting quotations
2.2 Stripe as a Capital Provider.
User acknowledges that Stripe is a Capital Provider only in certain Approved Territories in which Stripe offers Stripe Capital Advances, and only with respect to Stripe Capital Advances.
“Capital Provider” means an entity that underwrites and provides Stripe Capital Financing, or any of their respective affiliates, assigns, agents, subcontractors, or representatives.
Qualifications & exceptions
Stripe's provider role is limited to Stripe Capital Advances in certain territories.
Not stated here
Which entities act as Capital Provider for Stripe Capital Loans is not stated here.
Account & Service Control · Restriction or exception
Help identify Prospects, use only Stripe-approved marketing to your Connected Accounts, and pull materials on notice
On Stripe's request the User must cooperate to identify Prospects, the Platform Users or Connected Accounts eligible for a Prequalified Offer. The User must follow Stripe's guidelines when creating Marketing Materials and submit all of them, including ones based on Stripe templates, for Stripe's approval before use. It may market Stripe Capital Financing only to its own Connected Accounts, and Prequalified Offers only to Prospects, in each case within the Approved Territory, following all guidelines and instructions from Stripe (or Stripe on behalf of a Capital Provider) and the Documentation. It must immediately stop using any Marketing Materials when Stripe notifies it that they do not adhere to Stripe's guidelines, instructions or the Documentation, or present unacceptable risk to Stripe or a Capital Provider.
Supporting quotations
2.3 Marketing to Prospects.
Upon Stripe’s request, User must cooperate with Stripe to identify Prospects for Stripe Capital Financing.
User must comply with Stripe’s guidelines and directions when creating Marketing Materials. User must submit all Marketing Materials that User intends to use in connection with Stripe Capital Financing or the Stripe Capital for Platforms Services, including any Marketing Materials based on templates provided by Stripe, for approval by Stripe before they are used.
User is only permitted to market (i) Stripe Capital Financing to User’s Connected Accounts, and (ii) Prequalified Offers only to Prospects, in each instance within the Approved Territory. User must comply with all guidelines and instructions from Stripe, or Stripe on behalf of a Capital Provider, and the Documentation when marketing Stripe Capital Financing.
User must immediately discontinue using any Marketing Materials if Stripe notifies User that (i) the Marketing Materials do not adhere to Stripe’s guidelines, Stripe’s instructions, or the Documentation; or (ii) the Marketing Materials present unacceptable risk to Stripe or a Capital Provider.
“Marketing Materials” means the marketing materials developed for the purpose of promoting Stripe Capital Financing to select Platform Users and Connected Accounts, and Prequalified Offers to Prospects.
“Prospect” means a Platform User or Connected Account that is eligible for a Prequalified Offer.
Qualifications & exceptions
All Marketing Materials need Stripe's prior approval.
Marketing audience is limited to the User's Connected Accounts and, for Prequalified Offers, Prospects.
Charges & Financial Obligations · Company practice
Present Prequalified Offers within 1 business day as approved; Stripe may revoke offers or cancel financing freely
A Prequalified Offer is an offer to submit an application for Stripe Capital Financing. If the User elects to present them, it must use the form and substance Stripe approved, present each offer within 1 business day of receiving it, by email or another method Stripe approves in writing. If the User erroneously presents an offer, or a Capital Provider revokes one, the User must immediately take corrective action as Stripe instructs at its own expense; if Stripe erroneously presented the offer, the User still takes the corrective action but at Stripe's expense. Stripe may, for itself or a Capital Provider, revoke a Prequalified Offer or cancel or terminate a Stripe Capital Financing for any reason, before or after funds are disbursed, and disclaims all liability to the User for financings, revocations and cancellations. Using the Service does not guarantee that any Connected Account will receive an offer. A Financing Recipient is a Prospect who accepted an offer, was approved by a Capital Provider and agreed to Financing Terms.
Supporting quotations
2.4 Prequalified Offers.
If User has elected to present Prequalified Offers to Prospects, User must present all Prequalified Offers in the form and substance approved by Stripe. User must present a Prequalified Offer for a Prospect within 1 business day after User receives it. User may present a Prequalified Offer to a Prospect via email or by any other method approved by Stripe in writing. If User erroneously presents a Prospect or Connected Account with a Prequalified Offer, or if a Capital Provider decides to revoke a Prequalified Offer, then at User’s expense, User must immediately take corrective action as instructed by Stripe.
If Stripe erroneously presents a Prequalified Offer to a Prospect or Connected Account, or if a Capital Provider decides to revoke a Prequalified Offer, then at Stripe’s expense, User must immediately take corrective action as instructed by Stripe.
Stripe may, on behalf of itself or a Capital Provider, revoke a Prequalified Offer or cancel or terminate a Stripe Capital Financing for any reason whether before or after funds have been disbursed. Stripe disclaims all liability to User with respect to Stripe Capital Financings, including if a Prequalified Offer is revoked, or if a Stripe Capital Financing is cancelled or terminated.
User’s use of the Stripe Capital for Platforms Services does not in any way guarantee that a Connected Account will receive a Prequalified Offer.
“Prequalified Offer” means an offer to submit an application to receive Stripe Capital Financing.
“Financing Recipient” means a Prospect who has accepted a Prequalified Offer, has been approved by a Capital Provider, and has agreed to Financing Terms.
Qualifications & exceptions
The 1-business-day presentation deadline applies when the User elects to present offers itself.
Corrective action is at the User's expense for User errors and at Stripe's expense for Stripe errors.
Revocation or cancellation needs no reason and may happen after disbursement.
Not stated here
The Financing Terms between recipients and Capital Providers are separate documents, not supplied.
Account & Service Control · Procedure
Every Prospect must apply through the Application Flow; redirect any Prospect who asks you how to apply
The User must ensure all Prospects apply for Stripe Capital Financing through the Application Flow, the sequence of steps Prospects must follow when applying. If a Prospect contacts the User, or the User contacts a Prospect, about completing an application, the User must redirect the Prospect to the Application Flow through a process Stripe provides or approves.
Supporting quotations
2.5 Applying for Stripe Capital Financing.
User must ensure that all Prospects apply for Stripe Capital Financing via the Application Flow. If a Prospect contacts User, or User contacts a Prospect, regarding how to complete an application for Stripe Capital Financing, User must redirect that Prospect to the Application Flow via a process provided or approved by Stripe.
“Application Flow” means the sequence of steps that Prospects must take when applying for Stripe Capital Financing.
Qualifications & exceptions
Redirection must use a Stripe-provided or Stripe-approved process.
Charges & Financial Obligations · Restriction or exception
Neither you nor a Prospect picks the Capital Provider or financing type; recipients must comply with Financing Terms
Neither the User nor a Prospect may select or demand a specific Capital Provider or type of Stripe Capital Financing. The User must ensure that Prospects who become Financing Recipients cooperate with Stripe to comply with their Financing Terms, the loan or advance agreement among the Connected Account, the Capital Provider and other relevant parties, and that they can access financing-related information.
Supporting quotations
Neither User nor a Prospect may select or demand a specific Capital Provider or type of Stripe Capital Financing.
2.6 Financing Terms.
User must ensure that all Prospects that become Financing Recipients cooperate with Stripe to comply with its applicable Financing Terms and can access financing-related information.
“Financing Terms” means a Stripe Capital Loan agreement or a Stripe Capital Advance agreement, in either case, among a Connected Account, a Capital Provider, and any other relevant parties.
Qualifications & exceptions
The Financing Terms are separate agreements between the recipient and the Capital Provider, not supplied here.
Charges & Financial Obligations · Restriction or exception
Process financed accounts through Stripe until paid off; do not cut them off except for departure or serious risk
Unless Stripe permits otherwise in writing, the User must use the Stripe Payments Services for all Financing Recipients with outstanding obligations under a Stripe Capital Financing until those obligations are fully satisfied, and for all Prospects whose eligibility is under review. The User must not terminate or restrict a Financing Recipient's access to its Platform Services or the Stripe Payment Services, except where the recipient stops being a Platform User, or in cases of credit risk, fraud or other reasons posing an unreasonable legal or reputational risk to the User. If the User does terminate or restrict a recipient with outstanding obligations, it must immediately notify Stripe and take all actions Stripe directs to ensure the recipient pays in full.
Supporting quotations
2.7 Payment Processing Through Stripe.
Except as otherwise permitted by Stripe in writing, User must use the Stripe Payments Services for (a) all Financing Recipients with outstanding obligations under a Stripe Capital Financing until those obligations have been fully satisfied, and (b) all Prospects whose eligibility for Stripe Capital Financing is then-currently under review. User must not terminate or restrict a Financing Recipient’s access to User’s Platform Services or the Stripe Payment Services, except (x) if a Financing Recipient ceases to be a Platform User, or (y) in the event of credit risk, fraud, or other reasons which would pose an unreasonable legal or reputational risk to User.
If User terminates or restricts the access of a Financing Recipient to User’s Platform Services and that Financing Recipient has outstanding obligations under a Stripe Capital Financing, then User must immediately notify Stripe, and take all actions necessary, as directed by Stripe, to ensure that the Financing Recipient pays those outstanding amounts in full.
Qualifications & exceptions
The Stripe Payments requirement lasts until the financing is fully repaid, and also covers Prospects under review.
Cutting off a recipient is allowed only if they cease to be a Platform User or pose credit, fraud, legal or reputational risk.
Account & Service Control · Restriction or exception
Use the API and Dashboard per the Documentation, charge Connected Accounts no extra fees, give Stripe platform access
If Stripe makes the Stripe API or Dashboard available, the User may use them per the Documentation to access Program Data (application, eligibility, Servicer, Transaction, credential, record and compliance data Stripe uses for the Service) and Marketing Materials, and to give Connected Accounts and Prospects access to financing. The User must not charge its Connected Accounts additional fees in connection with the Service or a financing. At no cost to Stripe, the User must give Stripe an account on its platform and access to every surface that features, references or embeds Capital for Platforms components, so Stripe can use, test and monitor the User's use and marketing and its compliance with these terms.
Supporting quotations
2.8 Stripe API and Stripe Dashboard.
If Stripe makes the Stripe API or Stripe Dashboard available to User, then User may use them in accordance with the Documentation to access the Program Data and Marketing Materials and to provide Connected Accounts and Prospects with access to Stripe Capital Financing.
2.9 Additional Fees.
User must not charge User’s Connected Accounts additional fees in connection with Stripe Capital for Platforms Services or a Stripe Capital Financing.
2.10 Platform Access.
User must, at no cost to Stripe, provide Stripe with an account on User’s platform, and provide access to all surfaces on User’s platform that feature, reference, or embed components of Stripe Capital for Platforms Services to enable Stripe to use, test, and monitor User’s use and marketing of the Stripe Capital for Platforms Services and compliance with these Stripe Capital for Platforms Terms.
“Program Data” means data associated with an application for Stripe Capital Financing, eligibility criteria, Servicers, Transactions, access credentials, records, regulatory compliance data, and any other information Stripe uses or generates to provide the Capital for Platforms Services to User.
Qualifications & exceptions
API and Dashboard access is at Stripe's option ('if Stripe makes available').
The ban on additional fees covers both the Service and the financing itself.
Account & Service Control · Procedure
Answer financing questions only with unmodified Pre-Approved Responses; forward Complaints within 3 business days
Unless Section 2.11 says otherwise, the User must use Pre-Approved Responses, the Stripe-approved communications, when answering questions or other communications from Platform Users, Connected Accounts, Prospects or Financing Recipients about the Service or financing, and must not modify them. Where a Pre-Approved Response cannot resolve the matter, the User must redirect the person to Stripe or follow Stripe's instructions. Any other contact about the Service or financing must follow Stripe's guidelines, instructions and the Documentation. Pre-Approved Responses may not be used for Complaints; the User must direct complainants to submit Complaints to capital-support@stripe.com within 3 business days after receipt. The User may reply to its own employees' inquiries or feedback.
Supporting quotations
2.11 Communication with Platform Users, Connected Accounts, Prospects, and Financing Recipients.
Unless otherwise described in this Section 2.11, User must use Pre-Approved Responses when responding to questions or other communications from Platform Users, Connected Accounts, Prospects, or Financing Recipients about the Stripe Capital for Platforms Services or Stripe Capital Financing. If a Platform User, Connected Account, Prospect, or Financing Recipient needs assistance that a Pre-Approved Response cannot resolve, then User must redirect that Platform User, Connected Account, Prospect, or Financing Recipient to Stripe or otherwise follow Stripe’s instructions for resolution.
Stripe will provide all Pre-Approved Responses and User must not modify a Pre-Approved Response in any way.
User must not use Pre-Approved Responses to respond to Complaints. User must direct Platform Users, Connected Accounts, Prospects, and Financing Recipients to submit Complaints regarding the Stripe Capital for Platforms Services and Stripe Capital Financing to capital-support@stripe.com within 3 business days after receipt. User may elect to reply to inquiries or feedback from User’s employees about the Stripe Capital for Platforms Services.
“Pre-Approved Responses” means the Stripe-approved communications used to respond to questions or reply to other communications.
Qualifications & exceptions
Pre-Approved Responses come from Stripe and may not be modified in any way.
The 3-business-day window runs from the User's receipt of the Complaint.
Not stated here
Whether the 3-business-day deadline binds the complainant or the User's redirection is not spelled out.
Account & Service Control · Procedure
Train your staff to Stripe’s guidelines, do not outsource duties without approval, accept Stripe monitoring and audits
The User must ensure all employees, contractors and agents with Capital for Platforms responsibilities receive training that complies with any written guidelines Stripe provides. Unless Stripe approves in writing, the User must not outsource or subcontract its obligations under these terms. Stripe may monitor and review the User's Stripe Account, API use, marketing activities and any policies, procedures, agreements, consents and disclosures the User gives its Platform Users, to check compliance; on written request the User must permit and cooperate with an audit by Stripe or its third-party auditor, including by providing additional information.
Supporting quotations
2.12 Training.
User must ensure that all employees, contractors, and agents with responsibilities related to Stripe Capital for Platforms Services receive training that complies with the guidelines that Stripe provides to User in writing (if any).
2.13 Outsourcing Prohibited.
Unless otherwise approved by Stripe in writing, User must not outsource or subcontract User’s obligations under these Stripe Capital for Platforms Terms to any third party.
2.14 Monitoring; Audit.
Stripe may monitor and review User’s Stripe Account, User’s use of the Stripe API, User’s marketing activities, and any other information, policies and procedures or agreements, consents, and disclosures that User makes available to User’s Platform Users, to ensure User’s compliance with these Stripe Capital for Platforms Terms. At Stripe’s written request, User must permit and cooperate with Stripe or its third-party auditor to audit User’s compliance with these Stripe Capital for Platforms Terms, which may include providing additional information upon request by Stripe or its third-party auditor.
Qualifications & exceptions
Training guidelines apply only if Stripe provides them in writing.
Audits follow Stripe's written request and may be conducted by a third-party auditor.
Charges & Financial Obligations · Context
After funds are paid out, a Servicer such as Stripe Servicing, Inc. manages the financing, not you
Where applicable, the Servicer provides all Servicing to Financing Recipients. Servicing is the management and administration of a Stripe Capital Financing after funds are disbursed, and a Servicer is an entity Stripe, a Capital Provider or a purchaser of the financing designates for that role, including Stripe Servicing, Inc. and its Affiliates, agents and subcontractors.
Supporting quotations
3. Servicing.
If applicable, the Servicer will provide all Servicing to Financing Recipients.
“Servicer” means an entity or group of entities that Stripe, a Capital Provider, or a purchaser of a Stripe Capital Financing may designate to manage a Stripe Capital Financing, including Stripe Servicing, Inc. (and its Affiliates, as applicable), and any of their respective agents, assigns, subcontractors, or representatives.
“Servicing” means the management and administration of Stripe Capital Financing after funds have been disbursed to the Financing Recipient.
Qualifications & exceptions
Applies 'if applicable'; the Servicer may be designated by Stripe, a Capital Provider or a purchaser of the financing.
Security & Safeguards · Company commitment
Both you and Stripe must comply with privacy, security and confidentiality Laws for Capital for Platforms data
Each party must comply with all Laws governing the privacy, protection, security, confidentiality and use of data provided, accessed or used in connection with the Stripe Capital for Platforms Services. The clause then lists specific User duties, beginning with consents, authorizations and disclosures for Platform User Data, which continue in the next packet.
Supporting quotations
4. Confidentiality; Data Privacy and Security.
4.1 Data Protection.
Each party must be compliant with all Laws governing the privacy, protection, security, confidentiality, and the use of data provided, accessed or used in connection with the Stripe Capital for Platforms Services. User must:
Qualifications & exceptions
The general compliance duty is mutual; the itemized duties that follow fall on the User.
Sharing & Disclosure · Procedure
Obtain and record consents to share Platform User Data with Stripe for marketing and underwriting; exclude end-user data
The User must obtain, record and manage all necessary consents and authorizations, and provide disclosures, including from and to its Platform Users, so that it may disclose Platform User Data to Stripe and Stripe may collect, use, process or disclose the Personal Data and other information the User gives Stripe or a Capital Provider for the Service or a financing, including for marketing and underwriting. Platform User Data is a Platform User's payment volume from other processors, transaction data and offline cash and check transactions that the User shares with Stripe. The User must ensure Platform User Data does not include a Platform User's own end users' personal data under the GDPR or personal information under the CCPA.
Supporting quotations
obtain all necessary consents, and authorizations, and record and manage those consents and authorizations and (ii) provide disclosures, including from and to User’s Platform Users, in each case to disclose Platform User Data to Stripe and enable Stripe to collect, use, process, or disclose Personal Data and other information User provides to Stripe or a Capital Provider in connection with the Stripe Capital for Platforms Services or a Stripe Capital Financing, including consents and authorizations for marketing and underwriting purposes
ensure that Platform User Data does not include a Platform User's end users' “personal data” as defined in the GDPR or “personal information” as defined in the CCPA.
“Platform User Data” means a Platform User’s payment volume information from other payment processors, transaction data, and offline transactions that User shares with Stripe, including from cash and checks.
“GDPR” means General Data Protection Regulation (EU) 2016/679.
User must:
Qualifications & exceptions
Consents must cover marketing and underwriting uses, not only service delivery.
End-user personal data (GDPR) or personal information (CCPA) must be excluded from what is shared.
Not stated here
The GDPR and CCPA are cited by name; their text is not supplied.
Use & Processing · Restriction or exception
No selling or renting the Data, use it only as permitted, and never be or expose Stripe to a credit-reporting regime
The User must not sell, rent or otherwise make available Data, or let others do so, for any purpose, including marketing or offering Stripe Capital Financing. It may use Data related to the Service or a financing only as this Agreement or other written agreements with Stripe expressly permit and in compliance with Laws. The User must not be a consumer credit reporting governmental agency or entity in an Approved Territory, and must ensure its data sharing under these terms does not subject Stripe to consumer credit reporting Laws there.
Supporting quotations
User must not sell, rent, or otherwise make available, or allow others to sell, rent, or otherwise make available Data for any purposes, including marketing or the issuing or offering of Stripe Capital Financing. User will use Data related to the Stripe Capital for Platforms Services or a Stripe Capital Financing only: (a) as expressly permitted by this Agreement or other written agreements between Stripe and User (or their Affiliates); and (b) in compliance with Laws. User must not be a consumer credit reporting governmental agency or entity in an Approved Territory, and User must ensure that its data sharing under these Capital for Platforms Service Terms will not subject Stripe to any consumer credit reporting Laws in an Approved Territory.
Qualifications & exceptions
The use limit is to express permissions in the Agreement or other written Stripe agreements.
Not stated here
'Data' is a capitalized term defined in the General Terms, not supplied.
Use & Processing · Restriction or exception
Program Data is Stripe’s; use it only for the Service and disclose it only to process recipients’ payments or as told
Program Data is Stripe Data. The User must not use it for any purpose unrelated to its use of the Capital for Platforms Services without Stripe's express written consent, and must not disclose it to third parties except as necessary to process Transactions for Financing Recipients with Stripe, in accordance with Law and the Card Network Rules, or as Stripe otherwise directs.
Supporting quotations
4.2 Program Data.
Program Data is Stripe Data. User must not use Program Data for any purpose unrelated to User’s use of Stripe Capital for Platforms Services without Stripe’s express written consent. User must not disclose Program Data to any third parties except as necessary to process Transactions for Financing Recipients with Stripe, and in accordance with Law and Card Network Rules, or as otherwise directed by Stripe.
Qualifications & exceptions
Other uses need Stripe's express written consent.
Not stated here
'Stripe Data' is defined in the General Terms, not supplied.
Sharing & Disclosure · Company practice
Stripe uses Data to screen Prospects, service loans, fight fraud, satisfy regulators and investors, and improve products
Stripe processes, analyzes and manages Data under its Privacy Policy to determine eligibility to become a Prospect, provide the Service, provide Servicing, mitigate fraud, financial loss or other harm, meet its obligations to regulators, Capital Providers, credit facilities financing loans and investors who may buy loans, and to analyze, develop and improve its products, systems and tools. Stripe provides Data to third-party service providers, Capital Providers, credit facilities, loan investors and its Affiliates to deliver the Service to the User, Platform Users, Connected Accounts and other users. The User consents to these uses. Stripe may retain the Platform User Data it receives according to applicable Law and its retention policies.
Supporting quotations
4.3 Stripe’s Use of Data.
Stripe processes, analyzes, and manages Data in accordance with Stripe’s Privacy Policy to (a) determine eligibility to become a Prospect, (b) provide the Stripe Capital for Platforms Services, (c) provide Servicing, (d) mitigate fraud, financial loss, or other harm, (e) fulfill Stripe’s obligations to regulatory authorities, Capital Providers, credit facilities involved in the financing of loans, and investors who may purchase loans, and (f) analyze, develop, and improve Stripe’s products, systems, and tools. Stripe provides Data to third-party service providers, Capital Providers, credit facilities involved in the financing of loans, investors who may purchase loans, and Stripe’s Affiliates, to allow Stripe to provide the Stripe Capital for Platforms Services to User, Platform Users, Connected Accounts, and other users.
User consents to Stripe’s use of Data for the purposes and in a manner consistent with this Section 4.3. Stripe may retain Platform User Data it receives from User in accordance with applicable Law and Stripe’s retention policies.
Qualifications & exceptions
The purposes include product development and improvement, not only delivering the Service.
Recipients include credit facilities and investors who may purchase loans.
Not stated here
Stripe's Privacy Policy and retention policies are not supplied; no retention period is stated.
Content & IP Rights · Permission or license
You license your Marks for Stripe’s marketing during the Term; at termination both stop using Marks, except Servicing
The User grants Stripe, and any third party Stripe engages to produce Marketing Materials, a fully paid-up, worldwide, non-exclusive license to use the User's Marks on Marketing Materials and Capital for Platforms materials during the Term. On termination or expiration of these terms, each party must immediately stop using the other's Marks for the Service, the Marketing Materials and all financings, except as necessary for the Servicer to fulfill its obligations on financings already provided to Financing Recipients.
Supporting quotations
5. Use of Trademarks and Marketing Guidelines.
User grants to Stripe, and any third party Stripe may engage to provide Marketing Materials, a fully paid-up, worldwide, non-exclusive license to use User’s Marks on Marketing Materials and any Stripe Capital for Platforms Services materials during the Term.
6. Term and Termination.
Upon termination or expiration of these Stripe Capital for Platforms Terms, each party will immediately cease using the other party’s Marks with respect to the Stripe Capital for Platforms Services, the Marketing Materials, and all Stripe Capital Financings, except as necessary to allow Servicer to fulfill its obligations in connection with Stripe Capital Financing provided to Financing Recipients.
Qualifications & exceptions
The license extends to third parties Stripe engages for Marketing Materials.
The post-termination exception preserves Servicer use of Marks for existing financings.
Legal Rights & Agreement Rules · Restriction or exception
You own your products; for Capital claims the liability cap uses 12 months of Capital Program Earnings instead of Fees
The User remains solely responsible for all products and services it provides to its Customers. For calculating each party's aggregate liability and indemnification obligations under the Agreement for claims arising from the Capital for Platforms Services, references to 'Fees' in the General Terms' limitation-of-liability provisions are read as Capital Program Earnings for the 12 months preceding the event giving rise to the claim.
Supporting quotations
7. Relationship of the Parties.
User remains solely responsible for all products and services User provides to User’s Customers.
8. Limitation of Liability.
For the purposes of calculating each party's aggregate liability and indemnification obligations under the Agreement with respect to any claim arising out of or relating to the Stripe Capital for Platforms Services, references to “Fees” in the limitation on liability provisions of the General Terms are deemed to refer to Capital Program Earnings for the 12-month period preceding the event giving rise to the claim.
Qualifications & exceptions
The substitution applies only to claims arising out of or relating to the Capital for Platforms Services.
'Capital Program Earnings' is a capitalized term whose definition is not in this packet.
Not stated here
The General Terms' limitation-of-liability provisions are not supplied, so the resulting cap cannot be computed here.
Legal Rights & Agreement Rules · Context
Capital for Platforms definitions: Application Flow, Approved Territory, Capital Provider, Card Network, CCPA, Complaint
Section 9 begins the definitions. The 'Application Flow' is the sequence of steps Prospects follow when applying. An 'Approved Territory' is a Stripe-approved jurisdiction where Connected Accounts may become Prospects. A 'Capital Provider' underwrites and provides Stripe Capital Financing. 'Card Network' and 'Card Network Rules' carry the usual Visa, Mastercard, American Express and Discover meaning. 'CCPA' is the California Consumer Privacy Act of 2018, cited as Cal. Civ. Code Sections 1798.100-1798.199, an external statute referenced by name only. A 'Complaint' is any expression of dissatisfaction with a product, service, policy or employee from a Platform User, Connected Account, Prospect or Financing Recipient about the Service or a financing, or a Governmental Authority's inquiry or request for examination about them. The definitions continue in the next packet.
Supporting quotations
9. Definitions.
“Application Flow” means the sequence of steps that Prospects must take when applying for Stripe Capital Financing.
“Approved Territory” means a Stripe-approved jurisdiction or region in which User’s Connected Accounts may be eligible to become Prospects.
“Capital Provider” means an entity that underwrites and provides Stripe Capital Financing, or any of their respective affiliates, assigns, agents, subcontractors, or representatives.
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
“Card Network Rules” means the Payment Method Rules published by a Card Network.
“CCPA” means California Consumer Privacy Act of 2018, Cal. Civ. Code Sections 1798.100-1798.199.
“Complaint” means any expression of dissatisfaction with a product, service, policy, or employee communicated by a Platform User, Connected Account, Prospect, or Financing Recipient related to the Stripe Capital for Platforms Services or a Stripe Capital Financing, or an inquiry or request for examination from a Governmental Authority in respect of the Stripe Capital for Platforms Services or a Stripe Capital Financing.
Qualifications & exceptions
The CCPA citation is to an external statute; its sections are not part of this document.
Legal Rights & Agreement Rules · Context
Capital for Platforms definitions: Connected Account, Data, Financing Recipient, Financing Terms, Platform User Data
The definitions continue. A 'Connected Account' is a Platform User onboarded to a Stripe Connect Platform or a Payout Recipient. 'Data' without a modifier means all Personal Data, Program Data and Platform User Data together. A 'Financing Recipient' is a Prospect who accepted an offer, was approved and agreed to 'Financing Terms', the loan or advance agreement among the Connected Account, Capital Provider and others. 'GDPR' is Regulation (EU) 2016/679. 'Marketing Materials' promote financing and offers. 'Platform Services' are what Platform Users receive from the platform, paid or not. A 'Platform User' is a user of the User's platform. 'Platform User Data' is a Platform User's other-processor payment volume, transaction data and offline cash and check transactions shared with Stripe. 'Pre-Approved Responses' are Stripe-approved communications. A 'Prequalified Offer' is an offer to apply for financing. 'Program Data' is application, eligibility, Servicer, Transaction, credential, record and compliance data Stripe uses or generates for the Service.
Supporting quotations
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
“Data” used without a modifier means all Personal Data, Program Data, and Platform User Data.
“Financing Recipient” means a Prospect who has accepted a Prequalified Offer, has been approved by a Capital Provider, and has agreed to Financing Terms.
“Financing Terms” means a Stripe Capital Loan agreement or a Stripe Capital Advance agreement, in either case, among a Connected Account, a Capital Provider, and any other relevant parties.
“GDPR” means General Data Protection Regulation (EU) 2016/679.
“Marketing Materials” means the marketing materials developed for the purpose of promoting Stripe Capital Financing to select Platform Users and Connected Accounts, and Prequalified Offers to Prospects.
“Platform Services” means the products and services that Platform Users receive from a Stripe Connect Platform, regardless of whether fees are charged (e.g., web development, customer support or hosting services).
“Platform User” means, where User is acting as a Stripe Connect Platform, a user of User’s platform.
“Platform User Data” means a Platform User’s payment volume information from other payment processors, transaction data, and offline transactions that User shares with Stripe, including from cash and checks.
“Pre-Approved Responses” means the Stripe-approved communications used to respond to questions or reply to other communications.
“Prequalified Offer” means an offer to submit an application to receive Stripe Capital Financing.
“Program Data” means data associated with an application for Stripe Capital Financing, eligibility criteria, Servicers, Transactions, access credentials, records, regulatory compliance data, and any other information Stripe uses or generates to provide the Capital for Platforms Services to User.
Qualifications & exceptions
'Data' is the umbrella term for the three data categories the Section 4 restrictions and Stripe's use rights operate on.
Legal Rights & Agreement Rules · Context
Capital for Platforms definitions: Prospect, Servicer, Servicing, Stripe Capital Advance, Financing, Services and Loan
A 'Prospect' is a Platform User or Connected Account eligible for a Prequalified Offer. A 'Servicer' is an entity Stripe, a Capital Provider or a loan purchaser designates to manage a financing, including Stripe Servicing, Inc.; 'Servicing' is managing a financing after disbursement. A 'Stripe Capital Advance' is a merchant cash advance or receivables-purchase agreement from a Capital Provider. 'Stripe Capital Financing' is a Stripe Capital Loan, Stripe Capital Advance or other commercial financing. The 'Stripe Capital for Platforms Services' support joint marketing of financing to Platform Users, Connected Accounts and Prospects. A 'Stripe Capital Loan' is an installment loan, revolving or open-end credit or other business financing product, including a business-purpose loan originated by a Capital Provider. A 'Back to Top' link closes the section.
Supporting quotations
“Prospect” means a Platform User or Connected Account that is eligible for a Prequalified Offer.
“Servicer” means an entity or group of entities that Stripe, a Capital Provider, or a purchaser of a Stripe Capital Financing may designate to manage a Stripe Capital Financing, including Stripe Servicing, Inc. (and its Affiliates, as applicable), and any of their respective agents, assigns, subcontractors, or representatives.
“Servicing” means the management and administration of Stripe Capital Financing after funds have been disbursed to the Financing Recipient.
“Stripe Capital Advance” means a merchant cash advance agreement or a purchase of receivables agreement provided by a Capital Provider to a Prospect.
“Stripe Capital Financing” means a Stripe Capital Loan or Stripe Capital Advance, as applicable, or other form of commercial financing.
“Stripe Capital for Platforms Services” means the Services that Stripe provides to User in support of efforts between User and Stripe to market Stripe Capital Financing to Platform Users, Connected Accounts, and Prospects.
“Stripe Capital Loan” means an installment loan, revolving or open-end credit, or other business financing product, including a business-purpose loan originated by a Capital Provider.
Legal Rights & Agreement Rules · Context
The Climate Terms cover two products from two entities: Stripe, LLC’s Climate Commitment and Frontier’s Climate Orders
The Stripe Climate Terms, last modified November 18, 2025, supplement the General Terms and govern Stripe Climate Commitment and Stripe Climate Orders. Stripe Climate Commitment, a suite of features for running the User's own corporate climate program, is provided by Stripe, LLC, and for that product every reference to 'Stripe' in these terms and the General Terms means Stripe, LLC. Stripe Climate Orders, meaning the Retirement Services, the Climate API and Dashboard section, Frontier Marketing Collateral and related services, are provided by Stripe's Affiliate Frontier Climate Operations, LLC, and for that product 'Stripe' in the General Terms means Frontier.
Supporting quotations
Stripe Climate
Last modified: November 18, 2025
1. Stripe Climate.
Stripe, LLC provides Stripe Climate Commitment, and for the purposes of Stripe Climate Commitment, each reference to “Stripe” in these Stripe Climate Terms and in the General Terms will be read as a reference to Stripe, LLC. Frontier Climate Operations, LLC (“Frontier”), Stripe’s Affiliate, provides Stripe Climate Orders, and for the purposes of Stripe Climate Orders, each reference to "Stripe" in the General Terms will be read as a reference to Frontier.
“Stripe Climate Commitment” means a suite of features Stripe provides that are designed to enable User to create and run User’s own corporate climate program.
“Stripe Climate Orders” means (a) the Retirement Services offered to User; (b) access to the Climate API and the Climate Orders portion of the Stripe Dashboard; (c) access to the Frontier Marketing Collateral
Qualifications & exceptions
The contracting entity differs by product: Stripe, LLC for Climate Commitment, Frontier for Climate Orders.
Charges & Financial Obligations · User right or choice
Climate Commitment is opt-in and changeable any time; Stripe deducts the funds from your balance, non-refundable
A User who elects to contribute Climate Commitment Funds, the amount it voluntarily allocates as a revenue percentage, flat monthly sum or another method Stripe accepts, must opt in during Stripe Account onboarding or in the Dashboard, and may opt out, change or pause the contribution at any time there. Stripe or an Affiliate may deduct the funds from the User's Stripe Account balance or User Bank Account per Transaction or as an aggregated periodic amount, as the Dashboard describes. Stripe allocates all the funds to advancing carbon removal, such as buying CRUs or funding research and development. The funds are not refundable.
Supporting quotations
2. Stripe Climate Commitment.
2.1 Opting In and Out, and Changes.
If User elects to contribute Climate Commitment Funds, User must opt in to contributions via the Stripe Account onboarding process or the Stripe Dashboard. User may opt out of, change, or pause a contribution at any time in User's Stripe Dashboard.
2.2 Climate Commitment Funds.
Stripe or its Affiliate may deduct the Climate Commitment Funds from User's Stripe Account balance or User Bank Account on a per-Transaction basis, or as an amount aggregated over a period of time, as described in User's Stripe Dashboard. Stripe will allocate all Climate Commitment Funds to advance the field of carbon removal, through activities such as purchasing CRUs, or funding research and development for new carbon removal technologies. Climate Commitment Funds are not refundable.
“Climate Commitment Funds” means the amount User chooses to voluntarily allocate to Climate Projects through Stripe Climate Commitment, as a percentage of User’s revenue or a flat monthly amount, or another method of calculation Stripe accepts.
Qualifications & exceptions
Contributions are voluntary and can be stopped, changed or paused at any time.
Once deducted, Climate Commitment Funds are not refundable.
Charges & Financial Obligations · Company commitment
Stripe decides when and where to allocate your Climate funds, reports back, keeps none for overhead, promises no results
The goal of Climate Commitment is to advance carbon removal, and the funds are used for that goal. Stripe will use reasonable efforts to fund impactful Climate Projects, but the recipients are developing new technology in an evolving industry, their survival and success are not guaranteed, development timelines are long, impact may not be immediate, and the chosen technologies may fail to deliver any carbon removal or may take years to produce results. Stripe decides when to allocate the funds to Climate Projects, informs the User how they were allocated, and will not apply them to its own corporate or administrative costs.
Supporting quotations
The goal of Stripe Climate Commitment is to help advance the field of carbon removal, and Climate Commitment Funds will be used in support of that goal. While Stripe will use reasonable efforts to fund impactful Climate Projects, companies receiving Climate Commitment Funds are developing new technology in an evolving industry and their survival and success in addressing climate issues are not guaranteed. Development timelines of many new technologies are long, the resulting impact may not be immediate, and there is always a risk that the chosen technologies fail to deliver any carbon removal.
Stripe will determine when to allocate Climate Commitment Funds to Climate Projects, and Stripe will inform User about how Climate Commitment Funds were allocated. Stripe will not apply Climate Commitment Funds toward its own corporate or administrative costs.
Qualifications & exceptions
Stripe's commitment is 'reasonable efforts' to fund impactful projects, with express risk that no carbon removal results.
Allocation timing is at Stripe's discretion; reporting back is promised.
Not stated here
'Climate Projects' is a capitalized term defined in the definitions section, analyzed in the next packet.
Legal Rights & Agreement Rules · Restriction or exception
Climate Commitment buys no certified carbon credits, nothing authorized under the Paris Agreement, maybe not deductible
The carbon removal services Stripe purchases with Climate Commitment Funds are not certified by any governmental or non-governmental body and are not 'authorized' under Article 6 of the Paris Agreement (cited by name; its text is not supplied). Stripe disclaims all warranties about their status under any program or standard, now or in future, about any current or future tax credit, benefit or treatment, and about any other financial benefit. The funds may not be eligible for a tax deduction; the User should consult its tax or legal advisor, and the funds exclude all Taxes except where the Documentation says otherwise.
Supporting quotations
The carbon removal services Stripe purchases are not certified by any governmental or non-governmental body. They are not “authorized” under Article 6 of the Paris Agreement. Stripe disclaims all warranties regarding (i) the status under applicable governmental or non-governmental programs or pursuant to standards set by governmental or non-governmental bodies, whether implemented now or in the future, (ii) the availability of any current or future tax credit, benefit, or treatment, or (iii) any other financial benefits, associated with the carbon removal services that Stripe purchases.
The Climate Commitment Funds may not be eligible for a tax deduction. User should consult with its tax or legal advisor on the local tax treatment of Climate Commitment Funds. Climate Commitment Funds exclude all Taxes, except as the Documentation states to the contrary.
“Paris Agreement” means the Paris Agreement to the United Nations Framework Convention on Climate Change, U.N. Doc. FCCC/CP/2015/L.9/Rev/1 (Dec. 12, 2015).
Qualifications & exceptions
Contributions are not carbon credits and carry no certification or tax-treatment warranty.
Taxes are excluded from the contribution amount unless the Documentation says otherwise.
Not stated here
Local tax treatment depends on the User's jurisdiction and is not stated.
Account & Service Control · Restriction or exception
Climate Orders may be used only under these terms and never for personal, family or household purposes
The User must use Stripe Climate Orders in compliance with the terms that apply to them and must not use them for personal, family or household use.
Supporting quotations
3. Stripe Climate Orders.
3.1 User's Use of Stripe Climate Orders.
User must use Stripe Climate Orders in compliance with these terms for Stripe Climate Orders. User must not use the Stripe Climate Orders for personal, family, or household use.
Charges & Financial Obligations · Company practice
Frontier buys removal units under future offtakes; supply is not guaranteed and Frontier may substitute or ration
Frontier acquires Carbon Removal Units (CRUs), specified amounts of carbon dioxide removed from the atmosphere, through Offtake Agreements, binding contracts to buy future tons of removal if and when delivered, and will review their sources and governing terms to the extent commercially reasonable. Frontier makes Retirement Services (permanently retiring a CRU from carbon markets in the selected year) available for purchase subject to CRU availability, Frontier securing the rights for future delivery, and Frontier actually receiving the CRUs. The User may check availability and buy through the Climate API or Dashboard, but it is the User's responsibility to verify that the CRUs meet its needs or a Beneficiary's. Frontier may be unable to acquire enough CRUs; the CRUs retired may come from an offtake signed after the User's purchase; and Frontier may substitute one supplier's CRU for another's or allocate current inventory among Purchasers.
Supporting quotations
3.2 CRUs.
Frontier uses Offtake Agreements to acquire CRUs. To the extent commercially reasonable, Frontier will review (i) the sources of CRUs; and (ii) the terms governing the generation of those CRUs.
Frontier will make Retirement Services available to User for purchase subject to: (i) the availability of CRUs in carbon markets; (ii) Frontier’s ability to secure all necessary rights (including contractual rights) for the future delivery of the CRUs; and (iii) Frontier’s receipt of those CRUs. User may verify the availability of CRUs for Retirement, and purchase Retirement Services using the Climate API or the Stripe Dashboard. While Frontier will provide User with information about the CRUs available for Retirement, it is User's responsibility to verify that the CRUs meet User's needs or the needs of a Beneficiary.
Frontier may be unable to acquire sufficient quantities of CRUs to fulfill orders for Retirement Services. The CRU(s) that Frontier ultimately Retires on User's behalf may have been generated from an Offtake Agreement that Frontier executed after User's initial purchase. In order to provide Retirement Services, Frontier reserves the right to: (i) substitute CRUs from any one carbon removal supplier with a CRU from a different carbon removal supplier; or (ii) allocate then-current inventory of CRUs among Purchasers.
“Carbon Removal Unit,” or “CRU,” means a specified amount of carbon dioxide removed from the atmosphere that is acquired via Offtake Agreements. CRUs may be either a full or a partial ton.
“Offtake Agreement” means a legally binding contract to buy future tons of carbon dioxide removal at an agreed price if and when delivered.
“Retire” or “Retirement” means the permanent removal of a specified CRU from all applicable carbon markets. Retirement may be further governed by the rules of a Registry.
“Retirement Services” means all actions taken to Retire a CRU in the selected Retirement Year.
“Beneficiary” means a business entity (i.e., not a natural person) that is an intended beneficiary of a Retirement or Retirement Services.
Qualifications & exceptions
Retirement Services depend on availability, secured delivery rights and receipt of the CRUs.
Frontier may substitute suppliers and allocate limited inventory among buyers.
Not stated here
Timing of eventual Retirement relative to purchase is not fixed.
Legal Rights & Agreement Rules · Restriction or exception
Purchased removal units are not Paris-authorized; Frontier warrants nothing about status, tax treatment or benefits
The CRUs are not 'authorized' under Article 6 of the Paris Agreement. Frontier disclaims all warranties about the CRUs' status under any governmental or non-governmental program or standard, now or in future, about any current or future tax credit, benefit or treatment, and about any other financial benefit associated with buying Retirement Services or the CRUs.
Supporting quotations
The CRUs are not “authorized” under Article 6 of the Paris Agreement. Frontier disclaims all warranties regarding (i) the status of CRUs under applicable governmental or non-governmental programs or pursuant to standards set by governmental or non-governmental bodies, whether implemented now or in the future, (ii) the availability of any current or future tax credit, benefit, or treatment, or (iii) any other financial benefits, associated with User's purchase of Retirement Services or the associated CRU(s).
Qualifications & exceptions
Mirrors the Climate Commitment disclaimer, here for Frontier's Climate Orders.
Charges & Financial Obligations · Company commitment
By the end of your Retirement Year Frontier retires the unit or transfers title, records it, sends a certificate
On or before the last day of the Retirement Year the User selected, Frontier will Retire the CRU on the User's behalf or, if applicable, transfer title to the User. If the User designated a Beneficiary, Frontier retires on the Beneficiary's behalf and includes its name in the Registry (any carbon offset registry or system tracking retirements) where permitted, recording the retirement under that Registry's rules. Frontier may be unable or not permitted to retire and record partial tons, and may combine partial CRUs and record them in its own name. When Frontier retires a CRU for the User or a Beneficiary, it notifies the User through the Climate API, Dashboard or another elected means and delivers a digital certificate evidencing the Retirement.
Supporting quotations
3.3 Retirement.
On or before the last day of the Retirement Year, Frontier: (i) on User's behalf, will Retire the CRU; or (ii) if applicable, will transfer title to the CRU to User. If User has designated a Beneficiary, Frontier will Retire the CRU on that Beneficiary’s behalf and include the Beneficiary’s name in the Registry, if permitted. Frontier will Retire and record the CRU in the applicable Registry in accordance with and subject to the rules of that Registry.
Frontier may not be able to, or may not be permitted to, Retire and record partial CRUs (i.e., partial tons) with a Registry. Frontier may combine partial CRUs and record them in Frontier’s name.
If Frontier Retires a CRU on User's behalf or on behalf of a Beneficiary, Frontier will notify User of the Retirement via the Climate API, the Stripe Dashboard, or, if applicable, by other means User elects in the Stripe Dashboard, and deliver a certificate to User evidencing Retirement. Certificates will be digital.
“Retirement Year” means the year User selects, either via the Climate API or in the Stripe Dashboard, for a CRU to be Retired.
“Registry” means any carbon offset registry or system that tracks the Retirement of a CRU.
Qualifications & exceptions
Partial-ton CRUs may be combined and recorded in Frontier's name rather than the User's.
Beneficiary naming in the Registry happens only if the Registry permits.
Charges & Financial Obligations · Restriction or exception
If units run short or cannot be retired in your name, Frontier may ration, refund without interest, or retire itself
If Frontier does not receive enough CRUs to fulfill all orders, it may in its sole discretion allocate CRUs among Purchasers or refund the Fees. If it determines it cannot retire a CRU in the User's or Beneficiary's name by the end of the Retirement Year, it will notify the User and may, in its sole discretion, refund the Fees, transfer title to the CRU, record the retirement in Frontier's own name and certify that, or take other reasonable remedial measures. Neither Frontier nor Stripe pays interest on Fees, Frontier has no further obligation for that retirement or any additional retirements, and Frontier is not liable for other losses, damages or costs from its inability to perform. If Frontier cannot contact the User or cannot refund (for example because the Stripe Account is closed), it will contribute the amounts due to carbon removal programs of its choosing. Frontier uses commercially reasonable efforts to retire on the User's or Beneficiary's behalf but does not guarantee retirement on a Beneficiary's behalf.
Supporting quotations
In the event Frontier does not receive sufficient CRUs to fulfill all orders for Retirement Services, Frontier reserves the right, in its sole discretion, to: (i) allocate CRUs among Purchasers; or (ii) refund the Fees.
If Frontier determines that it is unable to Retire a CRU in User's name or in the Beneficiary’s name on or prior to the last day of the Retirement Year of the CRU, Frontier will notify User and, in its sole discretion, Frontier may: (i) refund the applicable Fees; (ii) transfer title to the CRU to User; (iii) record the Retirement of the CRU in Frontier’s name and provide certification to User that Frontier completed the Retirement in Frontier’s name; or (iv) take other reasonable remedial measures. Neither Frontier nor Stripe will pay User any interest on Fees, and Frontier will have no further obligation to User regarding that Retirement and the associated CRU(s) nor any other obligation to complete any additional Retirements. Frontier will not be liable to User for any other losses, damages, or costs that User or others may suffer arising out of or relating to Frontier’s inability to perform the Retirement Services or the associated CRU.
If Frontier is unable to contact User, or is unable to provide a refund of Fees, for any reason (e.g., User has closed its Stripe Account), Frontier will contribute any amounts due to User to carbon removal programs of Frontier’s choosing.
Frontier will use commercially reasonable efforts to ensure a CRU can be Retired on User's behalf or on behalf of User's designated Beneficiary. Frontier does not guarantee that Frontier will be able to Retire a CRU on behalf of a Beneficiary.
Qualifications & exceptions
The remedy on failure is Frontier's choice among refund, title transfer, retirement in its own name or other reasonable measures.
Unrefundable amounts are donated to carbon removal programs Frontier chooses, not held for the User.
Legal Rights & Agreement Rules · Permission or license
You may name a business Beneficiary, must tell it yourself, share none of its data, and give Frontier power of attorney
The User may designate a Beneficiary, a business entity (not a natural person) intended to benefit from a retirement, when buying Retirement Services. The User, not Frontier, must notify the Beneficiary of the retirement; these terms benefit only the parties and Frontier owes a Beneficiary nothing. The User must not give Frontier a Beneficiary's Personal Data. To the extent necessary, the User grants Frontier a power of attorney to act on its or a Beneficiary's behalf to provide Climate Orders, and represents and warrants throughout the Term that it has secured the rights and consents from Beneficiaries needed for Frontier to act for them.
Supporting quotations
3.4 Beneficiaries.
User may designate a Beneficiary when User purchases Retirement Services. User is responsible for notifying a Beneficiary of a CRU’s Retirement. Frontier will not notify a Beneficiary of a CRU’s Retirement. These Stripe Climate Terms are intended solely for the benefit of the parties to these Stripe Climate Terms. Frontier has no obligation to any Beneficiary under these Stripe Climate Terms. When User designates a Beneficiary, User will not provide Frontier with a Beneficiary’s Personal Data.
3.5 Power of Attorney.
To the extent necessary, User grants to Frontier a power of attorney to act on User's behalf or on behalf of a Beneficiary to provide Stripe Climate Orders. User represents as of the Effective Date and warrants during the Term that User has secured the necessary rights and consents from the applicable Beneficiaries to enable Frontier to act on behalf of the applicable Beneficiaries.
Qualifications & exceptions
Beneficiaries must be business entities, and Frontier has no obligation to them.
The power of attorney is granted 'to the extent necessary' and backed by the User's warranty of Beneficiary consents.
Account & Service Control · Company practice
Frontier may suspend or end your Climate Orders access at any time for any reason; it offers only retirement
Frontier may at any time or for any reason suspend or terminate the User's access to Stripe Climate Orders, including its ability to advertise or publicize any CRUs or Climate Orders. The User agrees that Frontier offers solely the Retirement of CRUs and is not a marketplace, dealer or seller of carbon removal units or offtakes. Beyond what these terms state, the Stripe Parties including Frontier make no representation or warranty about Climate Orders or any CRU, including a CRU's availability at any time or the validity of its generation.
Supporting quotations
3.6 Suspension and Termination.
Frontier may, at any time or for any reason, suspend or terminate User's access to Stripe Climate Orders, including User's ability to advertise or publicize any CRUs or Stripe Climate Orders.
3.7 Disclaimer.
User agrees that Frontier offers solely the Retirement of CRUs, and that Frontier is not acting as a marketplace, dealer, or seller of carbon removal units or offtakes. Other than as provided herein, the Stripe Parties (including Frontier) make no representation or warranty of any kind whatsoever for Stripe Climate Orders or a CRU, including the availability of a CRU at any given time or the validity of a CRU’s generation.
Qualifications & exceptions
Suspension or termination needs no reason and covers the User's publicity about CRUs.
Legal Rights & Agreement Rules · Context
The Climate Terms keep applying to purchased retirements until retired, transferred or refunded; definitions begin
These Climate Terms continue to apply to all Retirement Services bought before termination, and their CRUs, until Frontier retires the CRUs for the User or Beneficiary, transfers them to the User, or refunds some or all of the Fees under Section 3.3. The definitions section then begins: a 'Beneficiary' is a business entity, not a natural person, intended to benefit from a retirement; a 'Carbon Removal Unit' or 'CRU' is a specified amount of carbon dioxide removed from the atmosphere, acquired via Offtake Agreements, in full or partial tons.
Supporting quotations
4. Term.
These Stripe Climate Terms will apply to all Retirement Services purchased prior to termination and the associated CRUs until (a) Frontier Retires the relevant CRUs on User's behalf or User's Beneficiary’s behalf, (b) the relevant CRUs have been transferred to User, or (c) Frontier refunds some or all of the Fees for the Retirement Services in the manner described in Section 3.3 of these Terms.
5. Definitions.
“Beneficiary” means a business entity (i.e., not a natural person) that is an intended beneficiary of a Retirement or Retirement Services.
“Carbon Removal Unit,” or “CRU,” means a specified amount of carbon dioxide removed from the atmosphere that is acquired via Offtake Agreements. CRUs may be either a full or a partial ton.
Qualifications & exceptions
Survival is tied to the completion of each purchased retirement, not a fixed period.
The Climate Terms define their vocabulary. The 'Climate API' is the set of APIs, sample code and guidelines for selecting Retirement Services and CRUs. 'Climate Commitment Funds' are the amount the User voluntarily allocates to Climate Projects as a revenue percentage, flat monthly sum or another accepted method; a 'Climate Project' is simply a climate project Stripe funds. 'Frontier Marketing Collateral' promotes Stripe Climate Orders. An 'Offtake Agreement' is a binding contract to buy future tons of removal if and when delivered; the 'Paris Agreement' is the 2015 UNFCCC agreement, cited by document number. A 'Purchaser' is a user buying Retirement Services. A 'Registry' tracks CRU retirements. To 'Retire' is to permanently remove a CRU from all carbon markets; 'Retirement Services' are the actions to retire a CRU in the 'Retirement Year' the User selects. 'Stripe Climate Commitment' is Stripe's suite for running a corporate climate program, and 'Stripe Climate Orders' are the Retirement Services, Climate API and Dashboard access, Frontier Marketing Collateral and Frontier's related services, including the integration with Stripe's payment processing. A 'Back to Top' link closes the section.
Supporting quotations
“Climate API” means the APIs that facilitate User’s selection of Retirement Services and any associated CRUs, and the sample code, instructions, requirements, and other guidelines as described in the Documentation.
“Climate Commitment Funds” means the amount User chooses to voluntarily allocate to Climate Projects through Stripe Climate Commitment, as a percentage of User’s revenue or a flat monthly amount, or another method of calculation Stripe accepts.
“Climate Project” means a climate project that Stripe funds.
“Frontier Marketing Collateral” means the marketing and promotional materials and other ancillary documents developed for the purpose of promoting Stripe Climate Orders.
“Offtake Agreement” means a legally binding contract to buy future tons of carbon dioxide removal at an agreed price if and when delivered.
“Paris Agreement” means the Paris Agreement to the United Nations Framework Convention on Climate Change, U.N. Doc. FCCC/CP/2015/L.9/Rev/1 (Dec. 12, 2015).
“Purchaser” means a user that purchases Retirement Services.
“Registry” means any carbon offset registry or system that tracks the Retirement of a CRU.
“Retire” or “Retirement” means the permanent removal of a specified CRU from all applicable carbon markets. Retirement may be further governed by the rules of a Registry.
“Retirement Services” means all actions taken to Retire a CRU in the selected Retirement Year.
“Retirement Year” means the year User selects, either via the Climate API or in the Stripe Dashboard, for a CRU to be Retired.
“Stripe Climate Commitment” means a suite of features Stripe provides that are designed to enable User to create and run User’s own corporate climate program.
and (d) all other services provided by Frontier and its Affiliates to facilitate the purchase or the provision of, as applicable, the foregoing, including the integration with the payment processing services provided by Stripe.
Qualifications & exceptions
'Climate Project' is defined only as a project Stripe funds, leaving selection entirely to Stripe.
Legal Rights & Agreement Rules · Context
The Connect Terms govern platforms that let their users accept payments, stacked on four other sets of terms
The Stripe Connect Terms, last modified September 28, 2026, supplement the General Terms and incorporate the Stripe Financial Services Terms, Stripe Connect Infrastructure Terms and Stripe Payments Terms by reference; together they govern use of the Stripe Connect Services as a Stripe Connect Platform. Regional Terms in Section 9 apply by the User's Stripe Account Country. Undefined terms come from the General, Financial Services, Connect Infrastructure or Payments Terms. The User may use the Connect Services under these terms to enable itself or its Connected Accounts to use the Stripe Payments Services alongside the User's Platform Services, the products and services Platform Users receive from the platform.
Supporting quotations
Stripe Connect—Platform
Last modified: September 28, 2026
1. Stripe Connect Services.
These terms (“Stripe Connect Terms”) supplement the General Terms and, together with the Stripe Financial Services Terms, the Stripe Connect Infrastructure Terms and the Stripe Payments Terms, each of which are incorporated into these Stripe Connect Terms by this reference, govern the use of the Stripe Connect Services as a Stripe Connect Platform. The Regional Terms in Section 9 (Regional Terms) of these Stripe Connect Terms apply based on User’s Stripe Account Country.
User may use the Stripe Connect Services in accordance with these Stripe Connect Terms to enable User or User’s Connected Accounts to use the Stripe Payments Services in conjunction with User’s Platform Services.
“Platform Services” means the products and services that Platform Users receive from a Stripe Connect Platform, regardless of whether fees are charged (e.g., web development, customer support or hosting services).
“Connected Account Agreement” means the agreement with Stripe that applies to Connected Accounts (except Payout Recipients), which is accessible on the Stripe Legal Page for the Connected Account's jurisdiction.
Qualifications & exceptions
These terms address the platform side; Connected Accounts are bound by the separate Connected Account Agreement.
Not stated here
The Connected Account Agreement is on the Stripe Legal Page and not supplied.
Account & Service Control · User right or choice
You may enroll each Platform User as a Connected Account, with Stripe Managed Risk (Stripe bears merchant losses) or not
The User may enroll each Platform User (a user of its platform) as a Connected Account as the Documentation describes. It may enroll Connected Accounts as SMR Connected Accounts, on which Stripe provides Stripe Managed Risk Services and so assumes liability for Merchant Losses with accompanying risk support, or as Non-SMR Connected Accounts, where it does not.
Supporting quotations
2. Connected Account Types and Risk.
2.1 Platform Account Options.
User may elect to enroll each Platform User as a Connected Account as described in the Documentation.
2.2 Stripe Managed Risk Services.
User may enroll its Connected Accounts as SMR Connected Accounts or Non-SMR Connected Accounts, in accordance with these Stripe Connect Terms.
“SMR Connected Account” means a Connected Account on which Stripe is providing Stripe Managed Risk Services.
“Non-SMR Connected Account” means a Connected Account on which Stripe is not providing Stripe Managed Risk Services.
“Stripe Managed Risk Services” means the Services that enable Stripe to assume liability for Merchant Losses as described in the Stripe Connect Terms, and perform accompanying risk-related support services.
“Platform User” means, where User is acting as a Stripe Connect Platform, a user of User’s platform.
Qualifications & exceptions
The choice between SMR and Non-SMR enrollment determines who bears Merchant Losses.
Account & Service Control · Restriction or exception
With Stripe Managed Risk, all your Connected Accounts must be on it, you use the required tools, and Radar stays on
When using Stripe Managed Risk Services, all of the User's Connected Accounts must be SMR Connected Accounts, except as Stripe approves in a signed writing or the Documentation permits, while transitioning pre-existing Platform Users from Non-SMR to SMR within a reasonable time per the Documentation, or while transitioning them from SMR to Non-SMR during the SMR Transition Period. The User must use all Stripe Technology Stripe requires for the service, such as Stripe-Hosted Onboarding, the Stripe-hosted web form and tools for collecting Platform User onboarding information. Stripe enables Radar on all SMR Connected Accounts by default and the User must not disable it.
Supporting quotations
2.3 Requirements for Using Stripe Managed Risk Services.
When using Stripe Managed Risk Services, all User’s Connected Accounts must be SMR Connected Accounts, except (i) as Stripe expressly approves in writing signed by the parties or as is otherwise permitted in the Documentation; (ii) when User is transitioning pre-existing Platform Users from Non-SMR Connected Accounts to SMR Connected Accounts, which User must do within a reasonable time period and in accordance with the Documentation; and (iii) when User is transitioning pre-existing Platform Users from SMR Connected Accounts to Non-SMR Connected Accounts during the SMR Transition Period.
User must use all applicable Stripe Technology that Stripe requires for using Stripe Managed Risk Services as described in the Documentation (e.g., Stripe-Hosted Onboarding). Stripe will enable Stripe Radar Services on all SMR Connected Accounts by default, and User must not disable these Services.
“Stripe-Hosted Onboarding” means the web form and set of onboarding tools hosted by Stripe used to collect onboarding information relating to Platform Users as described in the Documentation.
Qualifications & exceptions
Mixed SMR and Non-SMR portfolios are allowed only with Stripe's signed approval, Documentation permission, or during transitions.
Radar cannot be turned off on SMR Connected Accounts.
Charges & Financial Obligations · Procedure
To leave Stripe Managed Risk, stop using Connect for those accounts or migrate all volume; SMR fees keep applying
To transition off Stripe Managed Risk Services, the User must either permanently stop using the Connect Services for all SMR Connected Accounts or migrate all payments volume from SMR to Non-SMR Connected Accounts within a reasonable time. Stripe Managed Risk Services Fees continue to apply to all Transactions on SMR Connected Accounts during and after the SMR Transition Period, which runs from the first Transaction for a transitioning Platform User on a Non-SMR account until every transitioning user has transacted on their new account or all SMR accounts are closed, whichever is earlier.
Supporting quotations
2.4 Transitioning Off Stripe Managed Risk Services.
To transition off Stripe Managed Risk Services, User must either permanently stop using Stripe Connect Services with respect to all SMR Connected Accounts, or migrate all payments volume from SMR Connected Accounts to Non-SMR Connected Accounts within a reasonable time period. Stripe Managed Risk Services Fees will continue to apply for all Transactions on SMR Connected Accounts during and after the SMR Transition Period.
“SMR Transition Period” means the period starting when a Transaction is first initiated for any transitioning Platform User on a Non-SMR Connected Account until the earlier of when (i) a Transaction has been initiated for every Platform User on the Non-SMR Connected Account to which they are transitioning; and (ii) all SMR Connected Accounts are closed.
Qualifications & exceptions
SMR Fees continue on SMR Connected Account Transactions both during and after the transition period.
Not stated here
What counts as a reasonable migration period is not defined.
Charges & Financial Obligations · Restriction or exception
Once a Platform User starts transacting off Managed Risk, you and that user are jointly liable for its merchant losses
When a Platform User transitions to Non-SMR Connected Accounts, the User and that Platform User become jointly and severally liable to Stripe for all Merchant Losses (negative balances from Transactions, Disputes, Refunds and Reversals where the Connected Account is the settlement merchant) on all SMR Connected Accounts tied to that Platform User, from the moment a Transaction is first initiated for it on a Non-SMR account. Stripe may collect these amounts under the Agreement and the Connected Account Agreement. To the maximum extent Law permits, Stripe's aggregate liability for Merchant Losses on SMR accounts during the SMR Transition Period is capped at the Section 8.4 liability cap of the General Terms, and its liability ends when the Transition Period ends.
Supporting quotations
2.5 Liability for Merchant Losses During the SMR Transition Period.
In relation to a Platform User transitioning to using one or more Non-SMR Connected Accounts, User and the relevant Platform User become jointly and severally liable to Stripe for all Merchant Losses on all SMR Connected Accounts associated with that Platform User from when a Transaction is first initiated for that Platform User on a Non-SMR Connected Account. Stripe may collect these amounts (including Merchant Losses) according to the Agreement and the Connected Account Agreement, as applicable. To the maximum extent permitted by Law, Stripe’s aggregate liability for Merchant Losses on all SMR Connected Accounts during the SMR Transition Period will not exceed the amount of the cap stated in Section 8.4 (Liability Cap) of the General Terms. Stripe’s liability for Merchant Losses on SMR Connected Accounts ends at the end of the SMR Transition Period.
“Merchant Losses” means negative amounts on a Connected Account’s Stripe account balance resulting from Transactions, Disputes, Refunds, and Reversals where the Connected Account is the settlement merchant.
Qualifications & exceptions
Joint and several liability starts with the first Non-SMR Transaction for that Platform User.
Stripe's own exposure during the transition is capped by the General Terms' Section 8.4 cap, not supplied.
Not stated here
The amount of the Section 8.4 cap is in the General Terms, not supplied.
Charges & Financial Obligations · Restriction or exception
You answer to Stripe for all Connected Account activity, jointly with them, except SMR losses and Stripe’s own fault
As between the User and Stripe, the User is responsible for all Activity on its Connected Accounts whether or not it initiated it. It is liable to Stripe for all Transactions, Disputes, Refunds, Reversals and resulting Merchant Losses (except on SMR Connected Accounts to the extent Section 3.2 provides) and for other losses, damages and costs from use of the Services, including fines from Financial Providers or Governmental Authorities, except to the extent they arise from Stripe's breach, negligence, willful misconduct or fraud. The User remains jointly and severally liable with the Connected Accounts, and Stripe may collect from the User under the Agreement. If Stripe decides the User's responsibility for a Connected Account's Activity creates unacceptable risk, it may use the Section 5.5 remedies of the Payments Terms.
Supporting quotations
3. Liability for Connected Accounts.
3.1 Liability for all Connected Accounts.
As between User and Stripe, User is responsible for all Activity on its Connected Accounts, whether initiated by User or not. User is liable to Stripe for all: (a) Transactions, Disputes, Refunds, Reversals and resulting Merchant Losses (except with respect to SMR Connected Accounts to the extent stated in Section 3.2) and (b) other losses, damages, and costs that result from use of the Services, including any fines assessed by Financial Providers or Governmental Authorities, except to the extent the losses, damages, or costs arise from Stripe’s breach of this Agreement or Stripe’s negligence, willful misconduct, or fraud.
User remains jointly and severally liable with the applicable Connected Accounts to Stripe for these amounts, and Stripe may collect these amounts from User in accordance with the Agreement. Without limiting Stripe’s other rights and remedies in this Agreement, if Stripe determines that User’s responsibility for Activity on any Connected Account creates an unacceptable risk to Stripe, Stripe may exercise its remedies listed in Section 5.5 of the Stripe Payments Terms.
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
Qualifications & exceptions
Two carve-outs: SMR Connected Account losses under Section 3.2, and losses from Stripe's own breach, negligence, willful misconduct or fraud.
Stripe may invoke the Payments Terms Section 5.5 remedies (reversals, payout holds, reserves, suspension) on a risk finding.
Charges & Financial Obligations · Company commitment
On Managed Risk accounts Stripe bears merchant losses up to any agreed cap, except transition losses and your fault
Subject to the general liability rule in Section 3.1, as between the User and Stripe, Stripe is liable for Merchant Losses on SMR Connected Accounts up to the SMR Risk Cap, if the parties have agreed one in writing. Two exceptions apply: the SMR Transition Period rule in Section 2.5, and losses that arise from the User's fraud, violation of Law, breach of the Agreement including these Connect Terms, negligence, willful misconduct or misuse of the Connect Services. The General Terms' Section 8 limitations on liability do not apply to Stripe's liability for Merchant Losses under this clause.
Supporting quotations
Subject to Section 3.1, as between User and Stripe, Stripe is liable for Merchant Losses on SMR Connected Accounts up to the amount of the SMR Risk Cap (if any), except: (a) as stated in Section 2.5 of these Stripe Connect Terms; and (b) to the extent these Merchant Losses arise from User’s fraud, violation of Law, breach of the Agreement (including these Stripe Connect Terms), negligence, willful misconduct, or misuse of the Stripe Connect Services. The limitations on liability in Section 8 of the General Terms will not apply with respect to Stripe’s liability for Merchant Losses under this Section 3.2.
“SMR Risk Cap” means Stripe’s maximum liability for Merchant Losses, if agreed by the parties in writing.
Qualifications & exceptions
Stripe's liability is capped only if an SMR Risk Cap was agreed in writing ('if any').
Losses caused by the User's own fraud, unlawful conduct, breach, negligence, misconduct or misuse revert to the User.
Not stated here
Whether a particular User has an agreed SMR Risk Cap, and its amount, is outside this document.
Charges & Financial Obligations · Restriction or exception
You, not Stripe, file tax information reports like 1099s unless Law requires Stripe to; you indemnify for your failures
Unless Stripe notifies the User otherwise, Stripe will not file any Tax Information Reports (required tax information returns such as IRS Form 1099) and the User assumes sole responsibility and liability for filing all such reports required because of Services Stripe provides to the User or to its Connected Accounts; however, where Law requires, Stripe files them as the Documentation outlines. The User indemnifies Stripe for all Taxes and related interest, penalties and fees (other than income, franchise or similar taxes on the Fees) imposed on a Stripe Entity because the User failed to file a report on time. Stripe issues any Tax Information Reports to the User only, except that when Stripe itself files under Section 4.1 it issues them directly to the Connected Accounts.
Supporting quotations
4. Tax Reporting; Tax Invoicing.
4.1 Filing of Tax Information Reports.
Unless Stripe notifies User otherwise, Stripe will not file any, and User assumes sole responsibility and liability for filing all Tax Information Reports required to be filed as a result of Services Stripe provides to User under this Agreement or to Connected Accounts under their Connected Account Agreement. Notwithstanding the prior sentence, to the extent required by Law, Stripe will file Tax Information Reports as outlined in the Documentation.
4.2 Indemnity.
User will indemnify Stripe from all Taxes, and related interest, penalties and fees (excluding any income, franchise or similar taxes payable with respect to the Fees), if any, imposed on a Stripe Entity as a result of User’s failure to timely file any Tax Information Report under Section 4.1 of these Stripe Connect Terms.
4.3 Issuing Tax Forms.
Stripe will issue Tax Information Reports (if applicable) directly to User only. Notwithstanding the prior sentence, when Stripe files Tax Information Reports as stated in Section 4.1, Stripe will issue Tax Information Reports (if applicable) directly to the Connected Accounts.
“Tax Information Report” means a required tax information return or report, including IRS Form 1099, or any other similar form.
Qualifications & exceptions
Stripe's filing duty is limited to what Law requires, as outlined in the Documentation.
The indemnity excludes Stripe's own income, franchise or similar taxes on the Fees.
Not stated here
Which jurisdictions' Law requires Stripe to file is in the Documentation, not supplied.
Charges & Financial Obligations · Company practice
With Platform Pricing Control Stripe invoices you and you resupply to the account; otherwise Stripe invoices the account
Unless the Documentation says otherwise, for Transactions on Connected Accounts with Platform Pricing Control (the attribute letting the User set the fees that apply to the account), Stripe treats itself as providing Services to the User, issues Tax invoices to the User only, and treats the User as making separate supplies to its Connected Accounts for this purpose. For Transactions on Connected Accounts without Platform Pricing Control, Stripe provides its Services to the Connected Accounts and issues Tax invoices to them only.
Supporting quotations
4.4 Tax Invoices.
Unless otherwise described in the Documentation, for each Transaction on Connected Accounts with Platform Pricing Control, Stripe is providing its Services to User and will issue Tax invoices directly to User only, and User will be treated as making separate supplies to its Connected Accounts for purposes of this Section.
Unless otherwise described in the Documentation, for each Transaction on Connected Accounts without Platform Pricing Control, Stripe is providing its Services to the Connected Accounts and will issue Tax invoices directly to the Connected Accounts only.
“Platform Pricing Control” means the Connected Account attribute that enables User to determine, to the extent stated in the Documentation, the fees that apply with respect to the Connected Account.
Qualifications & exceptions
The Documentation can override either arrangement.
With Platform Pricing Control the User is treated as a reseller making separate supplies to its Connected Accounts for tax invoicing.
Account & Service Control · Procedure
For Singapore sole-proprietor or receipt-requesting accounts without a Dashboard, deliver receipts and keep records
Section 5 applies only to Relevant SG Connected Accounts: Singapore-based Connected Accounts without Stripe Dashboard access that are sole proprietors or, if not, that request a receipt. For them the User must deliver receipts containing the Receipt Requirements (transaction date, total amount including service fees and any exchange rate, and a unique reference number) within a reasonable time, keep retrievable, examinable delivery records, and give them to Stripe within 5 business days of a reasonable request. If Stripe believes the User's process does not meet the Receipt Requirements, the User must change it as Stripe requires.
Supporting quotations
5. Connected Accounts in Singapore.
This Section 5 only applies to Relevant SG Connected Accounts.
User must: (a) deliver receipts containing the Receipt Requirements to Relevant SG Connected Accounts within a reasonable time period; (b) maintain records of delivery in a retrievable and examinable format, and (c) at Stripe’s reasonable request, provide those records to Stripe within 5 business days of Stripe’s request. If Stripe believes that User’s existing process does not satisfy the Receipt Requirements, then, on Stripe’s request, User must modify that process as Stripe requires.
“Relevant SG Connected Accounts” means Connected Accounts based in Singapore that do not have access to a Stripe Dashboard and: (a) are sole proprietors; or (b) for Connected Accounts that are not sole proprietors, request a receipt from User.
“Receipt Requirements” means, for each Transaction on a Relevant SG Connected Account, the following information: (a) the date of the Transaction; (b) the total amount of the Transaction, including any service fees and relevant foreign exchange rates that apply to the Transaction; and (c) a unique reference number for the Transaction.
Qualifications & exceptions
Applies only to Relevant SG Connected Accounts.
Records must be produced within 5 business days of Stripe's reasonable request.
Legal Rights & Agreement Rules · Context
Terms applied to a Connected Account are read from its side; Connected Accounts cannot claim as third parties
Where these terms apply a defined term to a Connected Account rather than the User, the definition is read as referring to the Connected Account; for example, 'Services' applied to a Connected Account means the Stripe services available to it under the Connected Account Agreement, and 'Disputes' means the Disputes that account incurs. Connected Accounts are not third parties for the purposes of, and are not eligible to make a Claim under, Section 9 of the General Terms.
Supporting quotations
6. Definitions Applied to Connected Accounts; General Terms Clarification.
Where defined terms are applied to a Connected Account (rather than User) in these terms, the relevant definition will be deemed to reference the Connected Account (e.g., when the term Services is applied to a Connected Account it means the Stripe services that Stripe makes available to the Connected Account under the Connected Account Agreement, and when the term Disputes is applied to a Connected Account it means Disputes that Connected Account incurs). Connected Accounts are not third parties for the purposes of, or eligible to make a Claim under, Section 9 of the General Terms.
Qualifications & exceptions
Section 9 of the General Terms is not supplied; this clause removes Connected Accounts from whatever third-party rights it gives.
Charges & Financial Obligations · Restriction or exception
Your liability for your Connected Accounts has no cap or exclusion in the Agreement, except what Managed Risk covers
Except to the extent Stripe Managed Risk Services cover it where applicable, the User's liability for all Connected Accounts under these Connect Terms is not limited or excluded in any way, notwithstanding anything to the contrary in the Agreement. The General Terms' liability caps therefore do not protect the platform for Connected Account liabilities.
Supporting quotations
7. Liability Cap.
Except to the extent covered by Stripe Managed Risk Services if applicable, User’s liability for all Connected Accounts as described in these Stripe Connect Terms, is not limited or excluded in any way, notwithstanding anything to the contrary in this Agreement.
Qualifications & exceptions
The only carve-out is liability covered by Stripe Managed Risk Services.
Legal Rights & Agreement Rules · Context
Connect definitions: Connected Account and Agreement, Dispute, Merchant Losses, Non-SMR, Pricing Control, Platform User
Section 8 begins the definitions. A 'Connected Account' is a Platform User onboarded to the platform via Connect, or a Payout Recipient. The 'Connected Account Agreement' is the account's own agreement with Stripe on the Stripe Legal Page for its jurisdiction. A 'Dispute' is a Customer-initiated reversal including chargebacks. 'Merchant Losses' are negative balances from Transactions, Disputes, Refunds and Reversals where the Connected Account is the settlement merchant. A 'Non-SMR Connected Account' lacks Stripe Managed Risk Services. 'Platform Pricing Control' lets the User set the account's fees as the Documentation allows. 'Platform Services' are what Platform Users receive from the platform, paid or not, and a 'Platform User' is a user of the User's platform. The definitions continue in the next packet.
Supporting quotations
8. Definitions.
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
“Connected Account Agreement” means the agreement with Stripe that applies to Connected Accounts (except Payout Recipients), which is accessible on the Stripe Legal Page for the Connected Account's jurisdiction.
“Dispute” means an instruction a Customer initiates to reverse or invalidate a processed Transaction (including “chargebacks” and “disputes” as those terms may be used by Payment Method Providers).
“Merchant Losses” means negative amounts on a Connected Account’s Stripe account balance resulting from Transactions, Disputes, Refunds, and Reversals where the Connected Account is the settlement merchant.
“Non-SMR Connected Account” means a Connected Account on which Stripe is not providing Stripe Managed Risk Services.
“Platform Pricing Control” means the Connected Account attribute that enables User to determine, to the extent stated in the Documentation, the fees that apply with respect to the Connected Account.
“Platform Services” means the products and services that Platform Users receive from a Stripe Connect Platform, regardless of whether fees are charged (e.g., web development, customer support or hosting services).
“Platform User” means, where User is acting as a Stripe Connect Platform, a user of User’s platform.
The remaining Connect definitions: 'Receipt Requirements' are the date, total amount including fees and exchange rates, and unique reference for each Transaction on a Relevant SG Connected Account. 'Refund' and 'Reversal' carry their Payments Terms meanings. 'Relevant SG Connected Accounts' are Singapore accounts without Dashboard access that are sole proprietors or request receipts. An 'SMR Connected Account' has Stripe Managed Risk Services; the 'SMR Risk Cap' is Stripe's maximum Merchant Loss liability if agreed in writing; the 'SMR Transition Period' runs from the first Non-SMR Transaction for a transitioning user until all have transitioned or all SMR accounts close. 'Stripe-Hosted Onboarding' is Stripe's hosted onboarding form and tools. 'Stripe Managed Risk Services' let Stripe assume Merchant Loss liability with risk support. A 'Tax Information Report' is a required tax return such as IRS Form 1099.
Supporting quotations
“Receipt Requirements” means, for each Transaction on a Relevant SG Connected Account, the following information: (a) the date of the Transaction; (b) the total amount of the Transaction, including any service fees and relevant foreign exchange rates that apply to the Transaction; and (c) a unique reference number for the Transaction.
“Refund” means an instruction User initiates to provide a full or partial return of funds to a Customer for a processed Transaction.
“Relevant SG Connected Accounts” means Connected Accounts based in Singapore that do not have access to a Stripe Dashboard and: (a) are sole proprietors; or (b) for Connected Accounts that are not sole proprietors, request a receipt from User.
“Reversal” means the reversal of the settlement of funds for a Transaction.
“SMR Connected Account” means a Connected Account on which Stripe is providing Stripe Managed Risk Services.
“SMR Risk Cap” means Stripe’s maximum liability for Merchant Losses, if agreed by the parties in writing.
“SMR Transition Period” means the period starting when a Transaction is first initiated for any transitioning Platform User on a Non-SMR Connected Account until the earlier of when (i) a Transaction has been initiated for every Platform User on the Non-SMR Connected Account to which they are transitioning; and (ii) all SMR Connected Accounts are closed.
“Stripe-Hosted Onboarding” means the web form and set of onboarding tools hosted by Stripe used to collect onboarding information relating to Platform Users as described in the Documentation.
“Stripe Managed Risk Services” means the Services that enable Stripe to assume liability for Merchant Losses as described in the Stripe Connect Terms, and perform accompanying risk-related support services.
“Tax Information Report” means a required tax information return or report, including IRS Form 1099, or any other similar form.
Legal Rights & Agreement Rules · Restriction or exception
The Connect Regional Terms apply by country and override the Connect Terms where they conflict
Section 9 sets out Regional Terms for listed countries and regions. Where a Regional Term conflicts with the Stripe Connect Terms, the Regional Term prevails. Which apply depends on the User's Stripe Account Country, as Section 1 states.
Supporting quotations
9. Regional Terms.
The following Regional Terms apply for the countries or regions below. If there is a conflict between the Stripe Connect Terms and the Regional Terms, the Regional Terms prevail.
Qualifications & exceptions
Regional Terms prevail only to the extent of a conflict.
Account & Service Control · Procedure
United States: Payout Recipients are paid for you, have no Stripe contract, and need enrollment and the Recipient Notice
For Users in the United States, Stripe may enable payouts to Payout Recipients, third parties to whom Stripe lets the User pay out via Connect. Stripe provides no service directly to them, they have no contractual or business relationship with Stripe, and Stripe pays them on the User's behalf. They sign no Connected Account Agreement, and that concept does not apply to Payout Recipient Connected Accounts. The User must complete a Stripe account application for each Payout Recipient and enroll them as a Connected Account, each subject to Stripe's approval, and must ensure each receives the Stripe Recipient Notice (jurisdiction-specific information in the Documentation) before the first payout. Making payouts to Payout Recipients is a use of the Stripe Payments Services.
Supporting quotations
United States.
The following Regional Terms apply for Users in the United States.
9.1 Payout Recipients.
Stripe may enable User to make payouts to Payout Recipients. For the purpose of these payouts, Stripe does not provide any service directly to the Payout Recipients, and the Payout Recipients do not have a contractual or business relationship with Stripe. To the extent Stripe makes payouts to Payout Recipients, it does so on User’s behalf. To receive these payouts, Payout Recipients will not enter into a Connected Account Agreement, and that concept, as used in these Stripe Connect Terms, will not apply to Connected Accounts that are Payout Recipients.
User must complete a Stripe account application for each Payout Recipient and enroll them as a Connected Account. Each Payout Recipient is subject to Stripe’s approval. User must ensure that each Payout Recipient receives the Stripe Recipient Notice before User makes a payout to the Payout Recipient.
By making payouts to Payout Recipients, User is using Stripe Payments Services.
“Payout Recipient” means a third-party recipient to which Stripe enables User to make payouts via the Stripe Connect Services.
Qualifications & exceptions
Applies to Users in the United States.
Each Payout Recipient is subject to Stripe's approval and must receive the Stripe Recipient Notice before any payout.
Not stated here
The Stripe Recipient Notice is in the Documentation, not supplied.
Charges & Financial Obligations · Restriction or exception
Brazil: while you hold Connected Account funds through Connect you may not create liens over the related receivables
For Users in Brazil, if and as long as the User holds any Connected Account funds as part of its use of the Connect Services, it may not negotiate or create any liens or burdens over the related receivables of those funds.
Supporting quotations
Brazil.
The following Regional Terms apply for Users in Brazil.
9.1 No Liens or Burdens over Receivables related to Connected Accounts’ Funds.
If and as long as User holds any Connected Accounts funds as part of User’s use of Stripe Connect Services, User may not negotiate or create any liens or burdens over related receivables of those funds.
Qualifications & exceptions
Applies to Users in Brazil while they hold Connected Account funds.
Security & Safeguards · Procedure
France: you must load Stripe's stripe.js library on every payment page and use it to tokenize card details
For Users in France, the User must load the stripe.js JavaScript library from https://js.stripe.com/v2/ or https://js.stripe.com/v3/ on all pages where customers and donors interact when paying the User or its Connected Accounts, and must use stripe.js to tokenise Payment Method Account Details.
Supporting quotations
France.
The following Regional Terms apply for Users in France.
9.1 Use of Stripe.js.
User will load the stripe.js JavaScript library from https://js.stripe.com/v2/ or https://js.stripe.com/v3/ on all pages with which customers and donors interact when making payments to User or Connected Accounts. User must also use the stripe.js JavaScript library to tokenise Payment Method Account Details.
Qualifications & exceptions
Applies to Users in France.
Covers payments to the User and to its Connected Accounts, including donor pages.
Charges & Financial Obligations · Restriction or exception
India: you handle section 194-O withholding on Connected Account payments and take no payments for non-onboarded sellers
For Users in India, the User agrees that, in connection with section 194-O of the Income Tax Act, 1961 together with CBDT Circular No.17/2020 (external law cited by name, not supplied), it will assess, deduct, deposit and report withholding Taxes to the appropriate taxing authority on any amount paid or credited to Connected Accounts. The User must also ensure it does not accept payments through the Services for a seller not onboarded to its platform.
Supporting quotations
India.
9.1 Additional Tax Requirements.
User agrees that in connection with section 194-O of the Income Tax Act, 1961 (together with Circular No.17/2020 issued by Central Board of Direct Taxes), User will assess, deduct, deposit and report withholding Taxes to the appropriate taxing authority on any amount paid or credited to Connected Accounts.
9.2 User’s Connected Accounts.
User must ensure that it does not accept payments, through the Services, for a seller not onboarded to its platform.
Qualifications & exceptions
Applies to Users in India.
The statutory references are to external Indian tax law; their text is not part of this document.
Charges & Financial Obligations · Permission or license
Japan: you pass to Stripe the payment authority your Connected Accounts gave you; customers released once Stripe is paid
For Users in Japan, the User delegates to Stripe the authority each Connected Account granted it under the applicable Platform Provider Agreement (the User's agreements with that Connected Account) to process and receive payments. Once Stripe receives a Connected Account's Customer's funds for a Transaction, that customer is released from payment obligations to the Connected Account, whether or not Stripe or the User pays the Connected Account an equivalent amount. A Connected Account's Customer is a purchaser of the Connected Account's goods or services.
Supporting quotations
Japan.
The following Regional Terms apply for Users in Japan.
9.1 Delegating Authority for Connected Accounts.
User delegates to Stripe the authority that each Connected Account grants User under the applicable Platform Provider Agreement to process and receive payments. Once Stripe receives funds from a Connected Account’s Customer for a Transaction, that customer is released from payment obligations owed to the Connected Account, regardless of whether Stripe or User pays the Connected Account an equivalent amount. “Connected Account’s Customer” means a purchaser of goods or services provided by a Connected Account.
“Platform Provider Agreement” means, as to each Connected Account, collectively, the agreements that a Stripe Connect Platform has with that Connected Account.
Qualifications & exceptions
Applies to Users in Japan.
Customer release on Stripe's receipt does not depend on onward payment to the Connected Account.
Charges & Financial Obligations · Restriction or exception
Japan: top up a Connected Account only after a linked transaction, never in advance, and only up to the amount owed
For Users in Japan, when a Connected Account accepts a Connect Transaction (a transaction from the Connected Account's Customer in connection with the Platform Services), the User may conduct a Top-Up, a transfer into its Stripe Account to cover part of the Top-Up Amount, as the Documentation prescribes. This includes cases where the User uses a third-party payment provider or extends a promotional discount or coupon to the Connected Account's Customer. The Top-Up must be directly linked to a Connect Transaction, occur after that transaction has been processed (no pre-funding in anticipation of future transactions), and not exceed the Top-Up Amount, the sum the User or the customer owes the Connected Account after deducting fees and amounts payable to the User. On receipt of a Top-Up in the Connected Account's Stripe Account, the customer or the User is released from payment obligations to the Connected Account to that amount.
Supporting quotations
When a Connected Account accepts a Connect Transaction, User may conduct a Top-Up in the manner prescribed in the Documentation. In these cases (including where User uses a third-party payment services provider or where User wishes to extend a promotional discount or coupon to the Connected Account’s Customer), User must ensure that the Top-Up: (i) is directly linked to a Connect Transaction, (ii) occurs after the Connect Transaction has been processed (i.e., User may not pre-fund a Top-Up in anticipation of future Connect Transactions) and (iii) does not exceed the Top-Up Amount for each Connected Account.
“Connect Transaction” means a transaction from a Connected Account’s Customer in connection with the Platform Services. “Top-Up” means a transfer of funds into User’s Stripe Account to cover a portion of the Top-Up Amount. “Top-Up Amount” means the amount owed by User or the Connected Account’s Customer to the Connected Account (after deducting any fees or other amounts payable to User).
Qualifications & exceptions
Applies to Users in Japan.
Three conditions: linked to a Connect Transaction, after processing, and within the Top-Up Amount.
Charges & Financial Obligations · Restriction or exception
Japan: hold Connect Transaction funds in your account only as long as needed for authorization, delivery or refunds
For Users in Japan, the User may retain funds from a Connect Transaction in its Stripe Account only for as long as required to ensure the transaction is authorized and prevent unlawful or unauthorized transactions, to ensure the Connected Account delivers the goods or services owed to its customer before or upon receiving payment, or to facilitate Refunds or Disputes. A 'Back to Top' link closes the Connect Terms.
Supporting quotations
9.3 Restrictions on Retention Periods.
User may only retain funds received from a Connect Transaction in User’s Stripe Account for as long as required: (i) to ensure the Connect Transaction is authorized and prevent unlawful or unauthorized Connect Transactions; (ii) to ensure the Connected Account delivers the goods or services owed to the Connected Account’s Customer before or upon receiving payment; or (iii) to facilitate Refunds or Disputes.
Qualifications & exceptions
Applies to Users in Japan.
Retention is limited to the three stated purposes.
Not stated here
No maximum period is stated beyond 'as long as required'.
Legal Rights & Agreement Rules · Context
The Connect Infrastructure Terms apply when a Service incorporates them and let you create and manage Connected Accounts
The Stripe Connect Infrastructure Terms, last modified September 28, 2026, supplement the General Terms and apply to a Service only if that Service's terms incorporate them by reference. Undefined terms come from the General Terms. The User may use the Stripe Connect Services under these terms to create, manage and enable Services for its Connected Accounts; for a platform, the Connect Services are those that let it set up Services for Connected Accounts under these Infrastructure Terms and enable payments under the Connect Terms, while for a Connected Account they are the Services described in the Connected Account Agreement.
Supporting quotations
Stripe Connect—Infrastructure
Last modified: September 28, 2026
1. Stripe Connect Services.
These terms (“Stripe Connect Infrastructure Terms”) supplement the General Terms and apply to a Service if incorporated by reference into the applicable Service Terms. Capitalized terms that are not defined in these Stripe Connect Infrastructure Terms have the same meanings given to them in the General Terms. User may use the Stripe Connect Services in accordance with these Stripe Connect Infrastructure Terms to create, manage and enable Services for User’s Connected Accounts.
“Stripe Connect Services” means (a) if User is a Stripe Connect Platform, the Services that allow User to (i) create, manage and enable Services for User’s Connected Accounts, as described in the Stripe Connect Infrastructure Terms; and (ii) enable User or User’s Connected Accounts to use the Stripe Payments Services, as described in the Stripe Connect Terms (if applicable)
Qualifications & exceptions
These terms apply only where incorporated by another set of Service Terms, such as Connect, Capital for Platforms, Issuing Platform or Treasury for Platforms.
Legal Rights & Agreement Rules · Context
Stripe has its own contract with each Connected Account and may serve them outside your platform; you relay changes
Connected Accounts may use the Services under the Connected Account Agreement, the agreement with Stripe on the Stripe Legal Page for their jurisdiction. Stripe may suspend or stop Services to a Connected Account under that agreement, has a direct contractual relationship with each Connected Account and provides the Services directly to it. The User acknowledges that Connected Accounts may use Stripe services outside their relationship with the User. For Connected Accounts without a Stripe Dashboard, Stripe notifies the User when it modifies the Connected Account Agreement, and the User must promptly notify those Connected Accounts of the modification.
Supporting quotations
2. Stripe Obligations.
2.1 Connected Accounts.
Connected Accounts may use the Services in accordance with the Connected Account Agreement. Stripe may suspend or stop providing any Services to a Connected Account in accordance with the terms of the Connected Account Agreement. Stripe has a direct contractual relationship with each Connected Account under the Connected Account Agreement and will provide the Services directly to each Connected Account. User acknowledges that Connected Accounts may choose to use Stripe services outside of the Connected Accounts’ relationship with User.
2.2 Amendments to Connected Account Agreement.
For all Connected Accounts that do not have a Stripe Dashboard, Stripe will notify User if Stripe modifies the relevant Connected Account Agreement. User must notify those Connected Accounts of the modification promptly after User receives the modification notice from Stripe.
“Connected Account Agreement” means the agreement with Stripe that applies to Connected Accounts (except Payout Recipients), which is accessible on the Stripe Legal Page for the Connected Account's jurisdiction.
Qualifications & exceptions
The relay duty applies only to Connected Accounts that lack a Stripe Dashboard.
Not stated here
The Connected Account Agreement is not supplied.
Account & Service Control · Procedure
Integrate per the Documentation, use Connect and account data lawfully and per your agreements, disclose Platform Fees
The User must integrate the Stripe API and use the Connect Services under the Documentation and the Agreement, and must use the Connect Services and Connected Account Data in accordance with Law and its Platform Provider Agreement, its own agreements with each Connected Account. It must clearly and prominently disclose all Platform Fees, the fees it directs Stripe to charge Connected Accounts for its Platform Services, and, where charged separately, any Stripe Fees.
Supporting quotations
3. User Obligations.
3.1 Stripe Connect Services Integration and Use.
User must integrate the Stripe API and use the Stripe Connect Services in accordance with the Documentation and this Agreement. User must use the Stripe Connect Services and Connected Account Data in accordance with Law and User’s Platform Provider Agreement. User must clearly and prominently disclose all Platform Fees, if any, and, to the extent charged separately, any Fees.
“Platform Fees” means the fees User directs Stripe to charge User’s Connected Accounts for the Connected Accounts’ use of User’s Platform Services.
“Platform Provider Agreement” means, as to each Connected Account, collectively, the agreements that a Stripe Connect Platform has with that Connected Account.
Qualifications & exceptions
Fee disclosure covers Platform Fees and separately charged Stripe Fees.
Account & Service Control · Procedure
Keep Connected Accounts within their agreement and the law, report illegal or fraudulent activity at once, fight misuse
The User must ensure Connected Accounts do not use the Services in breach of the Connected Account Agreement or for any activity Law or the Agreement prohibits. It must immediately inform Stripe if it learns a Connected Account is engaged in illegal, fraudulent, deceptive or harmful activity or is breaching the Connected Account Agreement or the Agreement, and must cooperate with Stripe to reduce fraud or other misuse, including by providing relevant information.
Supporting quotations
3.2 Connected Accounts and Risk.
User must ensure that Connected Accounts do not use the Services in breach of the Connected Account Agreement or for any activity that Law or this Agreement prohibits. User must immediately inform Stripe if User becomes aware that a Connected Account is engaging in any activity that is illegal, fraudulent, deceptive or harmful, or in breach of the Connected Account Agreement or this Agreement. User must cooperate with Stripe to reduce the risk of fraud or other misuse of the Services, including by providing relevant information to Stripe.
Qualifications & exceptions
The reporting duty is triggered by the User becoming aware and requires immediate notice.
Security & Safeguards · Restriction or exception
Activity may be done by you or the account; you answer for all Activity under your credentials, even unauthorized
Depending on how the User integrates the Stripe API, a Connected Account may perform Activity itself or the User may perform it on the account's behalf. Activity is any action on or related to a Connected Account's Stripe Account that a platform or the account initiates through Stripe Technology or the Connect Services, including related communications. The User is responsible for all Activity initiated by itself, its representatives and anyone using its credentials, including its Stripe Account login and password and API key. Notwithstanding anything else in the Agreement, where Stripe or a Connected Account suffers losses from unauthorized Activity initiated by the User or on its behalf, the User is liable for them as between Stripe and the User.
Supporting quotations
3.3 Activity.
A Connected Account may perform Activity, or User may perform Activity on behalf of a Connected Account, depending on how User integrates the Stripe API into User’s Platform Services. User is responsible for all Activity initiated by User, User’s representatives, and any individual or entity using User’s credentials, including User’s Stripe Account login and password and User’s Stripe API key. Notwithstanding anything to the contrary in this Agreement, where either Stripe or a Connected Account incurs any losses, damages or costs based on unauthorized Activity initiated by User or on User’s behalf, then as between Stripe and User, User is liable for those losses, damages or costs.
“Activity” means any action taken on or related to a Connected Account's Stripe Account that a Stripe Connect Platform or a Connected Account initiates, submits or performs, either through the Stripe Technology or through the Stripe Connect Services, including communication regarding the Services as related to that Connected Account.
Qualifications & exceptions
Liability covers anyone using the User's credentials, so credential compromise falls on the User.
The unauthorized-Activity liability applies 'notwithstanding anything to the contrary in this Agreement'.
Sharing & Disclosure · Restriction or exception
Your agreement with each Connected Account must authorize your data access and Activity; never act beyond that authority
The User's Platform Provider Agreement must explain how the User accesses and uses Connected Account Data (data about Connected Accounts and Activity, which may include Protected Data and Stripe Data) and the Activity it may conduct on the accounts' behalf via Connect, and must authorize the User to perform that Activity and to share Connected Account Data with Stripe. The User must not use the Connect Services to access Connected Account Data or conduct Activity, or attempt to, that the Connected Account has not authorized or has withdrawn authorization for.
Supporting quotations
3.4 User’s Agreements with Connected Accounts.
User’s Platform Provider Agreement must explain how User accesses and uses Connected Account Data, and the Activity that User may conduct on the Connected Accounts’ behalf via the Stripe Connect Services. User’s Platform Provider Agreement must also authorize User to perform that Activity, and to share the Connected Account Data with Stripe.
3.5 Limitations.
User must not use the Stripe Connect Services to access any Connected Account Data or conduct any Activity, or attempt to do either, for which the relevant Connected Account has not authorized, or has withdrawn the authorization.
“Connected Account Data” means data about Connected Accounts and Activity, which may include Protected Data and Stripe Data.
Qualifications & exceptions
Authorization must cover both the User's Activity and its sharing of Connected Account Data with Stripe.
Withdrawn authorization ends the User's permitted access or Activity.
Not stated here
Protected Data and Stripe Data are defined in the General Terms, not supplied.
Account & Service Control · Procedure
Your own onboarding means you create accounts, collect data and get agreement; Stripe-onboarded accounts can cut you off
If the User onboards Platform Users through User-Hosted Onboarding (its own interface built on the Stripe API or embedded Stripe components), it must create and manage the Connected Accounts' Stripe accounts, collect and provide Connected Account Data as the Documentation prescribes, and ensure each Platform User agrees to the Connected Account Agreement before using any Stripe services; on request it must prove those agreements exist, and must change its acceptance process if Stripe believes it does not create a binding agreement. If the User uses Stripe-Hosted Onboarding, it gets access to certain Connected Account Data Stripe collects and must collect and provide additional data on request to validate an account. Where Stripe onboards Platform Users through Stripe-Hosted Onboarding, Connected Accounts without Platform Pricing Control may terminate the User's ability to conduct Activity on their accounts at any time.
Supporting quotations
4. Onboarding, Activity and Data.
4.1 User Onboarding Obligations.
If User onboards Platform Users using User-Hosted Onboarding, User must: (i) create and manage the Stripe accounts for its Connected Accounts; (ii) ensure that Connected Account Data is collected and provided to Stripe in the manner prescribed in the Documentation; and (iii) ensure that each Platform User agrees to the Connected Account Agreement before it uses any Stripe services. At Stripe’s request, User must provide proof as Stripe requires that these Connected Account Agreements have been entered into between the Connected Accounts and Stripe. If Stripe believes that User’s existing acceptance process does not create a binding agreement between Stripe and each Connected Account, then, on Stripe’s request, User must modify that process as Stripe requires.
If User uses Stripe-Hosted Onboarding, User will have access to certain Connected Account Data collected by Stripe. At Stripe’s request, User will collect and provide additional Connected Account Data to validate a Connected Account.
4.2 Ability to Conduct Activity.
If Stripe onboards Platform Users using Stripe-Hosted Onboarding, those Connected Accounts without Platform Pricing Control may terminate User’s ability to conduct Activity on their Stripe accounts at any time.
“User-Hosted Onboarding” means User’s onboarding user interface used to collect onboarding information relating to Platform Users built using: (a) the Stripe API; or (b) Stripe-developed components embedded into the Platform Services, each as described in the Documentation.
“Stripe-Hosted Onboarding” means the web form and set of onboarding tools hosted by Stripe used to collect onboarding information relating to Platform Users as described in the Documentation.
Qualifications & exceptions
Duties depend on whether onboarding is User-Hosted or Stripe-Hosted.
The termination right belongs only to Stripe-onboarded accounts without Platform Pricing Control.
Account & Service Control · Company practice
The General Terms govern Connected Account Data; Stripe may refuse or limit an account until it has enough information
Section 4 of the General Terms (not supplied) applies to all Connected Account Data the User provides to Stripe. Stripe may refuse to create a Stripe account for a Platform User, or limit the functionality available to one, until it is satisfied it has received sufficient information about that Platform User.
Supporting quotations
Section 4 of the General Terms applies to all Connected Account Data that User provides to Stripe. Stripe may refuse to create a Stripe account for a Platform User or limit the functionality available to a Platform User until Stripe is satisfied that it has received sufficient information about that Platform User.
Qualifications & exceptions
Stripe's refusal or limitation lasts until it is satisfied with the information received.
Not stated here
Section 4 of the General Terms is unknown; the General Terms are not supplied.
Use & Processing · Restriction or exception
Each side uses Connected Account Data per its consents; you secure consents, and Stripe may refuse unlawful instructions
Each party may use Connected Account Data in accordance with the Agreement and any consent or agreement it obtains from each Connected Account, which for Stripe includes the Connected Account Agreement. The User must give all notices and obtain all rights and consents needed for Stripe to lawfully process Connected Account Data as the User instructs. Stripe may refuse to process the data as instructed if it reasonably believes compliance would require it to violate Law or the Connected Account Agreement.
Supporting quotations
4.4 Data Use.
Each party may use Connected Account Data in accordance with this Agreement and any consent or agreement it obtains from each Connected Account, which, as to Stripe, includes the Connected Account Agreement. User must provide all notices and obtain all necessary rights and consents for Stripe to lawfully process Connected Account Data as User instructs. Stripe may refuse to process Connected Account Data as User instructs if Stripe reasonably believes complying with User’s instructions would require Stripe to violate Law or the Connected Account Agreement.
Qualifications & exceptions
Stripe's refusal requires a reasonable belief that compliance would breach Law or the Connected Account Agreement.
Charges & Financial Obligations · Restriction or exception
You may use Stripe’s 1099 Services, but you own tax compliance, accuracy and penalties, and Stripe validates nothing
The User may use the IRS Form 1099 Services, in which Stripe generates copies of IRS Form 1099 for Transactions, delivers recipient copies to Connected Accounts and files electronic copies with tax authorities, as the Documentation describes. When using them the User is responsible for, and Stripe disclaims all liability for, the User's legal obligations including Taxes, the accuracy of Tax calculations and any fine, penalty or sanction a Governmental Authority imposes from the use of the service, and the User's actions or inaction on any directions or recommendations received through it. Stripe does not validate and is not responsible for the accuracy of information the User or its Connected Accounts provide, and the service is not tax advice or tax filing or reporting assistance.
Supporting quotations
5. IRS Form 1099 Services.
5.1 IRS Form 1099 Services.
User may use the IRS Form 1099 Services to generate copies of IRS Form 1099 and deliver them to the applicable Governmental Authorities and Connected Accounts, as described in the Documentation.
5.2 Disclaimer.
When using IRS Form 1099 Services, User is responsible for, and Stripe disclaims all liability with respect to:
User's fulfillment of User's obligations under Law, including with respect to Taxes
the accuracy of the Tax calculations, and User's obligation to pay any fine, penalty, or other sanction imposed by a Governmental Authority as a result of the use of the IRS Form 1099 Services
User's action, or failure to act, as a result of any directions or recommendations User receives related to the use of the IRS Form 1099 Services.
5.3 Information Accuracy; No Tax Advice.
Stripe will not validate, and is not responsible for, the accuracy of the information User or User's Connected Accounts provide to Stripe. The IRS Form 1099 Services do not constitute tax advice, or tax filing or reporting assistance.
“IRS Form 1099 Services” means the Services where Stripe generates copies of IRS Form 1099 with respect to Transactions, delivers recipient copies of IRS Form 1099 to the applicable Connected Accounts, and files electronic copies of IRS Form 1099 with the applicable Governmental Authorities (e.g., state or federal tax authorities), in each case, to the extent stated in the Documentation.
“IRS” means Internal Revenue Service.
Qualifications & exceptions
Scope of the 1099 Services is 'to the extent stated in the Documentation'.
Stripe disclaims liability for calculation accuracy, penalties and reliance on its directions.
Legal Rights & Agreement Rules · Context
Infrastructure Terms applied to a Connected Account are read from its side; accounts cannot claim as third parties
Where these terms apply a defined term to a Connected Account rather than the User, the definition refers to the Connected Account; 'Services' applied to a Connected Account means the Stripe services available to it under the Connected Account Agreement, and 'Disputes' means that account's Disputes. Connected Accounts are not third parties for, and cannot make a Claim under, Section 9 of the General Terms. This mirrors Section 6 of the Connect Terms.
Supporting quotations
6. Definitions Applied to Connected Accounts; General Terms Clarification.
Where defined terms are applied to a Connected Account (rather than User) in these terms, the relevant definition will be deemed to reference the Connected Account (e.g., when the term Services is applied to a Connected Account it means the Stripe services that Stripe makes available to the Connected Account under the Connected Account Agreement, and when the term Disputes is applied to a Connected Account it means Disputes that Connected Account incurs). Connected Accounts are not third parties for the purposes of, or eligible to make a Claim under, Section 9 of the General Terms.
Qualifications & exceptions
Section 9 of the General Terms is not supplied.
Charges & Financial Obligations · Restriction or exception
If you onboard accounts yourself and fail to bind them to the Connected Account Agreement, your liability is unlimited
If the User onboards Platform Users through User-Hosted Onboarding, its liability arising from a failure to ensure each Connected Account agreed to the Connected Account Agreement in a legally binding way is not limited or excluded in any way, notwithstanding anything to the contrary in the Agreement.
Supporting quotations
7. Liability Cap.
If User onboards Platform Users using User-Hosted Onboarding, User’s liability arising out of or relating to User’s failure to ensure that each Connected Account agreed to the Connected Account Agreement in a legally binding way, is not limited or excluded in any way, notwithstanding anything to the contrary in this Agreement.
Qualifications & exceptions
Applies only where the User uses User-Hosted Onboarding.
Section 8 begins the definitions. 'Activity' is any action on or related to a Connected Account's Stripe Account initiated by a platform or the account through Stripe Technology or Connect, including related communications. A 'Connected Account' is a Platform User onboarded via Connect or a Payout Recipient; the 'Connected Account Agreement' is its own agreement with Stripe; 'Connected Account Data' is data about Connected Accounts and Activity, possibly including Protected Data and Stripe Data. 'Dispute' has the Payments meaning. 'IRS' is the Internal Revenue Service and the 'IRS Form 1099 Services' generate, deliver and file 1099 copies to the extent the Documentation states. A 'Payout Recipient' is a third party the User pays out to via Connect. 'Platform Fees' are fees the User directs Stripe to charge Connected Accounts for its Platform Services; 'Platform Pricing Control' lets the User set an account's fees; the 'Platform Provider Agreement' is the User's agreements with each Connected Account; 'Platform Services' are what Platform Users receive from the platform. The definitions continue in the next packet.
Supporting quotations
8. Definitions.
“Activity” means any action taken on or related to a Connected Account's Stripe Account that a Stripe Connect Platform or a Connected Account initiates, submits or performs, either through the Stripe Technology or through the Stripe Connect Services, including communication regarding the Services as related to that Connected Account.
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
“Connected Account Agreement” means the agreement with Stripe that applies to Connected Accounts (except Payout Recipients), which is accessible on the Stripe Legal Page for the Connected Account's jurisdiction.
“Connected Account Data” means data about Connected Accounts and Activity, which may include Protected Data and Stripe Data.
“Dispute” means an instruction a Customer initiates to reverse or invalidate a processed Transaction (including “chargebacks” and “disputes” as those terms may be used by Payment Method Providers).
“IRS” means Internal Revenue Service.
“IRS Form 1099 Services” means the Services where Stripe generates copies of IRS Form 1099 with respect to Transactions, delivers recipient copies of IRS Form 1099 to the applicable Connected Accounts, and files electronic copies of IRS Form 1099 with the applicable Governmental Authorities (e.g., state or federal tax authorities), in each case, to the extent stated in the Documentation.
“Payout Recipient” means a third-party recipient to which Stripe enables User to make payouts via the Stripe Connect Services.
“Platform Fees” means the fees User directs Stripe to charge User’s Connected Accounts for the Connected Accounts’ use of User’s Platform Services.
“Platform Pricing Control” means the Connected Account attribute that enables User to determine, to the extent stated in the Documentation, the fees that apply with respect to the Connected Account.
“Platform Provider Agreement” means, as to each Connected Account, collectively, the agreements that a Stripe Connect Platform has with that Connected Account.
“Platform Services” means the products and services that Platform Users receive from a Stripe Connect Platform, regardless of whether fees are charged (e.g., web development, customer support or hosting services).
Legal Rights & Agreement Rules · Context
Infrastructure definitions: Platform User, Connect Platform and Services, Stripe-Hosted and User-Hosted Onboarding
The remaining Infrastructure definitions. A 'Platform User' is a user of the User's platform where the User acts as a Stripe Connect Platform, which is any platform provider using the Stripe Connect Services. For a platform, the 'Stripe Connect Services' let it create, manage and enable Services for its Connected Accounts under these Infrastructure Terms and enable itself or its accounts to use Stripe Payments under the Connect Terms; for a Connected Account they are the Services in the Connected Account Agreement. 'Stripe-Hosted Onboarding' is Stripe's hosted web form and onboarding tools; 'User-Hosted Onboarding' is the User's own onboarding interface built on the Stripe API or embedded Stripe components. A 'Back to Top' link closes the Infrastructure Terms.
Supporting quotations
“Platform User” means, where User is acting as a Stripe Connect Platform, a user of User’s platform.
“Stripe Connect Platform” means a platform provider that uses the Stripe Connect Services.
or (b) if User is a Connected Account, the Services described in the Connected Account Agreement.
“Stripe-Hosted Onboarding” means the web form and set of onboarding tools hosted by Stripe used to collect onboarding information relating to Platform Users as described in the Documentation.
“User-Hosted Onboarding” means User’s onboarding user interface used to collect onboarding information relating to Platform Users built using: (a) the Stripe API; or (b) Stripe-developed components embedded into the Platform Services, each as described in the Documentation.
Legal Rights & Agreement Rules · Context
The Data Pipeline Terms govern Stripe syncing data from your Stripe Account to a warehouse or app you choose
The SDP Terms, last modified September 30, 2026, supplement the General Terms and govern use of the Stripe Data Pipeline Services and SDP Data. The Services let Stripe transfer data from the User's Stripe Account to the User's Destination by scheduled or real-time synchronization; SDP Data is the data so transferred. Undefined terms take their meaning from the General Terms, not supplied.
Supporting quotations
Stripe Data Pipeline
Last modified: September 30, 2026
1. Stripe Data Pipeline Services.
These terms (“SDP Terms”) supplement the General Terms and govern User’s use of the Stripe Data Pipeline Services and SDP Data. Capitalized terms that are not defined in these terms have the same meanings given to them in the General Terms.
“Stripe Data Pipeline Services” means the Services that enable Stripe to transfer data from User’s Stripe Account to the Destination, including both scheduled and real-time synchronization.
“SDP Data” means data Stripe transfers from User’s Stripe Account to a Destination.
Security & Safeguards · Procedure
Use the pipeline only with your own Destination, give accurate connection details, grant only minimum permissions
The User may use the Data Pipeline Services only in connection with its Destination, a supported data warehouse, third-party application or other service it selects to receive SDP Data. It must give Stripe accurate connection details and, where needed, access credentials including account identifier and region, must provision only the minimum permissions Stripe needs to connect, and must ensure Stripe has all rights to use those credentials to access the Destination and transmit SDP Data as the User instructs.
Supporting quotations
2. Use of the Stripe Data Pipeline Services.
2.1 Destination.
User may only use the Stripe Data Pipeline Services in connection with User’s Destination. User must provide Stripe with accurate connection details and, where applicable, access credentials required to establish the connection to User’s Destination, including any applicable account identifier and region. User must provision only the minimum permissions necessary for Stripe to establish the connection. User must ensure that Stripe has all rights and permissions necessary to use the credentials User provides to access the Destination and transmit SDP Data according to User’s instructions.
“Destination” means a supported data warehouse, third-party application, or other service selected by User to receive SDP Data.
Qualifications & exceptions
Permissions granted to Stripe must be the minimum necessary for the connection.
Not stated here
Which Destinations are supported is not listed here.
Use & Processing · Restriction or exception
Piped Stripe Data is for accounting and analytics only; Radar and Identity data only for fraud or security; no PHI
The User must not access or use, or let anyone else access or use, the Data Pipeline Services and Stripe Data for any purpose other than the one they are provided for, or in violation of Law or any Service Terms. Stripe Data made available through the pipeline may be used only for accounting and financial reporting, business analytics or other accounting-related business purposes, unless the General Terms, these SDP Terms or other Service Terms restrict them. Stripe Radar Data and Identity Services Data (Stripe Data received through the Stripe Identity Services) delivered through the pipeline may be used only for security or fraud prevention or as Stripe agrees in writing. On request the User must demonstrate compliance to Stripe's reasonable satisfaction, and neither the User nor its Connected Accounts may use the pipeline with Protected Health Information.
Supporting quotations
2.2 Restricted Uses.
User must not, and must not enable or allow any other party to, access or use the Stripe Data Pipeline Services and Stripe Data (a) for any purpose other than the purpose for which it is provided; or (b) in violation of any Law or Service Terms. If any Stripe Data is made available through the Stripe Data Pipeline Services, User must use that Stripe Data only for accounting and financial reporting, business analytics, or other accounting-related business purposes provided those purposes are not otherwise restricted by the General Terms, these SDP Terms, or any other Service Terms. Any Stripe Radar Data and Identity Services Data made available through Stripe Data Pipeline Services may only be used for security or fraud prevention purposes or as Stripe otherwise agrees in writing. Upon Stripe’s request, User will demonstrate its compliance with this section to Stripe’s reasonable satisfaction. User must not, and will ensure that its Connected Accounts (if applicable) do not, use the Stripe Data Pipeline Services in connection with Protected Health Information.
“Identity Services Data” means any Stripe Data that User receives from Stripe in connection with the Stripe Identity Services.
Qualifications & exceptions
General Stripe Data: accounting, financial reporting, business analytics and accounting-related purposes only.
Radar and Identity data: security or fraud prevention only, unless Stripe agrees otherwise in writing.
Protected Health Information is excluded for the User and its Connected Accounts.
Retention & Deletion · Procedure
You handle data subject requests about data moved to your Destination, including deleting it there when Law requires
The User is responsible for responding to Data Subject Requests, as defined in the DPA, relating to SDP Data transferred to a Destination, including deleting the applicable SDP Data from the Destination where Law requires.
Supporting quotations
2.3 Data Subject Requests.
User is responsible for responding to Data Subject Requests (as defined in the DPA) relating to SDP Data transferred to a Destination, including by deleting applicable SDP Data from the Destination where required by Law.
Qualifications & exceptions
Responsibility covers deletion at the Destination where Law requires.
Not stated here
The DPA (Data Processing Agreement) defining Data Subject Requests is not supplied.
Sharing & Disclosure · Permission or license
Once transferred, the Destination is custodian and Stripe is not liable for copies; Stripe moves data only as you direct
The User authorizes Stripe to transfer SDP Data to a Destination. After transfer, the Destination is the custodian of the data and Stripe is not responsible for any copy the User or Destination makes, including how it is stored, used, secured, modified or disclosed. The User must hold all rights and consents needed for Stripe to provide and the User to use the pipeline, including to retain, reproduce and disclose SDP Data, and must on request assist Stripe with its legal obligations, such as responding to data subjects or Governmental Authorities. Stripe will transfer SDP Data only at the User's direction and under the Agreement.
Supporting quotations
3. SDP Data.
User authorizes Stripe to transfer SDP Data to a Destination. After Stripe transfers SDP Data, (a) the Destination is the custodian of the SDP Data; and (b) Stripe is not responsible for any copy of the SDP Data that User or the Destination makes, including how it is stored, used, secured, modified, or disclosed. User must have all necessary rights and consents sufficient to enable Stripe to provide, and for User to use, the Stripe Data Pipeline Services, including to retain, reproduce, and disclose any SDP Data. Upon Stripe’s request, User will assist Stripe in complying with its obligations under Law, which assistance may include responding to requests by data subjects or a Governmental Authority.
Stripe will only transfer SDP Data at User’s direction and according to the terms of this Agreement.
Qualifications & exceptions
Stripe's responsibility ends at transfer; the Destination becomes custodian.
Stripe commits to transfer only on the User's direction.
Account & Service Control · Company practice
Stripe may cut the pipeline at once if your Destination drops needed features; it disconnects, and your duties survive
Stripe may, by notifying the User, immediately suspend or terminate access to the Data Pipeline Services if a Destination stops offering the features Stripe uses to provide them. On termination or suspension Stripe disconnects from the Destination, stops transmitting SDP Data and deletes the access credentials the User provided; the User loses access to any data syncs containing new SDP Data. The User's obligations under Sections 2.2 (restricted uses), 2.3 (data subject requests) and 3 (SDP Data), and any existing duty under the Agreement to delete or destroy data, survive termination.
Supporting quotations
4. Termination.
Stripe may, by notifying User, immediately suspend or terminate User’s access to the Stripe Data Pipeline Services if an applicable Destination stops offering the features or functionality that Stripe uses to provide the Stripe Data Pipeline Services. Upon termination or suspension of the Stripe Data Pipeline Services, Stripe will disconnect from the User’s applicable Destination(s), cease transmitting SDP Data to the applicable Destination, and delete any access credentials User provided to Stripe. User will lose access to any data syncs, automated or otherwise, containing new SDP Data. User’s obligations under Sections 2.2, 2.3, and 3 of these SDP Terms, and any existing obligation User has under the Agreement to delete or destroy data, will survive the termination of these SDP Terms.
Qualifications & exceptions
Termination requires notice but can be immediate.
The restricted-use, data-subject-request and SDP Data obligations survive.
Legal Rights & Agreement Rules · Restriction or exception
Using the pipeline does not make you compliant; you own configuration, data handling and Destination fees
Stripe does not warrant that using the Data Pipeline Services will make the User compliant with Law, including any notification duties to data subjects. The User remains fully responsible for, and the Stripe Parties disclaim liability for, the User's configuration of the service and the accuracy and completeness of its transfer instructions, the use, storage, security, modification and disclosure of SDP Data by the User or third parties, and fees the Destination charges. Stripe is not responsible for connection or transfer failures or delays caused by the Destination's technical limits.
Supporting quotations
5. Disclaimer.
Stripe does not warrant or represent that by using Stripe Data Pipeline Services, User will be in compliance with Law, including any required notification obligations User may have to any data subjects. User remains fully responsible for, and Stripe Parties disclaim all liability with respect to: (a) User’s configuration of Stripe Data Pipeline Services and the accuracy and completeness of User’s instructions to Stripe to transfer data, (b) User’s or any third party’s use, storage, security, modification, and disclosure of SDP Data, and (c) fees a Destination charges User. Stripe is not responsible for a failure or delay in connecting to, or transferring SDP Data to, a Destination due to the Destination’s technical limits.
Legal Rights & Agreement Rules · Context
Data Pipeline definitions: Connected Account, Destination, Identity Services Data, SDP Data, Data Pipeline Services
Section 6 defines the terms: a 'Connected Account' is a Platform User onboarded via Connect or a Payout Recipient; a 'Destination' is a supported data warehouse, third-party application or other service the User selects to receive SDP Data; 'Identity Services Data' is Stripe Data received through the Stripe Identity Services; 'SDP Data' is data Stripe transfers from the User's Stripe Account to a Destination; and the 'Stripe Data Pipeline Services' transfer that data by scheduled or real-time synchronization. The Stripe Radar Data definition follows in the next packet.
Supporting quotations
6. Definitions.
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
“Destination” means a supported data warehouse, third-party application, or other service selected by User to receive SDP Data.
“Identity Services Data” means any Stripe Data that User receives from Stripe in connection with the Stripe Identity Services.
“SDP Data” means data Stripe transfers from User’s Stripe Account to a Destination.
“Stripe Data Pipeline Services” means the Services that enable Stripe to transfer data from User’s Stripe Account to the Destination, including both scheduled and real-time synchronization.
Legal Rights & Agreement Rules · Context
Data Pipeline definition: Stripe Radar Data is the Radar Scores and other data received through Radar or Orchestrated
The last Data Pipeline definition: 'Stripe Radar Data' means the Radar Scores and other data the User receives through the Stripe Radar Services and, where applicable, the Stripe Orchestrated Services. Under Section 2.2 such data delivered through the pipeline may be used only for security or fraud prevention. A 'Back to Top' link closes the SDP Terms.
Supporting quotations
“Stripe Radar Data” means the Radar Scores and other data User receives through the Stripe Radar Services, and the Stripe Orchestrated Services (as applicable).
Charges & Financial Obligations · Restriction or exception
A Fee Credit settles what it was issued for and only discounts future Stripe Fees; no transfer, rental or sale
The Stripe Fee Credit Terms, last modified September 28, 2026, supplement the General Terms and govern Stripe Fee Credits: Stripe-issued amounts usable solely as a discount against future Fees, excluding amounts the User itself pays that become a credit, such as a prepayment. A Fee Credit constitutes full payment and settlement to the User for the purpose it was issued for. It is a discount against, and can only offset, future Fees accrued on the User's Stripe Account, subject to limitations shown in the Dashboard. The User may not transfer a Fee Credit between Stripe Accounts or license, rent or sell it for cash or other consideration.
Supporting quotations
Stripe Fee Credit Terms
Last modified: September 28, 2026
1. Stripe Fee Credits.
These Stripe Fee Credit Terms (“Fee Credit Terms”) supplement the General Terms and govern the use of the Stripe Fee Credits. Capitalized terms that are not defined in these terms have the same meanings given to them in the General Terms.
2. Using a Fee Credit.
The Fee Credit amount constitutes full payment and settlement to User with respect to the purpose for which it is issued. The Fee Credit is a discount against, and can only be used to offset, future Fees User accrues on User’s Stripe Account, subject to any limitations stated on User’s Stripe Dashboard. User may not (a) transfer a Fee Credit from one Stripe Account to another; or (b) license, rent, or sell a Fee Credit for cash or any other consideration.
“Fee Credit” means a Stripe-issued amount that User may use solely as a discount against future Fees, but does not include any amount User pays Stripe that becomes a fee credit (e.g., a prepayment).
Qualifications & exceptions
Accepting a Fee Credit is full settlement of whatever it was issued for.
Dashboard-stated limitations may further restrict use.
Not stated here
The circumstances in which Stripe issues Fee Credits are not stated here.
Charges & Financial Obligations · Company practice
Fee Credits expire on their Dashboard date; Stripe may end them early, suspend them while you owe money, or void them
A Fee Credit expires automatically after the expiry date shown in the Dashboard. Stripe may terminate it earlier if the Agreement or the relevant fee agreement terminates, and may cancel unused amounts after termination or expiry. If Fees or other amounts go unpaid when due, or the User otherwise breaches the Agreement, Stripe may suspend the Fee Credit until the User has paid everything owed and cured the breach. Stripe may void a Fee Credit if the User breaches these terms or the agreement, promotion or program under which it received the credit, and may then collect the credit's amount from the User in addition to other remedies.
Supporting quotations
3. Expiration and Cancelation.
The Fee Credit automatically expires after the expiry date stated on User’s Stripe Dashboard. Stripe may terminate a Fee Credit before its expiry date if (a) the Agreement terminates; or (b) the relevant fee agreement between the parties, if applicable, terminates. Stripe may cancel any unused Fee Credit amounts after they terminate or expire. If, after Stripe issues the Fee Credit, any Fees or other amounts are not paid to Stripe when due, or User is in breach of the Agreement for any other reason, then Stripe may suspend the Fee Credit until User has paid in full all outstanding Fees and other amounts User owes Stripe, and has rectified any breach of the Agreement. Stripe may void a Fee Credit if User breaches these Fee Credit Terms or the terms of any other agreement, promotion, or program under which User received the Fee Credit. If Stripe voids the Fee Credit, then in addition to any other remedy available to Stripe, Stripe may collect from User the amount of the Fee Credit.
Qualifications & exceptions
Suspension lasts until all outstanding amounts are paid and any breach is cured.
A voided credit can be clawed back as a debt.
Charges & Financial Obligations · Company practice
Fee Credits include any Taxes you must charge; Stripe may withhold Taxes unless you prove exemption or a reduced rate
The Fee Credit is inclusive of any applicable Taxes the User may be required to charge. If Stripe must withhold Taxes on a Fee Credit, it may deduct them from the credit and pay them to the taxing authority. A User exempt from, or eligible for a reduced rate on, those Taxes may give Stripe a copy of the original certificate meeting legal requirements that attests to its status.
Supporting quotations
4. Taxes.
The Fee Credit is inclusive of any applicable Taxes which may be required to be charged by User. If Stripe is required to withhold any Taxes applicable to a Fee Credit, Stripe may deduct those Taxes from the Fee Credit and pay those Taxes to the appropriate taxing authority. If User is exempt from paying, or are otherwise eligible to pay a reduced rate on, those Taxes, User may provide to Stripe a copy of the original certificate that satisfies applicable legal requirements attesting to its tax-exempt status or reduced rate eligibility.
Qualifications & exceptions
Withholding is deducted from the credit amount itself.
Exemption or reduced-rate treatment depends on the User supplying a qualifying certificate.
Legal Rights & Agreement Rules · Context
Fee Credit Terms definition: a Fee Credit is a Stripe-issued discount against future Fees, not a prepayment you made
Section 5 defines 'Fee Credit' as a Stripe-issued amount the User may use solely as a discount against future Fees, excluding any amount the User pays Stripe that becomes a fee credit, such as a prepayment. A 'Back to Top' link closes the Fee Credit Terms.
Supporting quotations
5. Definitions.
“Fee Credit” means a Stripe-issued amount that User may use solely as a discount against future Fees, but does not include any amount User pays Stripe that becomes a fee credit (e.g., a prepayment).
Qualifications & exceptions
Prepayments the User makes are not Fee Credits under these terms.
Legal Rights & Agreement Rules · Context
The Financial Connections Terms govern verifying end users' bank accounts and optionally receiving their account data
The Stripe Financial Connections Terms, last modified September 28, 2026, supplement the General Terms and incorporate the Stripe Financial Services Terms by reference; together they govern the Stripe Financial Connections Services, which let the User verify End User financial accounts and optionally receive Connections Data, the account identifiers, ownership information, balances and transactions that Stripe obtains from Data Sources and provides to the User. Regional Terms in Section 6 apply by the User's Stripe Account Country, and undefined terms come from the General Terms or Financial Services Terms.
Supporting quotations
Stripe Financial Connections
Last modified: September 28, 2026
1. Stripe Financial Connections Services.
These terms (“Stripe Financial Connections Terms”) supplement the General Terms and, together with the Stripe Financial Services Terms which are incorporated into these Stripe Financial Connections Terms by this reference, govern the use of the Stripe Financial Connections Services and Connections Data. The Regional Terms in Section 6 (Regional Terms) of these Stripe Financial Connections Terms apply based on User's Stripe Account Country.
“Stripe Financial Connections Services” means the Services that enable User to verify End User financial accounts and the option to receive Connections Data.
“Connections Data” means data associated with a Connections End User’s financial account that Stripe provides to User through the Stripe Financial Connections Services, which may include account identifiers (e.g., account and routing numbers, or institution and transit numbers), account ownership information, account balance, and account transactions, from Data Sources.
Qualifications & exceptions
Regional Terms in Section 6 apply based on the User's Stripe Account Country.
Use & Processing · Procedure
At least 14 days before collecting account data, get Stripe’s written approval of your purpose and consent screen
At least 14 days before first collecting Connections Data, the User must submit its Proposed Purpose for collecting, using and processing the data and, if it hosts the consents itself, the Proposed Express Consent UI it will use to obtain Express Consents (a Connections End User's express, informed, opt-in consent) on behalf of the User and Stripe. Stripe reviews promptly; on written approval the purpose becomes the Authorized Purpose and the interface the Express Consent UI. Any change to either must be submitted for review and approved in writing at least 14 days before it takes effect.
Supporting quotations
2. Use of the Stripe Financial Connections Services.
2.1 Authorized Purpose and Express Consent UI.
At least 14 days before User intends to collect Connections Data for the first time, User must submit (i) its intended purpose for collecting, using, and processing Connections Data (the “Proposed Purpose”); and (ii) if User hosts the Express consents, the user interface it will use to obtain Express Consents (the “Proposed Express Consent UI”) on behalf of User and Stripe for access to Connections Data. Stripe will promptly review User's Proposed Purpose and Proposed Express Consent UI. Upon Stripe’s written approval, the Proposed Purpose will become an "Authorized Purpose” and (if applicable) the Proposed Express Consent UI will become an “Express Consent UI”.
If User wishes to change an Authorized Purpose or an Express Consent UI, User must submit the proposed change to Stripe for review and obtain Stripe’s written approval at least 14 days before the proposed change is planned to take effect.
“Express Consent” means a Connections End User’s express, informed, opt-in consent to User’s collection, use, disclosure, and processing of that Connections End User’s Connections Data for the Authorized Purpose.
“Express Consent UI” means the user interface, including the text and consent mechanism included on that user interface, through which User obtains Express Consents.
Qualifications & exceptions
Both the initial submission and any change require 14 days' lead time and Stripe's written approval.
The consent UI submission applies only if the User hosts the consents itself.
Data Access & Collection · Procedure
Consents must meet Law and Link’s terms, disclose data and purpose clearly, bind your use, and be kept 24 months after
The User's Express Consents must be sufficient under Law. The User must clearly and conspicuously tell each Connections End User (an End User whose data the User seeks) what data it receives and the Authorized Purpose being consented to. Each Express Consent must comply with Link's Consumer Terms of Service, Link's Privacy Policy, Law and these terms, and the User may collect, use, retain, disclose and process each person's Connections Data only within that person's Express Consent. The User must keep records of each Express Consent during the Term and for at least 24 months afterwards.
Supporting quotations
2.2 Express Consents and Record Keeping.
User’s Express Consents must be sufficient under Law. User must clearly and conspicuously disclose to each Connections End User the data User is receiving, and the Authorized Purpose that the Connections End User is consenting to in their Express Consent.
Law and these Stripe Financial Connections Terms; and (b) User collects, uses, retains, discloses, and processes each Connections End User’s Connections Data only in compliance with that Connections End User’s Express Consent. During the Term and for at least 24 months after the end of the Term, User must maintain records of each Connections End User’s Express Consent.
“Connections End User” means an End User whose Connections Data User requests to access, collect, use, and process in connection with the Stripe Financial Connections Services.
Qualifications & exceptions
Link's Consumer Terms of Service and Privacy Policy are linked external documents, not supplied.
Consent records must be retained for at least 24 months after the Term ends.
Data Access & Collection · Restriction or exception
Material changes to your purpose, data handling or the account data you take need a new consent before the change
If the User obtained an Express Consent and later materially changes its Authorized Purpose, it must obtain a new Express Consent covering the updated purpose. If the Authorized Purpose includes receiving Connections Data and the User materially changes that data's scope, purpose, security, sharing or storage period, it must obtain a new Express Consent before the changes take effect. If the Authorized Purpose did not include financial account data the User will now collect as Connections Data, it must obtain an updated Express Consent before receiving the additional data.
Supporting quotations
2.3 Updates to Express Consents.
If User received an Express Consent from an End User and User later materially changes User’s Authorized Purpose, User must obtain a new Express Consent that covers the updated Authorized Purpose.
If User’s Authorized Purpose includes User’s receipt of Connections Data, and User later materially changes the scope, purpose, security, sharing, or period of storage of that data, User must obtain a new Express Consent before those changes go into effect.
If User’s Authorized Purpose does not include financial account data that User will collect as part of the Connections Data, User must obtain an updated Express Consent before receiving the additional Connections Data.
Qualifications & exceptions
Fresh consent is required before, not after, the material change or additional data collection.
Not stated here
What counts as a 'material' change is not defined.
Security & Safeguards · Restriction or exception
Financial Institutions must tell Stripe 14 days ahead; nobody may ask end users for their bank login credentials
If the User is a Financial Institution (for Canada, a federally or provincially regulated bank, trust or loan company, credit union or caisse populaire), additional conditions apply: at least 14 days before accessing the Financial Connections Services it must disclose that status through Stripe's submission process and provide any further information Stripe requests. Separately, the User must not request or obtain a Connections End User's login credentials for their financial account.
Supporting quotations
2.4 Financial Institution Users.
If User is a Financial Institution, additional conditions apply to User’s use of the Stripe Financial Connections Services. At least 14 days before accessing the Stripe Financial Connections Services, User must disclose to Stripe through the submission process Stripe communicates to User that User is a Financial Institution, and provide all additional information Stripe requests.
2.5 End User Login Credentials.
User must not request or obtain Connections End User login credentials for a Connections End User’s financial account.
"Financial Institution" means a bank, trust company, loan company, credit union, caisse populaire, or other financial institution that is federally or provincially regulated under Canadian Law, including under the Bank Act (S.C. 1991, c. 46), the Trust and Loan Companies Act (S.C. 1991, c. 45), or applicable provincial legislation.
Qualifications & exceptions
The Financial Institution definition shown is the Canadian Regional Term's; the general clause does not define the term.
The credential ban is absolute.
Not stated here
The additional conditions for Financial Institutions are not spelled out beyond the disclosure duty.
Content & IP Rights · Permission or license
You license your Marks so Stripe and Data Sources can name you to end users, and Stripe may pass on Data Source fees
In addition to the Marks license in Section 5.3 of the General Terms (not supplied), the User grants Stripe and its Affiliates a worldwide, non-exclusive, non-transferable, royalty-free license during the Term to use its and its Affiliates' Marks to identify the User to Connections End Users as a recipient of the Financial Connections Services, and to sublicense those Marks to Data Sources, the entities that provide financial account information to Stripe. If a Data Source imposes fees, charges or assessments on Stripe that are necessary to provide the Services, Stripe reserves the right to pass them on to the User.
Supporting quotations
2.6 Marks Usage.
In addition to the license User grants to Stripe in Section 5.3 of the General Terms, User grants to Stripe and its Affiliates a worldwide, non-exclusive, non-transferable, royalty-free license during the Term to (a) use Marks belonging to User or User’s Affiliates to identify User to the Connections End User as a recipient of the Stripe Financial Connections Services; and (b) sublicense those Marks to Data Sources.
2.7 Passthrough Fees.
If any Data Source imposes fees, charges, or assessments on Stripe that are necessary for Stripe to provide the Stripe Financial Connections Services, Stripe reserves the right to pass on to User those fees, charges, or assessments.
“Data Source” means an entity that provides financial account information to Stripe.
Qualifications & exceptions
The license lasts for the Term and may be sublicensed to Data Sources.
Passthrough is limited to Data Source charges necessary for Stripe to provide the Services.
Not stated here
Any passthrough amounts are not stated.
Retention & Deletion · User right or choice
Connections Data duties outlive the Agreement; you may request the data, verify only, or get identifiers when leaving
The User's obligations under Section 3 continue after the Term and survive termination. The User may request to receive Connections Data as part of the Services, but if it uses only the verification portion it receives none. When the User stops using the Stripe Payments Services, it may ask Stripe for the account identifiers of each Connections End User's financial account used to process transactions via the Approved Payment Network (the ACH Network under the US Regional Terms, or ACSS under the Canadian ones) as part of its use of Stripe Payments.
Supporting quotations
3. Connections Data.
User’s obligations under this Section 3 will continue after the Term, and this Section 3 will survive termination of this Agreement.
3.1 Receiving Connections Data.
User may request to receive Connections Data as part of the Stripe Financial Connections Services. However, if User chooses to use only the verification services portion of the Financial Connections Services, User will not receive Connections Data. When User stops using Stripe Payments Services, User may request that Stripe provide to User the account identifiers of each Connections End User’s financial account used to process transactions made via the Approved Payment Network as part of User’s use of Stripe Payments Services.
“Approved Payment Network” means the ACH Network.
“Approved Payment Network” means the ACSS.
Qualifications & exceptions
Section 3 survives termination.
Verification-only use yields no Connections Data.
Not stated here
Which Approved Payment Network definition applies depends on the User's Regional Terms.
Sharing & Disclosure · Restriction or exception
Share Connections Data only with service providers bound to equivalent obligations and only for the Authorized Purpose
The User may share Connections Data only with its service providers whose agreements impose obligations consistent with these Financial Connections Terms and Section 4 of the General Terms, and only for providing services that implement the Authorized Purpose. The User is responsible for its service providers' acts and omissions, including their compliance with the Agreement.
Supporting quotations
User may only share Connections Data with User’s service providers (a) whose agreement with User imposes on that service provider obligations consistent with those contained in these Stripe Financial Connections Terms and Section 4 of the General Terms; and (b) for the purpose of providing services to User that implement the Authorized Purpose. User is responsible for User’s service providers’ acts and omissions, including their compliance with this Agreement.
Qualifications & exceptions
Both conditions must hold: contractual flow-down of obligations and a purpose limited to the Authorized Purpose.
Not stated here
Section 4 of the General Terms is not supplied.
Use & Processing · Restriction or exception
Never use account data without the person’s Express Consent, sell it, share it for marketing, or use it unlawfully
The User must not, and must not enable or allow any third party to, use a Connections End User's Connections Data in any way without an appropriate Express Consent from that person; sell any Connections Data; share it, including with any third party for use in marketing or for the third party's marketing purposes; or use or transfer it for fraudulent purposes or otherwise in violation of Law.
Supporting quotations
3.3 Using Connections Data.
User must not, and must not enable or allow any third party to:
use a Connections End User’s Connections Data in any way if User has not obtained an appropriate Express Consent from the applicable Connections End User
sell any Connections Data
share the Connections Data, including with any third party for use in marketing or for the third party’s marketing purposes
use or transfer the Connections Data for fraudulent purposes or otherwise in violation of Law.
Qualifications & exceptions
The prohibitions extend to enabling or allowing third parties to do these things.
Use & Processing · Restriction or exception
Stripe is not a consumer reporting agency; do not use account data as or to build a consumer report without approval
Stripe is not a consumer reporting agency as defined in the FCRA, which these terms define as the Fair Credit Reporting Act and the Equal Credit Opportunity Act, both cited as 15 U.S.C. Section 1681 et seq. (external statutes cited by name only). Except as Stripe's authorized representative approves, the User must not use Connections Data in any way as a consumer report or to generate a consumer report under the FCRA.
Supporting quotations
3.4 FCRA Compliance.
Stripe is not a consumer reporting agency as defined in the FCRA. Except as Stripe’s authorized representative approves, User must not use any Connections Data (a) in any way as a consumer report; or (b) to generate a consumer report under FCRA.
“FCRA” means Fair Credit Reporting Act, 15 U.S.C. Section 1681, et seq. and Equal Credit Opportunity Act, 15 U.S.C. Section 1681, et seq.
Qualifications & exceptions
Consumer-report use is allowed only with approval from Stripe's authorized representative.
The statutory citation is external; the definition's citation of the same section for both Acts is reproduced as written.
Use & Processing · Company practice
Stripe acts as your processor for account data and separately asks end users to let it use the data as its own
Stripe, and any third party it engages, acts as the User's processor (service provider) in facilitating the User's access to Connections Data. In addition, through the Financial Connections Services Stripe asks Connections End Users for consent to separately collect, use, retain, disclose and process their Connections Data as an independent controller under the Stripe Consumer Terms of Service (the terms for End Users' use of Stripe's End User Services, linked) and Stripe's Privacy Policy. 'End User' and 'End User Service' take their meanings from the Privacy Policy and the Consumer Terms respectively.
Supporting quotations
3.5 Stripe as a Service Provider and Independent Controller.
Stripe, and any third party Stripe engages, will act as User’s processor (e.g., service provider) for the purposes of facilitating User’s access to Connections Data. In addition, Stripe will request, through the Stripe Financial Connections Services, consent from Connections End Users for Stripe to separately collect, use, retain, disclose, and process Connections Data as an independent controller of that data under the
“Stripe Consumer Terms of Service” means the terms that apply to an End User’s use of Stripe’s End User Services located at
“End User” has the meaning given to it in Stripe’s Privacy Policy.
“End User Service” has the meaning given to it in the Stripe Consumer Terms of Service.
Qualifications & exceptions
Stripe wears two hats: processor for the User and independent controller under its own consumer terms.
The Stripe Consumer Terms of Service and Privacy Policy are linked, not supplied.
Not stated here
What Stripe does with the data as independent controller is governed by its Privacy Policy, not this document.
Security & Safeguards · Procedure
The Security Addendum binds you as Financial Provider Terms; give Stripe end-user contacts for notices; report bad data
The User must comply with the Financial Connections Security Addendum attached at the end of these terms for its collection, use or disclosure of Connections Data; the Addendum counts as Financial Provider Terms, so it prevails over conflicting Agreement provisions. If Stripe wants to notify Connections End Users, for example for a legally required data-subject notification or a change to its consumer terms or Privacy Policy, the User must on request promptly provide their contact information including email addresses. If the User identifies or suspects that Connections Data it received is inaccurate, it must promptly notify Stripe at fc-intake@stripe.com.
Supporting quotations
3.6 Data Security Requirements.
User must comply with the terms of the Financial Connections Security Addendum attached at the end of these Stripe Financial Connections Terms with respect to User’s collection, use, or disclosure of any Connections Data, and those terms are considered Financial Provider Terms for the purposes of this Agreement.
3.7 Connections End User Notifications.
If Stripe wishes to send a notice to Connections End Users (e.g., because Stripe believes that Law requires a data subject notification, or because Stripe modifies its legal terms that apply to Connections End Users, including its Privacy Policy), then upon Stripe’s request, User must promptly provide Connections End Users’ contact information (including email addresses) to Stripe.
3.8 Notifications to Stripe.
If User identifies or suspects that the Connections Data received is inaccurate, User must promptly notify Stripe at fc-intake@stripe.com.
Qualifications & exceptions
The Security Addendum is treated as Financial Provider Terms.
Contact-sharing is triggered by Stripe's request for a notice to Connections End Users.
Not stated here
The Security Addendum's content is analyzed in later packets of this document.
Sharing & Disclosure · Company practice
Stripe may hand Data Sources your name, end-user names and consents, even onsite; answer requests within 14 days
To meet its obligations to Data Sources, Stripe may provide them the User's name, the names of Connections End Users associated with that source, all Express Consents and related records and other information the User provided under Section 4, and may, with the User's reasonable cooperation, obtain and verify that information onsite at the User's premises. The User must respond to Stripe's information requests under these terms within 14 days; failing that, Stripe may suspend or terminate access to the Financial Connections Services immediately. Section 4 survives termination.
Supporting quotations
4. Cooperation and Audit.
4.1 Stripe May Provide Data to Data Sources.
To comply with Stripe’s obligations to Data Sources, Stripe may (a) provide the following to Data Sources: (i) User’s name; (ii) any Connections End User’s name associated with that Data Source; (iii) all Express Consents and related records; (iv) all other information User provided to Stripe under this Section 4; and (b) with User’s reasonable cooperation, obtain and verify the information required under this Section 4.1 onsite at User’s premises.
4.2 Responses.
User must respond to Stripe’s requests for information under these Stripe Financial Connections Terms no later than 14 days after Stripe’s request. Stripe may suspend or terminate User’s access to the Stripe Financial Connections Services immediately if User fails to timely provide this information to Stripe.
4.3 Survival.
This Section 4 will survive termination of this Agreement.
Qualifications & exceptions
Onsite verification requires the User's reasonable cooperation.
The 14-day response deadline carries an immediate suspension or termination remedy.
Legal Rights & Agreement Rules · Context
Financial Connections definitions: Connections Data and End User, Data Source, Express Consent, FCRA, Consumer Terms
Section 5 defines the terms. 'Connections Data' is financial-account data from Data Sources that Stripe provides to the User, such as account identifiers, ownership, balance and transactions. A 'Connections End User' is an End User whose data the User seeks; 'End User' takes the Privacy Policy's meaning and 'End User Service' the Consumer Terms' meaning. A 'Data Source' provides financial account information to Stripe. 'Express Consent' is the end user's express, informed, opt-in consent for the Authorized Purpose, obtained through the 'Express Consent UI'. 'FCRA' means the Fair Credit Reporting Act and Equal Credit Opportunity Act, cited as 15 U.S.C. Section 1681 et seq. The 'Stripe Consumer Terms of Service' are Stripe's linked terms for End Users. The Financial Connections Services definition follows in the next packet.
Supporting quotations
5. Definitions.
“Connections Data” means data associated with a Connections End User’s financial account that Stripe provides to User through the Stripe Financial Connections Services
“Connections End User” means an End User whose Connections Data User requests to access, collect, use, and process in connection with the Stripe Financial Connections Services.
“Data Source” means an entity that provides financial account information to Stripe.
“End User” has the meaning given to it in Stripe’s Privacy Policy.
“End User Service” has the meaning given to it in the Stripe Consumer Terms of Service.
“Express Consent” means a Connections End User’s express, informed, opt-in consent to User’s collection, use, disclosure, and processing of that Connections End User’s Connections Data for the Authorized Purpose.
“Express Consent UI” means the user interface, including the text and consent mechanism included on that user interface, through which User obtains Express Consents.
“FCRA” means Fair Credit Reporting Act, 15 U.S.C. Section 1681, et seq. and Equal Credit Opportunity Act, 15 U.S.C. Section 1681, et seq.
“Stripe Consumer Terms of Service” means the terms that apply to an End User’s use of Stripe’s End User Services located at
Legal Rights & Agreement Rules · Restriction or exception
Financial Connections Services verify end users' accounts with optional data; the Regional Terms override on conflict
The 'Stripe Financial Connections Services' are the Services that let the User verify End User financial accounts, with the option to receive Connections Data. Section 6 sets out Regional Terms for listed countries and regions; where a Regional Term conflicts with the Financial Connections Terms, the Regional Term prevails.
Supporting quotations
“Stripe Financial Connections Services” means the Services that enable User to verify End User financial accounts and the option to receive Connections Data.
6. Regional Terms.
The following Regional Terms apply for the countries or regions below. If there is a conflict between the Stripe Financial Connections Terms and the Regional Terms, the Regional Terms prevail.
Qualifications & exceptions
Regional Terms prevail only to the extent of a conflict.
Sharing & Disclosure · Restriction or exception
United States: Stripe is a GLBA service provider for Financial Institutions; Section 1033 data holders sign access terms
For Users in the United States, if the User is a Financial Institution as defined in the Gramm-Leach-Bliley Act (15 U.S.C. Sections 6802-6809, an external statute cited by name), Stripe acts as the User's service provider under GLBA for accessing and sharing Connections Data with it. If the User controls Connections End User data covered by rules implementing Section 1033 of the Consumer Financial Protection Act of 2010 (also external), then on Stripe's reasonable request the User must enter into an agreement with Stripe enabling Stripe and its Data Sources to access and use that data for uses the End User approves.
Supporting quotations
United States.
The following Regional Terms apply for Users in the United States.
6.1 US Financial Institution Users.
If User is a Financial Institution, Stripe will act as User's service provider under GLBA for the purpose of accessing and sharing Connections Data with User.
6.2 Consumer Data Access.
If User controls any Connections End User data covered by rules implementing Section 1033 of the Consumer Financial Protection Act of 2010, then upon Stripe's reasonable request, User will enter into an agreement with Stripe to enable Stripe and its Data Sources to access and use that Connections End User data for uses approved by the End User.
"Financial Institution" has the meaning given to it in the GLBA.
"GLBA" means Gramm-Leach Bliley Act, 15 U.S.C. Sections 6802-6809.
Qualifications & exceptions
Applies to Users in the United States.
The Section 1033 agreement duty is triggered by Stripe's reasonable request and limited to end-user-approved uses.
Not stated here
The GLBA and Section 1033 are cited by name; their text and implementing rules are not supplied.
Legal Rights & Agreement Rules · Context
United States definitions: the Approved Payment Network is the Nacha-run ACH Network; Financial Institution and GLBA
For Users in the United States, the 'ACH Network' is the automated clearinghouse payment network that Nacha's member organizations control and manage, and it is the 'Approved Payment Network'. 'Financial Institution' takes its meaning from the GLBA, defined as the Gramm-Leach Bliley Act, 15 U.S.C. Sections 6802-6809.
Supporting quotations
6.3 Definitions.
"ACH Network" means the automated clearinghouse payment network that the member organizations of Nacha control and manage.
“Approved Payment Network” means the ACH Network.
"Financial Institution" has the meaning given to it in the GLBA.
"GLBA" means Gramm-Leach Bliley Act, 15 U.S.C. Sections 6802-6809.
Qualifications & exceptions
Applies to Users in the United States.
Legal Rights & Agreement Rules · Context
Canada definitions: the Approved Payment Network is the ACSS run by Payments Canada; Financial Institution defined
For Users in Canada, the 'ACSS' is the Automated Clearing Settlement System operated by Payments Canada (the Canadian Payments Association's operating name, running the national clearing and settlement infrastructure under the Canadian Payments Act) that clears and settles payment items including pre-authorized debits, and it is the 'Approved Payment Network'. A 'Financial Institution' is a bank, trust company, loan company, credit union, caisse populaire or other institution regulated under Canadian federal or provincial Law, including the Bank Act and the Trust and Loan Companies Act.
Supporting quotations
Canada.
The following Regional Terms apply for Users in Canada.
6.1 Definitions.
"ACSS" means the Automated Clearing Settlement System, the electronic clearing and settlement system operated by Payments Canada that facilitates the clearing and settlement of payment items, including pre-authorized debits.
“Approved Payment Network” means the ACSS.
"Financial Institution" means a bank, trust company, loan company, credit union, caisse populaire, or other financial institution that is federally or provincially regulated under Canadian Law, including under the Bank Act (S.C. 1991, c. 46), the Trust and Loan Companies Act (S.C. 1991, c. 45), or applicable provincial legislation.
"Payments Canada" means Payments Canada, the operating brand name of the Canadian Payments Association, and the organization responsible for the clearing and settlement infrastructure for payments in Canada, operating under the Canadian Payments Act.
Qualifications & exceptions
Applies to Users in Canada.
The Canadian statutes are cited by name; their text is not supplied.
Security & Safeguards · Context
The Security Addendum sets data-security duties that last as long as you hold or control any Connections Data
The Financial Connections Security Addendum, last modified April 20, 2026, applies to users of the Financial Connections Service and sets out data security requirements for the User's collection, use or disclosure of Connections Data for as long as the User possesses or controls that data. Its Regional Terms in Section 4 apply by the User's Stripe Account Country, and undefined terms take their meaning from the Stripe Services Agreement.
Supporting quotations
Financial Connections Security Addendum
Last modified: April 20, 2026
This Financial Connections Security Addendum (“Security Addendum”) applies to users of the Stripe Financial Connections Service. This Security Addendum sets out data security requirements relating to User’s collection, use or disclosure of any Connections Data for as long as User possesses or controls the Connections Data. The Regional Terms in Section 4 (Regional Terms) of this Security Addendum apply based on User's Stripe Account Country.
Qualifications & exceptions
Duties persist for as long as the User possesses or controls Connections Data, independent of the Agreement's term.
Under Section 3.6 of the Financial Connections Terms the Addendum counts as Financial Provider Terms.
Security & Safeguards · Procedure
You must run a comprehensive, risk-appropriate security program that keeps account data secure, confidential and lawful
The User must develop, implement, maintain and enforce a comprehensive information security program with administrative, technical and physical safeguards appropriate to its business risk and the sensitivity of the Connections Data it holds. The program must be designed to maintain data integrity and keep Connections Data secure and confidential, protect against anticipated threats to its security or integrity, and prevent unauthorized access or use that could substantially harm or inconvenience an End User, taking account of evolving technologies and threats with protection commensurate with the risks. It must also comply with all Laws applicable to the User's collection, use, retention or disclosure of Connections Data.
Supporting quotations
1. Obligation to maintain a Security Program
1.1 General.
User must develop, implement, maintain and enforce a comprehensive information security program, including administrative, technical, and physical safeguards appropriate to the nature and risk of User’s business activities and the sensitivity of the Connections Data in User’s possession or control (“Security Program”).
1.2 Security Program Objectives.
User must design the Security Program in a manner that achieves the following objectives: (a) maintaining data integrity and ensuring the Connections Data is kept secure and confidential; (b) protecting against any anticipated threats or hazards to the security or integrity of Connections Data; and (c) preventing Connections Data from any unauthorized access or use that could result in substantial harm or inconvenience to an End User. User must take into account evolving technologies and the changing threat landscape while providing a level of protection commensurate with the risks associated with the Connections Data.
1.3 Compliance with Law.
User must ensure that the Security Program complies with any Laws applicable to User’s collection, use, retention or disclosure of the Connections Data.
Qualifications & exceptions
Safeguards must be proportionate to the User's business risk and the data's sensitivity, and keep pace with evolving threats.
Security & Safeguards · Procedure
Your security program must assess risk, encrypt data in transit and at rest, delete data once unneeded, and test systems
Without limiting the general duty, the Security Program must address how the User will periodically assess the program's adequacy and the risks to Connections Data; protect all Connections Data in transit over external networks and at rest with encryption no less protective than industry standards; delete Connections Data where Law requires or, otherwise, reasonably promptly and as far as feasible once it is no longer needed for the Authorized Purpose, legitimate business operations or legal compliance; and perform periodic vulnerability assessments and penetration testing on systems that store or process Connections Data. Further requirements continue in the next packet.
Supporting quotations
2. Security Program Requirements.
Without limiting the foregoing, User’s Security Program must address how User will perform the following:
Periodically assess (A) the adequacy of the Security Program and (B) risks related to the security of Connections Data
Protect all Connections Data, both in transit over external networks and at rest, via secure encryption techniques no less protective than industry security standards
Delete Connections Data (A) where required by Law, or (B) if deletion is not required by Law, reasonably promptly, and to the extent reasonably feasible, once retention of the Connections Data is not necessary for any of the following purposes: (1) the Authorized Purpose, (2) business operations or other legitimate business purposes, or (3) compliance with Law
Perform periodic vulnerability assessments and penetration testing on systems where Connections Data is stored or otherwise processed
Qualifications & exceptions
Deletion is required by Law where applicable, and otherwise once none of the three retention grounds remains.
Not stated here
No specific encryption standard or testing frequency is named.
Security & Safeguards · Procedure
Vet and bind providers, restrict access, monitor and log, patch promptly, store data only where approved, insure, screen
The Security Program must also address overseeing service providers, including cloud providers, that access Connections Data, by selecting and retaining ones capable of appropriate safeguards and contractually requiring measures consistent with the Addendum; maintaining reasonable access controls so only authorized people with a business need can access the data; monitoring systems storing it for unauthorized access and logging suspected incidents; patching vulnerabilities in a timely fashion; storing Connections Data only within the Approved Storage Jurisdictions unless Stripe agrees in advance in writing; maintaining insurance reasonable for the risk of handling the data; and, to the extent Law permits, running appropriate background checks on personnel who will access unencrypted Connections Data.
Supporting quotations
Oversee any of User’s service providers (including cloud providers) who access Connections Data by taking reasonable steps to select and retain service providers that are capable of maintaining appropriate safeguards for the Connections Data and contractually requiring those service providers to implement and maintain appropriate security measures for the Connections Data that are consistent with the terms of this Security Addendum
Maintain reasonable access controls to ensure that only authorized individuals that have a business need for accessing Connections Data are able to access Connections Data
Monitor User’s systems that store Connections Data for any unauthorized access and log any suspected unauthorized access
Patch vulnerabilities in a timely fashion
Store Connections Data only within the Approved Storage Jurisdictions, unless Stripe agrees in advance in writing
Maintain a level of insurance that is reasonable based on the risk associated with User’s collection, use, retention and disclosure of Connections Data
To the extent permitted by Law, conduct appropriate background checks of personnel who will receive access to unencrypted Connections Data.
Qualifications & exceptions
Storage outside the Approved Storage Jurisdictions requires Stripe's advance written agreement.
Background checks are required only to the extent Law permits and for staff with access to unencrypted data.
Not stated here
What level of insurance is 'reasonable' is not specified.
Security & Safeguards · Procedure
Tell Stripe immediately of any unauthorized access, loss, use, disclosure or modification of Connections Data
The User must notify Stripe immediately at fc-intake@stripe.com if it becomes aware of any unauthorized access to or loss of Connections Data held by it or any of its service providers, or any unauthorized use, disclosure or modification of Connections Data by it or its service providers.
Supporting quotations
3. Data Incident Notification.
User must notify Stripe immediately at fc-intake@stripe.com if User becomes aware of any unauthorized (a) access to or loss of Connections Data in User’s or any of User’s service providers’ possession or control; and (b) use, disclosure or modification of Connections Data by User or any of User’s service providers.
Qualifications & exceptions
The duty covers incidents at the User's service providers as well as its own.
Security & Safeguards · Restriction or exception
Addendum Regional Terms prevail; United States users must meet the GLBA Safeguards Rule and store data only in the US
The Addendum's Regional Terms apply by country and prevail over the Addendum on conflict. For Users in the United States, the Security Program must comply with the GLBA Safeguards Rule (16 CFR Part 314), if applicable, and the Approved Storage Jurisdictions are the fifty U.S. states and the District of Columbia.
Supporting quotations
4. Regional Terms.
The following Regional Terms apply to the Security Addendum for the countries or regions below. If there is a conflict between the Security Addendum and these Regional Terms, these Regional Terms prevail.
United States.
The following Regional Terms apply for Users in the United States.
4.1 GLBA Safeguards Rule.
User must ensure that the Security Program complies with the GLBA Safeguards Rule (16 CFR Part 314), if applicable.
4.2 Definitions.
“Approved Storage Jurisdictions” means the fifty (50) states of the U.S. and the District of Columbia.
Qualifications & exceptions
Applies to Users in the United States.
The Safeguards Rule duty applies 'if applicable'; the regulation is cited by name, not supplied.
Security & Safeguards · Restriction or exception
Canada: Connections Data may be stored in Canada, the 50 U.S. states or the District of Columbia
For Users in Canada, the Approved Storage Jurisdictions under the Security Addendum are Canada, the fifty U.S. states and the District of Columbia. A 'Back to Top' link closes the Financial Connections Terms and Addendum.
Supporting quotations
Canada.
The following Regional Terms apply for Users in Canada.
4.1 Definitions.
“Approved Storage Jurisdictions” means Canada, the fifty (50) states of the U.S. and the District of Columbia.
Qualifications & exceptions
Applies to Users in Canada.
Legal Rights & Agreement Rules · Context
The Global Payouts Fiat Terms cover fiat payments from your Financial Account to third parties, not stablecoins
The Stripe Global Payouts Fiat Terms, last modified April 24, 2026, supplement the General Terms, the Financial Services Terms and the Stripe Treasury Terms and govern the Stripe Global Payouts Fiat Services, which let the User make fiat-currency Outbound Payments (payments from its Financial Account to a Recipient, a third party in a Transaction Territory). They cover only fiat Outbound Payments; stablecoin or other digital-asset exchange, custody, transmission or payout is governed by the Stablecoin Treasury Terms, Global Payouts Stablecoin Terms and Stablecoin Partner Terms. When Stripe makes an Outbound Payment to a Recipient on the User's behalf, no direct relationship arises between Stripe and the Recipient. Undefined terms come from the General, Financial Services or Treasury Terms.
Supporting quotations
Stripe Global Payouts Fiat
Last modified: April 24, 2026
1. Global Payouts Services.
1.1 Operation of These Terms.
These terms (“Stripe Global Payouts Fiat Terms”) supplement the General Terms, the Stripe Financial Services Terms, and the Stripe Treasury Terms, and govern the use of the Stripe Global Payouts Fiat Services. For the avoidance of doubt, these Stripe Global Payouts Fiat Terms are limited to fiat currency Outbound Payments and do not govern the exchange, custody, transmission, or payout of Stablecoin or any other digital asset, which are governed by the Stripe Stablecoin Treasury Terms, the Stripe Global Payouts Stablecoin Terms, and the Stablecoin Partner Terms, as applicable.
1.2 Description of Global Payouts Fiat Services.
The Stripe Global Payouts Fiat Services enable User to make fiat currency Outbound Payments. When Stripe makes an Outbound Payment to a Recipient on User’s behalf, it does not create any direct relationship between Stripe and the Recipient.
“Stripe Global Payouts Fiat Services” means the Services that enable User to make fiat currency Outbound Payments from User's Financial Account to Recipients.
“Outbound Payment” means a fiat currency payment from the Financial Account to a Recipient.
“Recipient” means a third party located in a Transaction Territory, that receives a fiat currency payment or transfer from User's Financial Account.
Qualifications & exceptions
Limited to fiat currency; digital assets fall under the stablecoin terms.
Recipients have no direct relationship with Stripe.
Charges & Financial Obligations · Company practice
Payout count and value limits may apply; Stripe may exceed, cut or change them at its discretion, usually without notice
There may be limits on the number and value of Outbound Payments the User can make from its Financial Account, described in the Dashboard or otherwise communicated by Stripe. Stripe may at its discretion allow payments exceeding the limits, or temporarily reduce them without notice unless the Financial Account Regulatory Requirements require otherwise, and may change the limits at any time in its sole discretion.
Supporting quotations
2. Transaction Limits.
There may be limits on the number and value of Outbound Payments that User can make from User’s Financial Account, which, if applicable, are described on the Stripe Dashboard or otherwise communicated to User by Stripe. Stripe, in its discretion, may allow Outbound Payments that exceed applicable limits or temporarily reduce User’s limits from time to time without notice, unless the Financial Account Regulatory Requirements require otherwise. Stripe may change the limits at any time, in its sole discretion.
Qualifications & exceptions
Reductions without notice are subject to the Financial Account Regulatory Requirements.
Not stated here
The limit amounts are in the Dashboard, not stated here.
Sharing & Disclosure · Procedure
Your contracts with payees must link Stripe’s Privacy Policy and name Stripe as your payment provider processing data
The User must include in any applicable contracts with its Recipients a link to Stripe's Privacy Policy and state that it uses Stripe as its payment services provider and that Stripe processes Recipients' data under that policy. The Fiat Terms' single definition names the Stripe Global Payouts Fiat Services as the Services for fiat Outbound Payments to Recipients; a 'Back to Top' link closes the terms.
Supporting quotations
3. Privacy Policies.
User must include, in any applicable contracts between User and User’s Recipients, a link to Stripe’s Privacy Policy, and state that User uses Stripe as User’s payment services provider and that Stripe processes Recipients’ data in accordance with its Privacy Policy.
4. Definitions.
“Stripe Global Payouts Fiat Services” means the Services that enable User to make fiat currency Outbound Payments from User's Financial Account to Recipients.
Qualifications & exceptions
Applies to applicable contracts between the User and its Recipients.
Not stated here
Stripe's Privacy Policy is not supplied.
Legal Rights & Agreement Rules · Context
The Global Payouts Stablecoin Terms (Preview) govern Stripe’s interface for telling a Stablecoin Partner to pay out
The Stripe Global Payouts Stablecoin Terms, last modified September 28, 2026, supplement the General Terms and incorporate the Financial Services Terms, the Stripe Treasury Terms and the Stripe Stablecoin Treasury Terms by reference. They govern the Stripe Global Payouts Stablecoin Services: the user interface, data transmission and related technology Stripe provides so the User can instruct a Stablecoin Partner to complete Stablecoin Payout Transactions. The Services are Preview Services. Undefined terms come from the General Terms or Financial Services Terms.
Supporting quotations
Stripe Global Payouts Stablecoin (Preview)
Last modified: September 28, 2026
1. Operation of These Terms.
These terms ("Stripe Global Payouts Stablecoin Terms") supplement the General Terms and, together with the Stripe Financial Services Terms, the Stripe Treasury Terms, and the Stripe Stablecoin Treasury Terms, each of which is incorporated into these Stripe Global Payouts Stablecoin Terms by this reference, govern User's use of the Stripe Global Payouts Stablecoin Services. Capitalized terms that are not defined in these terms have the same meanings given to them in the General Terms or the Stripe Financial Services Terms. The Stripe Stablecoin Global Payouts Stablecoin Services are Preview Services.
"Stripe Global Payouts Stablecoin Services" means the user interface, data transmission, and related technology services that Stripe provides to enable User to instruct the Stablecoin Partner to complete Stablecoin Payout Transactions.
Qualifications & exceptions
The Services are expressly Preview Services.
Stripe's product here is an interface; the stablecoin services themselves belong to the Stablecoin Partner.
Not stated here
What Preview status entails is governed by the General Terms, not supplied.
Charges & Financial Obligations · Context
Payouts are fiat-funded or direct from your wallet; Stripe only moves fiat or relays instructions, never holds coins
The Services let the User initiate Stablecoin Payout Transactions as Fiat-Funded Stablecoin Payouts, where Stripe transfers fiat from the User's Financial Account to the User's account with the Stablecoin Partner, which exchanges it for Stablecoin and sends it to the recipient's Designated Wallet, or as Direct Stablecoin Payouts, where the User instructs the Partner through Stripe's interface to send Stablecoin from the User's Stablecoin Partner Wallet to the recipient's wallet. For fiat-funded payouts Stripe's role is limited to moving the fiat; for direct payouts it is limited to providing the interface. Stripe creates no direct relationship with the Stablecoin Payout Recipient and does not hold, custody, transmit or pay out any Stablecoin. All stablecoin exchange, custody and payout services are performed solely by the Stablecoin Partner under its own terms. These terms govern transactions initiated through Stripe's interface; transactions the User initiates directly with the Partner outside it are governed solely by the Stablecoin Partner Terms.
Supporting quotations
2. Stripe Global Payouts Stablecoin Services.
2.1 Description of Services.
The Stripe Global Payouts Stablecoin Services enable User to initiate Stablecoin Payout Transactions as either Fiat-Funded Stablecoin Payouts or Direct Stablecoin Payouts. In the case of Fiat-Funded Stablecoin Payouts, Stripe's role is limited to facilitating the transfer of fiat currency from User's Financial Account to User’s account with the Stablecoin Partner. In the case of Direct Stablecoin Payouts, Stripe's role is limited to providing the technology interface through which User issues the payout instruction to the Stablecoin Partner. Stripe does not create any direct relationship between Stripe and the Stablecoin Payout Recipient, nor does Stripe hold, custody, transmit, or pay out any Stablecoin as part of any Stablecoin Payout Transaction.
2.2 Stablecoin Partner.
All Stablecoin services, including exchange, custody, and payout services are performed solely by the Stablecoin Partner under the Stablecoin Partner Terms. These Stripe Global Payouts Stablecoin Terms govern all Stablecoin Payout Transactions that User initiates through the Stripe Global Payouts Stablecoin Services, whether as a Fiat-Funded Stablecoin Payout or a Direct Stablecoin Payout. Stablecoin Payout Transactions that User initiates directly with the Stablecoin Partner outside of the Stripe Global Payouts Stablecoin Services interface are not governed by these Stripe Global Payouts Stablecoin Terms and are subject solely to the applicable Stablecoin Partner Terms.
"Direct Stablecoin Payout" means a Stablecoin Payout Transaction initiated by User through the Stripe Global Payouts Stablecoin Services by which User instructs the Stablecoin Partner, through Stripe's interface, to transmit Stablecoin directly from User's Stablecoin Partner Wallet to a Stablecoin Payout Recipient's Designated Wallet.
"Fiat-Funded Stablecoin Payout" means a Stablecoin Payout Transaction initiated by User through the Stripe Global Payouts Stablecoin Services by which (a) Stripe transfers fiat currency from User's Financial Account to User’s account with the Stablecoin Partner; and (b) the Stablecoin Partner exchanges that fiat currency for Stablecoin and transmits the Stablecoin to a Stablecoin Payout Recipient's Designated Wallet.
"Stablecoin Payout Transaction" means either a Fiat-Funded Stablecoin Payout or a Direct Stablecoin Payout, as applicable.
"Stablecoin Payout Recipient" means a recipient designated by User to receive Stablecoin in connection with a Stablecoin Payout Transaction via a Designated Wallet.
"Designated Wallet" means a cryptocurrency wallet address designated by User or a Stablecoin Payout Recipient to receive Stablecoin in connection with a Stablecoin Payout Transaction.
Qualifications & exceptions
Stripe never holds, custodies, transmits or pays out Stablecoin.
Transactions made directly with the Stablecoin Partner outside Stripe's interface fall outside these terms.
Not stated here
The Stablecoin Partner Terms are external and not supplied.
Charges & Financial Obligations · Restriction or exception
Fund fiat payouts from your Financial Account and direct payouts from your wallet; Stripe’s duty ends on handoff
A Fiat-Funded Stablecoin Payout may be funded only with fiat held in the User's Financial Account under the Stripe Treasury Terms, and the User must keep enough there to cover each payout; Stripe deducts the amount from the Available Balance when it transfers the funds to the Stablecoin Partner, at which point its obligations for that payout are fully satisfied. A Direct Stablecoin Payout is funded solely from Stablecoin in the User's Stablecoin Partner Wallet, which the User must keep sufficiently funded; Stripe's role ends once the User issues the instruction through the interface. For all Stablecoin Payout Transactions, Stripe is not responsible for the Partner's exchange rate, the amount of Stablecoin delivered or the timing of delivery to the Designated Wallet.
Supporting quotations
2.3 Funding Stablecoin Payout Transactions.
A Fiat-Funded Stablecoin Payout may only be funded through fiat currency funds held in User's Financial Account, which is governed by the Stripe Treasury Terms, and User must maintain sufficient funds in User's Financial Account to cover each payout. For each Fiat-Funded Stablecoin Payout, Stripe will deduct the fiat currency amount from User's Financial Account Available Balance at the time Stripe transfers those funds to the Stablecoin Partner, at which point Stripe's obligations with respect to that Fiat-Funded Stablecoin Payout are satisfied in full.
With respect to all Stablecoin Payout Transactions, Stripe is not responsible for the exchange rate applied by the Stablecoin Partner (if any), the amount of Stablecoin delivered to a Stablecoin Payout Recipient, or the timing of delivery to the Designated Wallet.
Qualifications & exceptions
Stripe's obligations are satisfied at the moment of fiat transfer or instruction issuance, before the recipient receives anything.
Exchange rate, delivered amount and delivery timing are the Stablecoin Partner's domain.
Charges & Financial Obligations · Company practice
If a stablecoin payout fails, Stripe or the Partner may retry; if it still fails, the amount comes back net of fees
If a Stablecoin Payout Transaction is unsuccessful, the User authorizes Stripe or the Stablecoin Partner, as applicable, to retry it. If neither can complete it, Stripe notifies the User and the amount deducted, fiat from the Financial Account for a fiat-funded payout or Stablecoin from the Stablecoin Partner Wallet for a direct payout, is returned to the account it came from, subject to any applicable fees and the Stablecoin Partner Terms.
Supporting quotations
2.4 Retrying Stablecoin Payout Transactions.
If a Stablecoin Payout Transaction is unsuccessful, User authorizes Stripe or the Stablecoin Partner, as applicable, to retry the Stablecoin Payout Transaction. If Stripe or the Stablecoin Partner are not able to complete the Stablecoin Payout Transaction, Stripe will notify User and the amount deducted in connection with that transaction
will be returned to the account from which it was deducted, in each case subject to any applicable fees and the terms stated in the Stablecoin Partner Terms.
Qualifications & exceptions
Returns are subject to applicable fees and the Stablecoin Partner Terms.
Not stated here
Retry limits and timing are not stated.
Account & Service Control · Company practice
Stripe may restrict coins or payout types, suspend the Service, and refuse any payout for fraud, failed screening or Law
Stripe may add or restrict access to particular Stablecoin or fiat denominations or payout types at any time in its sole discretion, and may suspend or terminate access to the Service under the General Terms. It may also refuse any individual Stablecoin Payout Transaction at any time, including where it determines the User, a recipient or a Stablecoin Partner is engaged in fraudulent, unlawful, deceptive or abusive activity, where the Designated Wallet fails blockchain monitoring or compliance screening under Section 2.8, where the User lacks sufficient funds in its Financial Account or Stablecoin in its wallet, or for any reason Law permits or requires.
Supporting quotations
2.5 Stripe's Right to Restrict.
Stripe may add or restrict access to particular denominations of Stablecoin or fiat currency, or types of Stablecoin Payout Transactions, at any time in its sole discretion. Stripe may suspend or terminate User's access to the Stripe Global Payouts Stablecoin Services at any time in accordance with the General Terms. In addition to Stripe's right to restrict access to the Stripe Global Payouts Stablecoin Services generally, Stripe may refuse any individual Stablecoin Payout Transaction at any time, including if (a) Stripe determines that User, a Stablecoin Payout Recipient, or a Stablecoin Partner is engaged in any fraudulent, unlawful, deceptive, or abusive activity; (b) the Designated Wallet fails blockchain monitoring or compliance screening under Section 2.8; (c) User has insufficient funds in its Financial Account, or an insufficient Stablecoin balance in its Stablecoin Partner Wallet, as applicable; or (d) for any reason permitted or required by Law.
Qualifications & exceptions
Denomination and payout-type restrictions are at Stripe's sole discretion.
Refusal of individual payouts is 'including' the listed grounds, so not limited to them.
Legal Rights & Agreement Rules · Restriction or exception
Stripe disclaims outages, wrong wallet data, price swings and Partner failures; sent stablecoin cannot be recalled
To the extent Law permits, Stripe is not liable for losses from suspension, termination or interruption of the Service or the Stablecoin Partner Services; incorrect or incomplete Payout Information (the wallet address and recipient identity details required), including a wrong or invalid Designated Wallet; a payout failing because the wallet is incompatible with the Stablecoin; value fluctuations between initiation and delivery; the Stablecoin Partner rejecting, delaying or failing to complete a payout for any reason; the Partner's default, insolvency or bankruptcy; any act or omission of the Partner in exchange, custody, transmission or payout; an insufficient wallet balance at execution; or the irreversibility of any transaction, including stablecoin sent to a wrong or unintended wallet. Once the Stablecoin Partner has started transmitting Stablecoin to a Designated Wallet, the transaction cannot be amended, cancelled, reversed or recalled.
Supporting quotations
To the extent Law permits, Stripe is not liable to User for any losses, damages, or costs resulting from: (a) the suspension, termination, or interruption of the Stripe Global Payouts Stablecoin Services or the Stablecoin Partner Services; (b) User or any Stablecoin Payout Recipient providing incorrect or incomplete Payout Information, including an incorrect or invalid Designated Wallet address; (c) the failure of a Stablecoin Payout Transaction due to the Designated Wallet being incompatible with the Stablecoin being transmitted; (d) fluctuations in the value of Stablecoin between the time User initiates a Stablecoin Payout Transaction and the time the Stablecoin is delivered to the Designated Wallet; (e) the Stablecoin Partner rejecting, delaying, or failing to complete a Stablecoin Payout Transaction for any reason; (f) the Stablecoin Partner’s default, insolvency, or bankruptcy; (g) any act or omission of the Stablecoin Partner in connection with the exchange, custody, transmission, or payout of Stablecoin; (h) User's Stablecoin Partner Wallet having an insufficient Stablecoin balance to fund a Direct Stablecoin Payout at the time of execution; or (i) the irreversibility of any Stablecoin Payout Transaction, including where Stablecoin has been transmitted to an incorrect, invalid, or unintended Designated Wallet address. Stablecoin Payout Transactions cannot be amended, cancelled, reversed, or recalled once the Stablecoin Partner has initiated the transmission of Stablecoin to a Designated Wallet.
"Payout Information" means all information necessary to complete a Stablecoin Payout Transaction, including the Stablecoin Payout Recipient's Designated Wallet address and such identifying information about the Stablecoin Payout Recipient as Stripe or the Stablecoin Partner may require from time to time, including name, address, and government-issued identification.
Qualifications & exceptions
The disclaimer applies to the extent Law permits.
Irreversibility attaches from the moment the Partner initiates transmission.
Charges & Financial Obligations · Company practice
On a depeg, Stripe and the Partner may suspend the coin or continue at market rate, with no liability
A Depeg Event is any occurrence where Stripe or the Stablecoin Partner determines, in its sole discretion, that a Stablecoin's price has failed to hold its intended fiat peg. If one occurs, Stripe and the Partner may immediately suspend the Service for the affected Stablecoin or continue providing it at the prevailing Stablecoin-to-fiat market exchange rate. Stripe is not liable for losses from a Depeg Event, including any difference between the rate when the User initiated a payout and the rate at which the Partner executes the exchange, if it chooses to.
Supporting quotations
2.7 Depeg Event.
If a Depeg Event occurs with respect to any Stablecoin, Stripe and the Stablecoin Partner may immediately (a) suspend the Stripe Global Payouts Stablecoin Services with respect to the affected Stablecoin; or (b) continue providing the Stripe Global Payouts Stablecoin Services with respect to the affected Stablecoin at its prevailing Stablecoin-to-fiat market exchange rate. Stripe is not liable to User for any losses, damages, or costs arising from a Depeg Event, including any difference between the exchange rate applicable at the time User initiates a Stablecoin Payout Transaction and the rate at which the Stablecoin Partner executes the exchange, if it chooses to do so.
“Depeg Event” means any occurrence where Stripe or the Stablecoin Partner determines, in its sole discretion, that the price of a Stablecoin has failed to maintain its intended peg to the fiat value to which it is linked.
Qualifications & exceptions
Whether a Depeg Event has occurred is decided by Stripe or the Partner in sole discretion.
The response, suspension or market-rate continuation, is their choice.
Security & Safeguards · Company practice
Stripe or the Partner may screen wallets, delay payouts for review and reject risky wallets without liability
Stripe or the Stablecoin Partner may, at their discretion, run blockchain monitoring and screening on any Designated Wallet involved in a payout. If a wallet presents fraud, compliance, sanctions or other risk, they may perform a manual compliance review, which may delay the payout or the availability of funds in the User's Financial Account or Stablecoin in its wallet. They may reject any transfer to a wallet presenting excessive risk or where Law requires, and Stripe is not liable for losses from any delay or rejection resulting from this monitoring or screening.
Supporting quotations
2.8 Blockchain Monitoring and Compliance Screening.
Stripe or the Stablecoin Partner, in their discretion, may conduct blockchain monitoring and screening on any Designated Wallet in connection with a Stablecoin Payout Transaction. If Stripe or the Stablecoin Partner identifies a Designated Wallet as presenting fraud, compliance, sanctions, or other risk, then Stripe or the Stablecoin Partner, as applicable, may perform a manual compliance review of the Designated Wallet, which may cause delays in completing the Stablecoin Payout Transaction or the availability of funds in User's Financial Account, or the availability of Stablecoin in User’s Stablecoin Partner Wallet, or both. Stripe or the Stablecoin Partner, in their discretion, may reject any transfer to a Designated Wallet that presents an excessive risk, or if required by Law. Stripe is not liable to User for any losses, damages, or costs arising from any delay or rejection resulting from blockchain monitoring or compliance screening.
Qualifications & exceptions
Screening and rejection are discretionary; rejection is also mandatory where Law requires.
Sharing & Disclosure · Permission or license
You authorize sharing your and payees' personal data with the Partner and regulators, and must secure consents
The User authorizes Stripe and the Stablecoin Partner to share the User's Personal Data and that of Stablecoin Payout Recipients with each other and with relevant regulators, tax authorities and implicated digital asset service providers on an ongoing basis to meet their regulatory and tax obligations. The User must give each recipient the necessary notices and obtain the rights and consents enabling Stripe and the Partner to lawfully collect, use, retain and disclose recipients' Personal Data, including names, dates of birth, physical addresses, Designated Wallet addresses, contact information and government-issued identification numbers, as needed to process payouts. Stripe and the Partner may require additional Personal Data from the User or recipients at any time as a condition of continued access, and may temporarily suspend access pending receipt.
Supporting quotations
2.9 Stablecoin Payout Recipient Data.
User authorizes Stripe and the Stablecoin Partner to share User's Personal Data and the Personal Data of Stablecoin Payout Recipients with each other and with any relevant regulatory bodies, tax authorities or implicated digital asset service providers on an ongoing basis to meet their respective regulatory compliance and tax obligations. User must provide all necessary notices to, and obtain all necessary rights and consents from, each Stablecoin Payout Recipient sufficient to enable Stripe and the Stablecoin Partner to lawfully collect, use, retain, and disclose Stablecoin Payout Recipients' Personal Data, including their names, dates of birth, physical addresses, Designated Wallet addresses, contact information, and government-issued identification numbers, as necessary to process Stablecoin Payout Transactions. Stripe and the Stablecoin Partner may require additional Personal Data from User or Stablecoin Payout Recipients at any time as a condition to continued access to the Stripe Global Payouts Stablecoin Services, and may temporarily suspend access to the Stripe Global Payouts Stablecoin Services pending receipt of that information.
Qualifications & exceptions
Sharing is ongoing and for regulatory compliance and tax purposes.
Access may be suspended until requested additional Personal Data is provided.
Security & Safeguards · Procedure
You must report suspected fraud to Stripe at once and to authorities, and cooperate, or risk suspension
Stripe treats any actual or suspected unauthorized access or activity on the User's use of the Service as potentially fraudulent. The User must notify Stripe immediately on becoming aware of or suspecting such activity, promptly report it to the relevant legal authorities and give Stripe a copy of any report they prepare, and in any investigation cooperate fully with the authorities, the Stablecoin Partner and Stripe and complete required affidavits or statements promptly, accurately and thoroughly. Failure to cooperate may lead to suspension of access to the Service.
Supporting quotations
2.10 Potentially Fraudulent Activity.
Stripe will treat any actual or suspected unauthorized access or unauthorized activity associated with User's use of the Stripe Global Payouts Stablecoin Services as potentially fraudulent. User must notify Stripe immediately if User becomes aware of or suspects any potentially fraudulent activity in connection with the Stripe Global Payouts Stablecoin Services. User must promptly report any such activity to the relevant legal authorities and provide Stripe with a copy of any relevant report prepared by those authorities. In connection with any investigation of potentially fraudulent activity, User must (a) cooperate fully with the relevant legal authorities, the Stablecoin Partner, and Stripe; and (b) complete any required affidavits or statements promptly, accurately, and thoroughly. User's failure to cooperate in any such investigation may result in suspension of User's access to the Stripe Global Payouts Stablecoin Services.
Qualifications & exceptions
Both immediate notice to Stripe and a report to legal authorities are required.
Legal Rights & Agreement Rules · Restriction or exception
Stripe provides no payments or financial service to your stablecoin payees and need not answer their support requests
Stripe provides no payments service or other financial service to Stablecoin Payout Recipients in connection with the Stripe Global Payouts Stablecoin Services. The User is responsible for all its communications with recipients, and Stripe has no obligation to respond to recipients' communications or support requests.
Supporting quotations
2.11 Stripe Does Not Provide Services to Stablecoin Payout Recipients.
Stripe does not provide any payments service or other financial service to Stablecoin Payout Recipients in connection with the Stripe Global Payouts Stablecoin Services. User is responsible for all of User's communications with Stablecoin Payout Recipients, and Stripe is under no obligation to respond to communications or support requests from Stablecoin Payout Recipients.
Charges & Financial Obligations · Company practice
Payout limits appear on the Dashboard; Stripe may change or cut them without notice and the Partner may add its own
Limits may apply to the number and value of Stablecoin Payout Transactions and, if applicable, are described on the Stripe Dashboard or otherwise communicated by Stripe or the Stablecoin Partner. Limits may apply separately to Fiat-Funded Stablecoin Payouts and Direct Stablecoin Payouts. Stripe may at its discretion allow transactions over the limits or temporarily reduce the User's limits without notice unless Law requires otherwise, and may change its limits at any time in its sole discretion. The Stablecoin Partner may independently impose additional limits under the Stablecoin Partner Terms.
Supporting quotations
3. Transaction Limits.
There may be limits on the number and value of Stablecoin Payout Transactions that User can make, which, if applicable, are described on the Stripe Dashboard or otherwise communicated to User by Stripe or the Stablecoin Partner. Such limits may apply separately to Fiat-Funded Stablecoin Payouts and Direct Stablecoin Payouts, as described in the Documentation or communicated to User by Stripe or the Stablecoin Partner. Stripe, in its discretion, may allow Stablecoin Payout Transactions that exceed applicable limits or temporarily reduce User's limits from time to time without notice, unless applicable Law requires otherwise. Stripe may change its limits at any time in its sole discretion. The Stablecoin Partner may independently impose additional limits on Stablecoin Payout Transactions as described in the Stablecoin Partner Terms.
Qualifications & exceptions
Reductions without notice are subject to any contrary requirement of Law.
Not stated here
The actual limit amounts are not stated in these terms.
Charges & Financial Obligations · Company practice
You owe any taxes on stablecoin payouts; Stripe gives no tax advice but may file tax reports and send you copies
Stablecoin Payout Transactions may be subject to Taxes. The User acknowledges that tax Laws for stablecoin transactions may be uncertain and evolving and that Stripe is not responsible for assessing, collecting, reporting or remitting any Taxes the User owes from using the Service, the Stablecoin Partner Services or other transactions with a Stablecoin Partner. Stripe provides no investment or tax advice. Law may require Stripe to file periodic informational returns with taxing authorities about the User's use of the Service, and Stripe may send the User tax-related information electronically. The Stablecoin Partner may also have independent tax reporting obligations under its own terms.
Supporting quotations
4. Taxes.
Stablecoin Payout Transactions may be subject to Taxes. User acknowledges that tax Laws applicable to Stablecoin transactions may be uncertain and evolving, and that it is not Stripe's responsibility to assess, collect, report, or remit any Taxes owed by User arising from: (a) the use of the Stripe Global Payouts Stablecoin Services; (b) the use of the Stablecoin Partner Services; or (c) any other transactions User may enter into with a Stablecoin Partner. Stripe does not provide investment or tax advice. Stripe may be required to submit tax information reports to tax authorities regarding these transactions and may send User a copy of such tax information. Specifically, Law may require Stripe to file periodic informational returns with taxing authorities related to User's use of the Stripe Global Payouts Stablecoin Services, and Stripe may send tax-related information electronically to User. The Stablecoin Partner may also have independent tax reporting obligations with respect to Stablecoin Payout Transactions, as described in the applicable Stablecoin Partner Terms.
Qualifications & exceptions
Stripe's tax reporting is conditioned on Law requiring it.
Legal Rights & Agreement Rules · Context
Defined terms: Direct and Fiat-Funded Stablecoin Payouts, Designated Wallet, Payout Recipient and Payout Information
A Direct Stablecoin Payout is a transaction where the User, through Stripe's interface, instructs the Stablecoin Partner to send Stablecoin from the User's Stablecoin Partner Wallet to a recipient's Designated Wallet. A Fiat-Funded Stablecoin Payout is one where Stripe transfers fiat from the User's Financial Account to the User's Partner account and the Partner exchanges it for Stablecoin and sends it to the recipient's Designated Wallet. A Stablecoin Payout Transaction is either type. A Designated Wallet is the cryptocurrency wallet address designated by the User or a recipient to receive the Stablecoin. A Stablecoin Payout Recipient is a recipient the User designates to receive Stablecoin via a Designated Wallet. Payout Information is all information needed to complete a payout, including the wallet address and recipient identifying details Stripe or the Partner may require, such as name, address and government-issued identification.
Supporting quotations
5. Definitions.
"Designated Wallet" means a cryptocurrency wallet address designated by User or a Stablecoin Payout Recipient to receive Stablecoin in connection with a Stablecoin Payout Transaction.
"Direct Stablecoin Payout" means a Stablecoin Payout Transaction initiated by User through the Stripe Global Payouts Stablecoin Services by which User instructs the Stablecoin Partner, through Stripe's interface, to transmit Stablecoin directly from User's Stablecoin Partner Wallet to a Stablecoin Payout Recipient's Designated Wallet.
"Fiat-Funded Stablecoin Payout" means a Stablecoin Payout Transaction initiated by User through the Stripe Global Payouts Stablecoin Services by which (a) Stripe transfers fiat currency from User's Financial Account to User’s account with the Stablecoin Partner; and (b) the Stablecoin Partner exchanges that fiat currency for Stablecoin and transmits the Stablecoin to a Stablecoin Payout Recipient's Designated Wallet.
"Payout Information" means all information necessary to complete a Stablecoin Payout Transaction, including the Stablecoin Payout Recipient's Designated Wallet address and such identifying information about the Stablecoin Payout Recipient as Stripe or the Stablecoin Partner may require from time to time, including name, address, and government-issued identification.
"Stablecoin Payout Recipient" means a recipient designated by User to receive Stablecoin in connection with a Stablecoin Payout Transaction via a Designated Wallet.
"Stablecoin Payout Transaction" means either a Fiat-Funded Stablecoin Payout or a Direct Stablecoin Payout, as applicable.
Legal Rights & Agreement Rules · Context
Defined terms: Stablecoin, Stablecoin Partner, Partner Services, Partner Terms and Depeg Event
A Stablecoin is any fiat-backed cryptocurrency a Stablecoin Partner supports, as updated in the Partner Terms and Documentation. A Stablecoin Partner is an entity, possibly a Stripe Affiliate or a third party, that provides stablecoin exchange, custody, transmission or payout services to the User under the Stablecoin Partner Terms. Stablecoin Partner Services are the Partner's services connected to Stripe's stablecoin Services, which may include account and wallet creation, conversion between Stablecoin and fiat, custody, transmission or payout, and other services the Partner offers. Stablecoin Partner Terms govern the Partner's provision and the User's use of those services and may be updated. A Depeg Event is any occurrence where Stripe or the Partner determines in its sole discretion that a Stablecoin's price has failed to hold its intended fiat peg.
Supporting quotations
“Depeg Event” means any occurrence where Stripe or the Stablecoin Partner determines, in its sole discretion, that the price of a Stablecoin has failed to maintain its intended peg to the fiat value to which it is linked.
"Stablecoin" means any fiat-backed cryptocurrency supported by a Stablecoin Partner, which may be updated from time to time as stated in the applicable Stablecoin Partner Terms and the Documentation.
"Stablecoin Partner" means an entity, which may be a Stripe Affiliate or a third party, that provides stablecoin-related services to User, including the exchange, custody, transmission, or payout of Stablecoin, under the applicable Stablecoin Partner Terms.
"Stablecoin Partner Services" means any services provided by a Stablecoin Partner to User in connection with Stripe's Stablecoin-related Services, which may include: (a) the creation and maintenance of accounts and associated wallet addresses for User; (b) the exchange or conversion of Stablecoins to fiat currency and vice versa; (c) the custody of Stablecoins; (d) the transmission or payout of Stablecoins to designated wallet addresses; and (e) such other Stablecoin-related services as the Stablecoin Partner may offer from time to time, as described in the applicable Stablecoin Partner Terms.
"Stablecoin Partner Terms" means the terms that govern the Stablecoin Partner's provision, and User's access to and use of, the Stablecoin Partner Services, and which may be updated from time to time.
Legal Rights & Agreement Rules · Context
Defined term: the Global Payouts Stablecoin Services are only the interface letting you instruct the Partner
The Stripe Global Payouts Stablecoin Services are defined as the user interface, data transmission and related technology services Stripe provides to enable the User to instruct the Stablecoin Partner to complete Stablecoin Payout Transactions. This definition confines Stripe's role to the instruction layer; the stablecoin exchange, custody and payout themselves are performed by the Partner.
Supporting quotations
"Stripe Global Payouts Stablecoin Services" means the user interface, data transmission, and related technology services that Stripe provides to enable User to instruct the Stablecoin Partner to complete Stablecoin Payout Transactions.
Legal Rights & Agreement Rules · Context
The Stripe Identity Terms supplement the General Terms and govern the Identity Services and Submitted Data
The Stripe Identity Terms, last modified September 28, 2026, supplement the General Terms and govern use of the Stripe Identity Services and of Submitted Data. Capitalized terms not defined in these terms take their meaning from the General Terms. The Stripe Identity Services are the Services that let Stripe collect and verify, and Stripe and the User store, information about individuals to verify their identity.
Supporting quotations
Stripe Identity
Last modified: September 28, 2026
1. Stripe Identity Services.
These terms (“Stripe Identity Terms”) supplement the General Terms and govern the use of the Stripe Identity Services and Submitted Data. Capitalized terms that are not defined in these Stripe Identity Terms have the same meanings given to them in the General Terms.
“Stripe Identity Services” means the Services that enable Stripe to collect and verify, and Stripe and User to store, information regarding individuals for the purpose of verifying the identity of those individuals.
Use & Processing · Restriction or exception
You may use Stripe Identity only for legal compliance, fraud and misuse prevention, safety and permitted uses
The User may use the Stripe Identity Services only to evaluate the identity of Submitted Individuals to the extent necessary to meet the User's compliance obligations under Law; to prevent fraud related to the User's goods and services; to prevent misuse of them; to improve the safety or security of the User's business, operations and services; and in compliance with the Stripe Identity Permitted Businesses list.
Supporting quotations
2. Use of the Stripe Identity Services.
2.1 Permitted Uses.
User may use the Stripe Identity Services only:
(a) to evaluate the identity of Submitted Individuals to the extent necessary to satisfy User’s compliance obligations under Law;
(b) to prevent fraud as related to User’s goods and services;
(c) to prevent misuse of User’s goods and services;
(d) to improve the safety or security of User’s business, operations and services; and
(e) in compliance with the [Stripe Identity Permitted Businesses](https://stripe.com/docs/identity/use-cases) list.
Qualifications & exceptions
Identity evaluation for compliance is limited to the extent necessary under Law.
Use must also comply with the Stripe Identity Permitted Businesses list, which is external Documentation.
Use & Processing · Restriction or exception
You must not alter the Identity flow, call Stripe your due-diligence agent, disclose Identity data or compete
Beyond the unsupported or prohibited use cases in the Stripe Identity Permitted Businesses list, the User must not, and must not let anyone else, modify the Stripe Identity Services, including their branding, appearance, user experience or the manner or language used to obtain consent from Submitted Individuals; represent or imply that Stripe acts as the User's agent for meeting Due Diligence Requirements (AML, KYC, KYB and CDD obligations under Law); disclose Identity Services Data to any third party except as Law requires; use the Services or Identity Services Data to build or support a competing product; or use them in a way that would violate any Law.
Supporting quotations
2.2 Restricted Uses.
Without limiting the unsupported or prohibited use cases identified in the Stripe Identity Permitted Businesses list, User must not, and must not enable or allow any other party to:
(a) modify the Stripe Identity Services in any way, including by changing (i) the branding, appearance or user experience of the Stripe Identity Services; or (ii) the manner or language used to obtain consent from Submitted Individuals;
(b) represent or imply that Stripe is acting as User’s agent or appointed by User for the purpose of conducting or meeting User’s Due Diligence Requirements;
(c) disclose Identity Services Data to any third party, except as Law requires;
(d) use the Stripe Identity Services or Identity Services Data to create or support a product that competes with the Stripe Identity Services;
(e) use the Stripe Identity Services or Identity Services Data in a manner that would violate any Law;
“Due Diligence Requirements” means requirements imposed by Law that govern, are related to, or are similar to Anti-Money Laundering (AML), Know Your Customer (KYC), Know Your Business (KYB) and Customer Due Diligence (CDD).
“Identity Services Data” means any Stripe Data that User receives from Stripe in connection with the Stripe Identity Services.
Qualifications & exceptions
Disclosure of Identity Services Data is allowed only where Law requires it.
Use & Processing · Restriction or exception
No selling Identity data, verifying people who cannot consent, or using results for credit, insurance, housing or jobs
The User must not reuse, sell, rent, transfer, make available or communicate Identity Services Data by any means, including a 'sale' as the CCPA defines it where applicable. The User must not use the Stripe Identity Services to evaluate an individual who cannot give legally binding consent because of age or any other reason. The User must not use the Services as a factor in deciding anyone's eligibility for credit, insurance, housing or employment, or in any way that would make Stripe a 'consumer reporting agency' or make the Stripe Data the User receives a 'consumer report' under Law.
Supporting quotations
(f) reuse, sell, rent, transfer, make available, or communicate orally or through other means the Identity Services Data (including as the term “sell” is defined in the CCPA, as applicable);
(g) use the Stripe Identity Services to evaluate an individual who is incompetent to provide legally binding consent because of their age or for any other reason; or
(h) use the Stripe Identity Services as a factor in determining any person’s eligibility for credit, insurance, housing or employment, or in a manner that would cause Stripe to be a “consumer reporting agency” or cause Stripe Data User receives to constitute a “consumer report”, each as described under Law.
“CCPA” means California Consumer Privacy Act of 2018, Cal. Civ. Code Sections 1798.100-1798.199.
Qualifications & exceptions
The CCPA definition of 'sell' applies where that statute is applicable.
Use & Processing · Procedure
Offer a non-biometric option where Law requires, handle refusals yourself, use sensitive data only as stated
Where Law requires, the User must give each individual an alternative verification method that does not process biometric information. If an individual declines Selfie Verification (verification of an ID Image using biometric identifiers and facial recognition), the User may use the Services to offer an alternative without it. If an individual refuses the User's use of the Stripe Identity Services at all, Stripe need not perform them and the User alone must provide another way to evaluate that person. Any sensitive information the User receives in Identity Services Data, including government identification numbers, may be used only for the purposes in Section 3.2 (the purposes communicated to the individuals and disclosed to Stripe at onboarding) or as Law permits.
Supporting quotations
2.3 Further Obligations.
In connection with User’s use of the Stripe Identity Services:
(a) If Law requires, User must provide each individual with an alternative method of verification that does not involve processing any biometric information.
(b) If an individual does not consent to Selfie Verification, User may use the Stripe Identity Services to offer an alternative method of verification that does not use Selfie Verification.
(c) If an individual does not consent to User’s use of the Stripe Identity Services, then Stripe is not obligated to perform the Stripe Identity Services and User is solely responsible for providing an alternative means of evaluating that individual.
(d) To the extent User receives sensitive information (including any government identification numbers) in the Identity Services Data, User will use such information only for the purposes described in Section 3.2 of these Stripe Identity Terms, or as permitted under Law.
“Selfie Verification” means the verification of an ID Image using biometric identifiers and facial recognition technology.
User may use Identity Services Data solely for the purpose (i) that User communicated to the Submitted Individuals (and obtained their consent where required by Law); and (ii) that User disclosed to Stripe during the onboarding process for Stripe Identity Services.
Qualifications & exceptions
The non-biometric alternative is mandatory only where Law requires it.
Sensitive-data use is limited to Section 3.2 purposes or what Law permits.
Use & Processing · Company practice
Submitted ID data is Protected Data; Stripe may return verification and OCR results, which count as Stripe Data
Submitted Data, meaning all data, information, photos, ID Images and documents submitted through the Stripe Identity Services, is Protected Data under the Agreement. Unless the Stripe Identity Services Documentation says otherwise or the User instructs Stripe not to, Stripe may generate and give the User verification results and optical character recognition results from submitted documents. Those results are Stripe Data for purposes of the Agreement.
Supporting quotations
3. Use of Data.
3.1 Stripe’s Use of Submitted Data.
Submitted Data is Protected Data for purposes of this Agreement. As part of the Stripe Identity Services, unless the Stripe Identity Services Documentation specifies otherwise, or User instructs Stripe not to do so, Stripe may generate and provide to User verification results and optical character recognition (OCR) results from any documents submitted through the Stripe Identity Services. The results for the Stripe Identity Services are Stripe Data for the purposes of this Agreement.
“Submitted Data” means all data, information, photos, ID Images, and documents (including copies of documents) submitted through the Stripe Identity Services.
Qualifications & exceptions
The User can instruct Stripe not to generate results, and the Documentation may vary the default.
Use & Processing · Restriction or exception
You may use Identity results only for the purpose you told the individuals and disclosed to Stripe at onboarding
The User may use Identity Services Data solely for the purpose it communicated to the Submitted Individuals, obtaining their consent where Law requires, and that it disclosed to Stripe during onboarding for the Stripe Identity Services. The User may use Submitted Data solely for the purpose it notified to the Submitted Individuals, again with consent where Law requires.
Supporting quotations
3.2 User’s Use of Identity Services Data and Submitted Data.
User may use Identity Services Data solely for the purpose (i) that User communicated to the Submitted Individuals (and obtained their consent where required by Law); and (ii) that User disclosed to Stripe during the onboarding process for Stripe Identity Services. User may use Submitted Data solely for the purpose that User notified Submitted Individuals (and obtained their consent where required by Law).
Qualifications & exceptions
Consent from the individuals is required where Law requires it.
Legal Rights & Agreement Rules · Restriction or exception
Stripe Identity is as is; Stripe does not promise it catches all fraud or meets your due-diligence duties
Stripe does not represent or warrant that the Stripe Identity Services will let the User fulfill its legal obligations, including Due Diligence Requirements. Except as otherwise provided, the Services are provided 'as is' and 'as available'. Stripe does not guarantee that they will detect or prevent all fraudulent, illegal or risky activity or correctly evaluate anyone's identity, and makes no warranty that they will enable the User to comply with Law; the User remains solely responsible for meeting its legal obligations.
Supporting quotations
4. No Warranties; Disclaimers.
4.1 No Warranty.
Stripe does not represent or warrant that the Stripe Identity Services will enable User to fulfill User’s obligations under Law, including with respect to Due Diligence Requirements.
4.2 Disclaimers.
Except as otherwise provided herein, the Stripe Identity Services are provided on an “as is” and “as available” basis. Further:
(a) Stripe does not guarantee that the Stripe Identity Services will detect or prevent all fraudulent, illegal, or risky activities or correctly evaluate the identity of any individual.
(b) Stripe makes no representation or warranty that the Stripe Identity Services will enable User to comply with Law, and User remains solely responsible for ensuring that User meets User’s legal obligations.
Qualifications & exceptions
The disclaimer applies except as otherwise provided in these terms.
Legal Rights & Agreement Rules · Restriction or exception
You are liable for your decisions; Stripe is not liable for undetected fraud, failed due diligence or wrong results
The User is responsible and liable for its actions and decisions in connection with the Stripe Identity Services, including whether to enter business relationships with anyone. Stripe and its Affiliates are not liable for losses, damages or costs the User suffers from fraudulent, illegal or risky activity the Services did not detect or prevent, nor for losses caused by the User's failure to meet its Due Diligence Requirements (AML, KYC, KYB and CDD obligations under Law) or by the Services failing to correctly evaluate any individual.
Supporting quotations
(c) User is responsible and liable for User’s actions and decisions in connection with the Stripe Identity Services, including User’s decisions to enter, or not enter, into business relationships with any persons.
(d) Stripe and its Affiliates are not liable for any losses, damages, or costs that User suffers in connection with any fraudulent, illegal, or risky, activities that the Stripe Identity Services did not detect or prevent.
(e) Stripe and its Affiliates are not liable for any losses, damages, or costs caused by User’s failure to meet any of User’s Due Diligence Requirements, or by the Stripe Identity Services failing to correctly evaluate any individual.
“Due Diligence Requirements” means requirements imposed by Law that govern, are related to, or are similar to Anti-Money Laundering (AML), Know Your Customer (KYC), Know Your Business (KYB) and Customer Due Diligence (CDD).
Use & Processing · Procedure
Every verification request must pass Stripe a link to the privacy policy version that applies to that individual
For each evaluation request submitted to the Stripe Identity Services, the User must use the Stripe API to give Stripe a link to the version of the User's online Privacy Policy that applies to the Submitted Individual, meaning the person whose Verification Data is submitted.
Supporting quotations
5. Privacy and Data Protection.
5.1 Disclosing User’s Privacy Policy.
In connection with each evaluation request that is submitted to the Stripe Identity Services, User must use the Stripe API to provide to Stripe a link to the version of User’s online Privacy Policy that applies to the Submitted Individual.
“Submitted Individual” means an individual whose Verification Data is submitted through the Stripe Identity Services.
Sharing & Disclosure · Procedure
Your privacy policy must name Stripe as an independent controller and disclose data rights, uses and transfers
If the User receives any Submitted Data or Stripe Data through the Stripe Identity Services, its Privacy Policy must at a minimum: state that the User and Stripe are each independent controllers of Personal Data and that Stripe processes it under Stripe's Privacy Policy and these terms in addition to acting as the User's service provider (Stripe offers model wording about sharing personally identifying information with Stripe for risk evaluation and identity verification); state how Submitted Individuals can make data subject requests, including deletion and access, with contact details; state how the User will use Submitted Data and Stripe Data, including, where Law requires, whether it will sell or disclose Submitted Data as 'sell' is defined in the CCPA; where Law requires, state the alternative verification methods for people who do not consent, that Submitted Data may be sent outside the User's jurisdiction including to the United States, and that it may go to third-party service providers including Governmental Authorities to evaluate the individual; and include everything else Law requires. If the User receives no Submitted Data or Stripe Data, the policy need only meet the controller statement, data-rights and Law-required disclosure items (Section 5.2(a), (b) and (d)).
Supporting quotations
5.2 Requirements for User’s Privacy Policy.
If User receives access to any Submitted Data or Stripe Data as part of the Stripe Identity Services, User’s Privacy Policy must, at a minimum:
(a) state that User and Stripe are each independent controllers of Personal Data, and that Stripe will process Personal Data in accordance with Stripe’s Privacy Policy and these Stripe Identity Terms, in addition to acting as a service provider to User. For example, User may choose to add the following to User’s Privacy Policy if it does not already include a disclosure to this effect: "We use Stripe for risk and identity verification services. We share personally identifying information with Stripe, which analyzes and uses it to operate and improve the services it provides to us, including for risk evaluation and identity verification.
(b) state the process through which Submitted Individuals can submit data subject requests (including data deletion and data access) to User, and provide User’s contact information for this purpose;
(c) state the ways in which User will use Submitted Data and Stripe Data, including, if Law requires, whether User will sell or disclose Submitted Data (including as the term “sell” is defined in the CCPA);
(d) if Law requires, (i) state the alternative verification methods that User makes available to individuals who do not consent to be verified by the Stripe Identity Services; (ii) state that using the Stripe Identity Services may include transmitting Submitted Data outside of User’s jurisdiction, including to the United States; and (iii) state that Submitted Data may be submitted to third-party service providers, including Governmental Authorities, for the purpose of evaluating a Submitted Individual; and
(e) include all other information Law requires User to include.
5.3 Minimum Requirements.
If User does not receive access to any Submitted Data or Stripe Data as part of the Stripe Identity Services, User’s Privacy Policy must, at a minimum, satisfy the requirements of Section 5.2(a), (b) and (d) of these Stripe Identity Terms.
Qualifications & exceptions
The full list applies when the User receives Submitted Data or Stripe Data; otherwise only items (a), (b) and (d) apply.
Several disclosures are required only if Law requires them.
Use & Processing · Company practice
Your privacy policy cannot contradict Stripe's data rights, and Stripe may notify or obtain consent itself
The User's Privacy Policy must not contain terms that contradict the rights of Stripe or its service providers to use Submitted Data for the purposes in these terms or as the Submitted Individual otherwise authorized, for example through consent screens in the Stripe Identity Services. Depending on the User's implementation, Stripe may itself give notice to or obtain consent from Submitted Individuals as described in the Stripe Identity Services Documentation so that it can provide the Services.
Supporting quotations
5.4 No Inconsistent Terms.
User’s Privacy Policy must not contain any terms that contradict Stripe’s or any Stripe service provider’s rights to use Submitted Data for the purposes described in these Stripe Identity Terms or as otherwise authorized by the Submitted Individual (e.g., through consent screens provided through the Stripe Identity Services).
5.5 Stripe may Notify or Obtain Consent.
Depending upon User’s implementation of the Stripe Identity Services, Stripe may provide notice to or obtain consent from Submitted Individuals as described in the Stripe Identity Services Documentation for the purpose of enabling Stripe to provide the Stripe Identity Services.
“Stripe Identity Services Documentation” means the Documentation, along with other documentation that Stripe makes available to User (including via email and the Stripe Dashboard), relating to the Stripe Identity Services.
Qualifications & exceptions
Stripe's own notices or consent prompts depend on how the User implements the Services.
Data Access & Collection · Procedure
You must obtain all consents for data use and Stripe's collection, including before Stripe sends verification SMS
The User must obtain all consents from Submitted Individuals required for the User's use of Submitted Data and for Stripe's collection and use of any Personal Data the User submits in connection with the Stripe Identity Services. If the User gives Stripe contact details such as phone numbers or email addresses for evaluation, Stripe may verify them by sending each individual a message, including SMS, and the User must obtain each individual's consent before Stripe sends it.
Supporting quotations
5.6 User’s Obligation to Obtain Consent.
User must obtain all consents from Submitted Individuals that are required for (a) User’s use of Submitted Data; and (b) Stripe’s collection and use of any Personal Data that User submits to Stripe in connection with User’s use of the Stripe Identity Services. If User provides Stripe with contact information for individuals (e.g. phone numbers or email addresses) for evaluation, Stripe may verify that contact information by sending each individual a message (including SMS). User must obtain consent from each Submitted Individual prior to Stripe sending them a message (including SMS).
Security & Safeguards · Procedure
Keep reasonable safeguards on Submitted Data or face suspension, and help Stripe send breach or notice emails
The User must implement and maintain safeguards and security controls reasonable for the size, nature and maturity of its business and industry to protect Submitted Data and Stripe Data against unauthorized access, use and disclosure; if it fails to, Stripe may suspend or restrict its access to the Stripe Identity Services in addition to other remedies. If Stripe must send a data subject notification to Submitted Individuals related to the User's use of the Services, including a data breach or a required Stripe Privacy Policy update notice, the User must assist, including by emailing those individuals on Stripe's behalf as Stripe directs.
Supporting quotations
5.7 Security Controls.
User must implement and maintain safeguards and security controls that are reasonable for the size, nature and maturity of User’s business and industry to protect Submitted Data and Stripe Data against unauthorized access, use and disclosure. If User fails to do so, in addition to all other remedies available to Stripe, Stripe may suspend or restrict User’s access to the Stripe Identity Services.
5.8 Assistance to Notify.
If Stripe is required to send a data subject notification to any Submitted Individuals related to User’s use of the Stripe Identity Services, including a data breach or required notice about a Stripe Privacy Policy update, User must assist Stripe in notifying Submitted Individuals, including by emailing those Submitted Individuals on Stripe’s behalf and as Stripe directs.
Qualifications & exceptions
Suspension is in addition to all other remedies available to Stripe.
Account & Service Control · Procedure
Stripe may demand proof of compliant use, your business standing and purpose; answer within 14 days or lose access
The User must provide information Stripe requests to confirm compliance with the Agreement, including information verifying that its use of the Stripe Identity Services and its receipt and use of Stripe Data and Submitted Data comply with these terms and Law, that it has not modified the Services without Stripe's consent, its industry, business activities, licensing and regulatory standing, and its purpose for using the Services. The User must respond promptly and no later than 14 days after the request; Stripe may suspend or terminate access to the Services immediately if the User fails to provide requested information under this Section 6.
Supporting quotations
6. Audit.
6.1 Obligation to Provide Information.
User must provide information that Stripe requests for the purpose of ensuring that User complies with this Agreement, including information verifying:
(a) that User’s use of the Stripe Identity Services complies with these Stripe Identity Terms and Law;
(b) that User’s receipt and use of the Stripe Data and Submitted Data complies with these Stripe Identity Terms and Law;
(c) that User has not modified the Stripe Identity Services without Stripe’s consent;
(d) User’s industry, business activities, licensing and regulatory standing; and
(e) User’s purpose for using the Stripe Identity Services.
6.2 Obligation to Respond Promptly.
User must respond to Stripe’s requests for information promptly, but no later than 14 days after Stripe’s request. Stripe may suspend or terminate User’s access to the Stripe Identity Services immediately if User fails to provide information Stripe requests under this Section 6.
Retention & Deletion · Company commitment
Stripe stores Submitted Data 7 years on your instruction, deletes personal data on request, may delete at termination
The User instructs Stripe to store a copy of Submitted Data on its behalf for 7 years after verification, or, within Stripe's standard maximum retention period, for a different period the User sets per the Stripe Identity Services Documentation. The User is responsible for determining how long Law requires it to keep Submitted Data, for storing it (itself or through Stripe) for that period, and for fulfilling all data subject requests it receives about Submitted Data or Stripe Data. If the User or a data subject asks Stripe to delete an individual's Personal Data for the Identity Services, Stripe will delete the Personal Data it possesses. On termination of these terms Stripe may delete the copies of Submitted Data and Stripe Data it stored on the User's behalf.
Supporting quotations
7. Retention and Deletion of Data.
7.1 Data Stripe Stores on User’s Behalf.
The following terms govern Stripe’s storage of Submitted Data on User’s behalf:
(a) User instructs Stripe to store on User’s behalf a copy of Submitted Data for a period of 7 years following verification, or subject to Stripe's standard maximum retention period for Users, a different period as User may instruct according to the Stripe Identity Services Documentation. User is responsible for (i) determining how long Law requires User to store copies of Submitted Data; (ii) storing (either through User or through Stripe) the Submitted Data for the time period Law requires; and (iii) fulfilling all data subject requests that User receives with respect to the Submitted Data or Stripe Data. If User or a data subject requests that Stripe delete an individual's Personal Data with respect to the Stripe Identity Services, Stripe will delete any such Personal Data Stripe possesses.
(b) Upon termination of these Stripe Identity Terms, Stripe may delete copies of Submitted Data and Stripe Data that Stripe has stored on User’s behalf.
Qualifications & exceptions
The 7-year default can be changed by the User within Stripe's standard maximum retention period.
Deletion at termination is at Stripe's option ('may').
Not stated here
Stripe's standard maximum retention period is not stated in these terms.
Retention & Deletion · Company practice
Apart from storage on your behalf, Stripe may keep its own copy of Submitted Data and results as long as Law permits
Notwithstanding the Section 7.1 rules on data Stripe stores on the User's behalf, Stripe may retain a copy of Submitted Data and Stripe Data for its own purposes for as long as Law permits. This retention is not bounded by the User's 7-year instruction or by deletion requests under Section 7.1.
Supporting quotations
7.2 Data Stripe Stores for its Own Purposes.
Notwithstanding Section 7.1 of these Stripe Identity Terms, Stripe may retain a copy of Submitted Data and Stripe Data as long as Law permits.
Qualifications & exceptions
Retention for Stripe's own purposes is limited only by what Law permits.
Use & Processing · Restriction or exception
No use of Stripe Identity for any FCRA 'permissible purpose' or in violation of the GLBA, DPPA, HIPAA or similar laws
The User must not use the Stripe Identity Services for any 'permissible purpose' as defined in the FCRA (the Fair Credit Reporting Act and Equal Credit Opportunity Act, 15 U.S.C. Section 1681 et seq.), or in a way that would violate the GLBA (Gramm-Leach-Bliley Act, 15 U.S.C. Sections 6802-6809), the United States Driver's Privacy Protection Act, the Health Insurance Portability and Accountability Act, or any substantially similar Law.
Supporting quotations
8. Restriction.
User must not use the Stripe Identity Services for any “permissible purpose” under (and as defined in) the FCRA, or in a manner that would violate the GLBA, the United States Driver's Privacy Protection Act, the United States Health Insurance Portability and Accountability Act, or other substantially similar Law.
“FCRA” means Fair Credit Reporting Act, 15 U.S.C. Section 1681, et seq. and Equal Credit Opportunity Act, 15 U.S.C. Section 1681, et seq.
“GLBA” means Gramm-Leach Bliley Act, 15 U.S.C. Sections 6802-6809.
Legal Rights & Agreement Rules · Context
Defined terms: CCPA, Due Diligence Requirements, ID Image, Identity Services Data, Selfie Verification and more
The Identity Terms define the CCPA (California Consumer Privacy Act of 2018); Due Diligence Requirements (AML, KYC, KYB and CDD requirements under Law); ID Image (an image of an individual submitted through the Services, including one captured from an identification document); Identity Services Data (Stripe Data the User receives in connection with the Services); Selfie Verification (verifying an ID Image with biometric identifiers and facial recognition); Stripe Identity Permitted Businesses (the use cases and business locations listed in the Documentation); Stripe Identity Services; Stripe Identity Services Documentation (the Documentation plus other material Stripe provides, including by email and the Dashboard); Submitted Data (all data, photos, ID Images and documents submitted through the Services); and Submitted Individual (a person whose Verification Data is submitted).
Supporting quotations
9. Definitions.
“CCPA” means California Consumer Privacy Act of 2018, Cal. Civ. Code Sections 1798.100-1798.199.
“Due Diligence Requirements” means requirements imposed by Law that govern, are related to, or are similar to Anti-Money Laundering (AML), Know Your Customer (KYC), Know Your Business (KYB) and Customer Due Diligence (CDD).
“ID Image” means an image of an individual submitted through the Stripe Identity Services, including an image captured from an individual’s identification document.
“Identity Services Data” means any Stripe Data that User receives from Stripe in connection with the Stripe Identity Services.
“Selfie Verification” means the verification of an ID Image using biometric identifiers and facial recognition technology.
“Stripe Identity Permitted Businesses” means the use cases and business locations supported by Stripe Identity, as listed in the [Documentation](https://stripe.com/docs/identity/use-cases).
“Stripe Identity Services” means the Services that enable Stripe to collect and verify, and Stripe and User to store, information regarding individuals for the purpose of verifying the identity of those individuals.
“Stripe Identity Services Documentation” means the Documentation, along with other documentation that Stripe makes available to User (including via email and the Stripe Dashboard), relating to the Stripe Identity Services.
“Submitted Data” means all data, information, photos, ID Images, and documents (including copies of documents) submitted through the Stripe Identity Services.
“Submitted Individual” means an individual whose Verification Data is submitted through the Stripe Identity Services.
Not stated here
'Verification Data' is used in the Submitted Individual definition but is not itself defined in these terms.
Legal Rights & Agreement Rules · Context
The Stripe Invoicing Terms supplement the General Terms and govern the Invoicing Services
The Stripe Invoicing Terms, last modified November 18, 2025, supplement the General Terms and govern the User's use of the Stripe Invoicing Services, the Services that let the User invoice Customers for its products and services and confirm receipt of payment. Capitalized terms not defined here take their General Terms meaning.
Supporting quotations
Stripe Invoicing
Last modified: November 18, 2025
1. Use of Invoicing Services.
These terms (“Stripe Invoicing Terms”) supplement the General Terms and govern User’s use of the Stripe Invoicing Services. Capitalized terms that are not defined in these terms have the same meanings given to them in the General Terms.
5. Definitions.
“Stripe Invoicing Services” means the Services that enable User to invoice Customers for User’s products and services and to confirm receipt of payment for invoices.
Legal Rights & Agreement Rules · Procedure
You must configure invoicing to comply with Law and own invoice content, data accuracy, customer disputes and edits
The User is responsible for configuring and using the Stripe Invoicing Services in compliance with Law, including deciding whether they must be supplemented with third-party services, and for ensuring that the form and content of invoices meet its needs and achieve the legal or tax effects it intends. The User is also responsible for the accuracy of information it gives Stripe for the Services, for resolving disputes with Customers about its use of the Services, and for its own modifications, additions, uploaded templates and revised translations on its invoices or hosted invoicing page.
Supporting quotations
2. User’s Obligations.
User is responsible for configuring and using Stripe Invoicing Services in compliance with Law, including determining if the Stripe Invoicing Services need to be supplemented using additional third party services. User must ensure that the form and content of invoices meet User’s needs and achieve the legal or tax effects that User intends. User is responsible for: (a) ensuring the accuracy of information User provides to Stripe in connection with the Stripe Invoicing Services; (b) resolving any disputes between User and Customers related to User’s use of Stripe Invoicing Services; and (c) User’s modifications or additions, uploaded templates, and revised translations to User’s invoices or hosted invoicing page.
Use & Processing · Restriction or exception
No use of Invoicing in ways the Documentation prohibits or with Protected Health Information, even by Connected Accounts
The User must not use the Stripe Invoicing Services in ways the Documentation expressly prohibits, and must not, and must ensure its Connected Accounts (Platform Users onboarded to a Stripe Connect Platform, or Payout Recipients) do not, use the Services in connection with Protected Health Information.
Supporting quotations
3. Services Restrictions.
User must not use the Stripe Invoicing Services in ways expressly prohibited in the Documentation. User must not, and must ensure that its Connected Accounts (if applicable) do not, use the Stripe Invoicing Services in connection with Protected Health Information.
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
Qualifications & exceptions
The Connected Account obligation applies only where the User has Connected Accounts.
Use & Processing · Permission or license
You authorize Stripe to surface your invoicing data in, and use it to power features of, your other Stripe Services
The User authorizes Stripe to make data from the User's use of the Stripe Invoicing Services available to the User in other Services the User uses, and to use it to enable features and functionality in those other Services.
Supporting quotations
4. Data Use.
User authorizes Stripe to make data from User’s use of Stripe Invoicing Services available to User in other Services that User uses and to enable features and functionality in other Services that User uses.
Qualifications & exceptions
The data is made available to the User within other Services the User already uses.
Legal Rights & Agreement Rules · Context
The UK/EEA Issuing Accountholder Terms supplement the General Terms and incorporate the Financial Services Terms
The Stripe Issuing Accountholder Terms for the United Kingdom and European Economic Area, last modified September 28, 2026, supplement the General Terms and, with the Stripe Financial Services Terms incorporated by reference, govern the User's use of the Stripe Issuing Accountholder Services. Undefined capitalized terms take their meaning from the General Terms and the Financial Services Terms. Stripe and its Affiliates make the Accountholder Services, which include access to the Stripe Issuing Program (a Card issuing program and related services), available to Stripe Issuing Accountholders, meaning businesses that completed onboarding and were approved for a Stripe Issuing Account.
Supporting quotations
Stripe Issuing—Accountholder (United Kingdom and European Economic Area)
Last modified: September 28, 2026
1. Stripe Issuing Services - Accountholder.
These terms (“Stripe Issuing Accountholder Terms”) supplement the General Terms and, together with the Stripe Financial Services Terms which are incorporated into these terms by this reference, govern User’s use of the Stripe Issuing Accountholder Services. Capitalized terms that are not defined in these terms have the same meanings given to them in the General Terms and the Stripe Financial Services Terms.
2. Overview.
Stripe and its Affiliates make available the Stripe Issuing Accountholder Services, which includes access to the Stripe Issuing Program, for Stripe Issuing Accountholders.
“Stripe Issuing Accountholder” means a business or organization that has successfully completed the onboarding requirements described in these Stripe Issuing Accountholder Terms and been approved for a Stripe Issuing Account.
“Stripe Issuing Accountholder Services” means Services that Stripe and its Affiliates make available to Stripe Issuing Accountholders, including (a) providing Stripe Issuing Accountholders with access to the Stripe Issuing Program; (b) enabling Stripe Issuing Accountholders to manage Card spend, and (c) other services described in these Stripe Issuing Accountholder Terms.
“Stripe Issuing Program” means a Card issuing program and related services that Stripe and its Affiliates make available to Stripe Issuing Accountholders, together with the Stripe Issuing Accountholder Services.
Account & Service Control · User right or choice
You may appoint an Issuing Administrator to run your card program and are responsible for everything they do
The User may appoint a Stripe Issuing Administrator, the individual who manages its participation in the Stripe Issuing Program, to administer the program on its behalf, for example requesting Cards for Issuing Authorized Users, changing the Stripe Issuing Account and managing how authorized users use Cards. The User must ensure the Administrator complies with these terms and is responsible for the Administrator's acts and omissions in connection with the program.
Supporting quotations
3. Use of the Stripe Issuing Services.
3.1 Stripe Issuing Administrator.
User may appoint a Stripe Issuing Administrator to administer the Stripe Issuing Program on User’s behalf (e.g., requesting Cards for Issuing Authorized Users, making changes to the Stripe Issuing Account, managing how Issuing Authorized Users use Cards). User must ensure that the Stripe Issuing Administrator complies with these Stripe Issuing Accountholder Terms. User is responsible for the Stripe Issuing Administrator’s acts and omissions in connection with the Stripe Issuing Program.
“Stripe Issuing Administrator” means the individual that a Stripe Issuing Accountholder appoints to manage its participation in the Stripe Issuing Program.
Account & Service Control · Procedure
Your cardholders may use Cards only for business purchases; you are liable for them and they are not Stripe's customers
In its agreement with its Issuing Authorized Users (individuals such as employees, contractors or representatives it authorizes to make Card Transactions on its behalf), the User must specify that their use of the Stripe Issuing Program and Account is solely for business-related purchases. The User must ensure they comply with these terms, including the ban on conducting or dealing with a Prohibited or Restricted Business, and is responsible and liable for their acts and omissions with Cards. The User may impose liability on them only as Law allows. Issuing Authorized Users act under the User's authority and are not Stripe customers.
Supporting quotations
3.2 Issuing Authorized Users.
In the agreement between User and User’s Issuing Authorized Users, User must specify that the Issuing Authorized User’s use of the Stripe Issuing Program and Stripe Issuing Account must be solely for business-related purchases. User must ensure that Issuing Authorized Users comply with these Stripe Issuing Accountholder Terms, including the prohibition on conducting, or dealing with, a Prohibited or Restricted Business. User is responsible and liable for User’s Issuing Authorized Users’ acts and omissions in connection with their use of Cards. User may only impose liability on Issuing Authorized Users in connection with the Stripe Issuing Program as Law allows. Issuing Authorized Users act under User’s authority and are not customers of Stripe.
“Issuing Authorized User” means an individual a Stripe Issuing Accountholder authorizes to use a Card to make Card Transactions on the Stripe Issuing Accountholder’s behalf (e.g., the Stripe Issuing Accountholder’s employee, independent contractor or representative designated as an authorized user).
Qualifications & exceptions
Liability may be passed to Issuing Authorized Users only as Law allows.
Account & Service Control · Restriction or exception
You must be a commercial business, use the account for business only, and follow the Issuing Program Guidelines
The User must be a commercial business enterprise and the Stripe Issuing Account is for business purposes only. The User must not use, or let an Issuing Authorized User use, the Accountholder Services for Card Unauthorized Purposes, and must comply, and ensure its Administrator and authorized users comply, with the Stripe Issuing Program Guidelines, the product design, marketing, compliance, reporting and other requirements Stripe and its Affiliates set for the Issuing Services, as updated from time to time.
Supporting quotations
3.3 Compliance.
User must be a commercial business enterprise and the Stripe Issuing Account is for business purposes only. User must not use, or permit an Issuing Authorized User to use, the Stripe Issuing Accountholder Services for Card Unauthorized Purposes; and will comply, and ensure that User’s Stripe Issuing Administrator and Issuing Authorized Users comply, with the Stripe Issuing Program Guidelines.
“Stripe Issuing Program Guidelines” means all product design, marketing, compliance, reporting, and other guidelines and requirements Stripe and its Affiliates establish related to the Stripe Issuing Services, as updated from time to time.
Qualifications & exceptions
The Program Guidelines may be updated from time to time.
Account & Service Control · Procedure
Forward every Issuing Complaint within 3 business days; Stripe or your Platform Provider handles your inquiries
The User must submit each Issuing Complaint it receives, meaning any expression of dissatisfaction with a product, service, policy or employee related to a Stripe Issuing Program, to its Platform Provider or, if it has none, to issuing-support@stripe.com within 3 business days of receipt. Stripe, or the User's Platform Provider where applicable, manages all inquiries from the User about the Accountholder Services, including use of Cards and lost, stolen or damaged Cards.
Supporting quotations
3.4 Issuing Complaint Handling.
User must submit each Issuing Complaint User receives to User’s Platform Provider or, if User does not have one, to issuing-support@stripe.com within 3 business days after User receives the Issuing Complaint.
3.6 Inquiries.
Stripe (or, if applicable, User’s Platform Provider) will manage all inquiries from User regarding Stripe Issuing Accountholder Services, including inquiries related to the use of Cards, and lost, stolen or damaged Cards.
“Issuing Complaint” means any expression of dissatisfaction with a product, service, policy, or employee related to a Stripe Issuing Program.
“Platform Provider” means the platform that gives User access to the Stripe Issuing Program (if User is a Connected Account or if User otherwise accesses the Stripe Issuing Program through a platform).
Data Access & Collection · Company practice
Stripe may require your business details and cardholders' names, addresses, birthdates and ID documents at any time
Stripe may require the User to provide User Information, information about Issuing Authorized Users including name, address, birthdate and government-issued identification documents, and information about the User's activities and intended use of the Accountholder Services. This may be in addition to information already provided for other Services, and the User must promptly provide all additional financial and other information Stripe requests from time to time.
Supporting quotations
3.5 Providing Information.
Stripe may require User to provide User Information, information regarding Issuing Authorized Users (including name, address, birthdate, and government-issued identification documents), and information about User’s activities and intended use of the Stripe Issuing Accountholder Services. This information may be in addition to information User has previously provided to Stripe in connection with other Services. User must promptly provide all additional financial and other information Stripe requests from time to time.
Content & IP Rights · Procedure
Custom Card designs need Stripe approval for compliance, Law and reputation; rejections come back with changes
The User may request specific designs for Cards (Card Network-branded payment cards, physical or digitized, issued for business purposes) issued to it or its Issuing Authorized Users. Every proposed design must go to Stripe for review and approval through Stripe's required process. Stripe reviews designs for compliance with the Agreement, Law and Stripe reputational considerations; if it does not approve one, it recommends modifications that would meet the requirements, and the User must resubmit the modified design through the same process.
Supporting quotations
4. Cards.
4.1 Card Design.
User may request specific Card designs for Cards issued to User or Issuing Authorized Users. User must provide all proposed Card designs to Stripe for review and approval using the process Stripe requires. Stripe will review Card design proposals for compliance with this Agreement, Law, and Stripe reputational considerations. If Stripe does not approve a proposed Card design, Stripe will recommend modifications that, if made, will meet these requirements. User must resubmit the modified Card design to Stripe for approval using the same process.
“Card” means a Card Network-branded payment card (which may be a physical card or tokenized, encrypted, or digitized form of a physical card) issued to a Stripe Issuing Accountholder for the Stripe Issuing Accountholder’s business purposes in connection with the Stripe Issuing Program.
Charges & Financial Obligations · Company commitment
Cards and replacements ship at your or your platform expense to EEA or UK addresses; risk passes on shipment
The User may order Cards through its Stripe Dashboard or, if applicable, its Platform Provider. At the User's or Platform Provider's expense, Stripe procures and ships Cards per the order to the EEA or UK address specified, and ships replacements for Cards reported lost, stolen or damaged. Risk of loss passes to the recipient, the User or Platform Provider as applicable, when Stripe ships the Card to the ordered address.
Supporting quotations
4.2 Card Orders.
User may order Cards through User’s Stripe Dashboard (or, if applicable, through User’s Platform Provider). At User’s (or, if applicable, User’s Platform Provider’s) expense, Stripe will procure and ship (a) Cards based on the information contained in the applicable Card order to the address in the EEA or UK specified in that Card order; and (b) replacements for Cards reported as lost, stolen or damaged. Risk of loss for Cards passes to the recipient (either User or User’s Platform Provider, as applicable) when Stripe ships the Card to the address specified in the order.
Qualifications & exceptions
Shipping addresses must be in the EEA or UK.
Account & Service Control · Procedure
Cards must be activated through your Dashboard or Platform Provider before anyone uses them
The User must activate each Card through its Stripe Dashboard or, if applicable, its Platform Provider before it or its Issuing Authorized Users use the Card. Stripe provides activation instructions directly or with the Card delivery, and the User passes them to its Administrators and authorized users. Once activated, Issuing Authorized Users may use Cards to initiate Card Transactions on the User's behalf.
Supporting quotations
4.3 Card Activation.
User must activate a Card through User’s Stripe Dashboard (or, if applicable, through User’s Platform Provider) before User or User’s Issuing Authorized Users use that Card. Stripe will provide activation instructions to User, either directly or with delivery of Cards. User will provide those instructions to User’s Stripe Issuing Administrators and Issuing Authorized Users. Once a Card is activated, Issuing Authorized Users may use Cards to initiate Card Transactions on User’s behalf.
Account & Service Control · Company practice
Cards stay Stripe property; Stripe may cancel or suspend any Card, and you must return or destroy cancelled ones
Cards are Stripe's property. If Stripe asks, the User must promptly return a Card, or make its Issuing Authorized User return it, as Stripe instructs, and must immediately and at its own expense return cancelled Cards or certify in writing that they were destroyed. Stripe may in its reasonable discretion cancel, suspend or restrict a Card at any time, including where Law or Card Network Rules require or where a Card is used for a Card Unauthorized Purpose (a fraudulent or illegal purpose, a consumer, personal or household purpose, or any purpose unrelated to the Issuing Services). Stripe will notify the User as soon as practicable afterwards and, where Law permits, give reasons, and will issue a replacement or lift the restriction as soon as practicable after it decides in its sole discretion that the reasons no longer exist.
Supporting quotations
4.4 Ownership and Cancellation of Cards.
Cards are the property of Stripe. If Stripe requests that User or an Issuing Authorized User return a Card, then User must return, or ensure that the Issuing Authorized User returns, that Card promptly to Stripe as Stripe instructs. User will immediately and at User’s expense return cancelled Cards to Stripe or provide written certification that cancelled Cards have been destroyed.
Stripe may, in its reasonable discretion, cancel, suspend or restrict the use of a Card at any time, including as required by Law or Card Network Rules, or if a Card is used for a Card Unauthorized Purpose. Stripe will notify User as soon as practicable after cancelling, suspending or restricting a Card, and to the extent Law permits, will inform User of the reasons for the cancellation, suspension or restriction. Stripe will issue a replacement Card or lift the suspension or restriction of a Card as soon as practicable after Stripe, in its sole discretion, determines that the reasons for cancellation, suspension or restriction cease to exist.
“Card Unauthorized Purpose” means (a) a fraudulent or illegal purpose; (b) a consumer, personal, or household purpose; and (c) any purpose unrelated to the Stripe Issuing Services.
“Card Network Rules” means the Payment Method Rules published by a Card Network.
Qualifications & exceptions
Reasons are given only to the extent Law permits.
Whether the grounds have ceased is Stripe's sole-discretion decision.
Content & IP Rights · Permission or license
You give Stripe a worldwide royalty-free, sublicensable license to put your marks on Cards; revoking it recalls none
The User must hold the rights needed to use, and let Stripe use, the User Materials (Marks or other materials to be placed on Cards, or other materials provided for the Issuing Program) on Cards and for the program. The User grants Stripe and its Affiliates a worldwide, non-exclusive, royalty-free license to use the User Materials on Cards and program materials, with the right to sublicense to third parties Stripe engages to create them. If the User terminates or revokes the license, Stripe will stop producing new Cards with the materials and stop using them for the program, but need not recall, destroy or replace existing Cards, and is not liable for delays or failures caused by the revocation.
Supporting quotations
4.5 User Materials.
User must have the necessary rights in the User Materials to use (and grant Stripe the rights to use) the User Materials on the Cards and for the purposes of the Stripe Issuing Program. User grants to Stripe and its Affiliates a worldwide, non-exclusive, royalty-free license to use the User Materials on Cards and applicable Stripe Issuing Program materials. User also grants to Stripe and its Affiliates the right to sublicense these rights to third parties that Stripe engages to create Cards and applicable Stripe Issuing Program materials.
If User terminates or revokes the license to the User Materials, then (a) Stripe will stop producing new Cards carrying the User Materials and stop using the User Materials for the purposes of the Stripe Issuing Program; (b) Stripe will not be obligated to recall, destroy or replace any existing Cards carrying the User Materials; and (c) Stripe will not be liable for any delay or failure in performing its obligations to the extent they are adversely affected by the termination or revocation.
“User Materials” means (a) all Marks or other materials that User or a Stripe Issuing Accountholder wish to place on Cards; or (b) all other materials that User provides to Stripe for the purposes of the Stripe Issuing Programs.
Qualifications & exceptions
The license is non-exclusive and the User may revoke it, with the stated consequences.
Charges & Financial Obligations · Context
Your Issuing Account is an E-money Payment Account holding the balance across all Cards, with per-Card sub-accounts
The Stripe Issuing Account, the account Stripe or an Affiliate maintains for the accountholder, is an E-money Payment Account under the EEA or UK electronic money and payment services regulations. It contains informational sub-accounts for each Card, records the Card Transactions processed for each Card, and holds the outstanding E-money balance across all Cards issued to the User. All Cards issued to the User are linked to it.
Supporting quotations
5. Operation of Stripe Issuing Accounts and Processing of Card Transactions.
5.1 Stripe Issuing Accounts.
The Stripe Issuing Account is an E-money Payment Account. The Stripe Issuing Account will contain sub-accounts (for information purposes only) related to each Card. The Stripe Issuing Account will contain details of Card Transactions processed in respect of each Card, and the outstanding amount of E-money which is held in the Stripe Issuing Account across all Cards issued to User. All Cards issued to User are linked to User’s Stripe Issuing Account.
“Stripe Issuing Account” means the account Stripe or a Stripe Affiliate maintains for a Stripe Issuing Accountholder, and each subaccount to that account.
“E-money” means electronic money as defined in SI No. 183/2011 – European Communities (Electronic Money) Regulations 2011.
“Payment Account” means a payment account as that term is defined in SI No. 6/2018 – European Union (Payment Services) Regulations 2018.
“E-money” means electronic money as defined in the Electronic Money Regulations 2011 (SI 2011/99).
“Payment Account” means a payment account as that term is defined in the Payment Services Regulations 2017 (Statutory Instrument 2017/752).
Qualifications & exceptions
Sub-accounts per Card are for information purposes only.
Charges & Financial Obligations · Company practice
Stripe may decline or reverse any Card Transaction for security, funds, breach or risk reasons, without liability
Stripe uses a Card Network to authorize, clear and settle all Card Transactions (payments with a Card or, if permitted, ATM cash) on the User's Cards. Stripe may decline or reverse a Card Transaction for any reason, including concerns about Card security or use without authorization or for a Card Unauthorized Purpose (a fraudulent or illegal purpose, a consumer, personal or household purpose, or any purpose unrelated to the Issuing Services); insufficient E-money loaded; a belief that the User is breaching the Agreement, the Connected Account Agreement or another agreement with a Stripe Entity; a belief that the transaction is suspicious, fraudulent, illegal or unacceptably risky; merchant, processor or scheme errors or refusals; or a prohibited or restricted merchant. On request, if practicable and Law permits, Stripe will give the reason for a decline. Stripe is not liable for losses, damages, costs, fines, fees or penalties related to reversed or declined transactions.
Supporting quotations
5.2 Card Transactions.
Stripe will use a Card Network to authorize, clear, and settle all Card Transactions initiated on User’s Cards. Stripe may decline to authorize a Card Transaction or reverse a Card Transaction for any reason, including if (a) Stripe is concerned about the security of the Card or Stripe suspects that the Card is being used without valid authorization or for a Card Unauthorized Purpose; (b) insufficient E-money is loaded onto the Card; (c) Stripe believes that User is acting in breach of this Agreement or the Connected Account Agreement (if applicable) or any other agreement User may have with a Stripe Entity; (d) Stripe believes the Card Transaction is suspicious, fraudulent, illegal or exposes User, Stripe or others to risks unacceptable to Stripe; (e) there are errors, failures or refusals by merchants, payment processors or payment schemes related to the Card Transaction; or (f) the Card Transaction is with a prohibited or restricted merchant or a merchant operating a Prohibited or Restricted Business. If Stripe declines to authorize a Card Transaction, Stripe will, on request, if practicable and to the extent Law permits, inform User of the reason. Stripe is not liable for any losses, damages, costs, fines, fees, or penalties related to reversed or declined Card Transactions.
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
“Card Transaction” means a transaction to make a payment with a Card or, if permitted, to obtain cash at an automatic teller machine (ATM).
“Connected Account Agreement” means the agreement with Stripe that applies to Connected Accounts (except Payout Recipients), which is accessible on the Stripe Legal Page for the Connected Account's jurisdiction.
“Card Unauthorized Purpose” means (a) a fraudulent or illegal purpose; (b) a consumer, personal, or household purpose; and (c) any purpose unrelated to the Stripe Issuing Services.
Qualifications & exceptions
The listed grounds are examples; the right applies 'for any reason'.
Reasons for a decline are given on request, if practicable and to the extent Law permits.
Charges & Financial Obligations · Company practice
A Card Transaction is authorized once your cardholder completes the point-of-sale steps, and cannot then be revoked
Depending on Card features, authorization may cover a single transaction, a series of recurring transactions, or a pre-authorization of a future transaction for a specified or unspecified amount. Stripe treats a Card Transaction as authorized and consented to by the User when an Issuing Authorized User follows the merchant's or Stripe's instructions to authorize it at the point of sale, including online, for example by entering a PIN, signing a receipt, providing Card and other requested details, tapping, waving or swiping the Card, or completing multi-factor authentication such as strong customer authentication under Law. Once Stripe receives an authorization it cannot be withdrawn or revoked.
Supporting quotations
5.3 Authorization of Card Transactions.
Subject to the features of the Card, the authorization of a Card Transaction may include authorizing a single Card Transaction or a series of recurring Card Transactions, or pre-authorizing a future Card Transaction for a specified or unspecified amount. Stripe will treat Card Transactions as authorized and consented to by User where Issuing Authorized Users follow the instructions provided by a merchant or Stripe to effectively authorize the Card Transaction at the point of sale (including online), including where the Issuing Authorized User (as applicable) (a) enters a Personal Identification Number (PIN); (b) signs a sales receipt; (c) provides Card and other requested details; (d) taps, waves or swipes the Card at a card reader; or (e) fulfills multi-factor authentication requirements (including strong customer authentication, as defined under Law). Authorisation of a Card Transaction cannot be withdrawn or revoked once received by Stripe.
Qualifications & exceptions
Authorization forms depend on the features of the Card.
Charges & Financial Obligations · Company practice
Card Transactions are deducted immediately, open-amount purchases hold estimated funds, and Stripe settles net of fees
Stripe receives a Card Transaction when it gets the settlement instruction from the Card Network, and deducts the amount from the Stripe Issuing Account balance as soon as the transaction is made. Where the final amount is unknown at authorization, a hold may be placed on available funds for the estimated amount authorized by or for the User; those funds are unavailable for any other purpose until the merchant or Card Network releases the hold or Stripe receives the final amount or final payment order. Stripe settles Card Transactions to the Card Network, net of fees and amounts owed to Stripe, within the required settlement time frame.
Supporting quotations
5.4 Processing of Card Transactions.
Stripe receives a Card Transaction at the time Stripe receives the Card Transaction settlement instruction from the relevant Card Network. Stripe will deduct the amount of a Card Transaction from the balance of the Stripe Issuing Account as soon as the Card Transaction is made. When a Card is used to initiate a Card Transaction where the final amount of the Card Transaction is unknown at the time of authorization, a hold may be placed on available funds in the Stripe Issuing Account for an estimated amount of the Card Transaction as authorized by (or on behalf of) User. The funds subject to the hold will not be available to User for any other purpose until the merchant or the Card Network releases the hold, or until Stripe receives the final amount of the Card Transaction or receives the final payment order.
5.5 Card Transaction Settlement.
Stripe will settle Card Transactions, net of fees and amounts owed to Stripe, to the relevant Card Network within the required settlement time frame.
Legal Rights & Agreement Rules · Context
Definitions: Issuing Authorized User, Complaint, Platform Provider, Issuing Account, Accountholder, Program and Services
These definitions finish Section 14. A 'Connected Account Agreement' is the agreement with Stripe that applies to Connected Accounts other than Payout Recipients, found on the Stripe Legal Page for the account's jurisdiction. An 'Issuing Authorized User' is an individual the accountholder authorizes to use a Card on its behalf, such as an employee, contractor or representative. An 'Issuing Complaint' is any expression of dissatisfaction with a product, service, policy or employee related to a Stripe Issuing Program. A 'Platform Provider' is the platform that gives the User access to the program, where the User is a Connected Account or otherwise reaches the program through a platform. The 'Stripe Issuing Account' is the account Stripe or an Affiliate maintains for the accountholder and each subaccount. A 'Stripe Issuing Accountholder' is a business or organization that finished onboarding and was approved for an account. The 'Stripe Issuing Accountholder Services' include access to the program and Card spend management, and a 'Stripe Issuing Administrator' is the individual the accountholder appoints to manage its participation. The 'Stripe Issuing Program' is the Card issuing program and related services plus those Services. 'Stripe Issuing Program Guidelines' are the product design, marketing, compliance, reporting and other guidelines and requirements Stripe and its Affiliates set, as updated from time to time. 'Stripe Issuing Services' are the Accountholder Services and the Stripe Issuing Platform Services, which let the User co-market the Accountholder Services to its Platform Users and provide access to them for Stripe Issuing Accountholders. A 'Supported Currency' is a currency Stripe communicates as supported, and 'User Materials' are the Marks or other materials the User or accountholder wants on Cards and other materials the User gives Stripe for the program.
Supporting quotations
“Connected Account Agreement” means the agreement with Stripe that applies to Connected Accounts (except Payout Recipients), which is accessible on the Stripe Legal Page for the Connected Account's jurisdiction.
“Issuing Authorized User” means an individual a Stripe Issuing Accountholder authorizes to use a Card to make Card Transactions on the Stripe Issuing Accountholder’s behalf (e.g., the Stripe Issuing Accountholder’s employee, independent contractor or representative designated as an authorized user).
“Issuing Complaint” means any expression of dissatisfaction with a product, service, policy, or employee related to a Stripe Issuing Program.
“Platform Provider” means the platform that gives User access to the Stripe Issuing Program (if User is a Connected Account or if User otherwise accesses the Stripe Issuing Program through a platform).
“Stripe Issuing Account” means the account Stripe or a Stripe Affiliate maintains for a Stripe Issuing Accountholder, and each subaccount to that account.
“Stripe Issuing Accountholder” means a business or organization that has successfully completed the onboarding requirements described in these Stripe Issuing Accountholder Terms and been approved for a Stripe Issuing Account.
“Stripe Issuing Accountholder Services” means Services that Stripe and its Affiliates make available to Stripe Issuing Accountholders, including (a) providing Stripe Issuing Accountholders with access to the Stripe Issuing Program; (b) enabling Stripe Issuing Accountholders to manage Card spend, and (c) other services described in these Stripe Issuing Accountholder Terms.
“Stripe Issuing Administrator” means the individual that a Stripe Issuing Accountholder appoints to manage its participation in the Stripe Issuing Program.
“Stripe Issuing Program” means a Card issuing program and related services that Stripe and its Affiliates make available to Stripe Issuing Accountholders, together with the Stripe Issuing Accountholder Services.
“Stripe Issuing Program Guidelines” means all product design, marketing, compliance, reporting, and other guidelines and requirements Stripe and its Affiliates establish related to the Stripe Issuing Services, as updated from time to time.
“Stripe Issuing Services” means the Stripe Issuing Accountholder Services and Stripe Issuing Platform Services.
“Stripe Issuing Platform Services” means the Services that allow User to co-market the Stripe Issuing Accountholder Services to User’s Platform Users and provide access to the Stripe Issuing Accountholder Services to Stripe Issuing Accountholders.
“Supported Currency” means a currency supported under the Stripe Issuing Accountholder Services as communicated to User by Stripe.
“User Materials” means (a) all Marks or other materials that User or a Stripe Issuing Accountholder wish to place on Cards; or (b) all other materials that User provides to Stripe for the purposes of the Stripe Issuing Programs.
Qualifications & exceptions
The Issuing Program Guidelines can be updated by Stripe and Stripe's Affiliates from time to time.
Not stated here
The Guidelines themselves are not part of this document.
Charges & Financial Obligations · User right or choice
Redeem Issuing Account funds at par any time, except money spent or held; redeeming all cancels Cards
The User may redeem the funds in the Stripe Issuing Account at any time, in whole or in part, at par value. The User is not entitled to a refund of money already spent on, or held for, authorized Card Transactions. Redemption requests go through the communication methods Stripe specifies, including the Stripe Technology, and state the amount. If the User redeems all the funds, Stripe cancels the Cards and the User must, at its own expense, immediately return the cancelled Cards in its possession or control or certify in writing that cancelled or unused Cards were destroyed. Redeemed funds are returned by bank transfer to a User Bank Account, and the User must provide any documents Stripe reasonably requests to process the request.
Supporting quotations
User may redeem the funds on the Stripe Issuing Account at any time in whole or in part at par value. User is not entitled to a refund of money that has already been spent on or held for authorized Card Transactions. User must request redemptions via the communication methods specified by Stripe (including through the Stripe Technology), specifying the amount of redemption. If User chooses to redeem all of the funds on the Stripe Issuing Account, Stripe will cancel the Cards and User will, at User’s sole expense (a) immediately return the cancelled Cards in User’s possession or under User’s control, or (b) provide written certification of destruction of any cancelled or unused Cards. All redeemed funds will be returned to User by bank transfer to a User Bank Account. User will provide Stripe with any documents reasonably requested by Stripe to enable Stripe to process a redemption request.
Qualifications & exceptions
Redemption is at par value and does not cover money already spent on or held for authorized Card Transactions.
Redeeming all funds triggers Card cancellation and return or written certification of destruction at the User's expense.
Not stated here
The communication methods Stripe specifies for redemption requests are not listed in these terms.
Charges & Financial Obligations · Restriction or exception
Stripe may block redemption on breach, Card Unauthorized Purpose or unacceptable risk
Stripe may prevent the User from redeeming funds in the Stripe Issuing Account if Stripe believes the User's actual or intended use of the account (a) breaches the Agreement or any other agreement between the User and Stripe, (b) is for a Card Unauthorized Purpose, which is a fraudulent or illegal purpose, a consumer, personal or household purpose, or any purpose unrelated to the Stripe Issuing Services, or (c) could expose the User, Stripe or others to risks Stripe finds unacceptable. Unless Law restricts it, Stripe will notify the User as soon as reasonably practicable if it takes that action.
Supporting quotations
6.3 Stripe Action.
Stripe may prevent User from redeeming funds in the Stripe Issuing Account if Stripe believes User’s use (or intended use) of the Stripe Issuing Account (a) breaches this Agreement or any other agreement between User and Stripe; (b) is for any Card Unauthorized Purpose; or (c) could expose User, Stripe or others to risks unacceptable to Stripe. Unless restricted by Law, Stripe will notify User as soon as reasonably practicable if Stripe takes that action.
“Card Unauthorized Purpose” means (a) a fraudulent or illegal purpose; (b) a consumer, personal, or household purpose; and (c) any purpose unrelated to the Stripe Issuing Services.
Qualifications & exceptions
The grounds turn on Stripe's belief about actual or intended use.
Notice follows the action, 'as soon as reasonably practicable', and is not required where Law restricts it.
Not stated here
No time limit or release process is stated for a block on redemption.
Charges & Financial Obligations · Restriction or exception
No cash back or Card Unauthorized Purpose; Stripe may require a daily limit and decline above it
The User and its Issuing Authorized Users may use the Cards for Card Transactions. The User must not use Cards to obtain cash back at the point of sale or for a Card Unauthorized Purpose (a fraudulent or illegal purpose, a consumer, personal or household purpose, or a purpose unrelated to the Stripe Issuing Services). Acting reasonably, Stripe may require the User to set a daily Card Transaction Limit, the maximum amount available for Card Transactions on a Card, to limit the risk of loss to Stripe and reduce declined transactions. If Stripe requires one, it may decline Card Transactions above that daily limit.
Supporting quotations
7.1 Use of the Cards.
User and User’s Issuing Authorized Users are permitted to use the Cards for Card Transactions. User must not use Cards (a) to obtain cash back at the point of sale; or (b) for a Card Unauthorized Purpose. Stripe may, acting reasonably, require User to establish a daily Card Transaction Limit to prevent the risk of loss to Stripe, and to reduce the rate of declined Card Transactions. If Stripe requires a daily Card Transaction Limit, Stripe may decline any Card Transactions in excess of the daily Card Transaction Limit.
“Card Transaction Limit” means the maximum amounts available for Card Transactions on a Card.
“Card Unauthorized Purpose” means (a) a fraudulent or illegal purpose; (b) a consumer, personal, or household purpose; and (c) any purpose unrelated to the Stripe Issuing Services.
Qualifications & exceptions
Stripe's power to require a daily limit must be exercised reasonably and for the stated purposes.
Not stated here
The amount of any daily limit is not stated here.
Account & Service Control · Procedure
Cards expire on their printed date; replacements may cost a fee; you set and pass on spend limits
Cards are valid until the expiry date printed on them. The User may request a replacement Card and Stripe may charge a fee for issuing replacements. The User, or its Platform Provider where applicable, may set limits or restrictions on the Stripe Issuing Account through the Stripe Dashboard, including spend limits on individual Card Transactions, a maximum spend in a given period, a cap on the number of cards issued to the account and the types of merchants where Cards may be used, and is responsible for communicating and implementing those limits to its Issuing Authorized Users.
Supporting quotations
Cards are valid for the period ending on the expiry date set out on the relevant Card. User may request a replacement Card and Stripe may charge a fee for the issuance of replacement Cards.
User, (or, if applicable, User’s Platform Provider) may establish limits or restrictions on User’s Stripe Issuing Account through User’s Stripe Dashboard, including spend limits on individual Card Transactions, a maximum spend limit in any given period, a limit on the number of cards issued to User’s Stripe Issuing Account and the types of merchants with which User’s Cards may be used. User (or, if applicable, User’s Platform Provider) is responsible for communicating and implementing any limits to User’s Issuing Authorized Users.
Qualifications & exceptions
Limits can be set by the User or, where applicable, its Platform Provider.
Not stated here
The replacement-card fee amount is not stated here.
Account & Service Control · Restriction or exception
You handle all cardholder support, Stripe gives none, and you cannot outsource it
The User, or its Platform Provider where applicable, handles all enquiries about Card usage and lost, damaged or stolen Cards, and all other enquiries from Issuing Authorized Users. Stripe will not provide support to Issuing Authorized Users for the Stripe Issuing Services. The User may not outsource Issuing Authorized User support to any third party.
Supporting quotations
7.2 Issuing Authorized User Servicing.
User (or, if applicable, User’s Platform Provider) will handle (a) all enquiries regarding Card usage and lost, damaged or stolen Cards and (b) all other enquiries from Issuing Authorized Users. Stripe will not provide support to Issuing Authorized Users in relation to the Stripe Issuing Services. User may not outsource Issuing Authorized User support to any third party.
Qualifications & exceptions
The duty sits with the User or its Platform Provider, if one applies.
Charges & Financial Obligations · Procedure
Report lost cards and bad transactions at once in the Dashboard and cancel Cards; 13-month limit
If the User believes a Card is lost or stolen, or that Card or account transactions were incorrectly executed, defective or unauthorized, it must immediately file a dispute for unauthorized Card Transactions through the Stripe Dashboard and cancel any compromised Cards through the Dashboard. Disputing a transaction does not cancel a Card, and the User may incur additional liability if it fails to cancel a compromised Card. For an incorrectly executed, defective or unauthorized charge, the User may first contact the merchant; if that fails it must notify Stripe through the Dashboard without undue delay and no later than 13 months after the transaction appears on the Stripe Issuing Account.
Supporting quotations
8. Card Disputes.
8.1 Reporting Unauthorized Transactions.
If User believes (a) User’s Card has been lost or stolen; or (b) there are incorrectly executed, defective, or unauthorized transactions on User’s Card or Stripe Issuing Account, User must immediately, (i) report any unauthorized Card Transactions to Stripe by filing a dispute through the Stripe Dashboard; and (ii) cancel any compromised Cards through the Stripe Dashboard. Disputing an incorrectly executed, defective, or unauthorized Card Transaction will not cancel a Card. User may incur additional liability if User fails to cancel a compromised Card through the Stripe Dashboard.
8.2 Reporting Incorrectly Executed Transactions.
If User believes that User’s Card or Stripe Issuing Account was subject to an incorrectly executed, defective, or unauthorized charge, User may contact the merchant to resolve the dispute regarding the relevant Card Transaction. If User is unable to resolve the dispute with the merchant, then User must notify Stripe of the incorrectly executed, defective or unauthorized Card Transaction through User’s Stripe Dashboard. User must notify Stripe of an incorrectly executed, defective, or unauthorized Card Transactions to Stripe without undue delay, and no later than 13 months from the date the Card Transaction appears on User’s Stripe Issuing Account.
Qualifications & exceptions
Disputing a transaction does not cancel the Card; cancellation is a separate step.
The 13-month outer limit runs from the date the transaction appears on the Stripe Issuing Account.
Charges & Financial Obligations · Company practice
Stripe decides in its sole discretion whether to credit a dispute and then takes your merchant claims
When the User reports an incorrectly executed, defective or unauthorized Card Transaction in the Stripe Dashboard, Stripe evaluates the information under Law and the Card Network Rules. If Stripe determines in its sole discretion that the transaction was incorrectly executed, defective or unauthorized, it credits the amount back to the Stripe Issuing Account. If Stripe fully or partially credits a transaction, the User agrees to transfer to Stripe, and sign any agreements needed to do so, all claims other than tort claims that the User may have against the merchant for that transaction.
Supporting quotations
8.3 Determining Incorrectly Executed, Defective, or Unauthorized Transactions.
When User notifies Stripe of an incorrectly executed, defective, or unauthorized Card Transaction through the Stripe Dashboard, Stripe will evaluate the submitted information in accordance with Law and the Card Network Rules. If Stripe determines, in its sole discretion, that the Card Transaction was incorrectly executed, defective, or unauthorized, Stripe will credit the amount of the applicable Card Transaction back to User’s Stripe Issuing Account. If Stripe fully or partially credits the amount of a Card Transaction to User’s Stripe Issuing Account, User agrees to transfer (and execute any necessary agreements to effect the transfer) to Stripe all claims (excluding tort claims) that User may have against the merchant for the Card Transaction.
Qualifications & exceptions
The credit decision is in Stripe's sole discretion, though Stripe evaluates under Law and Card Network Rules.
The transfer of claims excludes tort claims.
Not stated here
The outcome for a partially credited transaction on the User's remaining claim is not spelled out beyond the transfer of all non-tort claims.
Charges & Financial Obligations · Company commitment
Stripe reimburses disputes you did not authorize, minus a EUR 50 or GBP 35 share, with exclusions and recoupment
Stripe will reimburse the User for a card dispute where Stripe determines neither the User nor an Issuing Authorized User authorized the underlying Card Transaction. The User bears the first EUR 50 or GBP 35 (as applicable) of a dispute where Stripe reasonably believes the User should have been aware the Card was lost, misappropriated or stolen. Stripe is not liable for a card dispute where the User or an Issuing Authorized User used a Card for a Card Unauthorized Purpose (a fraudulent or illegal purpose, a consumer, personal or household purpose, or a purpose unrelated to the Stripe Issuing Services), intentionally or through gross negligence failed to use the Card as the Agreement or the Stripe Issuing Program Guidelines require, or where the User failed to notify Stripe immediately that the Card was lost, stolen or misappropriated. If Stripe reimburses a transaction and later determines it was duly authorized and correctly executed, or that Stripe is otherwise not liable, it may recoup or set off that amount from the Stripe Issuing Account.
Supporting quotations
Stripe will reimburse User for any card dispute where Stripe determines that neither User nor an Issuing Authorized User authorized the underlying Card Transaction, provided that (a) User will be responsible for the first €50 or £35 (as applicable) of a card dispute where Stripe reasonably believes User should have been aware that the Card was lost, misappropriated, or stolen; (b) Stripe will not be liable for any card dispute where (i) User or an Issuing Authorized User used a Card for a Card Unauthorized Purpose or either intentionally or as a result of gross negligence, failed to use the Card in accordance with the terms of this Agreement or the Stripe Issuing Program Guidelines; or (ii) User failed to immediately notify Stripe of the Card becoming lost, stolen or misappropriated (in accordance with Section 9 of these Stripe Issuing Accountholder Terms).
If Stripe reimburses User for an unauthorized Card Transaction and subsequently determines that the relevant Card Transaction was duly authorized and correctly executed or Stripe is otherwise not liable for the Card Transaction, Stripe may recoup or set off an amount equal to that reimbursed amount from User’s Stripe Issuing Account.
“Card Unauthorized Purpose” means (a) a fraudulent or illegal purpose; (b) a consumer, personal, or household purpose; and (c) any purpose unrelated to the Stripe Issuing Services.
“Stripe Issuing Program Guidelines” means all product design, marketing, compliance, reporting, and other guidelines and requirements Stripe and its Affiliates establish related to the Stripe Issuing Services, as updated from time to time.
Qualifications & exceptions
Reimbursement depends on Stripe's determination that neither the User nor an Issuing Authorized User authorized the transaction.
The first EUR 50 or GBP 35 falls on the User only where Stripe reasonably believes the User should have known the Card was lost, misappropriated or stolen.
Stripe may recoup or set off reimbursed amounts from the Stripe Issuing Account if it later finds the transaction was authorized or it was not liable.
Not stated here
The notification duty is cited as 'Section 9' of these terms, which is the Card Security section; the immediate reporting duty appears in Section 8.1, so the cross-reference is unclear.
Security & Safeguards · Restriction or exception
Secure Cards and Personal Data, use industry-standard encryption and anti-fraud measures, and monitor for fraud
The User must secure Cards and Personal Data in its possession or control and ensure its Issuing Authorized Users do the same. When Cards and Personal Data are stored or processed digitally, the User must use appropriate organizational, physical and technical measures, including industry-standard encryption and anti-fraud measures, for itself and its Issuing Authorized Users. The User must monitor the Stripe Issuing Account and each Card for suspicious or unauthorized activity and fraud.
Supporting quotations
9. Card Security.
9.1 Securing Cards and Account Data.
User must secure Cards and Personal Data in User’s possession or control, and User must ensure that User’s Issuing Authorized Users secure Cards and Personal Data in their possession or control. When stored or processed digitally, User must use appropriate organizational, physical and technical measures to secure Cards and Personal Data in User and User’s Issuing Authorized Users’ possession or control, including through the use of industry-standard encryption and anti-fraud measures. User must monitor for any suspicious or unauthorized activities and fraud on User’s Stripe Issuing Account and each Card.
Qualifications & exceptions
The duty covers the User and its Issuing Authorized Users.
Not stated here
What counts as 'appropriate' measures or 'industry-standard' encryption is not specified.
Legal Rights & Agreement Rules · Restriction or exception
You bear costs from lax safeguarding, late reporting or Card sharing; Stripe disclaims unauthorized-use losses
To the extent Law permits, the User is responsible for Card Transactions and for all costs, fees, fines and penalties the User or Stripe incur because an Issuing Authorized User failed to exercise reasonable care in safeguarding Cards from loss, theft or misappropriation or failed to promptly report loss, theft or fraud. If the User or an Issuing Authorized User lets another party use a Card or Personal Data for any purpose, the User is responsible for that use and all related losses, damages, costs, fines, fees or penalties. To the extent Law permits, Stripe is not liable for losses, damages, costs, fines, fees or penalties related to unauthorized access to or use of a Card or the Stripe Issuing Account, or to the User's failure to use or implement anti-fraud measures, security controls or other data security measures.
Supporting quotations
9.2 Unauthorized Transactions.
To the extent Law permits, User is responsible for Card Transactions, and all costs, fees, fines, and penalties User or Stripe incur related to an Issuing Authorized User’s failure to (a) exercise reasonable care in safeguarding Cards from loss, theft or misappropriation; or (b) promptly report loss or theft, including fraud.
To the extent Law permits, if User or an Issuing Authorized User allows another party to use the Card or Personal Data for any purpose, User is responsible for that use, including all losses, damages, costs, fines, fees, or penalties related to that use. To the extent Law permits, Stripe is not liable for any losses, damages, costs, fines, fees, or penalties related to (x) unauthorized access to or use of a Card or User’s Stripe Issuing Account; or (y) User’s failure to use or implement anti-fraud measures, security controls or any other data security measures.
Qualifications & exceptions
Each allocation applies 'to the extent Law permits'.
Charges & Financial Obligations · Company practice
Issuing fees follow the Pricing Page or your platform's rates, plus penalties; Stripe may change them on advance notice
Stripe provides the Stripe Issuing Services at the rates and fees on the Stripe Pricing Page unless the User and Stripe agree otherwise in writing. A User that is a Connected Account may receive the services through its Platform Provider at other rates or fees the platform discloses. The User is also responsible for penalties imposed on the User, Stripe or a Stripe Affiliate relating to the Stripe Issuing Account and all Cards. Fees and penalties may include periodic fees, foreign transaction fees, penalties for misuse, funds transfer fees, account maintenance fees, Card issuance or replacement fees and penalties for late or failed payments, and are on top of the amounts owed for Card Transactions. Stripe may change fees or penalties by giving advance notice before revisions apply to the User, subject to applicable Law.
Supporting quotations
10. Stripe Issuing Program Fees.
10.1 Stripe Issuing Program Fees.
Stripe will provide User the Stripe Issuing Services at the rates and for the fees described on the Stripe Pricing Page unless User and Stripe otherwise agree in writing. If User is a Connected Account, User may receive the Stripe Issuing Services through the relevant Platform Provider at other rates or fees disclosed to User by the Platform Provider. In addition to the fees, User is also responsible for any penalties imposed on User, Stripe or any Stripe Affiliate in relation to the Stripe Issuing Account and all Cards. Fees and penalties may include periodic fees, foreign transaction fees, penalties for misuse, funds transfer fees, account maintenance fees, Card issuance or replacement fees, and penalties for late or failed payments. All fees or penalties User owes are in addition to amounts User owes for Card Transactions on Cards. Stripe may change fees or penalties by providing User advance notice before revisions become applicable to User, subject to applicable Law.
Qualifications & exceptions
The listed fee types are examples ('may include').
Changes require advance notice before they apply, subject to applicable Law.
Not stated here
The fee amounts are on the Stripe Pricing Page or in the platform's disclosures, not supplied here.
The length of the advance notice is not stated.
Charges & Financial Obligations · Restriction or exception
You are responsible for all Card Transactions and Stripe's resulting losses; Stripe may deduct stamp duties and levies
As between the User and Stripe, the User is responsible for all Card Transactions and must reimburse Stripe for losses, damages, costs, fines, fees or penalties that Stripe and its Affiliates incur as a result of the actions or inactions of the User or its Issuing Authorized Users, including liability related to insufficient funds availability or debit reversals. Notwithstanding the Agreement or the Connected Account Agreement where applicable, Stripe may deduct all applicable government levies and stamp duties on Cards from the Stripe Issuing Account.
Supporting quotations
10.2 Liability for Losses.
As between User and Stripe, User is responsible for all Card Transactions and User will reimburse Stripe for any losses, damages, costs, fines, fees, or penalties that Stripe and its Affiliates incur that result from User’s actions or inactions, or those of User’s Issuing Authorized Users, including liability related to insufficient funds availability or debit reversals.
10.3 Card Stamp Duty.
Notwithstanding the terms of this Agreement (or the Connected Account Agreement, as applicable), Stripe may deduct all applicable government levies and stamp duties in respect of Cards from User’s Stripe Issuing Account.
Qualifications & exceptions
The reimbursement duty covers losses resulting from the actions or inactions of the User or its Issuing Authorized Users.
Sharing & Disclosure · Company practice
You must hold the rights and consents for cardholders' Personal Data; Stripe shares it with card printers and Affiliates
The User must have and maintain all rights and consents under Law for Stripe to collect, use, retain and disclose the Personal Data the User provides or authorizes Stripe to collect, including data Stripe may collect directly from Issuing Authorised Users. The User is solely responsible for telling Issuing Authorised Users that Stripe may receive Personal Data from the User, and must give them all necessary notices and obtain the rights and consents Stripe needs to lawfully collect, use, retain and disclose their Personal Data in the ways the Agreement (including Section 4.5 of the General Terms) and Stripe's Privacy Policy describe. Stripe provides Issuing Authorised Users' Personal Data to third-party service providers, including those engaged for Card printing, and their Affiliates, and to Stripe's Affiliates, to enable the Stripe Issuing Program. Stripe may delete or disconnect an Issuing Authorised User's Personal Data from the Stripe Issuing Account when Law or the Card Network Rules require.
Supporting quotations
User must have and maintain all necessary rights and consents under Law to provide to Stripe and to allow Stripe to collect, use, retain and disclose, all Personal Data that User provides to Stripe or authorize Stripe to collect, including data that Stripe may collect directly from Issuing Authorised Users. User is solely responsible for disclosing to Issuing Authorised Users that Stripe may receive Personal Data from User. User must provide all necessary notices to and obtain all necessary rights and consents from each Issuing Authorised User sufficient to enable Stripe to lawfully collect, use, retain and disclose their Personal Data in the ways this Agreement (including Section 4.5 of the General Terms) and Stripe's Privacy Policy describe. Stripe provides Issuing Authorised Users' Personal Data to third-party service providers, including third parties engaged for Card printing services, and their respective Affiliates, as well as to Stripe’s Affiliates, to enable Stripe to provide the Stripe Issuing Program. Stripe may delete or disconnect an Issuing Authorised User’s Personal Data from User’s Stripe Issuing Account when Law or the Card Network Rules require.
Qualifications & exceptions
The notice and consent duty falls entirely on the User for Issuing Authorised Users.
Stripe's deletion or disconnection is tied to what Law or the Card Network Rules require.
Not stated here
Section 4.5 of the General Terms and Stripe's Privacy Policy are cited but not supplied in this document.
Use & Processing · Restriction or exception
Use Personal Data tied to your Issuing Account only for internal business purposes and your Agreement duties
The User may use Personal Data related to its Stripe Issuing Account only for its internal business purposes and to fulfil its obligations under the Agreement.
Supporting quotations
11.2 User’s Use of Personal Data.
User must only use Personal Data related to User’s Stripe Issuing Account for User’s internal business purposes and to fulfil User’s obligations under this Agreement.
Qualifications & exceptions
The limit covers Personal Data related to the User's Stripe Issuing Account.
Legal Rights & Agreement Rules · Restriction or exception
Stripe is not liable for losses from delay or failure in actioning a Card Transaction request
Stripe is not liable to the User, Stripe Issuing Administrators or Issuing Authorized Users for losses, damages, costs, fines, fees or penalties they sustain because of a delay or failure in actioning a Card Transaction request.
Supporting quotations
Disclaimer of Liability.
Stripe is not liable to User, Stripe Issuing Administrators or Issuing Authorized Users for any losses, damages, costs, fines, fees, or penalties sustained by User, Stripe Issuing Administrators or Issuing Authorized Users due to delay or failure in actioning a Card Transaction request.
Qualifications & exceptions
The disclaimer covers delay or failure in actioning a Card Transaction request and is stated without any carve-out.
Not stated here
The terms do not say whether Law limits this disclaimer.
Account & Service Control · Company practice
Stripe may use its remedies for breach, nonpayment, over-limit use, stale information, excessive disputes, risk or Law
Stripe may exercise the remedies in Section 13.3 if (a) the User fails to comply with any obligation in the Issuing Accountholder Terms; (b) the User fails to pay amounts owed to Stripe or its Affiliates for the Stripe Issuing Program; (c) the User starts a Card Transaction that would exceed or violate a limit set for its use of the program; (d) Stripe determines the User gave inaccurate application information or failed to keep it current; or (e) the User has excessive Card Transaction disputes or unauthorized Card Transactions. Separately, Stripe may use the same remedies if it reasonably determines it may incur losses from credit, fraud, criminal activity or other risks associated with a User Entity after the terms terminate, or if Law requires. These rights do not limit Stripe's other rights or remedies.
Supporting quotations
13. Additional Remedies.
13.1 Stripe Remedies - Specific Triggers.
Without limiting Stripe’s other rights or remedies under this Agreement, Stripe may exercise any one or more of the remedies stated in Section 13.3 of these Stripe Issuing Accountholder terms if (a) User fails to comply with any of its obligations under these Stripe Issuing Accountholder Terms; (b) User fails to pay any amounts User owes to Stripe or any of its Affiliates in connection with the Stripe Issuing Program; (c) User initiates a Card Transaction that would exceed or violate a limit established for User’s use of the Stripe Issuing Program; (d) Stripe determines that User provided inaccurate information in User's application, or that User has failed to keep this information current; or (e) User experiences excessive Card Transaction disputes or unauthorized Card Transactions.
13.2 Stripe Remedies - General Trigger.
Without limiting Stripe’s other rights and remedies under this Agreement, Stripe may exercise any or all of the remedies stated in Section 13.3 of these Stripe Issuing Accountholder Terms if (a) Stripe reasonably determines that Stripe may incur losses resulting from credit, fraud, criminal activity, or other risks associated with a User Entity after these Stripe Issuing Accountholder Terms terminate; or (b) Law requires.
Qualifications & exceptions
The specific triggers do not limit Stripe's other rights or remedies.
The general trigger requires Stripe to reasonably determine a risk of loss tied to a User Entity after termination, or a legal requirement.
Not stated here
'Excessive' disputes is not defined with a number.
Account & Service Control · Company practice
Remedies: suspend or end the account and Cards, accelerate debts, refuse or reverse transactions, offboard
If a trigger in Section 13.1 or 13.2 (or another provision that refers to these remedies) occurs, Stripe may suspend or terminate the User's Stripe Issuing Account or any or all Cards, declare amounts the User owes due and payable, refuse to authorize any Card Transactions, reverse any Card Transactions, and terminate the Issuing Accountholder Terms and offboard the User as a Stripe Issuing Accountholder. These rights do not limit Stripe's other rights and remedies. If Stripe suspends the account or a Card, it may require the User to pay amounts owed to Stripe before reactivating the account or that Card.
Supporting quotations
13.3 Stripe Remedies - Scope.
Without limiting Stripe’s other rights and remedies under this Agreement, if a triggering event in Sections 13.1 or 13.2 of these Stripe Issuing Accountholder Terms (or any other provision of this Agreement that refers to these remedies) has occurred, then, Stripe may: (a) suspend or terminate User’s Stripe Issuing Account or any or all Cards; (b) declare any amounts User owes to Stripe due and payable; (c) refuse to authorize any Card Transactions; (d) reverse any Card Transactions; and (e) terminate these Stripe Issuing Accountholder Terms and offboard User as a Stripe Issuing Accountholder.
13.4 Reactivating after Suspension.
If Stripe suspends User’s Stripe Issuing Account or a Card, Stripe may require User to pay amounts User owes to Stripe before reactivating User’s Stripe Issuing Account or that Card.
Qualifications & exceptions
The remedies apply once a trigger in Section 13.1 or 13.2, or another provision that refers to them, has occurred.
Reactivation may be conditioned on paying amounts owed.
Charges & Financial Obligations · Company practice
Stripe and its Affiliates may set off Issuing program debts against other funds Stripe holds for you
Stripe, for itself and on behalf of each of its Affiliates, may set off any amounts the User owes in connection with its participation in the Stripe Issuing Program against other funds Stripe holds or processes on the User's behalf.
Supporting quotations
13.5 Right of Setoff.
Stripe, for itself and on behalf of each of its Affiliates, may set off any amounts User owes to Stripe in connection with User’s participation in the Stripe Issuing Program against other funds that Stripe holds or processes on User’s behalf.
Qualifications & exceptions
The set-off reaches other funds Stripe holds or processes on the User's behalf, not only Issuing Account funds.
Account & Service Control · User right or choice
You may close your Issuing Account or cancel any Card by notifying Stripe or your Platform Provider
The User may close its Stripe Issuing Account or cancel any Card by notifying Stripe or, if applicable, its Platform Provider.
Supporting quotations
13.6 Closing User’s Stripe Issuing Account.
User may close User’s Stripe Issuing Account or cancel any Card by notifying Stripe (or, if applicable, User’s Platform Provider).
Qualifications & exceptions
Notice goes to Stripe or, where applicable, the Platform Provider.
Not stated here
These terms do not state what happens to remaining funds on closure beyond the redemption terms elsewhere.
Section 14 begins the definitions. A 'Card' is a Card Network-branded payment card, physical or tokenized, encrypted or digitized, issued to a Stripe Issuing Accountholder for its business purposes in the Stripe Issuing Program. A 'Card Network' is a payment card network, including those of Visa, Mastercard, American Express and Discover, and 'Card Network Rules' are the Payment Method Rules a Card Network publishes. A 'Card Transaction' is a payment made with a Card or, if permitted, cash obtained at an ATM. A 'Card Transaction Limit' is the maximum amount available for Card Transactions on a Card. A 'Card Unauthorized Purpose' is a fraudulent or illegal purpose, a consumer, personal or household purpose, or any purpose unrelated to the Stripe Issuing Services. A 'Connected Account' is a Platform User with a Stripe Account onboarded to a Stripe Connect Platform through the Stripe Connect Services, or a Payout Recipient. The definitions continue in the next packet.
Supporting quotations
14. Definitions.
“Card” means a Card Network-branded payment card (which may be a physical card or tokenized, encrypted, or digitized form of a physical card) issued to a Stripe Issuing Accountholder for the Stripe Issuing Accountholder’s business purposes in connection with the Stripe Issuing Program.
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
“Card Network Rules” means the Payment Method Rules published by a Card Network.
“Card Transaction” means a transaction to make a payment with a Card or, if permitted, to obtain cash at an automatic teller machine (ATM).
“Card Transaction Limit” means the maximum amounts available for Card Transactions on a Card.
“Card Unauthorized Purpose” means (a) a fraudulent or illegal purpose; (b) a consumer, personal, or household purpose; and (c) any purpose unrelated to the Stripe Issuing Services.
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
Legal Rights & Agreement Rules · Context
UK/EEA Issuing Platform terms (Sept 28, 2026) supplement the General Terms and govern your role as a Connect Platform
These Stripe Issuing Platform Terms for the United Kingdom and European Economic Area, last modified September 28, 2026, supplement the General Terms and, together with the Stripe Financial Services Terms and Stripe Connect Infrastructure Terms (both incorporated by reference), govern the User's participation in the Stripe Issuing Program as a Stripe Connect Platform. If the User receives Cards and otherwise participates as a Stripe Issuing Accountholder, the Stripe Issuing Accountholder Terms apply instead for that role. Capitalized terms not defined here take their meaning from the General Terms, Financial Services Terms and Connect Infrastructure Terms.
Supporting quotations
Stripe Issuing—Platform (United Kingdom and European Economic Area)
Last modified: September 28, 2026
1. Stripe Issuing Services - Platform.
These terms (“Stripe Issuing Platform Terms”) supplement the General Terms and, together with the Stripe Financial Services Terms, and Stripe Connect Infrastructure Terms each of which are incorporated into these terms by this reference, govern User’s participation in the Stripe Issuing Program as a Stripe Connect Platform. If User receives Cards and otherwise participates in the Stripe Issuing Program as a Stripe Issuing Accountholder, the Stripe Issuing Accountholder Terms apply. Capitalized terms that are not defined in these terms have the same meanings given to them in the General Terms, Stripe Financial Services Terms, and Stripe Connect Infrastructure Terms.
Qualifications & exceptions
The accountholder role is governed by the Stripe Issuing Accountholder Terms, not these platform terms.
Not stated here
The General Terms and the Connect Infrastructure Terms are separate documents not supplied in this run.
Account & Service Control · Restriction or exception
You and Stripe set up a joint program; offer Issuing only to eligible Connected Accounts for business purposes
The User and Stripe will jointly establish a program through which eligible Connected Accounts may access a Stripe Issuing Program. The User must offer the Stripe Issuing Program only to eligible Connected Accounts and only for their business purposes.
Supporting quotations
2. Overview.
User and Stripe will jointly establish a program through which eligible Connected Accounts may access a Stripe Issuing Program. User must offer the Stripe Issuing Program only to eligible Connected Accounts for their business purposes.
Qualifications & exceptions
Eligibility of Connected Accounts and business-purpose use are both limits on the offer.
Not stated here
Eligibility criteria are not defined in this section.
Account & Service Control · Procedure
Stripe must approve your use of the Platform Services and each Connected Account; you must supply information on request
Stripe must approve the User's use of the Stripe Issuing Platform Services and, before approving, may require User Information and information about the User's activities and intended use, which may be separate from or in addition to what the User gave for other Services. The User must promptly provide information about its use of the Stripe Issuing Program that Stripe requests from time to time. Stripe must also approve each Connected Account before it can become a Stripe Issuing Accountholder.
Supporting quotations
3. Approvals and Onboarding.
3.1 Approvals.
(a) Platform Approval. Stripe must approve User’s use of the Stripe Issuing Platform Services and prior to granting its approval, Stripe may require User to provide User Information, and information about User’s activities and intended use of the Stripe Issuing Platform Services. This information may be separate from or in addition to information User previously provided to Stripe in connection with other Services. User must promptly provide information related to User’s use of the Stripe Issuing Program that Stripe may request from time to time.
(b) Connected Account Approval. Stripe must approve each Connected Account before it can become a Stripe Issuing Accountholder.
Qualifications & exceptions
Approval is required both for the platform and for each Connected Account.
Account & Service Control · Context
Stripe issues Cards directly to accountholders, who are its customers for regulated financial services, not you
Stripe provides the Stripe Issuing Platform Services to the User and the Stripe Issuing Services to Stripe Issuing Accountholders. Stripe issues Cards directly to a Stripe Issuing Accountholder, who gives them to Issuing Authorized Users for business-related purchases and as Stripe otherwise permits. The User acknowledges and agrees that for the Regulated Financial Services, Stripe's customers are the Stripe Issuing Accountholders, and not the User or any Issuing Authorized Users, who act under the accountholder's authority.
Supporting quotations
3.2 Use of the Issuing Platform Services.
Stripe will provide Stripe Issuing Platform Services to User, and Stripe Issuing Services to Stripe Issuing Accountholders. Stripe will issue Cards directly to a Stripe Issuing Accountholder for the Stripe Issuing Accountholder to provide to Issuing Authorized Users for use on business-related purchases and as otherwise permitted by Stripe. User acknowledges and agrees that, in respect of the Regulated Financial Services, Stripe’s customers are the Stripe Issuing Accountholders and not User or any Issuing Authorized Users (who will be acting under the authority of the Stripe Issuing Accountholder).
Qualifications & exceptions
The customer relationship statement is made for the Regulated Financial Services.
Account & Service Control · Restriction or exception
Territory: no accountholders domiciled outside the UK and Gibraltar (SPUKL Cards) or the EEA (STEL Cards)
The User must not offer, market or make the Stripe Issuing Program available to Connected Accounts domiciled outside (a) the UK and Gibraltar, for Cards issued by SPUKL (Stripe Payments UK Ltd), or (b) the EEA, for Cards issued by STEL (Stripe Technology Europe, Limited). The User must also ensure that no Stripe Issuing Accountholder is domiciled outside the UK and Gibraltar for SPUKL Cards, or outside the EEA for STEL Cards.
Supporting quotations
3.3 Stripe Issuing Program Territory.
User must not offer, market or make the Stripe Issuing Program available to Connected Accounts domiciled outside of (a) the UK and Gibraltar, for Cards issued by SPUKL; and (b) the EEA, for Cards issued by STEL. User must ensure that no Stripe Issuing Accountholder is domiciled outside of (i) the UK and Gibraltar, for Cards issued by SPUKL; and (ii) the EEA, for Cards issued by STEL.
“SPUKL” means Stripe Payments UK Ltd.
“STEL” means Stripe Technology Europe, Limited.
Qualifications & exceptions
The permitted territory depends on which entity issues the Card.
Account & Service Control · Procedure
If you host onboarding: use Stripe's form, present the Accountholder Terms unchanged, keep acceptance records
Either the User or Stripe may host the accountholder onboarding process. If the User hosts it, the User must configure the Stripe API to meet these requirements. Stripe supplies an approved electronic application form that the User must offer to Connected Accounts wishing to use the Accountholder Services; each Connected Account must give information identifying it and its Principal Owners, Stripe Issuing Administrators, Issuing Authorised Users and representatives and other information Stripe asks for, which Stripe may use to verify identity, determine eligibility and confirm it is not engaged in a Prohibited or Restricted Business, and to administer the program, and Stripe then decides whether to approve it. The User must present the Stripe Issuing Accountholder Terms to each Connected Account before it applies, ensure it agrees in the manner the Stripe Issuing Program Guidelines describe, and not modify or supplement those terms without Stripe's prior approval. The User must keep a retrievable, examinable record and description of the interfaces used to collect acceptance, with date and time, give them to Stripe on request, and change an acceptance process Stripe believes does not create a binding agreement between Stripe and the Connected Account.
Supporting quotations
4. Onboarding.
4.1 Stripe Issuing Accountholder Onboarding.
Either User or Stripe may host the Stripe Issuing Accountholder onboarding process.
(a) User Hosted Onboarding. If User hosts onboarding, User must configure the Stripe API to meet the following requirements:
(i) Stripe Issuing Accountholder Application. Stripe will make available to User an approved electronic application form for Stripe Issuing Accountholders. User must make this form available to Connected Accounts that wish to use the Stripe Issuing Accountholder Services. Each Connected Account must provide information identifying it and its Principal Owners, Stripe Issuing Administrators, Issuing Authorised Users and representatives and any other information requested by Stripe. Stripe may use this information to (A) verify the Connected Account’s identity; (B) determine the Connected Account’s eligibility to be a Stripe Issuing Accountholder and confirm it is not engaged in a Prohibited or Restricted Business; and (C) administer the Stripe Issuing Program. After Stripe receives a completed application, Stripe will determine whether the Connected Account is approved as a Stripe Issuing Accountholder.
(ii) Stripe Issuing Accountholder Terms. User must (A) present the Stripe Issuing Accountholder Terms to each Connected Account before that Connected Account submits its accountholder application, and (B) ensure that each Connected Account agrees to the Stripe Issuing Accountholder Terms in the manner the Stripe Issuing Program Guidelines describe. User must not modify or supplement any provision of the Stripe Issuing Accountholder Terms without Stripe’s prior approval.
(iii) Acceptance Records. User must maintain a record and description of the user interfaces used to collect acceptance (including date and time) of the Stripe Issuing Accountholder Terms in a retrievable and examinable format and at Stripe’s request, provide them to Stripe. If Stripe believes that User’s existing acceptance process does not create a binding agreement between Stripe and each Connected Account, upon Stripe’s request, User must modify that process as Stripe requires.
Qualifications & exceptions
These duties apply when the User hosts onboarding.
Stripe decides approval after receiving a completed application.
Account & Service Control · Procedure
Stripe may change the Accountholder Terms; you must pass on notice and stop serving accountholders who object
Stripe may modify the Stripe Issuing Accountholder Terms at any time and will notify the User. The User must notify its Stripe Issuing Accountholders of the change within the time period in Stripe's modification notice and, if Stripe asks, prove it did so. If an accountholder tells the User it does not agree to the updated terms, the User must stop making the Stripe Issuing Accountholder Services available to that accountholder before the proposed date the updated terms take effect. If Stripe hosts onboarding, the User must integrate with the applicable Stripe API according to the Documentation and the Agreement.
Supporting quotations
(iv) Updates to Stripe Issuing Accountholder Terms. Stripe may modify the Stripe Issuing Accountholder Terms at any time. Stripe will notify User if Stripe modifies the Stripe Issuing Accountholder Terms. User must notify User’s Stripe Issuing Accountholders of the modification within the time period specified by Stripe in the modification notice. At Stripe’s request, User must provide Stripe with proof of such notification. If any Stripe Issuing Accountholder informs User that they do not agree to the updated Stripe Issuing Accountholder Terms, User must stop making the Stripe Issuing Accountholder Services available to that Stripe Issuing Accountholder before the proposed date of entry into force of the updated Stripe Issuing Accountholder Terms.
(b) Stripe-Hosted Onboarding. If Stripe hosts the onboarding process, User must integrate with the applicable Stripe API according to the Documentation and this Agreement.
Qualifications & exceptions
The notice period is whatever Stripe's modification notice specifies.
An objecting accountholder must be cut off before the updated terms take effect.
Account & Service Control · Company practice
Stripe may use onboarding information to monitor people, and reject or end access for Law, High-Risk Persons or misuse
Stripe may use all information the User gives about a Connected Account to monitor each Stripe Issuing Accountholder's Principal Owners (individuals owning at least 25% of the equity of a legal entity, directly or indirectly), Stripe Issuing Administrators, Issuing Authorized Users, representatives and individuals with significant management responsibility, for the purpose of meeting Stripe's legal obligations. Stripe may reject any Connected Account's application and immediately terminate any accountholder's access to the Stripe Issuing Accountholder Services to comply with Law, or if any of those people becomes or is a High-Risk Person or the program is used for a Card Unauthorized Purpose.
Supporting quotations
4.2 Opening an Account.
Stripe may use all information that User provides to Stripe about a Connected Account to monitor each Stripe Issuing Accountholder’s Principal Owners, Stripe Issuing Administrators, Issuing Authorized Users, representatives, and individuals with significant responsibility for management, including executives and senior managers, for the purpose of meeting Stripe’s obligations under Law. Stripe may reject any Connected Account's application for, and terminate any Stripe Issuing Accountholder’s access to, the Stripe Issuing Accountholder Services immediately to comply with Law or if any Connected Account, Stripe Issuing Accountholder, Principal Owner, Stripe Issuing Administrator, Issuing Authorized User, representative, or individual with significant responsibility for management is or becomes a High-Risk Person or uses the Stripe Issuing Program for a Card Unauthorized Purpose.
“Principal Owner” means, with respect to a legal entity, an individual who directly or indirectly, through any contract, arrangement, understanding, relationship, or otherwise, owns at least 25% of the equity interests of the legal entity.
Qualifications & exceptions
Monitoring is for the purpose of meeting Stripe's obligations under Law.
Termination is immediate and tied to compliance with Law, High-Risk Person status or a Card Unauthorized Purpose.
Not stated here
'High-Risk Person' is a defined term outside this section and its definition is not in the packet.
Account & Service Control · Procedure
You provide all accountholder and cardholder support per Guidelines, cannot outsource it, and report Complaints monthly
Approved accountholders may designate Issuing Authorized Users to make Card Transactions on their behalf under the Accountholder Terms. The User must provide all support to, and handle all enquiries from, Stripe Issuing Accountholders and Issuing Authorized Users, including about Card usage and lost, damaged or stolen Cards, according to the Stripe Issuing Program Guidelines. Unless Stripe agrees otherwise, the User must not outsource this support to any third party. Monthly, or as Stripe otherwise requests, the User must give Stripe a report of the Issuing Complaints it received and handled in the prior month, as the Guidelines describe.
Supporting quotations
4.3 Issuing Authorized Users.
Approved Stripe Issuing Accountholders may designate Issuing Authorized Users to make Card Transactions on their behalf in accordance with the Stripe Issuing Accountholder Terms.
4.4 Issuing Authorized User Servicing.
User must provide all support to, and handle all enquiries from, Stripe Issuing Accountholders and Issuing Authorized Users, including regarding Card usage, and lost, damaged or stolen Cards. User must provide this support according to the Stripe Issuing Program Guidelines. Unless Stripe agrees otherwise, User must not outsource User’s support obligations to any third party. On a monthly basis or as otherwise requested by Stripe, User must provide to Stripe a report of Issuing Complaints that User received and handled during the prior month, as described in the Stripe Issuing Program Guidelines.
Qualifications & exceptions
Outsourcing is barred unless Stripe agrees otherwise.
The Complaint report is monthly or as Stripe otherwise requests.
Sharing & Disclosure · Restriction or exception
Disclose Personal Data sharing and give Stripe's Privacy Policy to prospects; never modify the Accountholder Terms
The User must disclose to all prospective Stripe Issuing Accountholders and prospective Issuing Authorized Users that the User may provide Personal Data to Stripe and that Stripe may receive or collect Personal Data, and must make Stripe's Privacy Policy available to each prospective accountholder before it participates in the Stripe Issuing Program. The User must not modify or supplement any provision of the Stripe Issuing Accountholder Terms.
Supporting quotations
4.5 Data Use Disclosure.
User must disclose to all prospective Stripe Issuing Accountholders and prospective Issuing Authorized Users that User may provide Personal Data to Stripe, and that Stripe may receive or collect Personal Data. User must ensure that Stripe’s Privacy Policy is made available to each prospective Stripe Issuing Accountholder prior to their participation in the Stripe Issuing Program.
4.6 No User Modifications.
User must not modify or supplement any provision of the Stripe Issuing Accountholder Terms.
Qualifications & exceptions
The Privacy Policy must be available before the prospective accountholder participates.
Not stated here
Stripe's Privacy Policy is not supplied in this document.
Charges & Financial Obligations · Restriction or exception
You are jointly and severally liable for all Issuing program activity and unauthorized-transaction refunds
Except as the Agreement expressly provides, and without prejudice to the Stripe Connect Infrastructure Terms, the User is responsible for all Activity relating to the Stripe Issuing Program, whether started by the User, a Stripe Issuing Accountholder, an Issuing Authorized User or anyone using the User's credentials. That includes use of the services for a Card Unauthorized Purpose (a fraudulent or illegal purpose, a consumer, personal or household purpose, or a purpose unrelated to the Stripe Issuing Services) or in violation of the Agreement or Card Network Rules, all Card Transactions on the Stripe Issuing Account, and any fees, losses, damages or costs Stripe incurs, including insufficient funds for Stripe's debit requests or debit reversals. Stripe may try to collect from accountholders first, but the User remains jointly and severally liable and Stripe may collect from the User. The User must reimburse Stripe for all amounts Stripe refunded to accountholders for unauthorized Card Transactions.
Supporting quotations
5. Responsibility for Activity.
Except as expressly provided in this Agreement, and without prejudice to the Stripe Connect Infrastructure Terms, User is responsible for all Activity relating to the Stripe Issuing Program, whether initiated by User, a Stripe Issuing Accountholder, an Issuing Authorized User, or any person using User’s credentials, including (a) use of the Stripe Issuing Services for a Card Unauthorized Purpose, or in violation of this Agreement, or the applicable Card Network Rules; (b) all Card Transactions on the Stripe Issuing Account; and (c) any fees, losses, damages or costs that Stripe incurs arising out of or relating to that Activity, including insufficient funds availability to cover debit requests from Stripe or due to debit reversals. Stripe may attempt to collect any amounts owed by Stripe Issuing Accountholders before Stripe collects these amounts from User. However, User remains jointly and severally liable to Stripe for these amounts, and Stripe may collect these amounts from User in accordance with this Agreement. User must reimburse Stripe for all amounts refunded by Stripe to Stripe Issuing Accountholders related to unauthorized Card Transactions.
“Card Unauthorized Purpose” means (a) a fraudulent or illegal purpose; (b) a consumer, personal, or household purpose; and (c) any purpose unrelated to the Stripe Issuing Services.
Qualifications & exceptions
Stripe may try to collect from accountholders first, but this does not release the User's joint and several liability.
The responsibility is subject to what the Agreement expressly provides otherwise.
Account & Service Control · Procedure
Card designs need Stripe approval; Stripe ships Cards and replacements at your expense, and risk passes when shipped
The User and its accountholders may request specific Card designs, but the User must submit every design to Stripe for review and approval through Stripe's process. Stripe checks designs against the Agreement, Card Network Rules, Law and Stripe reputational considerations; if it does not approve one it recommends modifications, and the User must resubmit the modified design the same way. The User may order Cards for accountholders through the Stripe Dashboard or API. At the User's expense, Stripe procures and ships Cards based on each order to the address in it, and replacements for Cards reported lost, stolen or damaged. Risk of loss passes to the recipient, the User or the accountholder as applicable, when Stripe ships the Card to the ordered address.
Supporting quotations
6. Cards and Card Orders.
6.1 Card Design.
User and User’s Stripe Issuing Accountholders may request specific Card designs. User must submit all Card designs to Stripe for review and approval using the process Stripe requires. Stripe will review Card design proposals for compliance with this Agreement, the Card Network Rules, Law and Stripe reputational considerations. If Stripe does not approve a proposed Card design, Stripe will recommend modifications that, if made, will meet these requirements. User must resubmit the modified design to Stripe for approval using the same process.
6.2 Card Orders.
User may order Cards on behalf of Stripe Issuing Accountholders through User’s Stripe Dashboard or the Stripe API. At User’s expense, Stripe will procure and ship (a) Cards based on the information contained in each Card order to the address specified in that Card order; and (b) replacements for Cards reported as lost, stolen or damaged. Risk of loss for Cards passes to the recipient (either User or the Stripe Issuing Accountholder, as applicable) when Stripe ships the Card to the address specified in the order.
Qualifications & exceptions
Design approval turns on the Agreement, Card Network Rules, Law and Stripe reputational considerations.
Card procurement and shipping, including replacements, are at the User's expense.
Account & Service Control · Company practice
Stripe owns each Card; it may demand return, cancel, repossess or restrict Cards, and decline or reverse transactions
Stripe owns each Card. If Stripe asks the User or an accountholder to return a Card, the User must return it, or ensure the accountholder returns it, promptly to Stripe. Stripe may cancel, repossess or restrict the use of Cards at any time and may decline to authorize or reverse any Card Transaction.
Supporting quotations
Stripe owns each Card. If Stripe requests that User or a Stripe Issuing Accountholder return a Card, then User must return, or ensure that the Stripe Issuing Accountholder returns, that Card promptly to Stripe. Stripe may cancel, repossess or restrict the use of Cards at any time, and may decline to authorised or reverse any Card Transaction.
Qualifications & exceptions
Stripe's rights to cancel, repossess, restrict, decline or reverse are stated without conditions in this clause.
Security & Safeguards · Restriction or exception
Personal Data you handle through the Dashboard or API must be secured as the Agreement requires
If the User processes, accesses, stores or retrieves Personal Data from its Stripe Dashboard or Stripe API, it must ensure that data is secured in accordance with the Agreement, including Sections 10.2 and 12 of these Stripe Issuing Platform Terms.
Supporting quotations
6.4 Personal Data Security.
If User processes, accesses, stores, or retrieves Personal Data from User's Stripe Dashboard or Stripe API, User must ensure that the Personal Data is secured in accordance with this Agreement, including Sections 10.2 and 12 of these Stripe Issuing Platform Terms.
Qualifications & exceptions
The duty applies to Personal Data the User processes, accesses, stores or retrieves from the Dashboard or API.
Not stated here
The cited Sections 10.2 and 12 and the Agreement's security requirements are in other sections of the document.
Content & IP Rights · Permission or license
You license your User Materials to Stripe and Affiliates for the Term, with the right to sublicense card makers
The User must have the necessary rights in the User Materials, the Marks or other materials to be placed on Cards or provided for the Issuing Program, to use them and to grant Stripe the right to use them on Cards and other program materials. The User grants Stripe and its Affiliates a worldwide, non-exclusive, royalty-free license during the Term to use the User Materials on Cards and applicable program materials, and the right to sublicense these rights to third parties Stripe engages to create Cards and those materials.
Supporting quotations
6.5 User Materials.
User must have the necessary rights in and to the User Materials to use (and grant Stripe the rights to use) the User Materials on the Cards and other materials related to the Stripe Issuing Program. User grants to Stripe and its Affiliates a worldwide, non-exclusive, royalty-free license during the Term to use the User Materials on Cards and applicable Stripe Issuing Program materials. User also grants to Stripe and its Affiliates the right to sublicense these rights to third parties that Stripe engages to create Cards and applicable Stripe Issuing Program materials.
“User Materials” means (a) all Marks or other materials that User or a Stripe Issuing Accountholder wish to place on Cards; or (b) all other materials that User provides to Stripe for the purposes of the Stripe Issuing Programs.
Qualifications & exceptions
The license runs during the Term, is non-exclusive and royalty-free, and extends to Affiliates and sublicensees engaged by Stripe.
Account & Service Control · Procedure
Stripe provides balances and monthly statements; you must give accountholders the information and statements promptly
Stripe provides the User, through the Stripe Technology, with the Stripe Issuing Account balances and a statement of Card Transactions for each Stripe Issuing Account in its program, and the User can download monthly statements there. Statements show information identifying each transaction and, where appropriate, the payee; the amount in the currency paid; the charges; where applicable the actual exchange rate; and the date of authorization or posting. The User must make Card Transaction information available to its accountholders on an ongoing basis and, on request, promptly give any statement, account information or balance to that accountholder. The Accountholder Terms contain the terms on spending limits, available spend and payment or repayment.
Supporting quotations
7. Funds and Card Transactions.
7.1 Card Transaction information.
Stripe will, through the Stripe Technology, provide User with the Stripe Issuing Account balances and a statement of Card Transactions for each Stripe Issuing Account on User’s Stripe Issuing Program. User will be able to download monthly Card Transaction statements via the Stripe Technology. The Card Transaction statements will show: (a) information related to each Card Transaction which will enable it to be identified and, where appropriate, information on the payee; (b) the amount of the Card Transaction shown in the currency in which the Card Transaction was paid; (c) the amount of charges for the Card Transaction; (d) where applicable, the actual exchange rate applied to the Card Transaction; and (e) the date on which the Card Transaction is authorized or posted to the relevant Stripe Issuing Account.
User must make Card Transaction information available to User’s Stripe Issuing Accountholders on an ongoing basis and upon request from any Stripe Issuing Accountholder promptly provide any statement of Card Transactions and Stripe Issuing Account information or balances to that Stripe Issuing Accountholder.
7.2 Stripe Issuing Accountholder Spend.
The Stripe Issuing Accountholder Terms contain the terms governing spending limits, available spend, and payment or repayment in connection with the Stripe Issuing Program.
Qualifications & exceptions
The User's duty to share statements runs to each of its accountholders, on an ongoing basis and promptly on request.
Legal Rights & Agreement Rules · Restriction or exception
Comply, and ensure accountholders comply, with the Guidelines, Law and Card Network Rules, for business use only
The User must (a) comply, and ensure all accountholders comply, with the Stripe Issuing Program Guidelines; (b) ensure accountholders and their Issuing Authorized Users comply with the Accountholder Terms and use the services according to Law and the Card Network Rules; (c) not take or fail to take, and ensure accountholders and Issuing Authorized Users do not take or fail to take, any action that could cause Stripe or its Affiliates to violate Law or Card Network Rules; and (d) ensure accountholders and Issuing Authorized Users use the services for business purposes only.
Supporting quotations
8. Compliance and Marketing.
8.1 General.
User must:
(a) comply with, and ensure all Stripe Issuing Accountholders comply with, the Stripe Issuing Program Guidelines;
(b) ensure that all Stripe Issuing Accountholders and their Issuing Authorized Users comply with the Stripe Issuing Accountholder Terms, and access and use the Stripe Issuing Accountholder Services according to Law and the Card Network Rules;
(c) not, and must ensure that Stripe Issuing Accountholders and Issuing Authorized Users do not, take or fail to take any action that could cause Stripe or any of its Affiliates to violate Law or any Card Network Rules; and
(d) ensure that Stripe Issuing Accountholders and Issuing Authorized Users use the Stripe Issuing Accountholder Services for business purposes only.
Qualifications & exceptions
The duties extend to accountholders and their Issuing Authorized Users.
Account & Service Control · Procedure
Run a compliance program Stripe may assess, and accept that Stripe may message your accountholders directly
The User must establish, maintain and act according to a compliance program that ensures the User and each accountholder comply with Law, the Card Network Rules and the Guidelines, and that the User complies with the Agreement. Stripe may assess the User's compliance with the Guidelines, and the User must promptly provide all information, documentation and assistance Stripe requires for that. As the Guidelines describe, Stripe may send communications directly to the User's Stripe Issuing Accountholders.
Supporting quotations
8.2 Compliance Program.
(a) Requirements. User must establish, maintain, and act according to a compliance program that enables and ensures that (i) User and each Stripe Issuing Accountholder complies with Law, the Card Network Rules, and the Stripe Issuing Program Guidelines; and (ii) User complies with this Agreement. Stripe may assess User’s compliance with the Stripe Issuing Program Guidelines and User must promptly provide all information, documentation, and assistance that Stripe requires to assess User’s compliance.
(b) Customer Communications. As described in the Stripe Issuing Program Guidelines, Stripe may send communications directly to User’s Stripe Issuing Accountholders.
Qualifications & exceptions
Direct Stripe communications to accountholders are as the Guidelines describe.
Not stated here
The Guidelines are not part of this document.
Account & Service Control · Restriction or exception
Stripe must approve your marketing; unmodified templates are pre-approved; Stripe PSP is named as issuer
Stripe must approve all marketing materials the User wants to use with the Stripe Issuing Services. Stripe may provide template materials the User may use without further approval as long as they are not materially modified. The User must submit all proposed marketing materials through a process Stripe communicates. Any marketing materials for the services must clearly identify Stripe PSP as the card issuer.
Supporting quotations
8.3 Marketing.
Stripe must approve all marketing materials that User wishes to use in connection with the Stripe Issuing Services. Stripe may provide template marketing materials to User, which User may use without further Stripe approval as long as the template marketing materials are not materially modified. User must submit all proposed marketing materials to Stripe using a process Stripe communicates to User. Any marketing materials for use in connection with the Stripe Issuing Services must clearly identify Stripe PSP as the card issuer.
Qualifications & exceptions
Templates are pre-approved only if not materially modified.
Charges & Financial Obligations · Company practice
Fees follow the Pricing Page; you owe fees and penalties your accountholders incur; Stripe may change them on notice
Stripe provides the Issuing Platform Services and Accountholder Services at the rates on the Stripe Pricing Page unless the User and Stripe agree otherwise in writing. The User is liable to Stripe for fees it and its accountholders incur, and for penalties imposed on the User, its accountholders or Stripe in relation to the User's use of the services. Fees and penalties may include periodic fees, foreign transaction fees, penalties for misuse, dispute fees for unauthorized or incorrectly executed transactions, funds transfer fees, account maintenance fees, Card issuance or replacement fees and penalties for late or failed payments, and are on top of amounts owed for Card Transactions and Card accounts. Stripe may change fees or penalties by giving advance notice before revisions apply to the accountholder, in accordance with Law. If Stripe ultimately collects from an accountholder amounts the User paid for that accountholder's Card Transactions, Stripe refunds the User what it collected.
Supporting quotations
Stripe will provide the Stripe Issuing Platform Services to User and the Stripe Issuing Accountholder Services to Stripe Issuing Accountholders at the rates and for the fees described on the Stripe Pricing Page, unless User and Stripe otherwise agree in writing. User is liable to Stripe for fees User and User’s Stripe Issuing Accountholders incur. In addition to the fees, User is also responsible for any penalties imposed on User, User’s Stripe Issuing Accountholders or Stripe in relation to User’s use of the Stripe Issuing Services. Fees and penalties may include periodic fees, foreign transaction fees, penalties for misuse, dispute fees for unauthorized or incorrectly executed transactions, funds transfer fees, account maintenance fees, Card issuance or replacement fees, and penalties for late or failed payments. All fees or penalties User owes are in addition to amounts owed for Card Transactions and Card accounts associated with each Stripe Issuing Account. Stripe may change fees or penalties by providing User or Stripe Issuing Accountholder (as applicable) advance notice before revisions become applicable to Stripe Issuing Accountholder, in accordance with Law. If Stripe is ultimately able to collect from a Stripe Issuing Accountholder the amounts that User paid to Stripe related to that Stripe Issuing Accountholder’s Card Transactions, Stripe will refund to User the amount Stripe collected from that Stripe Issuing Accountholder.
Qualifications & exceptions
The listed fee types are examples ('may include').
Stripe refunds the User only what it actually collects from the accountholder.
Not stated here
Fee amounts are on the Stripe Pricing Page, which is not supplied.
The length of advance notice is not stated.
Charges & Financial Obligations · Restriction or exception
You may pass certain fees to accountholders, not wallet or fraud-dispute fees; Stripe may review and order changes
Subject to the terms, the Card Network Rules and Law, the User may pass certain fees on to its accountholders. It must not pass on fees attributable to an accountholder's use of Apple Pay or any other digital wallet, or to a Card Transaction disputed as fraudulent or otherwise unauthorized. The User is solely responsible for communicating any use, recurring or application fees it charges accountholders for Platform Services connected to the Stripe Issuing Services, and must clearly communicate them before imposing them. Stripe may review the fees the User charges to see whether they comply with Stripe's requirements, the Card Network Rules and Law. If not, the User must immediately modify the fees and reimburse the accountholder as Stripe directs.
Supporting quotations
9.2 Fees.
Subject to these Stripe Issuing Platform Terms, the Card Network Rules and Law User may pass certain fees onto the applicable Stripe Issuing Accountholders. User must not pass any fees to any Stripe Issuing Accountholder that are attributable to (a) a Stripe Issuing Accountholder’s use of Apple Pay or any other digital wallet or (b) a Card Transaction that was disputed because it was fraudulent or otherwise unauthorized. User is solely responsible for communicating any use, recurring, or application fees charged to User’s Stripe Issuing Accountholders for their use of Platform Services in connection with the Stripe Issuing Services, and must clearly communicate those fees to Stripe Issuing Accountholders prior to imposing such fees.
Stripe may review the fees User charges its Stripe Issuing Accountholders in connection with the Stripe Issuing Services to determine whether the fees comply with Stripe’s requirements, the Card Network Rules and Law. If Stripe determines the fees do not comply, User must immediately modify the fees and reimburse the Stripe Issuing Accountholder as Stripe directs.
Qualifications & exceptions
Fee pass-through is subject to these terms, Card Network Rules and Law.
The ban covers digital wallet use and disputed fraudulent or unauthorized transactions.
Charges & Financial Obligations · Company practice
Stripe may collect government levies, stamp duties and similar taxes on Cards from you or your accountholders
Notwithstanding the Agreement or the Connected Account Agreement where applicable, and where applicable, Stripe may collect government levies, stamp duties and other similar taxes in respect of Cards issued to accountholders from the User or the User's accountholders, as appropriate.
Supporting quotations
9.3 Card Stamp Duty.
Notwithstanding the terms of this Agreement (or the Connected Account Agreement, as applicable), and where applicable, Stripe may collect government levies, stamp duties, and other similar taxes in respect of Cards issued to Stripe Issuing Accountholders from User or User’s Stripe Issuing Accountholders, as appropriate.
Qualifications & exceptions
The collection applies where applicable and from the User or accountholders as appropriate.
Use & Processing · Restriction or exception
Data use: Stripe's rights follow the Agreement; you may use Personal Data for five purposes and never sell it
Between Stripe and an accountholder, Stripe's rights to use Protected Data generated by the Stripe Issuing Program are governed by the Agreement and the Accountholder Terms. The User may process, use and disclose Personal Data only (i) in connection with its use of the Issuing Platform Services; (ii) to give accountholders access to the Accountholder Services; (iii) for its own fraud prevention and loss mitigation; (iv) to fulfil its obligations to Stripe; and (v) to comply with Law and the Card Network Rules. The User must not sell, rent, transfer, make available or communicate any Personal Data to a third party for monetary or other valuable consideration. The User must obtain and maintain all rights and consents under Law to provide the User Information it gives Stripe about its Principal Owners, employees, contractors and agents, and its Connected Accounts, accountholders and Issuing Authorized Users.
Supporting quotations
10. Data Use.
10.1 Data Use.
(a) Stripe’s Data Use. As between Stripe and a Stripe Issuing Accountholder, Stripe’s rights to use Protected Data generated by the Stripe Issuing Program are governed by the Agreement and the Stripe Issuing Accountholder Terms.
(b) User’s Data Use. User may process, use, and disclose Personal Data only for the following purposes: (i) in connection with User’s use of the Stripe Issuing Platform Services; (ii) to provide Stripe Issuing Accountholders access to the Stripe Issuing Accountholder Services; (iii) in connection with User’s own fraud prevention and loss mitigation activities; (iv) to fulfil User’s obligations to Stripe; and (v) to comply with Law and the Card Network Rules. Without limiting the previous sentence, User must not sell, rent, transfer, make available or communicate orally or through other means any Personal Data to a third party for monetary or other valuable consideration.
(c) Data Collection. User must obtain and maintain all necessary rights and consents under Law to provide the User Information that User provides to Stripe about each of User’s (i) Principal Owners and employees, independent contractors and agents; and (ii) Connected Accounts, Stripe Issuing Accountholders and Issuing Authorized Users.
Qualifications & exceptions
The five purposes are the only permitted uses of Personal Data.
The ban on selling covers transfer to a third party for monetary or other valuable consideration.
Not stated here
Protected Data is a defined term outside this packet.
Security & Safeguards · Restriction or exception
Secure Cards and Personal Data with industry-standard encryption, monitor for fraud, and ensure accountholders do too
The User must secure Cards and Personal Data in its possession or control and ensure its accountholders do the same. When stored or processed digitally, the User must use appropriate organisational and technical measures, including industry-standard encryption. The User must monitor, and ensure its accountholders monitor, for suspicious, fraudulent and unauthorized Card Transactions on each accountholder's Stripe Issuing Account and each Card.
Supporting quotations
10.2 Securing Cards and Account Data.
User must secure Cards and Personal Data in User’s possession or control, and User must ensure that its Stripe Issuing Accountholders secure Cards and Personal Data in their possession or control. When stored or processed digitally, User must use appropriate organisational and technical measures to secure the Cards and Personal Data in User’s possession or control, including through industry-standard encryption. User must monitor, and User must ensure that User’s Stripe Issuing Accountholders monitor, for suspicious, fraudulent and unauthorized Card Transactions on each Stripe Issuing Accountholder’s Stripe Issuing Account and each Card.
Qualifications & exceptions
The monitoring duty is both the User's and each accountholder's.
Not stated here
'Appropriate' measures are not specified beyond industry-standard encryption.
Legal Rights & Agreement Rules · Restriction or exception
You are responsible, to the extent Law permits, for Card use by others or by unauthorized persons
To the extent Law permits, if the User, an accountholder or an Issuing Authorized User lets another party use a Card or Personal Data for any purpose, or if an unauthorized person uses a Card or Personal Data, the User is responsible for that use, including all losses, damages, costs, fines, fees or penalties related to it.
Supporting quotations
10.3 Responsibility for Card Transactions.
To the extent Law permits, if User, a Stripe Issuing Accountholder or an Issuing Authorized User allows another party to use the Card or Personal Data for any purpose, or if an unauthorized person uses a Card or Personal Data, User is responsible for that use, including all losses, damages, costs, fines, fees, or penalties related to that use.
Qualifications & exceptions
The allocation applies 'to the extent Law permits'.
It covers use by unauthorized persons as well as permitted third parties.
Account & Service Control · Procedure
Give accountholders the Disputes API Form or a channel, send disputes to Stripe at once, and never block disputes
Stripe makes the Disputes API Form available to the User. The User must either configure the Stripe API to offer the form to its accountholders or provide a channel through which they can submit disputes to the User, and must immediately submit any disputes it receives to Stripe through the Stripe API or Dashboard. The User must not interfere with any accountholder's ability to dispute a Card Transaction.
Supporting quotations
Stripe will make the Disputes API Form available to User. User must either: (a) configure the Stripe API to make the Disputes API Form available to User’s Stripe Issuing Accountholders; or (b) provide a channel through which Stripe Issuing Accountholders can submit disputes to User. User must immediately submit any disputes User receives to Stripe through the Stripe API or the Stripe Dashboard.
User must not interfere with any Stripe Issuing Accountholder’s ability to dispute a Card Transaction.
Qualifications & exceptions
The User chooses between the form and its own channel but must forward disputes immediately either way.
Charges & Financial Obligations · Procedure
Report lost cards and unauthorized transactions at once, help accountholders file, and cancel compromised Cards
If a Card is lost or stolen, or an accountholder believes there are unauthorized transactions, the User must immediately (a) report those transactions to Stripe by filing a dispute through the Stripe Dashboard, or facilitate the accountholder filing one, and (b) cancel any compromised Cards through the Stripe API or Dashboard. Disputing an unauthorized transaction does not cancel a Card, and the User may incur additional liability if it fails to cancel compromised Cards.
Supporting quotations
11.2 Reporting Unauthorized Transactions.
If a Card is lost or stolen, or a Stripe Issuing Accountholder believes that there are unauthorized transactions on a Card, User must immediately (a) report those Card Transactions to Stripe by filing a dispute through the Stripe Dashboard or User must facilitate the Stripe Issuing Accountholder in filing a dispute for those Card Transactions to Stripe, and (b) cancel any compromised Cards through the Stripe API or the Stripe Dashboard. Disputing an unauthorized Card Transaction will not cancel a Card. If User fails to cancel any compromised Cards through the Stripe API or the Dashboard, User may incur additional liability.
Qualifications & exceptions
Disputing a transaction is separate from cancelling the Card.
Charges & Financial Obligations · Procedure
Defective charges go to the merchant first; accountholders must notify Stripe within 13 months
If the User believes a Card was subject to an incorrectly executed or defective charge, the accountholder must first contact the merchant. If that fails, the User must help the accountholder file a dispute through the Disputes API Form or another channel the User provides. Accountholders must notify Stripe of any incorrectly executed, defective or unauthorized Card Transactions without undue delay and in any event within 13 months of the date the transaction appears on their Stripe Issuing Account.
Supporting quotations
11.3 Reporting Defective or Incorrectly Executed Transactions.
If User believes that a Card was subject to an incorrectly executed or defective charge, the Stripe Issuing Accountholder must first contact the merchant to resolve the dispute regarding the relevant Card Transaction. If the Stripe Issuing Accountholder is unable to resolve the dispute with the merchant, then User must facilitate the Stripe Issuing Accountholder in filing a dispute for the Card Transaction through the Disputes API Form or another channel that User provides.
11.4 Timeline for Reporting Unauthorized, Defective, or Incorrectly Executed Transactions.
Stripe Issuing Accountholders must notify Stripe of any incorrectly executed, defective or unauthorized Card Transactions to Stripe without any undue delay, and, in any event, within 13 months of the date the Card Transaction appears on their Stripe Issuing Account.
Qualifications & exceptions
The merchant must be contacted first for incorrectly executed or defective charges.
The 13-month limit runs from the date the transaction appears on the accountholder's account.
Charges & Financial Obligations · Company practice
Stripe or the Card Network decides disputes in its sole discretion; you must abide and not pass dispute fees on
When an accountholder submits or reports an incorrectly executed, defective or unauthorized Card Transaction, Stripe evaluates the information under Law and the Card Network Rules. If Stripe or the Card Network determines in its sole discretion that the dispute is valid or the transaction was defective, incorrectly executed or unauthorized, Stripe credits the amount back to the applicable Stripe Issuing Account. The User must abide by the determination of any dispute and may not pass dispute fees it incurs from unauthorized Card Transactions on to an accountholder.
Supporting quotations
11.5 Determining Disputed Card Transactions.
When a Stripe Issuing Accountholder submits or reports an incorrectly executed, defective or unauthorized Card Transaction, Stripe will evaluate the submitted information in accordance with Law and the Card Network Rules. If Stripe or the Card Network determines, in its sole discretion, that the dispute is valid or the Card Transaction was defective, incorrectly executed or unauthorized, Stripe will credit the amount of the applicable Card Transaction back to the applicable Stripe Issuing Account. User must abide by the determination of any dispute. User may not pass any dispute fees User incurs as a result of any unauthorized Card Transactions on to a Stripe Issuing Accountholder.
Qualifications & exceptions
The determination is in the sole discretion of Stripe or the Card Network.
Security & Safeguards · Restriction or exception
Comply with the PCI Standards, ensure service providers do, and give Stripe assessment results on request
The User must comply, and ensure its service providers that store, access or transmit Personal Data comply, with the PCI Standards. On Stripe's request, the User must verify that its implementation of the Stripe Issuing Program complies with the PCI Standards and promptly provide the most recent assessment results to Stripe.
Supporting quotations
12. PCI Compliance.
User must, and User must ensure that User’s service providers that store, access, or transmit Personal Data, comply with the PCI Standards. Upon Stripe’s request, User must verify that User’s implementation of the Stripe Issuing Program complies with the PCI Standards and promptly provide the most recent assessment results to Stripe.
Qualifications & exceptions
The duty reaches service providers that store, access or transmit Personal Data.
Not stated here
'PCI Standards' is defined outside this packet.
Legal Rights & Agreement Rules · Restriction or exception
You indemnify the Stripe Parties for accountholder and cardholder conduct and all unauthorized Card Transactions
The User will indemnify the Stripe Parties against all Stripe Losses arising out of or relating to (a) accountholders' and Issuing Authorized Users' use of the Accountholder Services, including any act or omission related to them, and (b) all unauthorized Card Transactions. 'Stripe Losses' means all amounts awarded to the third party making a Claim, and all penalties, fines and third-party costs, including legal fees, paid by the Stripe Parties.
Supporting quotations
13. Indemnification.
User will indemnify the Stripe Parties against all Stripe Losses arising out of or relating to (a) the Stripe Issuing Accountholders’ and Issuing Authorized Users’ use of the Stripe Issuing Accountholder Services, including any Stripe Issuing Accountholder’s or Issuing Authorized User’s act or omission related to the Stripe Issuing Accountholder Services; and (b) all unauthorized Card Transactions.
“Stripe Losses” means all amounts awarded to the third party making a Claim, and all penalties, fines, and third-party costs (including legal fees) paid by the Stripe Parties.
Qualifications & exceptions
The indemnity covers all unauthorized Card Transactions, not only those the User caused.
Legal Rights & Agreement Rules · Restriction or exception
Stripe is also not liable for losses from delay or failure in servicing a Card Transaction request
In addition to the liability provisions in the Agreement, Stripe is not liable to the User, accountholders, Stripe Issuing Administrators or Issuing Authorized Users for losses, damages, costs, fines, fees or penalties related to delay or failure in servicing a Card Transaction request.
Supporting quotations
14. Liability.
14.1 Stripe Liability.
In addition to liability provisions in the Agreement, Stripe is not liable to User, Stripe Issuing Accountholder, Stripe Issuing Administrators or Issuing Authorized Users for any losses, damages, costs, fines, fees, or penalties incurred by User or any Stripe Issuing Accountholders, Stripe Issuing Administrators or Issuing Authorized Users related to delay or failure in servicing a Card Transaction request.
Qualifications & exceptions
This disclaimer is stated in addition to the Agreement's other liability provisions.
Legal Rights & Agreement Rules · Context
Definitions: Card, Card Network and Rules, Card Transaction, Unauthorized Purpose, Connected Account, Disputes Form
Section 15 begins the definitions. A 'Card' is a Card Network-branded payment card, physical or tokenized, encrypted or digitized, issued to an accountholder for its business purposes in the Stripe Issuing Program. A 'Card Network' is a payment card network including those of Visa, Mastercard, American Express and Discover, and 'Card Network Rules' are the Payment Method Rules a Card Network publishes. A 'Card Transaction' is a payment made with a Card or, if permitted, cash obtained at an ATM. A 'Card Unauthorized Purpose' is a fraudulent or illegal purpose, a consumer, personal or household purpose, or a purpose unrelated to the Stripe Issuing Services. A 'Connected Account' is a Platform User with a Stripe Account onboarded to a Stripe Connect Platform, or a Payout Recipient, and the 'Connected Account Agreement' is Stripe's agreement for Connected Accounts other than Payout Recipients, found on the Stripe Legal Page for the account's jurisdiction. The 'Disputes API Form' is an electronic form that lets the User and its Connected Account submit Card Transaction disputes to Stripe. The definitions continue in the next packet.
Supporting quotations
15. Definitions.
“Card” means a Card Network-branded payment card (which may be a physical card or tokenized, encrypted, or digitized form of a physical card) issued to a Stripe Issuing Accountholder for the Stripe Issuing Accountholder’s business purposes in connection with the Stripe Issuing Program.
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
“Card Network Rules” means the Payment Method Rules published by a Card Network.
“Card Transaction” means a transaction to make a payment with a Card or, if permitted, to obtain cash at an automatic teller machine (ATM).
“Card Unauthorized Purpose” means (a) a fraudulent or illegal purpose; (b) a consumer, personal, or household purpose; and (c) any purpose unrelated to the Stripe Issuing Services.
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
“Connected Account Agreement” means the agreement with Stripe that applies to Connected Accounts (except Payout Recipients), which is accessible on the Stripe Legal Page for the Connected Account's jurisdiction.
“Disputes API Form” means an electronic form that enables User and User’s Connected Account to submit disputed Card Transaction disputes to Stripe.
Legal Rights & Agreement Rules · Context
Definitions: Authorized User, Complaint, Principal Owner, SPUKL, STEL, Guidelines, Stripe Losses, User Materials
These definitions finish Section 15. An 'Issuing Authorized User' is an individual an accountholder authorizes to use a Card on its behalf, such as an employee, contractor or representative. An 'Issuing Complaint' is any expression of dissatisfaction with a product, service, policy or employee related to a Stripe Issuing Program. 'Platform Services' are the products and services Platform Users receive from a Stripe Connect Platform, whether or not fees are charged. A 'Principal Owner' is an individual who directly or indirectly owns at least 25% of the equity of a legal entity. 'SPUKL' is Stripe Payments UK Ltd and 'STEL' is Stripe Technology Europe, Limited. A 'Stripe Issuing Account' is the account Stripe or an Affiliate maintains for an accountholder, with its subaccounts; a 'Stripe Issuing Accountholder' is a business or organization that finished onboarding and was approved; the 'Accountholder Services' include program access and Card spend management; a 'Stripe Issuing Administrator' is the individual an accountholder appoints to manage its participation. The 'Stripe Issuing Platform Services' let the User co-market the Accountholder Services to its Platform Users and provide access to them for accountholders, and the 'Stripe Issuing Program' is the Card issuing program and related services with the Accountholder Services. The 'Stripe Issuing Program Guidelines' are the product design, marketing, compliance, reporting and other guidelines and requirements Stripe and its Affiliates set for the Issuing Services and Platform Services, including the Stripe Issuing marketing guidelines and the Stripe Issuing section of the Documentation, as updated from time to time. 'Stripe Losses' are amounts awarded to a third party making a Claim plus penalties, fines and third-party costs, including legal fees, paid by the Stripe Parties. 'User Materials' are the Marks or other materials the User or an accountholder wants on Cards, and other materials the User gives Stripe for the program.
Supporting quotations
“Issuing Authorized User” means an individual a Stripe Issuing Accountholder authorizes to use a Card to make Card Transactions on the Stripe Issuing Accountholder’s behalf (e.g., the Stripe Issuing Accountholder’s employee, independent contractor or representative designated as an authorized user).
“Issuing Complaint” means any expression of dissatisfaction with a product, service, policy, or employee related to a Stripe Issuing Program.
“Platform Services” means the products and services that Platform Users receive from a Stripe Connect Platform, regardless of whether fees are charged (e.g., web development, customer support or hosting services).
“Principal Owner” means, with respect to a legal entity, an individual who directly or indirectly, through any contract, arrangement, understanding, relationship, or otherwise, owns at least 25% of the equity interests of the legal entity.
“SPUKL” means Stripe Payments UK Ltd.
“STEL” means Stripe Technology Europe, Limited.
“Stripe Issuing Account” means the account Stripe or a Stripe Affiliate maintains for a Stripe Issuing Accountholder, and each subaccount to that account.
“Stripe Issuing Accountholder” means a business or organization that has successfully completed the onboarding requirements described in the Stripe Issuing Accountholder Terms and been approved for a Stripe Issuing Account.
“Stripe Issuing Accountholder Services” means Services that Stripe and its Affiliates make available to Stripe Issuing Accountholders, including (a) providing Stripe Issuing Accountholders with access to the Stripe Issuing Program; (b) enabling Stripe Issuing Accountholders to manage Card spend, and (c) other services described in the Stripe Issuing Accountholder Terms.
“Stripe Issuing Administrator” means the individual that a Stripe Issuing Accountholder appoints to manage its participation in the Stripe Issuing Program.
“Stripe Issuing Platform Services” means the Services that allow User to co-market the Stripe Issuing Accountholder Services to User’s Platform Users and provide access to the Stripe Issuing Accountholder Services to Stripe Issuing Accountholders.
“Stripe Issuing Program” means a Card issuing program and services that Stripe and its Affiliates make available to Stripe Issuing Accountholders, together with the Stripe Issuing Accountholder Services.
“Stripe Issuing Program Guidelines” means all product design, marketing, compliance, reporting, and other guidelines and requirements Stripe and its Affiliates establish related to the Stripe Issuing Services and Stripe Issuing Platform Services, including Stripe Issuing marketing guidelines and the Stripe Issuing section of the Documentation, as updated from time to time.
“Stripe Issuing Services” means the Stripe Issuing Accountholder Services and Stripe Issuing Platform Services.
“Stripe Losses” means all amounts awarded to the third party making a Claim, and all penalties, fines, and third-party costs (including legal fees) paid by the Stripe Parties.
“User Materials” means (a) all Marks or other materials that User or a Stripe Issuing Accountholder wish to place on Cards; or (b) all other materials that User provides to Stripe for the purposes of the Stripe Issuing Programs.
Qualifications & exceptions
The Program Guidelines can be updated by Stripe and its Affiliates from time to time.
Not stated here
The Guidelines and the Documentation section are not part of this document.
Legal Rights & Agreement Rules · Context
US Issuing Accountholder terms (Sept 28, 2026) supplement the General Terms and incorporate the Financial Services Terms
These Stripe Issuing Accountholder Terms for the United States, last modified September 28, 2026, supplement the General Terms and, together with the Stripe Financial Services Terms incorporated by reference, govern the User's use of the Stripe Issuing Accountholder Services. Capitalized terms not defined here take their meaning from the General Terms, the Financial Services Terms and the Financial Provider Terms.
Supporting quotations
Stripe Issuing—Accountholder (United States)
Last modified: September 28, 2026
These terms (“Stripe Issuing Accountholder Terms”) supplement the General Terms and, together with the Stripe Financial Services Terms which are incorporated into these terms by this reference, govern User’s use of the Stripe Issuing Accountholder Services. Capitalized terms that are not defined in these terms have the same meanings given to them in the General Terms, and the Stripe Financial Services Terms, and the Financial Provider Terms.
Not stated here
The General Terms, Financial Services Terms and Financial Provider Terms are separate documents not supplied in this run.
Legal Rights & Agreement Rules · Restriction or exception
You must agree to the Issuing Bank Terms for your program, and they prevail over this Agreement in a conflict
Stripe offers several Stripe Issuing Programs in partnership with several Issuing Banks. When the User signs up, Stripe, or the User's Platform Provider if applicable, presents the Issuing Bank Terms for the User's program, which the User must agree to in order to use the Accountholder Services. The User can see a description of its program and the applicable Issuing Bank Terms in its Stripe Dashboard. To the extent the Issuing Bank Terms conflict with the Agreement, the Issuing Bank Terms prevail. An 'Issuing Bank' is the Financial Provider, named in the Issuing Bank Terms for the program, that issues a Card, and 'Issuing Bank Terms' are that bank's Financial Provider Terms governing the User's participation.
Supporting quotations
1. Relationship to Issuing Bank Terms.
Stripe offers several Stripe Issuing Programs in partnership with several Issuing Banks. When User signs up to use the Stripe Issuing Accountholder Services, Stripe (or, if applicable, User’s Platform Provider) will present the applicable Issuing Bank Terms for User’s Stripe Issuing Program. To use the Stripe Issuing Accountholder Services, User must agree to these Issuing Bank Terms. User can view a description of User’s Stripe Issuing Program and access the applicable Issuing Bank Terms in User’s Stripe Dashboard. To the extent that there is a conflict between the Issuing Bank Terms and this Agreement, the Issuing Bank Terms will prevail.
“Issuing Bank” means the Financial Provider, identified in the Issuing Bank Terms for the applicable Stripe Issuing Program, that issues a Card.
“Issuing Bank Terms” means the applicable Issuing Bank’s Financial Provider Terms that govern User’s participation in the applicable Stripe Issuing Program.
Qualifications & exceptions
Agreement to the Issuing Bank Terms is a condition of using the Accountholder Services.
Not stated here
The Issuing Bank Terms themselves are presented in the Stripe Dashboard and are not supplied here.
Account & Service Control · Context
Stripe manages the Issuing Programs as each bank's program manager; the Issuing Banks issue Cards and accounts
The Issuing Banks provide, and Stripe manages, the Stripe Issuing Programs. As each Issuing Bank's program manager, Stripe processes applications for Stripe Issuing Accounts, performs onboarding, services accounts, sends communications, provides disclosures and provides account information. Each Issuing Bank issues Cards and Stripe Issuing Accounts under the applicable Issuing Bank Terms.
Supporting quotations
2. Structure of Stripe Issuing Programs.
2.1 Stripe as Program Manager.
The Issuing Banks provide, and Stripe manages, the Stripe Issuing Programs. Stripe, as each Issuing Bank’s program manager, performs certain activities in connection with the Stripe Issuing Programs, including processing applications for Stripe Issuing Accounts and performing onboarding services, servicing Stripe Issuing Accounts, sending communications, providing disclosures, and providing Stripe Issuing Account information. Each Issuing Bank issues Cards and Stripe Issuing Accounts under the applicable Issuing Bank Terms.
Account & Service Control · Procedure
Do not use the services until Stripe and the Issuing Bank approve; provide User Information whenever requested
The User must not use the Accountholder Services until Stripe and the applicable Issuing Bank approve its application. As a condition of approval, Stripe or the bank may require User Information and information about the User's activities and intended use, in addition to what the User gave for other Services. The User must provide all User Information and other information Stripe or the bank requests from time to time. If both approve, Stripe gives the User access to a Stripe Issuing Account and the User may participate in the program.
Supporting quotations
2.2 Approval and Providing Information.
(a) User must not use the Stripe Issuing Accountholder Services until Stripe and the applicable Issuing Bank approve User’s application. As a condition of its approval, Stripe or the Issuing Bank may require User to provide User Information and information about User’s activities and intended use of the Stripe Issuing Accountholder Services. This information may be in addition to information User may have previously provided to Stripe in connection with other Services. User must provide all User Information and all other information as Stripe or the applicable Issuing Bank requests from time to time.
(b) If Stripe and the applicable Issuing Bank approve User’s application, Stripe will provide User with access to a Stripe Issuing Account, and User may participate in the Stripe Issuing Program.
Qualifications & exceptions
Approval by both Stripe and the Issuing Bank is required before use.
Account & Service Control · Restriction or exception
You may appoint a Stripe Issuing Administrator but remain responsible for its acts and omissions
The User may appoint a Stripe Issuing Administrator to administer the program on its behalf, for example managing how Issuing Authorized Users use Cards. The User must ensure the Administrator complies with the Agreement and the Issuing Bank Terms and is responsible for its acts and omissions in connection with the program. The Issuing Bank Terms describe the relationship between the User and an Issuing Authorized User.
Supporting quotations
2.3 Appointment of Stripe Issuing Administrator.
User may appoint a Stripe Issuing Administrator to administer the Stripe Issuing Program on User’s behalf (e.g., managing how Issuing Authorized Users use Cards). User must ensure that the Stripe Issuing Administrator complies with this Agreement and the applicable Issuing Bank Terms. User is responsible for the Stripe Issuing Administrator’s acts and omissions in connection with the Stripe Issuing Program.
2.4 Relationship with Issuing Authorized Users.
The applicable Issuing Bank Terms describe the relationship between User and an Issuing Authorized User.
Qualifications & exceptions
The User answers for the Administrator's acts and omissions.
Account & Service Control · Procedure
Send each Issuing Complaint to your platform or Stripe within 3 business days; Stripe or your platform answers inquiries
The User must submit each Issuing Complaint it receives to its Platform Provider or, if it has none, to issuing-support@stripe.com within 3 business days after receiving it. Stripe, or the User's Platform Provider if applicable, manages all of the User's inquiries about the Accountholder Services, including Card use and lost, damaged or stolen Cards.
Supporting quotations
2.5 Issuing Complaint Handling.
User must submit each Issuing Complaint User receives to User’s Platform Provider or, if User does not have one, to issuing-support@stripe.com within 3 business days after User receives the Issuing Complaint.
2.6 Inquiries.
Stripe (or, if applicable, User’s Platform Provider) will manage all inquiries from User regarding the Stripe Issuing Accountholder Services, including inquiries related to the use of Cards, and lost, damaged, or stolen Cards.
Qualifications & exceptions
The 3-business-day period runs from the User's receipt of the Complaint.
Account & Service Control · Procedure
Card designs need Stripe approval; Cards and replacements ship at your expense and risk passes on shipment
The User may request specific Card designs for Cards issued to it or to Issuing Authorized Users, and must submit each proposed design to Stripe for review and approval through Stripe's process. Stripe reviews designs for compliance with the Agreement, Issuing Bank requirements, Card Network Rules, Law and Stripe reputational considerations, recommends changes if it does not approve, and the User must resubmit modified designs the same way. The User may order Cards through its Stripe Dashboard or Platform Provider. At the expense of the User or its Platform Provider, Stripe procures and ships Cards to the ordered address and replacements for Cards reported lost, stolen or damaged, and risk of loss passes to the recipient when Stripe ships.
Supporting quotations
3. Cards.
3.1 Card Designs.
User may request specific Card designs for Cards issued to User or to Issuing Authorized Users. User must provide all proposed Card designs to Stripe for review and approval using the process Stripe requires. Stripe will review Card design proposals for compliance with this Agreement, Issuing Bank requirements, the Card Network Rules, Law, and Stripe reputational considerations. If Stripe does not approve a proposed Card design, Stripe will recommend modifications that, if made, will meet these requirements. User must resubmit the modified Card design to Stripe for approval using the same process.
3.2 Card Orders.
User may order Cards through User’s Stripe Dashboard (or, if applicable, through User’s Platform Provider). At User’s, or, if applicable, User’s Platform Provider’s, expense, Stripe will procure and ship (a) Cards based on the information contained in the applicable Card order to the address specified in that Card order; and (b) replacements for Cards reported as lost, stolen or damaged. Risk of loss for Cards passes to the recipient (either User or User’s Platform Provider, as applicable) when Stripe ships the Card to the address specified in the order.
Qualifications & exceptions
Costs fall on the User or, if applicable, its Platform Provider.
Account & Service Control · Procedure
Activate each Card in the Dashboard before use; all Cards link to your Stripe Issuing Account
The User must activate a Card through its Stripe Dashboard, or through its Platform Provider if applicable, before the User or an Issuing Authorized User uses it. All Cards issued to the User are linked to its Stripe Issuing Account. Once activated, the User or its Issuing Authorized Users may use Cards to initiate Card Transactions on the User's behalf.
Supporting quotations
3.3 Card Activation.
User must activate a Card through User’s Stripe Dashboard (or, if applicable, through User’s Platform Provider) before User or an Issuing Authorized User uses that Card. All Cards issued to User are linked to User’s Stripe Issuing Account. Once a Card is activated, User or User’s Issuing Authorized Users, as applicable, may use Cards to initiate Card Transactions on User’s behalf.
Qualifications & exceptions
Activation must happen before first use.
Account & Service Control · Company practice
The Issuing Bank owns each Card; you must return Cards on request, and Stripe or the bank may cancel or restrict them
The applicable Issuing Bank owns each Card. If Stripe asks the User or an Issuing Authorized User to return a Card, it must be returned promptly to Stripe or the Issuing Bank as Stripe instructs. Stripe or the Issuing Bank may cancel, repossess or restrict the use of Cards at any time according to the Issuing Bank Terms.
Supporting quotations
The applicable Issuing Bank owns each Card. If Stripe requests that User or an Issuing Authorized User return a Card, then User must return, or ensure that the Issuing Authorized User returns, that Card promptly to Stripe or the Issuing Bank as Stripe instructs. Stripe or the applicable Issuing Bank may cancel, repossess or restrict the use of Cards at any time according to the applicable Issuing Bank Terms.
Qualifications & exceptions
The rights to cancel, repossess or restrict operate according to the Issuing Bank Terms.
Not stated here
The Issuing Bank Terms are not supplied here.
Content & IP Rights · Permission or license
You license your User Materials to Stripe and Affiliates; revoking the license does not recall existing Cards
The User must have the necessary rights in the User Materials to use them, and to let Stripe use them, on Cards and for the program. The User grants Stripe and its Affiliates a worldwide, non-exclusive, royalty-free license to use the User Materials on Cards and program materials, with the right to sublicense third parties Stripe engages to create them. If the User terminates or revokes the license, Stripe will stop producing new Cards carrying the User Materials and stop using them for the program, but is not obliged to recall, destroy or replace existing Cards, and is not liable for delay or failure in performing to the extent adversely affected by the termination or revocation.
Supporting quotations
3.5 User Materials.
User must have the necessary rights in the User Materials to use (and grant Stripe the rights to use) the User Materials on the Cards or for the purposes of the Stripe Issuing Program. User grants to Stripe and its Affiliates a worldwide, non-exclusive, royalty-free license to use the User Materials on Cards and applicable Stripe Issuing Program materials. User also grants to Stripe and its Affiliates the right to sublicense these rights to third parties that Stripe engages to create Cards and applicable Stripe Issuing Program materials. If User terminates or revokes the license to the User Materials, then (a) Stripe will stop producing new Cards carrying the User Materials and stop using the User Materials for the purposes of the Stripe Issuing Program; (b) Stripe will not be obligated to recall, destroy or replace any existing Cards carrying the User Materials; and (c) Stripe will not be liable for any delay or failure in performing its obligations to the extent they are adversely affected by the termination or revocation.
Qualifications & exceptions
The license is non-exclusive and royalty-free and extends to sublicensees engaged to create Cards.
Revocation stops new production and use but does not reach existing Cards.
Account & Service Control · Company practice
You may add Card restrictions; Stripe may limit Card use when a transaction exceeds Available Spend and is not paid
In addition to the restrictions in the Issuing Bank Terms, the User may set further restrictions on its Stripe Issuing Account and Cards in accordance with those terms, for example on the amount of individual Card Transactions and the types of merchants where Cards may be used. The Issuing Bank and Stripe may each prevent Cards from working outside the Territory. The User must communicate all applicable restrictions to its Issuing Authorized Users. If a Card Transaction exceeds Available Spend and the Issuing Bank, or Stripe for it, does not receive payment from another Payment Source, then in addition to the remedies in Section 7.2 Stripe may limit the ability of the User and its Issuing Authorized Users to make Card Transactions.
Supporting quotations
3.6 Limits and Available Spend.
In addition to the restrictions described in the applicable Issuing Bank Terms, User may establish additional restrictions related to User’s Stripe Issuing Account and Cards in accordance with the Issuing Bank Terms (e.g., on the dollar amount of individual Card Transactions, and the types of merchants with which User’s Cards may be used). Each of the Issuing Bank and Stripe may prevent Cards from functioning outside of the Territory. User must communicate all applicable restrictions to User’s Issuing Authorized Users. If at any time the amount of a Card Transaction exceeds Available Spend and the Issuing Bank (or Stripe on Issuing Bank’s behalf) does not receive payment from another Payment Source, then, in addition to all other remedies described in Section 7.2 of these Stripe Issuing Accountholder Terms, Stripe may limit User’s and User’s Issuing Authorized Users ability to make Card Transactions.
Qualifications & exceptions
Stripe's limit on Card Transactions applies where a transaction exceeds Available Spend and no other Payment Source pays.
Not stated here
'Available Spend', 'Payment Source' and 'Territory' are defined elsewhere and not in this packet.
Section 7.2 is cited but is in a later part of these terms.
Charges & Financial Obligations · Company practice
Stripe or the Issuing Bank may decline or reverse Card Transactions for the bank's listed reasons, without liability
Stripe or an Issuing Bank may reverse or decline to authorize a Card Transaction for any of the reasons in the applicable Issuing Bank Terms. Neither Stripe nor the Issuing Bank is liable for losses, damages, costs, fines, fees or penalties the User incurs related to reversed or declined Card Transactions.
Supporting quotations
4. Card Transactions.
4.1 Ability to Decline to Authorize a Card Transaction.
Stripe or an Issuing Bank may reverse or decline to authorize a Card Transaction for any of the reasons set forth in the applicable Issuing Bank Terms. Neither Stripe nor the Issuing Bank is liable for any losses, damages, costs, fines, fees, or penalties User incurs related to reversed or declined Card Transactions.
Qualifications & exceptions
The grounds are those in the Issuing Bank Terms.
Not stated here
The Issuing Bank Terms listing the grounds are not supplied here.
Charges & Financial Obligations · Company practice
Short on a Supported Currency, SPC converts from your default currency; quoted amounts and fees are estimates
Card Transactions in a Supported Currency, a currency Stripe tells the User it supports, are processed in that currency. If the User's balance in it is insufficient and its default-currency balance suffices, SPC converts the Card Transaction amount into the default currency to complete it. The exchange rate for any conversion is determined as stated in the Documentation, and quoted payout amounts and fees involving a conversion are estimates that may change with the rate at conversion time. The Issuing Bank Terms describe conversions Financial Providers may complete.
Supporting quotations
4.2 Currency Conversion.
If a Card Transaction is in a Supported Currency, Stripe will process the Card Transaction in the applicable Supported Currency. If User’s balance in the applicable Supported Currency is insufficient to complete the Card Transaction and User has a sufficient balance available in User’s default currency, SPC will convert the Card Transaction amount from the Supported Currency to User’s default currency to complete the Card Transaction. If a requested Card Transaction requires a currency conversion, then the exchange rate used for that conversion will be determined as stated in the Documentation. Where currency conversion is part of a Card Transaction, any quoted payout amounts and associated fees are estimates, and may fluctuate based on changes in the exchange rate that applies when the currency conversion takes place. The Issuing Bank Terms describe currency conversions that may be completed by Financial Providers.
“Supported Currency” means a currency supported under the Stripe Issuing Accountholder Services as communicated to User by Stripe.
Qualifications & exceptions
Quoted amounts and fees involving a currency conversion are estimates.
Not stated here
'SPC' is not defined in this packet.
The exchange rate is set 'as stated in the Documentation', which is not supplied.
Account & Service Control · Company practice
You are in default on breach, nonpayment, over-limit use, inaccurate information or unacceptable risk
The User is in default if (a) it violates Law or breaches the Accountholder Terms, the Issuing Bank Terms or the Card Network Rules; (b) it fails to pay amounts owed to Stripe or the Issuing Bank for the program; (c) it starts a Card Transaction that would exceed or violate a limit set for its use of the program; (d) Stripe or the bank determines it gave inaccurate application information or failed to keep it current; or (e) Stripe or the bank determines it poses an unacceptable regulatory, reputational or financial risk.
Supporting quotations
5. Default; Termination.
5.1 Default.
User is in default under these Stripe Issuing Accountholder Terms if (a) User violates Law, or breach these Stripe Issuing Accountholder Terms, the Issuing Bank Terms, or the Card Network Rules; (b) User fails to pay any amounts User owes to Stripe or the applicable Issuing Bank in connection with the Stripe Issuing Program; (c) User initiates a Card Transaction that would exceed or violate a limit established for User’s use of the Stripe Issuing Program; (d) Stripe or the applicable Issuing Bank determines that User provided inaccurate information in User’s application, or that User has failed to keep this information current; or (e) Stripe or the applicable Issuing Bank determines that User poses an unacceptable regulatory, reputational or financial risk.
Qualifications & exceptions
Limits (d) and (e) turn on a determination by Stripe or the Issuing Bank.
Not stated here
'Unacceptable' risk is not defined by any threshold.
Account & Service Control · Company practice
On default Stripe may suspend, terminate, accelerate debts and reverse transactions; payment may precede reactivation
If the User is in default, Stripe may (a) suspend or terminate the Stripe Issuing Account or any or all Cards; (b) declare amounts owed to Stripe or the Issuing Bank immediately due and payable; (c) refuse to authorize Card Transactions; (d) reverse Card Transactions; (e) terminate the Accountholder Terms; and (f) take any other action Stripe deems necessary. Stripe may also suspend or terminate the account or any Cards if the Issuing Bank directs it to. If Stripe suspends the account or a Card, it may require the User to pay amounts owed to Stripe or the bank before reactivating it.
Supporting quotations
5.2 Stripe’s Right to Suspend or Terminate.
If User is in default under these Stripe Issuing Accountholder Terms, Stripe may (a) suspend or terminate User’s Stripe Issuing Account or any or all Cards; (b) declare any amounts User owes to Stripe or the applicable Issuing Bank immediately due and payable; (c) refuse to authorize any Card Transactions; (d) reverse any Card Transactions; (e) terminate these Stripe Issuing Accountholder Terms; and (f) take any other action Stripe deems necessary. In addition, Stripe may suspend or terminate User’s Stripe Issuing Account or any Cards if the applicable Issuing Bank directs Stripe to do so.
5.3 Reactivating after Suspension.
If Stripe suspends User’s Stripe Issuing Account or a Card, Stripe may require User to pay amounts User owes to Stripe or the Issuing Bank before reactivating User’s Stripe Issuing Account or that Card.
Qualifications & exceptions
Stripe may act on its own default finding or on the Issuing Bank's direction.
Reactivation may depend on payment of amounts owed.
Charges & Financial Obligations · Company practice
Stripe may set off program debts against other funds it holds for you; you may close the account or a Card
Stripe, for itself and on behalf of the Issuing Bank, may set off any amounts the User owes to Stripe or the bank in connection with its participation in the Stripe Issuing Program against other funds Stripe or the bank holds or processes on the User's behalf. The User may close its Stripe Issuing Account or any Card by notifying Stripe or, if applicable, its Platform Provider.
Supporting quotations
Stripe, for itself and on behalf of the applicable Issuing Bank, may set off any amounts User owes to Stripe or the Issuing Bank in connection with User’s participation in the Stripe Issuing Program against other funds that Stripe or the Issuing Bank holds or processes on User’s behalf.
5.5 Closing User’s Stripe Issuing Account.
User may close User’s Stripe Issuing Account or any Card by notifying Stripe (or, if applicable, User’s Platform Provider).
Qualifications & exceptions
The set-off reaches other funds Stripe or the Issuing Bank holds or processes for the User, not only Issuing Account funds.
Sharing & Disclosure · Company practice
You must hold the rights and consents for cardholders' Personal Data; Stripe shares it with card printers and Affiliates
The User must have and maintain all rights and consents under Law for Stripe and the Issuing Bank to collect, use, retain and disclose the Personal Data the User provides or authorizes them to collect, including data Stripe may collect directly from Issuing Authorized Users. The User is solely responsible for telling Issuing Authorized Users that Stripe may receive Personal Data from the User and must give them the notices and obtain the rights and consents Stripe needs to lawfully collect, use, retain and disclose their Personal Data in the ways the Agreement (including Section 4 of the General Terms) and Stripe's Privacy Policy describe. Stripe provides Issuing Authorized Users' Personal Data to third-party service providers, including Card printers, and their Affiliates, and to Stripe's Affiliates, to enable the program. Stripe may delete or disconnect an Issuing Authorized User's Personal Data from the account when Law or the Card Network Rules require.
Supporting quotations
6. Data Protection.
6.1 Data Protection.
User must have and maintain all necessary rights and consents under Law to provide to Stripe and the applicable Issuing Bank, and to allow Stripe and the applicable Issuing Bank to collect, use, retain and disclose, all Personal Data that User provides to Stripe or any Issuing Bank or authorizes Stripe and any Issuing Bank to collect, including data that Stripe may collect directly from Issuing Authorized Users. User is solely responsible for disclosing to Issuing Authorized Users that Stripe may receive Personal Data from User. User must provide all necessary notices to and obtain all necessary rights and consents from each Issuing Authorized User sufficient to enable Stripe to lawfully collect, use, retain and disclose their Personal Data in the ways this Agreement (including Section 4 of the General Terms) and Stripe's Privacy Policy describe. Stripe provides Issuing Authorized Users' Personal Data to third-party service providers, including third parties engaged for Card printing services, and their respective Affiliates, as well as to Stripe’s Affiliates, to enable Stripe to provide the Stripe Issuing Program. Stripe may delete or disconnect an Issuing Authorized User’s Personal Data from User’s Stripe Issuing Account when Law or the Card Network Rules require.
Qualifications & exceptions
The notice and consent duty falls on the User.
Deletion or disconnection is tied to what Law or the Card Network Rules require.
Not stated here
Section 4 of the General Terms and Stripe's Privacy Policy are not supplied in this document.
Use & Processing · Restriction or exception
Use Personal Data only for internal business, never as a FCRA consumer report; Stripe may use it as the bank's terms say
The User must use Personal Data related to its Stripe Issuing Account only for its internal business purposes and to fulfil its obligations under the Agreement. It must not use Personal Data or Stripe Data as part of a 'consumer report' as the FCRA defines that term, or in any manner that could subject Stripe to the FCRA or any claim of unfair or illegal decision making. Without limiting its other rights under the Agreement, Stripe may process, use and disclose Personal Data for the purposes identified in the Issuing Bank Terms.
Supporting quotations
6.2 User’s Use of Personal Data and Stripe Data.
User must only use Personal Data related to User’s Stripe Issuing Account for User’s internal business purposes and to fulfill User’s obligations under this Agreement. User must not use Personal Data or Stripe Data as part of a “consumer report” as that term is defined in the FCRA or in any manner that could subject Stripe to the FCRA or any claim of unfair or illegal decision making.
6.3 Stripe’s Use of Personal Data on behalf of Issuing Bank.
Without limiting its other rights under the Agreement, Stripe may process, use and disclose Personal Data for the purposes identified in the Issuing Bank Terms.
Qualifications & exceptions
Stripe's additional use of Personal Data is for the purposes in the Issuing Bank Terms.
Not stated here
The Issuing Bank Terms listing Stripe's purposes are not supplied here.
The FCRA is cited as a defined term and its text is not supplied.
Account & Service Control · Company practice
Stripe may use its remedies on any of fourteen triggers, from overspend and disputes to insolvency and Change of Control
Stripe may exercise the remedies in Section 7.3 if it determines a User Entity (a) exceeded limits on Available Spend; (b) had excessive Card Transaction disputes or unauthorized Card Transactions; (c) is or is likely to become subject to an Insolvency Event; (d) has a negative Stripe Account Balance or owes liability to Stripe or its Affiliates; (e) has or is likely to have a deterioration in business or financial condition Stripe considers material; (f) breached or is likely to breach, or caused or is likely to cause Stripe to breach, the Agreement, any other Stripe services agreement or the Financial Provider Terms; (g) violated or is likely to violate Law or Financial Provider Terms; (h) caused or is likely to cause Stripe to violate Law or Financial Provider Terms; (i) had or is likely to have a Change of Control; (j) changed its business model without Stripe's prior consent, exposing Stripe to increased risk; (k) acted or did business in a way that presents an unacceptable risk; (l) must indemnify Stripe under the Agreement; (m) had its Stripe Issuing Account suspended or terminated; or (n) failed to comply with the Issuing Bank Terms on securing Cards and Personal Data. These rights do not limit Stripe's other rights or remedies.
Supporting quotations
7.1 Stripe Remedies - Specific Triggers.
Without limiting Stripe’s other rights or remedies under this Agreement, Stripe may exercise any one or more of the remedies stated in Section 7.3 of these Stripe Issuing Accountholder Terms if Stripe determines that a User Entity:
(a) has exceeded limits on Available Spend;
(b) has experienced excessive Card Transaction disputes or unauthorized Card Transactions;
(c) is or is likely to become the subject of an Insolvency Event;
(d) has a negative Stripe Account Balance, or owe liability to Stripe or any of its Affiliates;
(e) has experienced or is likely to experience a deterioration of its business or financial condition that Stripe considers to be material;
(f) has breached or is likely to breach, or has caused or is likely to cause Stripe to breach, this Agreement (or any other Stripe services agreement with a Stripe Entity) or the Financial Provider Terms applicable to the User Entity’s use of the Services;
(g) has violated or is likely to violate Law or Financial Provider Terms;
(h) has caused or is likely to cause Stripe to violate Law or Financial Provider Terms;
(i) has experienced or is likely to experience a Change of Control;
(j) has, without Stripe’s prior consent, changed its business model (including services supplied by a User Entity to its customers), exposing Stripe to increased risk;
(k) has acted in a manner or engaged in business, trading practice, or other activity that presents an unacceptable risk;
(l) is required to indemnify Stripe under this Agreement;
(m) has experienced a suspension or termination of its Stripe Issuing Account; or
(n) fails to comply with the applicable Issuing Bank Terms related to securing Cards and Personal Data.
Qualifications & exceptions
Many triggers apply where the event is 'likely', not only where it has happened.
The triggers turn on Stripe's determination, and the list does not limit Stripe's other rights or remedies.
Not stated here
'Excessive' disputes, 'material' deterioration and 'unacceptable risk' have no numeric threshold.
Account & Service Control · Company practice
Stripe may also use its remedies for post-termination loss risk linked to a User Entity or where Law requires
Stripe may exercise the Section 7.3 remedies if (a) it reasonably determines it may incur losses from credit, fraud, criminal activity or other risks associated with a User Entity after the Accountholder Terms terminate, or (b) Law requires. These rights do not limit Stripe's other rights or remedies.
Supporting quotations
7.2 Stripe Remedies - General Trigger.
Without limiting Stripe’s other rights or remedies under this Agreement, Stripe may exercise any or all of the remedies stated in Section 7.3 of these Stripe Issuing Accountholder Terms if (a) Stripe reasonably determines that Stripe may incur losses resulting from credit, fraud, criminal activity, or other risks associated with a User Entity after these Stripe Issuing Accountholder Terms terminate; or (b) Law requires.
Qualifications & exceptions
The loss-risk limb requires Stripe to reasonably determine a risk linked to a User Entity after termination.
Account & Service Control · Company practice
Remedies once triggered: a Reserve, suspended Card use, or a guarantee or letter of credit (list continues)
If a trigger in Section 7.1 or 7.2, or in another provision that refers to these remedies, occurs, Stripe may (a) establish, fund and use a Reserve; (b) suspend or terminate the ability of the User and its Authorized Users to make Card Transactions; and (c) require the User to provide a guarantee, including a personal, parent or bank guarantee, or a letter of credit in a form and substance satisfactory to Stripe. The list continues in the next packet. These rights do not limit Stripe's other rights or remedies.
Supporting quotations
7.3 Stripe Remedies - Scope.
Without limiting Stripe’s other rights or remedies under this Agreement, if a triggering event in Sections 7.1 or 7.2 of these Stripe Issuing Accountholder Terms (or any other provision of this Agreement that refers to these remedies) has occurred, then Stripe may:
(a) establish, fund, and use a Reserve;
(b) suspend or terminate User and User’s Authorized User’s ability to make Card Transactions;
(c) require User to provide a guarantee (including a personal, parent, or bank guarantee) or letter of credit in a form and substance that satisfies Stripe;
Qualifications & exceptions
The remedies are cumulative with Stripe's other rights and remedies.
Not stated here
'Reserve' is a defined term outside this packet.
The remedy list continues in the next packet.
Charges & Financial Obligations · Company practice
Remedies continued: debit User and group bank accounts, and set off or recoup amounts owed, due or not
The Section 7.3 remedies also let Stripe (d) debit the User Bank Accounts, or the bank or financial institution accounts of any or all User Group Entities that have an agreement with a Stripe Entity under which a Stripe Entity provides services; and (e) set off or recoup all amounts Stripe reasonably determines a User Entity owes to a Stripe Entity under the Agreement or another agreement against any amounts a Stripe Entity owes to a User Entity, whether the amounts are matured, unmatured, liquidated or unliquidated.
Supporting quotations
(d) debit the User Bank Accounts or the bank or financial institution accounts of any or all User Group Entities that have entered into an agreement with a Stripe Entity under which a Stripe Entity provides services; and
(e) setoff or recoup all amounts that Stripe reasonably determines a User Entity owes to a Stripe Entity under this Agreement or another agreement, against any amounts that a Stripe Entity, owes to a User Entity, whether the amounts owed are matured, unmatured, liquidated, or unliquidated.
Qualifications & exceptions
The debit right reaches User Group Entities' accounts only where they have an agreement with a Stripe Entity for services.
Set-off and recoupment cover amounts Stripe reasonably determines are owed, whether or not yet due or fixed in amount.
Not stated here
'User Entity', 'User Group Entities' and 'Stripe Entity' are defined elsewhere, not in this packet.
Legal Rights & Agreement Rules · Context
Definitions: Available Spend, Card, Card Transaction, Authorized User, Payment Source mean what bank terms say
Section 8 sets out the definitions. 'Available Spend', 'Card', 'Card Transaction', 'Issuing Authorized User' and 'Payment Source' each have the meaning given in the applicable Issuing Bank Terms, so their content is not stated in this document.
Supporting quotations
8. Definitions.
“Available Spend” has the meaning given to it in the applicable Issuing Bank Terms.
“Card” has the meaning given to it in the applicable Issuing Bank Terms.
“Card Transaction” has the meaning given in the applicable Issuing Bank Terms.
“Issuing Authorized User” has the meaning given to it in the applicable Issuing Bank Terms.
“Payment Source” has the meaning given to it in the applicable Issuing Bank Terms.
Qualifications & exceptions
These terms have no meaning here except by reference to the Issuing Bank Terms.
Not stated here
The Issuing Bank Terms are not supplied, so the content of these definitions is unknown here.
A 'Card Network' is a payment card network including those of Visa, Mastercard, American Express and Discover, and 'Card Network Rules' are the Payment Method Rules a Card Network publishes. 'FCRA' means the Fair Credit Reporting Act and the Equal Credit Opportunity Act, 15 U.S.C. Section 1681 et seq., external statutes referenced by name. An 'Issuing Bank' is the Financial Provider that issues a Card, named in the Issuing Bank Terms, which are that bank's Financial Provider Terms governing the User's participation. An 'Issuing Complaint' is any expression of dissatisfaction with a product, service, policy or employee related to a Stripe Issuing Program. A 'Platform Provider' is the platform that gives the User access to the program. 'SPC' is Stripe Payments Company, a Stripe Affiliate. The 'Stripe Issuing Account' is the account an Issuing Bank maintains for an accountholder, with its subaccounts, and a 'Stripe Issuing Accountholder' is a business or organization that finished onboarding and was approved for one. The 'Accountholder Services' are Services Stripe and its Affiliates make available on behalf of Issuing Banks, including integration with Issuing Banks, access to Cards and Card spend management. A 'Stripe Issuing Administrator' is the individual an accountholder appoints to manage its participation, and the 'Stripe Issuing Program' is the Card issuing services the Issuing Bank provides under its terms together with the Accountholder Services. A 'Supported Currency' is a currency Stripe communicates as supported, and 'User Materials' are the Marks or other materials the User or accountholder wants on Cards and other materials the User gives Stripe for the program.
Supporting quotations
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
“Card Network Rules” means the Payment Method Rules published by a Card Network.
“FCRA” means Fair Credit Reporting Act, 15 U.S.C. Section 1681, et seq. and Equal Credit Opportunity Act, 15 U.S.C. Section 1681, et seq.
“Issuing Bank” means the Financial Provider, identified in the Issuing Bank Terms for the applicable Stripe Issuing Program, that issues a Card.
“Issuing Bank Terms” means the applicable Issuing Bank’s Financial Provider Terms that govern User’s participation in the applicable Stripe Issuing Program.
“Issuing Complaint” means any expression of dissatisfaction with a product, service, policy, or employee related to a Stripe Issuing Program.
“Platform Provider” means the platform that gives User access to the Stripe Issuing Program (if User is a Connected Account or if User otherwise accesses the Stripe Issuing Program through a platform).
“SPC” means Stripe Payments Company, which is a Stripe Affiliate.
“Stripe Issuing Account” means the account an Issuing Bank maintains for a Stripe Issuing Accountholder, and each subaccount to that account.
“Stripe Issuing Accountholder” means a business or organization that has successfully completed the onboarding requirements described in these Stripe Issuing Accountholder Terms and been approved for a Stripe Issuing Account.
“Stripe Issuing Accountholder Services” means Services that Stripe and its Affiliates make available to Stripe Issuing Accountholders, on behalf of Issuing Banks, and related Stripe services, including (a) integration with Issuing Banks; (b) providing Stripe Issuing Accountholders with access to Cards; (c) enabling Stripe Issuing Accountholders to manage Card spend; and (d) other services described in the Stripe Issuing Accountholder Terms.
“Stripe Issuing Administrator” means the individual that a Stripe Issuing Accountholder appoints to manage its participation in the Stripe Issuing Programs.
“Stripe Issuing Program” means Card issuing services that the applicable Issuing Bank provides under the applicable Issuing Bank Terms, together with the Stripe Issuing Accountholder Services.
“Supported Currency” means a currency supported under the Stripe Issuing Accountholder Services as communicated to User by Stripe.
“User Materials” means (a) all Marks or other materials that User or a Stripe Issuing Accountholder wish to place on Cards; or (b) all other materials that User provides to Stripe for the purposes of the Stripe Issuing Programs.
Qualifications & exceptions
The FCRA citation is to an external statute; its text is not part of this document.
Legal Rights & Agreement Rules · Context
US Issuing Platform terms (Sept 28, 2026) supplement the General Terms and govern your role as a Connect Platform
These Stripe Issuing Platform Terms for the United States, last modified September 28, 2026, supplement the General Terms and, together with the Stripe Financial Services Terms and Stripe Connect Infrastructure Terms (each incorporated by reference), govern the User's participation in the Stripe Issuing Programs as a Stripe Connect Platform. If the User receives Cards and otherwise participates as a Stripe Issuing Accountholder, the Stripe Issuing Accountholder Terms apply for that role. Capitalized terms not defined here take their meaning from the General Terms, Financial Services Terms, Financial Provider Terms and Connect Infrastructure Terms.
Supporting quotations
Stripe Issuing—Platform (United States)
Last modified: September 28, 2026
1. Stripe Issuing Services.
These terms (“Stripe Issuing Platform Terms”) supplement the General Terms and, together with the Stripe Financial Services Terms, and Stripe Connect Infrastructure Terms each of which are incorporated into these terms by this reference, govern User’s participation in the Stripe Issuing Programs as a Stripe Connect Platform. If User receives Cards and otherwise participates in the Stripe Issuing Programs as a Stripe Issuing Accountholder, the Stripe Issuing Accountholder Terms apply. Capitalized terms that are not defined in these terms have the same meanings given to them in the General Terms, Stripe Financial Services Terms, Financial Provider Terms, and Stripe Connect Infrastructure Terms.
Qualifications & exceptions
The accountholder role is governed by the Accountholder Terms, not these platform terms.
Not stated here
The General Terms, Financial Provider Terms and Connect Infrastructure Terms are separate documents not supplied in this run.
Account & Service Control · Restriction or exception
You and Stripe set up a joint program with Issuing Banks; offer it only to eligible Connected Accounts for business use
The User and Stripe will jointly establish a program through which eligible Connected Accounts may access a Stripe Issuing Program. Stripe offers several programs in partnership with several Issuing Banks, and the User can see the program offered to its Connected Accounts in its Stripe Dashboard. The User must offer the program only to eligible Connected Accounts for their business purposes.
Supporting quotations
2. Overview.
2.1 Program.
User and Stripe will jointly establish a program through which eligible Connected Accounts may access a Stripe Issuing Program. Stripe offers several Stripe Issuing Programs in partnership with several Issuing Banks, and User can view the Stripe Issuing Program offered to User’s Connected Accounts through User’s Stripe Dashboard. User must offer the Stripe Issuing Program only to eligible Connected Accounts for their business purposes.
Qualifications & exceptions
The offer is limited to eligible Connected Accounts and business purposes.
Not stated here
Eligibility criteria are not stated in this section.
Account & Service Control · Procedure
Stripe and the Issuing Bank must both approve you and each Connected Account; supply information on request
Stripe and the applicable Issuing Bank must each approve the User's use of the Stripe Issuing Platform Services and, before approving, may require User Information and information about the User's activities and intended use, which may be separate from or additional to what the User gave for other Services. The User must promptly provide that information and any other information about its use of the program that Stripe or the bank requests from time to time. Stripe and the Issuing Bank must also approve each Connected Account before it can become a Stripe Issuing Accountholder.
Supporting quotations
3. Approvals and Onboarding.
3.1 Approvals.
(a) Platform Approval. Stripe and the applicable Issuing Bank must each approve User’s use of the Stripe Issuing Platform Services, and prior to granting their approval, they may require User to provide User Information and information about User’s activities and intended use of the Stripe Issuing Platform Services. This information may be separate from or in addition to information User previously provided to Stripe in connection with other Services. User must promptly provide this information, and any other information related to User’s use of the Stripe Issuing Program that Stripe or the applicable Issuing Bank may request from time to time.
(b) Connected Account Approval. Stripe and the applicable Issuing Bank must approve each Connected Account before it can become a Stripe Issuing Accountholder.
Qualifications & exceptions
Both Stripe and the Issuing Bank must approve the platform and each Connected Account.
Account & Service Control · Procedure
Either party may host onboarding, some programs require you to; if you host, use Stripe's application form
Either the User or Stripe may host the accountholder onboarding process, and certain programs may require the User to host it. If the User hosts, it must configure the Stripe API to meet these requirements. Stripe makes available an approved electronic application form that the User must offer to Connected Accounts wishing to use the Accountholder Services. Each Connected Account must submit all information Stripe and the Issuing Bank need to verify its identity, confirm it is not engaged in a Prohibited or Restricted Business, and confirm its eligibility. After a completed application, Stripe, on behalf of the Issuing Bank, decides whether to approve it as an accountholder.
Supporting quotations
3.2 Stripe Issuing Accountholder Onboarding.
Either User or Stripe may host the Stripe Issuing Accountholder onboarding process. Certain Stripe Issuing Programs may require User to host onboarding.
(a) User-Hosted Onboarding. If User hosts onboarding, User must configure the Stripe API to meet the following requirements:
(i) Stripe Issuing Accountholder Application. Stripe will make available to User an approved electronic application form for Stripe Issuing Accountholders. User must make this form available to Connected Accounts that wish to use the Stripe Issuing Accountholder Services. Each Connected Account must submit in its application all information necessary for Stripe and the Issuing Bank to (A) verify the Connected Account’s identity; (B) confirm that the Connected Account is not engaged in a Prohibited or Restricted Business; and (C) confirm the Connected Account’s eligibility to use the Stripe Issuing Accountholder Services. After Stripe receives a completed application, Stripe, on behalf of the applicable Issuing Bank, will determine whether the Connected Account is approved as a Stripe Issuing Accountholder.
Qualifications & exceptions
These requirements apply when the User hosts onboarding.
Stripe decides approval on behalf of the Issuing Bank.
Account & Service Control · Procedure
Present the Card Program and Issuing Bank Terms before applications, and keep retrievable acceptance records
The User must present the agreements the Documentation describes, including the Card Program Terms and the applicable Issuing Bank Terms, to each Connected Account before it submits its accountholder application, and must ensure each Connected Account agrees to them, in each case in the manner the Stripe Issuing Program Guidelines describe. The User must keep a retrievable, examinable record and description of the interfaces it uses to collect acceptance of the relevant Stripe and Issuing Bank terms, with date and time, give them to Stripe on request, and change an acceptance process Stripe believes does not create a binding agreement with Stripe and the Issuing Bank or does not meet the bank's requirements.
Supporting quotations
(ii) Presentation of Terms. User must (A) present the agreements described in the Documentation, including the Card Program Terms and the applicable Issuing Bank Terms to each Connected Account before that Connected Account submits its accountholder application; and (B) ensure that each Connected Account agrees to these terms, in each case in the manner the Stripe Issuing Program Guidelines describe.
(iii) Acceptance Records. User must maintain a record and description of the user interfaces that User uses to collect acceptance of the relevant Stripe terms and Issuing Bank terms (including date and time) in a retrievable and examinable format, and at Stripe’s request, provide them to Stripe. If Stripe believes that User’s existing acceptance process does not (A) create a binding agreement between each Connected Account and each of Stripe and the Issuing Bank; or (B) comply with the applicable Issuing Bank’s requirements, then, upon Stripe’s request, User must modify that process as Stripe or the Issuing Bank requires.
Qualifications & exceptions
Acceptance must be collected before the accountholder application is submitted.
Not stated here
The Card Program Terms and the Guidelines are not part of this document.
Sharing & Disclosure · Procedure
Ensure cardholders accept the Authorized User Terms, and disclose data sharing and Privacy Policy to prospects
Accountholders may designate Issuing Authorized Users to make Card Transactions on their behalf. The User must ensure each accountholder presents the Issuing Authorized User Terms to each Issuing Authorized User and that each agrees to them, in the manner the Guidelines describe, and on Stripe's request must give proof they were entered into. If Stripe believes the process does not create a binding agreement between accountholders and Issuing Authorized Users or does not meet the Issuing Bank's requirements, the User must modify it as Stripe or the bank requires. The User must also disclose to all prospective accountholders that it may give Personal Data to Stripe and the Issuing Bank and that they may receive or collect it, and ensure each prospective accountholder consents to Stripe's Privacy Policy.
Supporting quotations
(iv) Issuing Authorized User Terms. Stripe Issuing Accountholders may designate Issuing Authorized Users to make Card Transactions on their behalf. User must ensure that each Stripe Issuing Accountholder presents the Issuing Authorized User Terms to each Issuing Authorized User, and that each Issuing Authorized User agrees to the Issuing Authorized User Terms, in the manner described in the Stripe Issuing Program Guidelines. At Stripe’s request, User must provide proof as Stripe requires that these terms have been entered into by Issuing Authorized Users. If Stripe believes that User’s existing process does not (A) create a binding agreement between any Stripe Issuing Accountholders and each Issuing Authorized User; or (B) comply with the applicable Issuing Bank’s requirements, then, upon Stripe’s request, User must modify that process as Stripe or the Issuing Bank requires.
(v) Data Use Disclosure. User must disclose to all prospective Stripe Issuing Accountholders that User may provide Personal Data to Stripe and the applicable Issuing Bank, and that Stripe and the applicable Issuing Bank may receive or collect Personal Data. User must ensure that each prospective Stripe Issuing Accountholder consents to Stripe’s Privacy Policy.
Qualifications & exceptions
Consent to Stripe's Privacy Policy is required of each prospective accountholder.
Not stated here
The Issuing Authorized User Terms and Stripe's Privacy Policy are not supplied here.
Account & Service Control · Restriction or exception
Never modify any Stripe or Issuing Bank terms; if Stripe hosts onboarding, integrate with its API per the Documentation
The User must not modify or supplement any provision of any Stripe terms, including the Accountholder Terms and Issuing Authorized User Terms, or the Issuing Bank Terms. If Stripe hosts the onboarding process, the User must integrate with the applicable Stripe API according to the Documentation and the Agreement.
Supporting quotations
(vi) No User Modifications. User must not modify or supplement any provision of any Stripe terms, including the Stripe Issuing Accountholder Terms and Issuing Authorized User Terms, or the Issuing Bank Terms.
(b) Stripe-Hosted Onboarding. If Stripe hosts the onboarding process, User must integrate with the applicable Stripe API according to the Documentation and this Agreement.
Qualifications & exceptions
The ban on modification reaches Stripe terms and Issuing Bank Terms alike.
Account & Service Control · Procedure
You provide account management via the API and must pass Stripe's information on to accountholders unaltered
The User must provide account management services for accountholders, including access through the Stripe API to the Accountholder Services described in the Accountholder Terms, such as Card creation, Issuing Authorized User designation and account management. Stripe makes information, including Personal Data, available for the User to pass to accountholders. The User must not alter or delete this information and must pass all of it to the accountholders.
Supporting quotations
3.3 Stripe Issuing Account Management.
User must provide account management services for Stripe Issuing Accountholders. User must provide Stripe Issuing Accountholders access through the Stripe API to the Stripe Issuing Accountholder Services described in the Stripe Issuing Accountholder Terms, including Card creation, Issuing Authorized User designation and account management services. Stripe will make information, including Personal Data, available for User to pass to Stripe Issuing Accountholders. User must not alter or delete this information, and User must pass all of this information to the Stripe Issuing Accountholders.
Qualifications & exceptions
The User may not alter or delete the information Stripe supplies for accountholders.
Account & Service Control · Restriction or exception
Do not offer the program to Connected Accounts, or keep accountholders, outside the Territory
The User must not offer, market or make the Stripe Issuing Program available to Connected Accounts outside the Territory, and must ensure no Stripe Issuing Accountholder is domiciled outside the Territory.
Supporting quotations
3.4 Stripe Issuing Program Territory.
User must not offer, market or make the Stripe Issuing Program available to Connected Accounts outside of the Territory. User must ensure that no Stripe Issuing Accountholder is domiciled outside of the Territory.
Qualifications & exceptions
The limit is on both offering to Connected Accounts and on accountholders' domicile.
Not stated here
'Territory' is defined elsewhere and is not stated in this packet.
Account & Service Control · Procedure
Stripe and Issuing Banks may change their terms; pass notice on promptly and stop serving accountholders who object
Stripe may modify the Accountholder Terms, and each Issuing Bank may modify the applicable Issuing Bank Terms, at any time. Stripe will notify the User of a modification as applicable to its program. The User must notify its accountholders promptly after receiving the notice from Stripe. If any accountholder does not agree to the updated terms, the User must immediately stop making the Accountholder Services available to that accountholder.
Supporting quotations
4. Stripe Issuing Accountholder Terms and Stripe Issuing Accountholder Fees.
4.1 Updates to Stripe Issuing Accountholder Terms.
Stripe may modify the Stripe Issuing Accountholder Terms, and each Issuing Bank may modify the applicable Issuing Bank Terms, at any time. Stripe will notify User if Stripe modifies the Stripe Issuing Accountholder Terms or an Issuing Bank modifies the Issuing Bank Terms, in each case as applicable to User’s Stripe Issuing Program. User must notify User’s Stripe Issuing Accountholders of a modification promptly after User receives the modification notice from Stripe. If any Stripe Issuing Accountholder does not agree to the updated Stripe Issuing Accountholder Terms or Issuing Bank Terms, User must immediately stop making the Stripe Issuing Accountholder Services available to that Stripe Issuing Accountholder.
Qualifications & exceptions
The User must act promptly after Stripe's notice and stop service at once for an accountholder who does not agree.
Charges & Financial Obligations · Restriction or exception
You owe accountholder fees; pass-on limits apply; Stripe may review fees; program fees follow the Pricing Page
The User is liable to Stripe for fees it and its accountholders incur. Subject to the terms, Card Network Rules and Law, the User may pass certain fees on to accountholders, but not fees attributable to an accountholder's use of Apple Pay or any other digital wallet or to a Card Transaction disputed as fraudulent or otherwise unauthorized. The User is solely responsible for communicating any use, recurring or application fees it charges accountholders for Platform Services connected to the Issuing Services, and must communicate them clearly before imposing them. Stripe, on behalf of the Issuing Bank, may review the fees the User charges to see if they comply with the bank's requirements, Card Network Rules and Law, and if not the User must immediately modify them as Stripe directs. Stripe provides the Platform Services and Accountholder Services at the rates and fees on the Stripe Pricing Page unless the User and Stripe agree otherwise in writing.
Supporting quotations
4.2 Stripe Issuing Accountholder Fees.
User is liable to Stripe for fees User and User’s Stripe Issuing Accountholders incur. Subject to these Stripe Issuing Platform Terms, the Card Network Rules and Law, User may pass certain fees onto the applicable Stripe Issuing Accountholders. User must not pass any fees to any Stripe Issuing Accountholder that are attributable to (a) a Stripe Issuing Accountholder’s use of Apple Pay or any other digital wallet; or (b) a Card Transaction that was disputed because it was fraudulent or otherwise unauthorized. User is solely responsible for communicating any use, recurring, or application fees charged to User’s Stripe Issuing Accountholders for their use of Platform Services in connection with the Stripe Issuing Services, and must clearly communicate those fees to Stripe Issuing Accountholders prior to imposing such fees. Stripe, on behalf of the applicable Issuing Bank, may review the fees User charges User’s Stripe Issuing Accountholders in connection with the Stripe Issuing Services to determine whether the fees comply with that Issuing Bank’s requirements, the Card Network Rules and Law. If Stripe determines the fees do not comply, User must immediately modify the fees as Stripe directs.
4.3 Program Fees.
Stripe will provide the Stripe Issuing Platform Services to User and the Stripe Issuing Accountholder Services to Stripe Issuing Accountholders at the rates and for the fees described on the Stripe Pricing Page, unless User and Stripe otherwise agree in writing.
Qualifications & exceptions
Fee pass-through is subject to the terms, Card Network Rules and Law.
The ban covers digital wallet use and disputed fraudulent or unauthorized transactions.
Not stated here
Fee amounts are on the Stripe Pricing Page, which is not supplied here.
Charges & Financial Obligations · Restriction or exception
Stripe sends Tax Information Reports to you only; you indemnify Stripe for taxes caused by late filing
If applicable, Stripe issues Tax Information Reports only to the User, not to accountholders, and the User is responsible for any applicable Tax Information Reports or withholding to accountholders. The User will indemnify Stripe from all Taxes, and related interest, penalties and fees, other than income, franchise or similar taxes payable on the Fees, imposed on a Stripe Entity because the User failed to file Tax Information Reports on time. A 'Tax Information Report' is a required tax information return or report, including IRS Form 1099, or any similar form.
Supporting quotations
5. Taxes.
5.1 Reporting.
If applicable, Stripe will only issue Tax Information Reports to User, and not to Stripe Issuing Accountholders. User is responsible for any applicable Tax Information Reports, or withholding, to Stripe Issuing Accountholders.
5.2 Indemnity.
User will indemnify Stripe from all Taxes, and related interest, penalties and fees (excluding any income, franchise or similar taxes payable with respect to the Fees), if any, imposed on a Stripe Entity as a result of User’s failure to timely file any Tax Information Reports under Section 5.1 of these Stripe Issuing Platform Terms. “Tax Information Report” means a required tax information return or report, including IRS Form 1099, or any other similar form.
Qualifications & exceptions
The indemnity covers taxes imposed on a Stripe Entity because of the User's late or missed filings, and excludes income, franchise or similar taxes payable on the Fees.
Account & Service Control · Procedure
Card designs need Stripe review; Cards ship at your expense and risk passes when shipped
The User and its accountholders may request specific Card designs, and the User must submit all designs to Stripe for review through Stripe's process. Stripe checks designs against the Agreement, Issuing Bank requirements, Card Network Rules, Law and Stripe reputational considerations, recommends modifications if it does not approve, and the User must resubmit modified designs the same way. The User may order Cards for accountholders through the Stripe Dashboard or API. At the User's expense, Stripe procures and ships Cards to the ordered address and replacements for Cards reported lost, stolen or damaged. Risk of loss passes to the recipient, the User or the accountholder as applicable, when Stripe ships the Card.
Supporting quotations
6. Cards; Card Orders.
6.1 Card Design.
User and User’s Stripe Issuing Accountholders may request specific Card designs. User must submit all Card designs to Stripe for review using the process Stripe requires. Stripe will review Card design proposals for compliance with this Agreement, Issuing Bank requirements, the Card Network Rules, Law, and Stripe reputational considerations. If Stripe does not approve a proposed Card design, Stripe will recommend modifications that, if made, will meet these requirements. User must resubmit the modified design to Stripe for approval using the same process.
6.2 Card Orders.
User may order Cards on behalf of Stripe Issuing Accountholders through User’s Stripe Dashboard or the Stripe API. At User’s expense, Stripe will procure and ship (a) Cards based on the information contained in each Card order to the address specified in that Card order; and (b) replacements for Cards reported as lost, stolen or damaged. Risk of loss for Cards passes to the recipient (either User or the Stripe Issuing Accountholder, as applicable) when Stripe ships the Card to the address specified in the order.
Qualifications & exceptions
Procurement and shipping, including replacements, are at the User's expense.
Account & Service Control · Company practice
The Issuing Bank owns each Card; Stripe or the bank may recall, cancel, restrict, decline or reverse
The applicable Issuing Bank owns each Card. If Stripe asks the User or an accountholder to return a Card, it must be returned promptly to Stripe or the Issuing Bank as Stripe instructs. Stripe or the Issuing Bank may cancel, repossess or restrict the use of Cards at any time, and may decline to authorize or reverse any Card Transaction, according to the Issuing Bank Terms.
Supporting quotations
6.3 Card Ownership; Limitations.
The applicable Issuing Bank owns each Card. If Stripe requests that User or a Stripe Issuing Accountholder return a Card, then User must return, or ensure that the Stripe Issuing Accountholder returns, that Card promptly to Stripe or the applicable Issuing Bank as Stripe instructs. Stripe or the applicable Issuing Bank may cancel, repossess or restrict the use of Cards at any time, and may decline to authorize or reverse any Card Transaction, according to the applicable Issuing Bank Terms.
Qualifications & exceptions
These rights operate according to the Issuing Bank Terms.
Not stated here
The Issuing Bank Terms are not supplied here.
Security & Safeguards · Restriction or exception
Personal Data you handle through the Dashboard or API must be secured as the Agreement requires
If the User processes, accesses, stores or retrieves Personal Data from its Stripe Dashboard or API, it must ensure the data is secured in accordance with the Agreement, including Sections 10.2 and 12 of these Stripe Issuing Platform Terms.
Supporting quotations
6.4 Personal Data Security.
If User processes, accesses, stores, or retrieves Personal Data from User’s Stripe Dashboard or Stripe API, User must ensure that the Personal Data is secured in accordance with this Agreement, including Sections 10.2 and 12 of these Stripe Issuing Platform Terms.
Qualifications & exceptions
The duty applies to Personal Data the User processes, accesses, stores or retrieves from the Dashboard or API.
Not stated here
The cited Sections 10.2 and 12 are in a later part of these terms.
Content & IP Rights · Permission or license
You license your User Materials to Stripe and Affiliates for the Term, with the right to sublicense card makers
The User must have the necessary rights in the User Materials to use them, and let Stripe use them, on Cards and other program materials. The User grants Stripe and its Affiliates a worldwide, non-exclusive, royalty-free license during the Term to use the User Materials on Cards and applicable program materials, and the right to sublicense these rights to third parties Stripe engages to create Cards and those materials.
Supporting quotations
6.5 User Materials.
User must have the necessary rights in and to the User Materials to use (and grant Stripe the rights to use) the User Materials on the Cards and other materials related to the Stripe Issuing Programs. User grants to Stripe and its Affiliates a worldwide, non-exclusive, royalty-free license during the Term to use the User Materials on Cards and applicable Stripe Issuing Program materials. User also grants to Stripe and its Affiliates the right to sublicense these rights to third parties that Stripe engages to create Cards and applicable Stripe Issuing Program materials.
Qualifications & exceptions
The license runs during the Term, is non-exclusive and royalty-free, and extends to sublicensees engaged by Stripe.
Account & Service Control · Company practice
Stripe and the bank may use Connected Account information to vet and monitor people, and reject or end access
Stripe and the Issuing Bank may use all information the User gives about a Connected Account to (a) decide its eligibility to be an accountholder, (b) administer the programs, and (c) monitor each accountholder's Principal Owners (individuals owning at least 25% of the equity of a legal entity, directly or indirectly), Stripe Issuing Administrators, Issuing Authorized Users, representatives and individuals with significant management responsibility, to meet their obligations under Law. Stripe or an Issuing Bank may reject any Connected Account's application, or terminate any accountholder's access to the Accountholder Services, immediately to comply with Law, to manage risk associated with any User, or if any of those people is or becomes a High-Risk Person.
Supporting quotations
7. Use of Stripe Issuing Services.
7.1 Opening an Account.
Stripe and the Issuing Bank may use all information that User provides to Stripe about a Connected Account to (a) determine the Connected Account’s eligibility to be a Stripe Issuing Accountholder; (b) administer the Stripe Issuing Programs; and (c) monitor each Stripe Issuing Accountholder’s Principal Owners, Stripe Issuing Administrators, Issuing Authorized Users, representatives, and individuals with significant responsibility for management, including executives and senior managers, for the purpose of meeting Stripe’s and the applicable Issuing Bank’s respective obligations under Law. Stripe or an Issuing Bank may reject any Connected Account’s application for, or terminate any Stripe Issuing Accountholder’s access to, the Stripe Issuing Accountholder Services immediately to comply with Law, manage risk associated with any User, or if any Connected Account, Stripe Issuing Accountholder, or any Principal Owner, Stripe Issuing Administrator, Issuing Authorized User, representative, or individual with significant responsibility for management is or becomes a High-Risk Person.
“Principal Owner” means, with respect to a legal entity, an individual who directly or indirectly, through any contract, arrangement, understanding, relationship, or otherwise, owns at least 25% of the equity interests of the legal entity.
Qualifications & exceptions
Monitoring is to meet Stripe's and the Issuing Bank's obligations under Law.
Termination is immediate and may rest on Law, risk associated with any User, or High-Risk Person status.
Not stated here
'High-Risk Person' is defined outside this packet.
Account & Service Control · Procedure
You provide all accountholder and cardholder support per Guidelines, cannot outsource, and report Complaints monthly
The User must provide all support to, and handle all inquiries and Issuing Complaints from, accountholders and Issuing Authorized Users, including about Card usage and lost, damaged or stolen Cards, according to the Stripe Issuing Program Guidelines. Unless Stripe agrees otherwise, the User must not outsource this support to any third party. Monthly, the User must give Stripe a report of the Issuing Complaints it received and handled in the prior month, as the Guidelines describe, and at an Issuing Bank's request Stripe may require an anonymized sample of Complaints to validate the report.
Supporting quotations
7.2 Issuing Authorized User Servicing.
User must provide all support to, and handle all inquiries and Issuing Complaints from, Stripe Issuing Accountholders and Issuing Authorized Users, including regarding Card usage, and lost, damaged or stolen Cards. User must provide this support according to the Stripe Issuing Program Guidelines. Unless Stripe agrees otherwise, User must not outsource User’s support obligations to any third party. On a monthly basis, User must provide to Stripe a report of Issuing Complaints that User received and handled during the prior month as described in the Stripe Issuing Program Guidelines. At an Issuing Bank’s request, Stripe may require User to provide an anonymized sample of Issuing Complaints, if any, to validate the report.
Qualifications & exceptions
Outsourcing is barred unless Stripe agrees otherwise.
A sample of Complaints may be required at an Issuing Bank's request.
Not stated here
The Guidelines are not part of this document.
Charges & Financial Obligations · Restriction or exception
You are responsible, jointly and severally, for all Issuing program activity
Except as the Agreement expressly provides, and without prejudice to the Stripe Connect Infrastructure Terms, the User is responsible for all Activity relating to the Stripe Issuing Program, whether started by the User, an accountholder, an Issuing Authorized User or anyone using the User's credentials. That includes activity in violation of the Agreement or Card Network Rules, all Card Transactions on the Stripe Issuing Account, and any fees, losses, damages or costs Stripe incurs from that activity. Stripe may try to collect from accountholders first, but the User remains jointly and severally liable and Stripe may collect from the User under the Agreement.
Supporting quotations
7.3 Responsibility for Activity.
Except as expressly provided in this Agreement, and without prejudice to the Stripe Connect Infrastructure Terms, User is responsible for all Activity relating to the Stripe Issuing Program, whether initiated by User, a Stripe Issuing Accountholder, an Issuing Authorized User, or any person using User’s credentials, including (a) in violation of this Agreement, or the applicable Card Network Rules; (b) all Card Transactions on the Stripe Issuing Account; and (c) any fees, losses, damages, or costs that Stripe incurs arising out of or relating to that Activity. Stripe may attempt to collect any amounts owed by Stripe Issuing Accountholders before Stripe collects these amounts from User. However, User remains jointly and severally liable to Stripe for these amounts, and Stripe may collect these amounts from User in accordance with this Agreement.
Qualifications & exceptions
Stripe may try to collect from accountholders first without releasing the User's joint and several liability.
Account & Service Control · Company practice
Stripe and SPC manage bank relationships and may change banks; you must implement required service changes
As between the parties, Stripe, directly or through its Affiliate SPC, is responsible for all aspects of establishing and managing its relationships with Issuing Banks. Stripe and SPC rely on the applicable Issuing Bank to enable the Issuing Services. Stripe may add or remove Issuing Banks at any time and will notify the User in advance of a bank change that will affect the services. If Stripe or an Issuing Bank requires a change to all or part of the Issuing Services, the User must implement it promptly and as directed, comply with it, and ensure each accountholder implements and complies with it.
Supporting quotations
8. Issuing Banks.
8.1 Relationships with Issuing Banks.
As between the parties, Stripe, either directly or through its Affiliate, SPC, is responsible for all aspects of establishing and managing its relationships with Issuing Banks. Stripe and SPC rely on the applicable Issuing Bank to enable Stripe and SPC to provide the Stripe Issuing Services. Stripe may add or remove Issuing Banks at any time. Stripe will notify User in advance of an Issuing Bank change that will affect the Stripe Issuing Services.
8.2 Changes to the Stripe Issuing Services.
If Stripe or an Issuing Bank requires a change to all or part of the Stripe Issuing Services, User must implement that change promptly and as Stripe or the Issuing Bank directs. User must comply with, and User must ensure that each Stripe Issuing Accountholder implements and complies with, the change.
Qualifications & exceptions
Advance notice is promised only for a bank change that will affect the services.
Not stated here
The length of advance notice is not stated.
Legal Rights & Agreement Rules · Restriction or exception
Comply, and ensure accountholders comply, with the Guidelines, Card Program Terms, bank terms, Law and Network Rules
The User must (a) comply, and ensure all accountholders comply, with the Stripe Issuing Program Guidelines; (b) ensure all accountholders comply with the Card Program Terms and the applicable Issuing Bank Terms and use the Accountholder Services according to Law and the Card Network Rules; and, in the next packet, further duties follow.
Supporting quotations
9. Compliance and Marketing.
9.1 General.
User must:
(a) comply with, and ensure all Stripe Issuing Accountholders comply with, the Stripe Issuing Program Guidelines;
(b) ensure that all Stripe Issuing Accountholders comply with the Card Program Terms and applicable Issuing Bank Terms, and access and use the Stripe Issuing Accountholder Services according to Law and the Card Network Rules;
Qualifications & exceptions
The list of compliance duties continues in the next packet.
Not stated here
The Card Program Terms and Guidelines are not part of this document.
Legal Rights & Agreement Rules · Restriction or exception
More duties: Authorized User Terms, no Law violations, compliant fees, and business use only
The User must also (c) ensure all Issuing Authorized Users comply with the Issuing Authorized User Terms; (d) not take or fail to take, and ensure accountholders and Issuing Authorized Users do not take or fail to take, any action that could cause Stripe or any Issuing Bank to violate Law or Card Network Rules; (e) ensure the fees it charges its Connected Accounts comply with the Issuing Bank's requirements, Card Network Rules and Law; and (f) ensure accountholders and Issuing Authorized Users use the Accountholder Services for business purposes only.
Supporting quotations
(c) ensure that all Issuing Authorized Users comply with the Issuing Authorized User Terms;
(d) not, and must ensure that Stripe Issuing Accountholders and Issuing Authorized Users do not, take or fail to take any action that could cause Stripe or any Issuing Bank to violate Law or any Card Network Rules;
(e) ensure the fees User charges User’s Connected Accounts comply with the Issuing Bank’s requirements, the Card Network Rules, and Law; and
(f) ensure that Stripe Issuing Accountholders and Issuing Authorized Users use the Stripe Issuing Accountholder Services for business purposes only.
Qualifications & exceptions
These duties continue the list begun in the previous packet.
Account & Service Control · Procedure
Run a compliance program Stripe and the bank may assess; send compliance notices; Stripe may message accountholders
The User must establish, maintain and act according to a compliance program that ensures the User and each accountholder comply with Law, the Card Network Rules and the Guidelines, and that the User complies with the Agreement. Stripe and the Issuing Bank may assess the User's compliance with the Guidelines, and the User must promptly provide all information, documentation and assistance they require. As the Guidelines describe, the User must send certain compliance-related communications to its accountholders, and Stripe may send communications directly to them, including on behalf of an Issuing Bank.
Supporting quotations
9.2 Compliance Program.
(a) Requirements. User must establish, maintain, and act according to a compliance program that enables and ensures that (i) User and each Stripe Issuing Accountholder complies with Law, the Card Network Rules, and the Stripe Issuing Program Guidelines; and (ii) User complies with this Agreement. Stripe and Issuing Bank may assess User’s compliance with the Stripe Issuing Program Guidelines and User must promptly provide all information, documentation, and assistance that Stripe or Issuing Bank require to assess User’s compliance.
(b) Customer Communications. As described in the Stripe Issuing Program Guidelines, (a) User must send certain compliance-related communications to User’s Stripe Issuing Accountholders; and (b) Stripe may send communications directly to User’s Stripe Issuing Accountholders, including on behalf of an Issuing Bank.
Qualifications & exceptions
Direct communications by Stripe may be made on behalf of an Issuing Bank.
Not stated here
The Guidelines are not part of this document.
Account & Service Control · Restriction or exception
Stripe must approve your marketing materials; unmodified Stripe templates need no further approval
Stripe must approve all marketing materials the User wishes to use with the Stripe Issuing Services. Stripe may provide template materials the User may use without further approval as long as they are not modified. The User must submit all proposed marketing materials through a process Stripe communicates.
Supporting quotations
9.3 Marketing.
Stripe must approve all marketing materials that User wishes to use in connection with the Stripe Issuing Services. Stripe may provide template marketing materials to User, which User may use without further Stripe approval as long as the template marketing materials are not modified. User must submit all proposed marketing materials to Stripe using a process Stripe communicates to User.
Qualifications & exceptions
Templates are pre-approved only if not modified.
Use & Processing · Restriction or exception
Data use: Stripe's rights follow the Card Program Terms; you use Personal Data for five purposes and never sell it
Between Stripe and an accountholder, Stripe's rights to use Protected Data generated by the Stripe Issuing Programs are governed by the Card Program Terms and the Issuing Authorized User Terms. The User may process, use and disclose Personal Data only (i) in connection with its use of the Issuing Platform Services; (ii) to give accountholders access to the Accountholder Services; (iii) for its own fraud prevention and loss mitigation; (iv) to fulfill its obligations to Stripe or an Issuing Bank; and (v) to comply with Law and the Card Network Rules. The User must not sell, rent, transfer, make available or communicate any Personal Data to a third party for monetary or other valuable consideration. It must also obtain and maintain all rights and consents under Law to provide the User Information it gives Stripe and the Issuing Bank about its Principal Owners, employees, contractors and agents, and its Connected Accounts, accountholders and Issuing Authorized Users.
Supporting quotations
10. Data Use.
10.1 Data Use.
(a) Stripe’s Data Use. As between Stripe and a Stripe Issuing Accountholder, Stripe’s rights to use Protected Data generated by the Stripe Issuing Programs are governed by the Card Program Terms and the Issuing Authorized User Terms.
(b) User’s Data Use. User may process, use, and disclose Personal Data for only the following purposes: (i) in connection with User’s use of the Stripe Issuing Platform Services; (ii) to provide Stripe Issuing Accountholders access to the Stripe Issuing Accountholder Services; (iii) in connection with User’s own fraud prevention and loss mitigation activities; (iv) to fulfill User’s obligations to Stripe or an Issuing Bank; and (v) to comply with Law and the Card Network Rules. Without limiting the previous sentence, User must not sell, rent, transfer, make available or communicate orally or through other means any Personal Data to a third party for monetary or other valuable consideration.
(c) Data Collection. User must obtain and maintain all necessary rights and consents under Law to provide the User Information that User provides to Stripe and the applicable Issuing Bank about each of User’s (i) Principal Owners and employees, contractors and agents; and (ii) Connected Accounts, Stripe Issuing Accountholders and Issuing Authorized Users.
Qualifications & exceptions
The five purposes are the only permitted uses of Personal Data.
The ban on selling covers transfer to a third party for monetary or other valuable consideration.
Not stated here
Protected Data and the Card Program Terms are not defined or supplied in this document.
Security & Safeguards · Restriction or exception
Secure Cards and Personal Data with industry-standard encryption and monitor for fraud, and ensure accountholders do too
The User must secure Cards and Personal Data in its possession or control and ensure its accountholders do the same. When stored or processed digitally, it must use appropriate organizational and technical measures, including industry-standard encryption. The User must monitor, and ensure its accountholders monitor, for suspicious and unauthorized activity and fraud on each accountholder's Stripe Issuing Account and each Card.
Supporting quotations
10.2 Securing Cards and Account Data.
User must secure Cards and Personal Data in User’s possession or control, and User must ensure that User’s Stripe Issuing Accountholders secure Cards and Personal Data in their possession or control. When stored or processed digitally, User must use appropriate organizational and technical measures to secure the Cards and Personal Data in User’s possession or control, including through industry-standard encryption. User must monitor, and User must ensure that User’s Stripe Issuing Accountholders monitor, suspicious and unauthorized activities and fraud on each Stripe Issuing Accountholder’s Stripe Issuing Account and each Card.
Qualifications & exceptions
The monitoring duty is both the User's and each accountholder's.
Not stated here
'Appropriate' measures are not specified beyond industry-standard encryption.
Legal Rights & Agreement Rules · Restriction or exception
You bear fees, penalties and losses from lax safeguarding, late reporting, sharing a Card or unauthorized use
The User is responsible for all fees and penalties resulting from an accountholder's or Issuing Authorized User's failure to exercise reasonable care in safeguarding Cards from loss or theft or to promptly report loss, theft or fraud. To the extent Law permits, if the User, an accountholder or an Issuing Authorized User lets another party use a Card or Personal Data for any purpose, or if an unauthorized person uses a Card or Personal Data, the User is responsible for that use, including all losses, damages, costs, fines, fees or penalties related to it.
Supporting quotations
10.3 Responsibility for Card Transactions.
User is responsible for all fees and penalties incurred resulting from a Stripe Issuing Accountholder or Issuing Authorized User’s failure to (a) exercise reasonable care in safeguarding Cards from loss or theft, or (b) promptly report loss or theft, including fraud. Additionally, to the extent Law permits, if User, a Stripe Issuing Accountholder or an Issuing Authorized User allows another party to use the Card or Personal Data for any purpose, or if an unauthorized person uses a Card or Personal Data, User is responsible for that use, including all losses, damages, costs, fines, fees, or penalties related to that use.
Qualifications & exceptions
The second allocation applies 'to the extent Law permits'.
Use & Processing · Restriction or exception
Never use Personal Data or Stripe Data as a FCRA consumer report or in a way that exposes Stripe to the FCRA
The User must not use Personal Data or Stripe Data as part of a 'consumer report' as the FCRA defines that term. It must not use any Stripe Data in any manner that could subject Stripe to the FCRA or any claim of unfair or illegal decision making.
Supporting quotations
10.4 Additional Data Restrictions.
User must not use Personal Data or Stripe Data as part of a “consumer report” as that term is defined in the FCRA. User must not use any Stripe Data in any manner that could subject Stripe to the FCRA or any claim of unfair or illegal decision making.
Qualifications & exceptions
The restriction covers both Personal Data and Stripe Data.
Not stated here
The FCRA is cited as a defined term and its text is not supplied.
Account & Service Control · Procedure
Give accountholders the Disputes API Form or a channel, send disputes to Stripe at once, and never block disputes
Stripe makes the Disputes API Form available to the User. The User must either configure the Stripe API to offer it to its accountholders or provide a channel through which they can submit disputes to the User, and must immediately submit any disputes it receives to Stripe through the Stripe API or Dashboard. The User must not interfere with any accountholder's ability to dispute a Card Transaction.
Supporting quotations
11. Card Disputes.
11.1 Disputes Generally; Disputes API Form.
Stripe will make the Disputes API Form available to User. User must either (a) configure the Stripe API to make the Disputes API Form available to User’s Stripe Issuing Accountholders; or (b) provide a channel through which Stripe Issuing Accountholders can submit disputes to User. User must immediately submit any disputes User receives to Stripe through the Stripe API or the Stripe Dashboard.
User must not interfere with any Stripe Issuing Accountholder’s ability to dispute a Card Transaction.
Qualifications & exceptions
The User chooses between the form and its own channel but must forward disputes immediately either way.
Charges & Financial Obligations · Company practice
Open-amount purchases place a hold on your balance for the estimated amount until released or finalized
When a Card is used for a purchase whose final amount is unknown at authorization (for example, an open-amount authorization), Stripe may place a hold on available funds in the Stripe Issuing Account for the estimated amount the User, or someone acting for the User, authorized. Held funds cannot be used for anything else until the merchant or the Card Network releases the hold, or until Stripe receives the final amount or the final payment order. The hold is a possibility (Stripe 'may' place it), and the terms do not state how long a hold can last.
Supporting quotations
When a Card is used to initiate a Card Transaction where the final amount of the Card Transaction is unknown at the time of authorization, a hold may be placed on available funds in the Stripe Issuing Account for an estimated amount of the Card Transaction as authorized by (or on behalf of) User. The funds subject to the hold will not be available to User for any other purpose until the merchant or the Card Network releases the hold, or until Stripe receives the final amount of the Card Transaction or receives the final payment order.
Qualifications & exceptions
Applies only where the final amount is unknown at the time of authorization.
The hold is for an estimated amount, not necessarily the final amount.
Not stated here
The terms give no maximum duration for a hold.
Charges & Financial Obligations · Company practice
Stripe deducts a Card Transaction immediately and settles it to the Card Network net of fees and amounts you owe
Stripe treats a Card Transaction as received when the Card Network sends its settlement instruction, and deducts the amount from the Stripe Issuing Account balance as soon as the transaction is made. Stripe then settles Card Transactions to the relevant Card Network, net of fees and any amounts the User owes Stripe, within the time frame the settlement rules require. The terms do not say which fees or amounts owed are netted or what the required time frame is.
Supporting quotations
Stripe receives a Card Transaction at the time Stripe receives the Card Transaction settlement instruction from the relevant Card Network. Stripe will deduct the amount of a Card Transaction from the balance of the Stripe Issuing Account as soon as the Card Transaction is made.
5.5 Card Transaction Settlement.
Stripe will settle Card Transactions, net of fees and amounts owed to Stripe, to the relevant Card Network within the required settlement time frame.
Qualifications & exceptions
Settlement is net of fees and amounts owed to Stripe.
Settlement time frame is whatever is 'required', not a fixed period stated here.
Not stated here
The settlement time frame and the fees netted are not stated in these terms.
Charges & Financial Obligations · Company practice
Short on a Supported Currency, Stripe converts from your default currency; Card Network conversions add an FX fee
Card Transactions in a Supported Currency (one Stripe tells the User it supports) are processed in that currency. If the User's balance in it is insufficient but the default-currency balance suffices, Stripe converts the transaction into the default currency to complete it, at an exchange rate determined as the Documentation states; any quoted amounts and fees involving conversion are estimates that may change with the rate at conversion time. If a Card Network performs the conversion, the amount is converted at that network's reference rate at clearing time and a foreign exchange fee applies; the networks publish their reference rates and a comparison to European Central Bank rates. When paying in a currency other than a Supported Currency, the applicable rate is shown at the time of the transaction.
Supporting quotations
5.6 Currency Conversions.
If a Card Transaction is in a Supported Currency, Stripe will process the Card Transaction in the applicable Supported Currency. If User’s balance in the applicable Supported Currency is insufficient to complete the Card Transaction, and User has a sufficient balance available in User’s default currency, Stripe will convert the Card Transaction from the Supported Currency to User’s default currency to complete the Card Transaction. If a requested Card Transaction requires a currency conversion, then the exchange rate used for that conversion will be determined as stated in the Documentation. Where currency conversion is part of a Card Transaction, any quoted payout amounts and associated fees are estimates, and may fluctuate based on changes in the exchange rate that applies when the currency conversion takes place.
If a Card Network completes a currency conversion, the amount payable will be converted at the relevant Card Network's reference exchange rate at the clearing time of the Card Transaction, and a foreign exchange fee will apply.
When paying in a currency other than a Supported Currency, the applicable exchange rate will be shown at the time of the Card Transaction.
“Supported Currency” means a currency supported under the Stripe Issuing Accountholder Services as communicated to User by Stripe.
Qualifications & exceptions
Quoted amounts and fees involving a conversion are estimates.
The foreign exchange fee amount is not stated in these terms.
Not stated here
Stripe's own conversion rate is set 'as stated in the Documentation', which is external.
Charges & Financial Obligations · User right or choice
You may claim a refund for an unexpectedly large open-amount charge within 8 weeks, unless the amount was known ahead
The User may request a refund for a Card Transaction whose authorization did not specify the exact amount, where the merchant charged more than the User could reasonably have expected given normal spending patterns on the Card or the circumstances. The claim is not accepted if the amount was made available to the User at least 4 weeks before the transaction date, or if the claim is made more than 8 weeks after the transaction was debited from the Stripe Issuing Account.
Supporting quotations
5.7 Refunds.
User may submit a refund request in relation to Card Transactions where the authorization did not specify the exact amount of the Card Transaction at the time of authorization and the amount charged by the merchant is more than User could reasonably have expected taking into account normal spending patterns on the Card or the circumstances of the Card Transaction. A claim for a refund in these circumstances will not be accepted if the amount of the Card Transaction was made available to User at least 4 weeks before the Card Transaction date, or if the claim is made more than 8 weeks after the Card Transaction was debited from the Stripe Issuing Account.
Qualifications & exceptions
Only for transactions authorized without an exact amount.
Barred if the amount was disclosed 4 weeks ahead or the claim is later than 8 weeks after debit.
Account & Service Control · Company commitment
You get monthly statements through Stripe Technology and must review them and report problems without undue delay
Stripe, or the User's Platform Provider where applicable, provides the Stripe Issuing Account balance and a statement of Card Transactions through the Stripe Technology, and the User can access and download monthly statements there. Statements show information identifying each transaction and, where appropriate, the payee; the amount in the currency paid; the charges; where applicable the actual exchange rate applied; and the authorization or posting date. The User must regularly and carefully review its transactions to spot unauthorized or incorrectly executed ones and, where appropriate, notify Stripe without undue delay under the Agreement.
Supporting quotations
5.8 Card Transaction information.
Stripe (or, if applicable, User’s Platform Provider) will, through the Stripe Technology, provide User with the Stripe Issuing Account balance and a statement of Card Transactions. User will be able to access and download monthly Card Transaction statements via the Stripe Technology (or, if applicable, from User’s Platform Provider). The Card Transaction statements will show (a) information related to each Card Transaction which will enable it to be identified and, where appropriate, information on the payee; (b) the amount of the Card Transaction shown in the currency in which the Card Transaction was paid; (c) the amount of charges for the Card Transaction; (d) where applicable, the actual exchange rate applied to the Card Transaction; and (e) the date the Card Transaction is authorized on or posted to the Stripe Issuing Account. User must carefully review its Card Transactions on a regular basis to identify unauthorized or incorrectly executed transactions and, where appropriate, notify Stripe without undue delay in accordance with the terms of this Agreement if an unauthorized or incorrectly executed transaction has occurred.
Charges & Financial Obligations · Company practice
Loaded funds are held by Stripe PSP on your behalf and safeguarded under Law, but are not deposits and earn no interest
The User may load funds at par value onto the Stripe Issuing Account through the Stripe Technology using the funding mechanisms Stripe makes available. All funds in the account are safeguarded by Stripe PSP (Stripe Technology Europe, Limited for the EEA or Stripe Payments UK Ltd for the UK, the additional party providing Regulated Financial Services) in compliance with Law. The User acknowledges that the funds are held by Stripe PSP on its behalf, are not deposits, and earn no interest.
Supporting quotations
6. Loading and Redeeming Funds.
6.1 Loading Funds.
User may load funds at par value onto the Stripe Issuing Account using the Stripe Technology via the funding mechanisms Stripe makes available. All funds in the Stripe Issuing Account are safeguarded by Stripe PSP in compliance with Law. User acknowledges and agrees that funds in the Stripe Issuing Account are held by Stripe PSP on User’s behalf and are not deposits. User will not earn any interest on any funds held in the Stripe Issuing Account.
Stripe Technology Europe, Limited (“Stripe PSP”) is an additional party to this Agreement solely for the purposes of (a) providing Regulated Financial Services; and (b) acting as a Payment Method Acquirer.
Stripe Payments UK Ltd (“Stripe PSP”) is an additional party to this Agreement solely for the purposes of (a) providing Regulated Financial Services; and (b) acting as a Payment Method Acquirer.
Qualifications & exceptions
Funds are safeguarded, not deposit-protected, and earn no interest.
Security & Safeguards · Restriction or exception
You must cancel a lost, stolen or compromised Card immediately; a dispute alone does not cancel it
If a Card is lost or stolen, or an accountholder tells the User that transactions on a Card are fraudulent or unauthorized, the User must immediately cancel the affected Card through the Stripe API or Dashboard. Disputing a fraudulent or unauthorized transaction does not cancel the Card. If the User does not cancel a compromised Card this way, the User may bear additional liability; the terms do not say how much.
Supporting quotations
11.2 Reporting Unauthorized Transactions.
If a Card is lost or stolen, or a Stripe Issuing Accountholder informs User that there are fraudulent or unauthorized transactions on a Card, User must immediately cancel the affected Card through the Stripe API or the Stripe Dashboard. Disputing a fraudulent or unauthorized Card Transaction will not cancel a Card. If User fails to cancel a compromised Card through the Stripe API or the Stripe Dashboard, User may incur additional liability.
Qualifications & exceptions
Cancellation must be through the Stripe API or the Stripe Dashboard.
Not stated here
The extent of the additional liability is not stated here.
Charges & Financial Obligations · Procedure
Stripe evaluates reported card disputes and credits valid ones; you must abide and cannot pass costs to accountholders
When an accountholder reports an erroneous or unauthorized Card Transaction, Stripe evaluates the information in line with Law. If Stripe or the Card Network decides the dispute is valid or the transaction was erroneous or unauthorized, Stripe credits the amount back to the accountholder's Stripe Issuing Account. The User must abide by the dispute outcome and must not act against it, including by passing on to an accountholder any costs the User incurs from fraudulent or unauthorized transactions.
Supporting quotations
11.3 Reporting Disputed Card Transactions.
When a Stripe Issuing Accountholder submits or reports an erroneous or unauthorized Card Transaction, Stripe will evaluate the submitted information in accordance with Law. If Stripe or the Card Network determines that the dispute is valid or the Card Transaction was erroneous or unauthorized, Stripe will credit the amount of the applicable Card Transaction back to the applicable Stripe Issuing Account. User must abide by the determination of any dispute. User must not perform any act or omission that conflicts with Stripe or the Card Network’s determination of a dispute, including by passing through any costs User incurs resulting from fraudulent or unauthorized Card Transactions to a Stripe Issuing Accountholder.
Qualifications & exceptions
Either Stripe's or the Card Network's determination can make the dispute valid.
Security & Safeguards · Restriction or exception
You and your service providers must comply with PCI Standards and share assessment results on request
The User must comply with the PCI Standards, and must make sure its service providers that store, access or transmit Personal Data comply too. When Stripe asks, the User must verify that its implementation of the Stripe Issuing Program meets the PCI Standards and promptly give Stripe its most recent assessment results.
Supporting quotations
12. PCI Compliance.
User must, and User must ensure that User’s service providers that store, access or transmit Personal Data, comply with the PCI Standards. Upon Stripe’s request, User must verify that User’s implementation of the Stripe Issuing Program complies with the PCI Standards and promptly provide the most recent assessment results to Stripe.
Qualifications & exceptions
Verification and results are due on Stripe's request, with results needed promptly.
Legal Rights & Agreement Rules · Restriction or exception
You indemnify Stripe for accountholders' use of the card services and for all unauthorized or disputed Card Transactions
The User will indemnify the Stripe Parties against all Stripe Losses arising from (a) accountholders' and authorized users' use of the Stripe Issuing Accountholder Services, including their acts or omissions, and (b) all unauthorized or disputed Card Transactions. Stripe Losses are the amounts awarded to a third party making a Claim, plus penalties, fines and third-party costs, including legal fees, that the Stripe Parties pay.
Supporting quotations
13. Indemnification.
User will indemnify the Stripe Parties against all Stripe Losses arising out of or relating to (a) the Stripe Issuing Accountholders’ and Issuing Authorized Users’ use of the Stripe Issuing Accountholder Services, including any Stripe Issuing Accountholder’s or Issuing Authorized User’s act or omission related to the Stripe Issuing Accountholder Services; and (b) all unauthorized or disputed Card Transactions.
“Stripe Losses” means all amounts awarded to the third party making a Claim, and all penalties, fines, and third-party costs (including legal fees) paid by the Stripe Parties.
Qualifications & exceptions
Covers both accountholders' own acts or omissions and unauthorized or disputed Card Transactions.
Not stated here
Whether any cap applies is not stated in this clause.
Legal Rights & Agreement Rules · Permission or license
Stripe may act if you charge improper fees, have excessive fraud, fail to cancel cards, miss PCI or breach rules
Stripe may use the remedies in Section 14.3 if it determines that a User Entity (a) charges accountholders unauthorized or noncompliant fees, (b) has excessive unauthorized Card Transactions, (c) fails to cancel a lost, stolen or fraud-reported Card as required, (g) has breached or is likely to breach, or is likely to cause Stripe to breach, this Agreement, another Stripe services agreement or the applicable Financial Provider Terms, (h) has violated or is likely to violate Law or Financial Provider Terms, (i) has caused or is likely to cause Stripe to violate them, or (n) fails, or its service providers fail, to meet PCI Standards. Several triggers apply to likely future conduct, and the decision is Stripe's.
Supporting quotations
14.1 Stripe Remedies - Specific Triggers.
Without limiting Stripe’s other rights or remedies under this Agreement, Stripe may exercise any one or more of the remedies stated in Section 14.3 of these Stripe Issuing Platform Terms if Stripe determines that a User Entity:
(a) is charging Stripe Issuing Accountholders for unauthorized or noncompliant fees in connection with the Stripe Issuing Platform Services;
(b) has experienced excessive unauthorized Card Transactions;
(c) fails to immediately cancel a lost or stolen Card, or fails to cancel a Card with reported fraudulent or unauthorized transactions in the manner described in the Issuing Bank Terms;
(g) has breached or is likely to breach, or has caused or is likely to cause Stripe to breach, this Agreement (or any other Stripe services agreement with a Stripe Entity) or the Financial Provider Terms applicable to the User Entity’s use of the Services;
(h) has violated or is likely to violate Law or Financial Provider Terms;
(i) has caused or is likely to cause Stripe to violate Law or Financial Provider Terms;
(n) fails, or its service providers fail, to comply with PCI Standards.
Qualifications & exceptions
Each trigger depends on Stripe's own determination.
Several triggers apply when conduct is merely likely, not yet occurred.
Remedies are in addition to Stripe's other rights.
Not stated here
The terms do not define how many unauthorized transactions count as excessive.
Legal Rights & Agreement Rules · Permission or license
Stripe may act if you face insolvency, owe Stripe, change control or business model, or present unacceptable risk
Stripe may use the remedies in Section 14.3 if it determines that a User Entity (d) is or is likely to become subject to an Insolvency Event, (e) has a negative Stripe Account Balance or owes liability to Stripe or its Affiliates, (f) has experienced or is likely to experience a deterioration in business or financial condition Stripe considers material, (j) has experienced or is likely to experience a Change of Control, (k) has changed its business model without Stripe's prior consent, exposing Stripe to increased risk, (l) has acted or traded in a way that presents an unacceptable risk, or (m) is required to indemnify Stripe under the Agreement.
Supporting quotations
Without limiting Stripe’s other rights or remedies under this Agreement, Stripe may exercise any one or more of the remedies stated in Section 14.3 of these Stripe Issuing Platform Terms if Stripe determines that a User Entity:
(d) is or is likely to become the subject of an Insolvency Event;
(e) has a negative Stripe Account Balance, or owe liability to Stripe or any of its Affiliates;
(f) has experienced or is likely to experience a deterioration of its business or financial condition that Stripe considers to be material;
(j) has experienced or is likely to experience a Change of Control;
(k) has, without Stripe’s prior consent, changed its business model (including services supplied by a User Entity to its customers), exposing Stripe to increased risk;
(l) has acted in a manner or engaged in business, trading practice or other activity that presents an unacceptable risk;
(m) is required to indemnify Stripe under this Agreement; or
Qualifications & exceptions
Each trigger depends on Stripe's own determination.
Several triggers apply when the event is merely likely, not yet occurred.
A business model change triggers only if made without Stripe's prior consent and it increases Stripe's risk.
Not stated here
What counts as an unacceptable risk is not defined in this clause.
Legal Rights & Agreement Rules · Permission or license
Stripe may also use those remedies if it expects post-termination losses, or if Law requires
Stripe may also use the Section 14.3 remedies if it reasonably determines it may incur losses from credit, fraud, criminal activity or other risks associated with a User Entity after the Issuing Platform Terms end, or if Law requires.
Supporting quotations
14.2 Stripe Remedies - General Trigger.
Without limiting Stripe’s other rights or remedies under this Agreement, Stripe also may exercise any or all of the remedies stated in Section 14.3 of these Stripe Issuing Platform Terms if (a) Stripe reasonably determines that Stripe may incur losses resulting from credit, fraud, criminal activity or other risks associated with a User Entity after these Stripe Issuing Platform Terms terminate; or (b) Law requires.
Qualifications & exceptions
Stripe's determination must be reasonable.
Charges & Financial Obligations · Permission or license
Remedies include a Reserve, suspending card activity, requiring a guarantee and debiting bank accounts
Once a trigger in Section 14.1 or 14.2 (or another provision that refers to these remedies) has occurred, Stripe may: (a) set up, fund and use a Reserve, including enforcing any security interest or lien held for it, without demand, legal process or notice, and apply it toward liabilities the User owes any Stripe Entity; (b) suspend or end the User's ability to submit new applications, or an accountholder's ability to make Card Transactions; (c) require a personal, parent or bank guarantee or letter of credit in a form Stripe finds satisfactory; and (d) debit the User's bank accounts, or those of User Group Entities that have agreements with a Stripe Entity.
Supporting quotations
14.3 Scope.
Without limiting Stripe’s other rights or remedies under this Agreement, if a triggering event in Sections 14.1 or 14.2 of these Stripe Issuing Platform Terms (or any other provision of this Agreement that refers to these remedies) has occurred, then Stripe may:
(a) establish, fund, use, and apply a Reserve, which may include enforcing or drawing down upon, without demand, legal process, or notice of any kind, any security interest or lien held by Stripe in respect of the Reserve, by applying the Reserve funds toward settlement of any liabilities owed by User to any Stripe Entity;
(b) suspend or terminate User’s ability to submit new applications, or Stripe Issuing Accountholder’s ability to make Card Transactions;
(c) require User to provide a guarantee (including a personal, parent, or bank guarantee) or letter of credit in a form and substance that satisfies Stripe;
(d) debit the User Bank Accounts or the bank or financial institution accounts of any or all User Group Entities that have entered into an agreement with a Stripe Entity under which a Stripe Entity provides services; and
Qualifications & exceptions
Available only after a listed trigger has occurred.
Reserve enforcement can happen without demand, legal process or notice.
Not stated here
The size of any Reserve is not stated here.
Charges & Financial Obligations · Permission or license
Stripe may debit your and group entities' bank accounts and set off or recoup amounts owed against amounts it owes
Among the remedies Stripe may use after a trigger event, it may (d) debit the User's bank accounts, or those of any or all User Group Entities that have an agreement under which a Stripe Entity provides services, and (e) set off or recoup any amounts Stripe reasonably determines a User Entity owes a Stripe Entity under this or another agreement against any amounts a Stripe Entity owes a User Entity, whether those amounts are matured or unmatured, liquidated or unliquidated.
Supporting quotations
(d) debit the User Bank Accounts or the bank or financial institution accounts of any or all User Group Entities that have entered into an agreement with a Stripe Entity under which a Stripe Entity provides services; and
(e) setoff or recoup all amounts that Stripe reasonably determines a User Entity owes to a Stripe Entity under this Agreement or another agreement, against any amounts that a Stripe Entity owes to a User Entity whether the amounts owed are matured, unmatured, liquidated, or unliquidated.
Qualifications & exceptions
Available only once a listed trigger event has occurred.
Set-off needs Stripe's reasonable determination that the amount is owed.
Set-off reaches amounts owed under this agreement or another agreement.
Not stated here
The terms do not say whether Stripe gives notice before debiting or setting off.
Legal Rights & Agreement Rules · Context
Several card terms are defined only by reference to the Issuing Bank's own terms
“Card”, “Card Program Terms”, “Card Transaction”, “Issuing Authorized User” and “Issuing Authorized User Terms” are not defined in this document: each has the meaning given in the applicable Issuing Bank Terms, which are the Issuing Bank's own Financial Provider Terms governing the User's participation in the Stripe Issuing Program. Those bank terms are not part of this saved document.
Supporting quotations
“Card” has the meaning given to it in the applicable Issuing Bank Terms.
“Card Program Terms” has the meaning given to it in the applicable Issuing Bank Terms.
“Card Transaction” has the meaning given in the applicable Issuing Bank Terms.
“Issuing Authorized User” has the meaning given to it in the applicable Issuing Bank Terms.
“Issuing Authorized User Terms” has the meaning given to it in the applicable Issuing Bank Terms.
“Issuing Bank Terms” means the applicable Issuing Bank’s Financial Provider Terms that govern User’s participation in the applicable Stripe Issuing Program.
Qualifications & exceptions
The meaning depends on the applicable Issuing Bank Terms.
Not stated here
The Issuing Bank Terms are not supplied, so these five terms' full meaning is unknown from this document.
Legal Rights & Agreement Rules · Context
Definitions: the Issuing Bank, the Issuing Program, the accountholder and the platform and accountholder services
The Issuing Bank is the Financial Provider named in the Issuing Bank Terms that issues a Card. The Stripe Issuing Program is the card issuing program and services Stripe and its Affiliates make available to accountholders through the Issuing Bank. A Stripe Issuing Accountholder is a business or organization approved for a Stripe Issuing Account after onboarding, and the Stripe Issuing Account is the account an Issuing Bank maintains for it, including each subaccount. Stripe Issuing Platform Services let the User co-market the accountholder services to its Platform Users and give accountholders access to them; Stripe Issuing Accountholder Services are what Stripe and its Affiliates provide to accountholders on behalf of Issuing Banks (bank integration, Card access, spend management and other services). Stripe Issuing Services covers both. The Administrator is the individual an accountholder appoints to manage its participation, and SPC is Stripe Payments Company, a Stripe Affiliate.
Supporting quotations
“Issuing Bank” means the Financial Provider, identified in the Issuing Bank Terms for the applicable Stripe Issuing Program, that issues a Card.
“Stripe Issuing Administrator” or “Administrator” means the individual that a Stripe Issuing Accountholder appoints to manage its participation in the Stripe Issuing Program.
“Stripe Issuing Program” means a Card issuing program and services that Stripe and its Affiliates, via Issuing Bank, make available to Stripe Issuing Accountholders, together with the Stripe Issuing Accountholder Services.
“Stripe Issuing Platform Services” means the Services that allow User to co-market the Stripe Issuing Accountholder Services to User’s Platform Users and provide access to the Stripe Issuing Accountholder Services to Stripe Issuing Accountholders.
“Stripe Issuing Services” means the Stripe Issuing Accountholder Services and Stripe Issuing Platform Services.
“SPC” means Stripe Payments Company, which is a Stripe Affiliate.
“Stripe Issuing Account” means the account an Issuing Bank maintains for a Stripe Issuing Accountholder, and each subaccount to that account.
“Stripe Issuing Accountholder” means a business or organization that has successfully completed the onboarding requirements described in the Stripe Issuing Accountholder Terms and been approved for a Stripe Issuing Account.
“Stripe Issuing Accountholder Services” means Services that Stripe and its Affiliates make available to Stripe Issuing Accountholders, on behalf of Issuing Banks, and related Stripe services, including (a) integration with Issuing Banks; (b) providing Stripe Issuing Accountholders with access to Cards; (c) enabling Stripe Issuing Accountholders to manage Card spend; and (d) other services described in the Stripe Issuing Accountholder Terms.
Legal Rights & Agreement Rules · Context
Definitions: Card Network (Visa, Mastercard, American Express, Discover) and Card Network Rules
A Card Network is a payment card network, including those run by Visa, Mastercard, American Express and Discover. Card Network Rules are the Payment Method Rules a Card Network publishes. The word “including” means the list of networks is not exhaustive.
Supporting quotations
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
“Card Network Rules” means the Payment Method Rules published by a Card Network.
Qualifications & exceptions
The named networks are examples, not a complete list.
Not stated here
The Card Network Rules themselves are published by the networks and are not in this document.
Legal Rights & Agreement Rules · Context
Definitions: Connected Account, Platform Services and Principal Owner (25% or more equity)
A Connected Account is either a Platform User with a Stripe Account onboarded to a Stripe Connect Platform through the Stripe Connect Services, or a Payout Recipient. Platform Services are the products and services Platform Users receive from a Stripe Connect Platform, whether or not fees are charged (for example web development, customer support or hosting). A Principal Owner of a legal entity is an individual who directly or indirectly, through any contract, arrangement, understanding or relationship, owns at least 25% of its equity.
Supporting quotations
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
“Platform Services” means the products and services that Platform Users receive from a Stripe Connect Platform, regardless of whether fees are charged (e.g., web development, customer support or hosting services).
“Principal Owner” means, with respect to a legal entity, an individual who directly or indirectly, through any contract, arrangement, understanding, relationship, or otherwise, owns at least 25% of the equity interests of the legal entity.
Qualifications & exceptions
Principal Owner counts indirect ownership as well as direct.
Legal Rights & Agreement Rules · Context
Definitions: the Disputes API Form and what counts as an Issuing Complaint
The Disputes API Form is an electronic form that lets the User and its Connected Accounts submit Card Transaction disputes to Stripe. An Issuing Complaint is any expression of dissatisfaction with a product, service, policy or employee related to a Stripe Issuing Program, a deliberately broad definition.
Supporting quotations
“Disputes API Form” means an electronic form that enables User and User’s Connected Accounts to submit Card Transaction disputes to Stripe.
“Issuing Complaint” means any expression of dissatisfaction with a product, service, policy, or employee related to a Stripe Issuing Program.
Qualifications & exceptions
An Issuing Complaint needs no formal wording; any expression of dissatisfaction related to a Stripe Issuing Program counts.
Legal Rights & Agreement Rules · Context
Definitions: FCRA (two Acts, both cited as 15 U.S.C. Section 1681), IRS and Tax Information Report
“FCRA” is defined as the Fair Credit Reporting Act and the Equal Credit Opportunity Act, and the source cites the same “15 U.S.C. Section 1681, et seq.” for both. This explanation reports the citation as written and does not resolve the law. “IRS” means the Internal Revenue Service. A Tax Information Report is a required tax information return or report, including IRS Form 1099 or any similar form.
Supporting quotations
“FCRA” means Fair Credit Reporting Act, 15 U.S.C. Section 1681, et seq. and Equal Credit Opportunity Act, 15 U.S.C. Section 1681, et seq.
“IRS” means Internal Revenue Service.
“Tax Information Report” means a required tax information return or report, including IRS Form 1099, or any other similar form.
Qualifications & exceptions
The FCRA definition covers two named Acts but gives one identical citation for both, as written in the source.
Not stated here
The cited statute is not supplied; the repeated citation is left as written.
Content & IP Rights · Context
Definition: User Materials covers marks on Cards and all other materials you give Stripe for the Issuing Programs
“User Materials” means (a) all Marks or other materials that the User or an accountholder wants placed on Cards, and (b) all other materials the User provides to Stripe for the Stripe Issuing Programs. The definition is broad: it is not limited to logos on Cards.
Supporting quotations
“User Materials” means (a) all Marks or other materials that User or a Stripe Issuing Accountholder wish to place on Cards; or (b) all other materials that User provides to Stripe for the purposes of the Stripe Issuing Programs.
Qualifications & exceptions
Includes materials the accountholder wishes to place on Cards, not only materials from the User.
Security & Safeguards · Context
Advanced Fraud Tools Terms supplement the General Terms (last modified July 20, 2026)
These Advanced Fraud Tools Terms, last modified July 20, 2026, supplement the General Terms and govern the User's use of the Advanced Fraud Tools Services and the Advanced Fraud Tools Data. Capitalized terms not defined here take their meaning from the General Terms and, where they apply, the Stripe Issuing Platform Services Terms and Stripe Issuing Accountholder Services Terms. The services are tools designed to help the User detect and evaluate the risk that a Card Transaction Authorization or related activity is fraudulent, and information about them is available through the Stripe Dashboard or as Stripe otherwise makes it available. The data is the risk scores, levels, rates, assessments and alerts the User receives, plus all other data it receives through the services.
Supporting quotations
Last modified: July 20, 2026
These terms (“Advanced Fraud Tools Terms”) supplement the General Terms and govern the use of the Advanced Fraud Tools Services and the Advanced Fraud Tools Data. Capitalized terms that are not defined in these terms have the same meanings given to them in the General Terms, and as applicable, the Stripe Issuing Platform Services Terms and Stripe Issuing Accountholder Services Terms. User may access information regarding the Advanced Fraud Tools Services via the Stripe Dashboard, or as Stripe may otherwise make available to User.
“Advanced Fraud Tools Services” means the Services that are designed to enable User to detect and evaluate the risk that a Card Transaction Authorization or other related activity is fraudulent, and may, at User’s option, include:
“Advanced Fraud Tools Data” means Authorization Risk Scores, Card Testing Risk Levels, Merchant Dispute Rates, Fraud Disputability Assessments, Compromised Card Alerts, and all other data User receives through the Advanced Fraud Tools Services.
Qualifications & exceptions
Defined terms fall back to the General Terms and the Issuing Platform and Accountholder Services Terms.
Not stated here
The optional features listed under the Advanced Fraud Tools Services definition continue beyond this section.
Security & Safeguards · Restriction or exception
You may use the fraud tools and data only to detect and block fraud and unauthorized card authorizations
The User may use the Advanced Fraud Tools Services and Data solely to help detect and block actual or potential fraud and unauthorized Card Transaction Authorizations, in connection with the User's use of the Services or with its card transactions processed through a Third-Party Service.
Supporting quotations
2. Permitted Use.
User may use the Advanced Fraud Tools Services and Advanced Fraud Tools Data solely to help detect and block actual or potential fraud and unauthorized Card Transaction Authorizations, in each case, in connection with User’s use of the Services or User’s card transactions processed via a Third-Party Service.
Qualifications & exceptions
Use is limited to fraud detection and blocking.
Covers the User's use of the Services and card transactions processed through a Third-Party Service.
Use & Processing · Restriction or exception
You must use the fraud tools data under Stripe's Privacy Policy and keep personal data you provide accurate and complete
The User must use Advanced Fraud Tools Data only in accordance with Stripe's Privacy Policy, and must use reasonable efforts to make sure all Personal Data it provides to Stripe is accurate and complete. The Privacy Policy is a linked document that is not part of this saved text.
Supporting quotations
3.1 Privacy Policy.
User must only use Advanced Fraud Tools Data in accordance with [Stripe’s Privacy Policy](https://stripe.com/privacy).
3.2 Personal Data.
User must use reasonable efforts to ensure that all Personal Data that User provides to Stripe is accurate and complete.
Qualifications & exceptions
Accuracy duty is a reasonable-efforts standard.
Not stated here
The content of Stripe's Privacy Policy is not supplied here.
Retention & Deletion · Restriction or exception
Fraud tools data is Stripe Data: you must delete it on termination or on request, unless Law requires you to keep it
Advanced Fraud Tools Data, and any subset of it, is Stripe Data under the Agreement. The User must promptly delete or destroy all of it in its possession or control (a) when these terms end or (b) at any time Stripe asks. The User may keep copies only to the extent Law requires, and then may use them only to comply with Law.
Supporting quotations
3.3 Advanced Fraud Tools Data.
Advanced Fraud Tools Data, and any subset thereof, is Stripe Data for the purposes of this Agreement. User will promptly delete or destroy all Advanced Fraud Tools Data in User’s possession or control received in connection with the Advanced Fraud Tools Services (a) upon termination of these Advanced Fraud Tools Terms; or (b) at any time upon Stripe’s request. However, in each case User may retain copies of the Advanced Fraud Tools Data to the extent Law requires, so long as User uses the Advanced Fraud Tools Data only to comply with Law.
“Advanced Fraud Tools Data” means Authorization Risk Scores, Card Testing Risk Levels, Merchant Dispute Rates, Fraud Disputability Assessments, Compromised Card Alerts, and all other data User receives through the Advanced Fraud Tools Services.
Qualifications & exceptions
The retention exception applies only to the extent Law requires it.
Retained copies may be used only to comply with Law.
Use & Processing · Restriction or exception
No use of the fraud tools for credit, insurance, housing or employment decisions, discrimination or adverse action
The User must not, and must not let any third party, use the Advanced Fraud Tools Services or Data (a) as a factor in deciding anyone's eligibility for credit, insurance, housing or employment, or in a way that could make Stripe a consumer reporting agency or make the data a consumer report under the FCRA (if applicable); or (e) to discriminate on race, gender or other protected characteristics, or to take any adverse action as the FCRA describes it (if applicable).
Supporting quotations
User must not, and must not enable or allow any third party, to:
(a) use the Advanced Fraud Tools Services or Advanced Fraud Tools Data as a factor in determining any person’s eligibility for credit, insurance, housing or employment, or in any way that could cause Stripe to be a “consumer reporting agency” or cause any part of the Advanced Fraud Tools Data to constitute a “consumer report,” as each term is described in the FCRA (if applicable);
(e) use the Advanced Fraud Tools Services or Advanced Fraud Tools Data to discriminate based on race, gender, or other protected characteristics, or take any “adverse action” as that term is described in the FCRA (if applicable);
Qualifications & exceptions
The FCRA references apply only if the FCRA applies.
The ban reaches third parties the User enables or allows.
Sharing & Disclosure · Restriction or exception
You may not sell, share, disclose, download or store the fraud tools data
The User must not, and must not let a third party, (b) sell, rent, transfer, make available or communicate Advanced Fraud Tools Data orally or by other means, with “sell” as the CCPA defines it, or (c) disclose, download or store the data. Disclosure is allowed where Law requires it.
Supporting quotations
User must not, and must not enable or allow any third party, to:
(b) sell, rent, transfer, make available, or communicate orally or through other means Advanced Fraud Tools Data (including as the term “sell” is defined in the CCPA);
(c) disclose (except as Law requires), download, or store the Advanced Fraud Tools Data;
Qualifications & exceptions
Disclosure is permitted where Law requires it.
The ban reaches third parties the User enables or allows.
Not stated here
The store ban sits alongside a deletion duty and a Law-required retention exception; the terms do not say how to reconcile storing with a retained copy beyond those two clauses.
Use & Processing · Restriction or exception
No building competing models or products, training your own products, or evaluating outside transactions
The User must not, and must not let a third party, (d) use the Advanced Fraud Tools Services or Data to validate, train, enhance or deploy machine learning models or algorithms derived from, a substitute for, or substantially similar to the services, or to develop or commercially offer any security or fraud detection product or service; (f) except as Section 2 allows, use them to evaluate transactions not processed through the Services; or (g) use the services provided to train or improve the User's own products and services. Section 2 allows use for card transactions processed through a Third-Party Service.
Supporting quotations
User must not, and must not enable or allow any third party, to:
(d) use the Advanced Fraud Tools Services or Advanced Fraud Tools Data to (i) validate, train, enhance or deploy any machine learning models or algorithms that are derived from, a substitute for, or substantially similar to, the Advanced Fraud Tools Services; or (ii) directly or indirectly develop or otherwise make available on a commercial basis any security or fraud detection product or service;
(f) except as allowed under Section 2 of these Issuing Fraud Tools Services Terms, use the Advanced Fraud Tools Services or Advanced Fraud Tools Data to evaluate transactions not processed through the Services; or
(g) use Advanced Fraud Tools Services provided to train or improve User products and services.
Qualifications & exceptions
The evaluation ban has an exception for what Section 2 allows.
The ban reaches third parties the User enables or allows.
Not stated here
Section 2 is cited as 'these Issuing Fraud Tools Services Terms', a name that differs slightly from 'Advanced Fraud Tools Terms'.
Legal Rights & Agreement Rules · Restriction or exception
You are solely responsible for your use and decisions; added rules may lengthen authorization times
The User is solely responsible for how it uses the Advanced Fraud Tools Services and Data and for the decisions and actions it takes in connection with them. The User also acknowledges that choosing to input and use additional rules with the services may lengthen authorization times for applicable Card Transaction Authorizations.
Supporting quotations
5. Responsibility for Decisions and Disclaimers.
5.1 Responsibility for Decisions.
(a) User is solely responsible for: User’s use of the Advanced Fraud Tools Services and Advanced Fraud Tools Data, as well as the decisions User makes and the actions User takes in connection with the Advanced Fraud Tools Services and Advanced Fraud Tools Data.
(b) User acknowledges that its choice to input and use additional rules with the Advanced Fraud Tools Services may result in longer authorization times for applicable Card Transaction Authorizations.
Qualifications & exceptions
Longer authorization times are a possibility tied to the User's choice to add rules.
Not stated here
The terms give no figure for how much longer authorizations may take.
Use & Processing · Company practice
Fraud scores, levels, rates and alerts are snapshots that do not auto-update
Authorization Risk Scores, Card Testing Risk Levels, Merchant Dispute Rates, Compromised Card Alerts and Fraud Disputability Assessments are based on data available when each is generated and do not automatically update when that data later changes. The Advanced Fraud Tools Services use data from transactions processed through the Services.
Supporting quotations
5.2 Disclaimers.
(a) Authorization Risk Scores, Card Testing Risk Levels, Merchant Dispute Rates, Compromised Card Alerts, and Fraud Disputability Assessments are based on data available to the Advanced Fraud Tools Services at the time it is generated, and they do not auto-update to reflect any subsequent changes to that data.
(b) The Advanced Fraud Tools Services use data from transactions processed through the Services.
Qualifications & exceptions
Outputs reflect the data available at the time they are generated.
Not stated here
The terms do not say how often outputs are regenerated.
Legal Rights & Agreement Rules · Restriction or exception
Fraud data is not advice and guarantees nothing; Stripe disclaims liability for fraud, blocked sales and score errors
The Advanced Fraud Tools Data is not legal or compliance advice, or advice on whether to go ahead with a transaction with another person. Using the services or data does not guarantee prevention of fraudulent Card Transaction Authorizations, compromised Cards, Card Testing Attacks or other fraud. Stripe is not liable for losses, damages or costs arising from (a) unauthorized transactions, compromised Cards, Card Testing Attacks and other fraud; (b) non-fraudulent transactions the services may block; or (c) the accuracy of the scores and other data, and any action the User or Stripe takes based on them.
Supporting quotations
(c) The Advanced Fraud Tools Data does not constitute legal or compliance advice, or advice as to whether User should proceed with a transaction with another person.
(d) User’s use of the Advanced Fraud Tools Services or the Advanced Fraud Tools Data does not guarantee the prevention of fraudulent Card Transaction Authorizations, compromised Cards, Card Testing Attacks, or other fraudulent activity. Stripe is not liable for any losses, damages, or costs arising out of or relating to (a) unauthorized transactions, compromised Cards, Card Testing Attacks, and other fraudulent activity; (b) non-fraudulent transactions that may be blocked by the Advanced Fraud Tools Services; or (c) the accuracy of the Authorization Risk Scores and other Advanced Fraud Tools Data, and any actions that User or Stripe may take based on the Authorization Risk Scores and other Advanced Fraud Tools Data.
Qualifications & exceptions
The liability disclaimer covers actions taken by either the User or Stripe based on the scores.
Not stated here
Whether other parts of the Agreement limit or restore any of these disclaimers is not stated here.
Security & Safeguards · Company practice
Fraud tools services may include risk scores, compromised card alerts, analytics, SMS verifications and other features
The Advanced Fraud Tools Services are Services designed to help the User detect and evaluate the risk that a Card Transaction Authorization or related activity is fraudulent. At the User's option they may include (a) an Authorization Risk Score, Card Testing Risk Level, Merchant Dispute Rate and Fraud Disputability Assessment for each authorization; (b) Compromised Card Alerts; (c) extra data, analytics and fraud indicators through the Stripe API and Dashboard, such as risk characteristic reports and anomalous spend alerts; (d) SMS fraud alert verifications; and (e) other fraud detection features Stripe may make available.
Supporting quotations
“Advanced Fraud Tools Services” means the Services that are designed to enable User to detect and evaluate the risk that a Card Transaction Authorization or other related activity is fraudulent, and may, at User’s option, include:
(a) access to an Authorization Risk Score, Card Testing Risk Level, Merchant Dispute Rate, and Fraud Disputability Assessment for each Card Transaction Authorization;
(b) Compromised Card Alerts for potentially compromised cards;
(c) access to additional data, analytics, and indicators of fraud via the Stripe API and Stripe Dashboard, including Card Transaction Authorization risk characteristic reports, anomalous spend alerts, and other supplemental fraud and risk data;
(d) access to SMS fraud alert verifications; and
(e) access to other fraud detection features and capabilities that Stripe may make available to User.
Qualifications & exceptions
The features are available at the User's option.
Item (e) covers other features only as Stripe may make them available.
Not stated here
Which features the User actually receives is not stated; it depends on what Stripe makes available.
Use & Processing · Context
Definitions: fraud risk scores, levels, rates, assessments and alerts
Advanced Fraud Tools Data is the scores, levels, rates, assessments and alerts below plus all other data the User receives through the services. An Authorization Risk Score is a risk score or level for a Card Transaction Authorization based on Stripe Data, including the Merchant Dispute Rate and Card Testing Risk Level. A Card Testing Risk Level is the likelihood an authorization is or will be affected by Card Testing Attacks. A Merchant Dispute Rate assesses the historical dispute rate of a merchant's Transactions for the period Stripe has provided Stripe Payments Services to that merchant. A Fraud Disputability Assessment is the likelihood an authorization can be disputed if fraud occurs. A Compromised Card Alert is a notification that a card may have been compromised by a Card Testing Attack.
Supporting quotations
“Advanced Fraud Tools Data” means Authorization Risk Scores, Card Testing Risk Levels, Merchant Dispute Rates, Fraud Disputability Assessments, Compromised Card Alerts, and all other data User receives through the Advanced Fraud Tools Services.
“Authorization Risk Score” means a risk score or level associated with a Card Transaction Authorization based on Stripe Data, including the Merchant Dispute Rate and the Card Testing Risk Level.
“Card Testing Risk Level” means the level assigned to a Card Transaction Authorization that represents the likelihood the Card Transaction Authorization is or will be impacted by Card Testing Attacks.
“Fraud Disputability Assessment” means, with respect to a Card Transaction Authorization, an assessment of the likelihood that the Card Transaction Authorization can be disputed in the event of fraud.
“Merchant Dispute Rate” means an assessment of the historical dispute rate of a merchant’s Transactions for the time period during which Stripe has provided Stripe Payments Services to that merchant.
“Compromised Card Alert” means a notification that a card may have been compromised by a Card Testing Attack.
Qualifications & exceptions
The scores are assessments of likelihood, not findings of fact.
Merchant Dispute Rate looks only at the period Stripe has served that merchant.
Not stated here
How the scores and levels are calculated is not stated.
Security & Safeguards · Context
Definitions: Card Testing Attack and Card Transaction Authorization (payments and ATM cash requests)
A Card Testing Attack means repeated fraudulent tests of card account numbers until a valid number is found. A Card Transaction Authorization is an authorization request to make a payment with a card or to get cash at an automatic teller machine (ATM), so the fraud tools cover cash requests as well as purchases.
Supporting quotations
“Card Testing Attack” means repeated fraudulent tests of card account numbers until a valid card account number is found.
“Card Transaction Authorization” means an authorization request to make a payment with a card or obtain cash at an automatic teller machine (ATM).
Account & Service Control · Context
Link Agent Wallet Terms supplement the General Terms; the services are Preview Services (last updated October 2, 2026)
These Link Agent Wallet Terms, last updated October 2, 2026, supplement the General Terms and govern the User's use of the Link Agent Wallet Services. Capitalized terms not defined here take their General Terms meaning. The Link Agent Wallet Services are Preview Services, and they let a User Agentic Agent start Link Transactions for a Mutual End User with the User or third-party merchants. A User Agentic Agent is the User's agentic interface, AI-powered system or product that lets Mutual End Users start (or start on their behalf) a Link Transaction, and a Mutual End User is a Customer with a Link account who authorizes that agent to connect to it.
Supporting quotations
Last updated: October 2, 2026
These terms (“Link Agent Wallet Terms”) supplement the General Terms and govern User’s use of the Link Agent Wallet Services. Capitalized terms that are not defined in these Link Agent Wallet Terms have the same meanings given to them in the General Terms. The Link Agent Wallet Services are Preview Services.
“Link Agent Wallet Services” means the Services that enable User Agentic Agent to initiate Link Transactions on behalf of the Mutual End User with User or third-party merchants.
“User Agentic Agent” means a User agentic interface, artificial intelligence-powered system, or product that enables Mutual End Users to initiate (or initiate on their behalf) a Link Transaction.
“Mutual End User” means a Customer that has a Link account and authorizes User Agentic Agent to connect to Customer’s Link account.
Qualifications & exceptions
The services are Preview Services.
Not stated here
What Preview status changes for the User is set by other parts of the General Terms, not here.
Account & Service Control · Restriction or exception
If you control the Link terms screen, you must ensure end users accept the Link End User Terms and prove it on request
If the User controls how the Link End User Terms are shown to Mutual End Users, then before a Mutual End User uses Link through the Link Agent Wallet Services, the User must ensure the Mutual End User has agreed to those terms, including consenting to Stripe's use of Mutual End User Data. The User must keep a current URL for the terms, give Stripe the proof it requires of consent when asked, and change its acceptance process as Stripe requires if Stripe believes the process does not create a binding agreement between Stripe and each Mutual End User.
Supporting quotations
(a) Mutual End User Experience. If User controls how the Link End User Terms are presented to Mutual End Users, then prior to a Mutual End User using Link through the Link Agent Wallet Services, User will ensure that Mutual End User has agreed to the Link End User Terms, including consenting to Stripe’s use of Mutual End User Data. User will maintain a current URL for the Link End User Terms. At Stripe’s request, User must provide proof as Stripe requires that the Mutual End User has consented to and accepted the Link End User Terms. If Stripe believes that the User’s existing acceptance process does not create a binding agreement between Stripe and each Mutual End User, then, on Stripe’s request, User must modify that process as Stripe requires.
“Link End User Terms” means the terms of service, data policies, and other published terms and policies that govern a Mutual End User’s use of Link, and Stripe’s use of the Mutual End User’s Personal Data or information in connection therewith.
Qualifications & exceptions
Applies only if the User controls how the Link End User Terms are presented.
The duty to change the acceptance process arises on Stripe's belief and request.
Not stated here
The Link End User Terms themselves are not part of this saved text.
Account & Service Control · Restriction or exception
Stripe keeps sole control over Link and you must promptly apply its requested changes to how Link is presented
Stripe keeps sole decision-making authority, responsibility and control over the Services, including Stripe-enabled payment surfaces on Stripe web pages and iframes. The User must promptly make the changes Stripe requests to how Link, including any feature or functionality, is presented or made available to Mutual End Users.
Supporting quotations
(b) Changes. Stripe retains sole decision-making authority, responsibility and control over the Services, including any Stripe-enabled payment surfaces on Stripe web pages, and iframes. User will promptly incorporate changes requested by Stripe with respect to how Link, including any feature or functionality, is presented or made available to Mutual End Users.
Not stated here
The terms set no limit on what changes Stripe may request.
Charges & Financial Obligations · Restriction or exception
If you control approvals, end users must approve spend limits before a Link Transaction and you must document it
If the User controls how a Mutual End User approves the amount of a Link Transaction or sets and approves spend limits, the User must ensure the Mutual End User approves spend limits for one or more Link Transactions before the User Agentic Agent starts them. The User must document the approval details, including the method, give Stripe a copy before the transaction starts, and promptly give Stripe any approval information it requests.
Supporting quotations
(c) Transaction Approval. If User controls how the Mutual End User approves the amount of the Link Transaction or establishes and approves spend limits for one or more Link Transactions, then User will ensure that the Mutual End User approves spend limits for one or more Link Transactions prior to the initiation of the applicable Link Transaction(s) by or through User Agentic Agent. User will document the details of the approval, including the method of approval, and provide a copy of that approval to Stripe prior to the initiation of the Link Transaction. Upon Stripe’s request, User will promptly provide Stripe with necessary approval information in a timely and efficient manner.
“Link Transaction” means a Transaction initiated via User’s Link integration.
Qualifications & exceptions
Applies only if the User controls how approval or spend limits are set.
Approval must come before the Link Transaction starts.
Data Access & Collection · Company practice
You send Stripe the Mutual End User's data for prefill, access validation, analytics and enabling the services
For Link Transactions started by or through the User Agentic Agent, the User will send Stripe the Mutual End User Data for four purposes: (i) prefilling the Mutual End User's details in Link login, verification or account creation; (ii) validating the Mutual End User's access to Link; (iii) performing analytics; or (iv) otherwise enabling the Link Agent Wallet Services and related Services. Mutual End User Data means name, email address, verification information, other information Stripe reasonably requests for verification, and associated metadata from the User's website.
Supporting quotations
(d) Transaction Details. With respect to Link Transactions initiated by or through User Agentic Agent, User will send to Stripe the Mutual End User Data for the purposes of (i) prefilling those Mutual End User details in the Link login, verification, or account creation; (ii) validating Mutual End User’s access to Link; (iii) performing analytics; or (iv) otherwise enabling the Link Agent Wallet Services and related Services.
“Mutual End User Data” means Mutual End User’s name, email address, verification information, other information Stripe reasonably requests for verification purposes, associated metadata from User’s website, and other information Stripe requests associated metadata from User’s website.
Qualifications & exceptions
Applies to Link Transactions started by or through the User Agentic Agent.
Not stated here
The fourth purpose, enabling related Services, is open-ended.
Charges & Financial Obligations · Restriction or exception
You must keep Link enabled as a Payment Method while using Link Agent Wallet, under the Link terms and fees
The User will enable Link as a Payment Method and must keep it enabled for as long as it uses the Link Agent Wallet Services. Use of Link is subject to the Link Payment Method Terms and the corresponding fees on the Stripe Pricing Page. If the User has already enabled Link, the terms and pricing it previously agreed to apply.
Supporting quotations
(a) Link Payment Method. User will enable Link as a Payment Method, and must have Link Payment Method enabled for the duration of its use of the Link Agent Wallet Services. User’s use of the Link Payment Method is subject to the Link Payment Method Terms and corresponding fees on the Stripe Pricing Page. To the extent User has already enabled the Link Payment Method, previously agreed to terms and pricing apply.
Qualifications & exceptions
Previously agreed terms and pricing apply if Link was already enabled.
Not stated here
The Link Payment Method Terms and fee amounts are not part of this saved text.
Sharing & Disclosure · Restriction or exception
You must work on joint marketing, consider offering Financial Insights, and use shared data only as authorized
The User will use commercially reasonable efforts to develop mutually agreed marketing and promotion for Link through its Agentic Agent, and will in good faith evaluate offering Stripe's Financial Insights open banking product (which lets Mutual End Users share financial account data with the User's Agentic Agent) where available in the Territory. If a Mutual End User shares financial account data this way, the User will use it only for purposes the Mutual End User authorized.
Supporting quotations
(b) Marketing; Services Availability. User will use commercially reasonable efforts to collaborate and develop mutually agreed-upon marketing and promotional activities and materials relating to the use of Link through the User’s Agentic Agent. User will, in good faith, evaluate making Stripe’s “Financial Insights” product offering (which is an open banking solution that enables Mutual End Users to share their financial account data with User’s Agentic Agent ) available to Mutual End Users through User’s Agentic Agent, to the extent such offering is available in the Territory. To the extent a Mutual End User uses Financial Insights to share financial account data with User through User’s Agentic Agent, User will only use such data for purposes the Mutual End User has authorized.
Qualifications & exceptions
Marketing is commercially reasonable efforts toward mutually agreed activities.
Financial Insights evaluation is in good faith and only where available in the Territory.
Shared financial data may be used only for purposes the end user authorized.
Not stated here
The duty is to evaluate, not to offer, Financial Insights.
Account & Service Control · Restriction or exception
You must make Link the default payment solution in your agentic agent and use the services only per Documentation
The User must make Link the default payment solution for Mutual End Users through its Agentic Agent. The User must use the Link Agent Wallet Services only in accordance with the Documentation, these terms, and any technical specifications Stripe gives or publishes.
Supporting quotations
(c) Link Presentment. User will make Link the default payment solution for Mutual End Users through User’s Agentic Agent.
(d) Documentation. User must use the Link Agent Wallet Services only in accordance with Documentation, these Link Agent Wallet Terms and any technical specifications that Stripe provides to User or publishes.
Not stated here
The Documentation and technical specifications are not in this saved text.
Use & Processing · Restriction or exception
You must not profile data subjects or subject them to significant automated decision-making
The User must not process Personal Data to evaluate, analyze or predict the characteristics or behavior of data subjects (Profiling), including by building behavioral profiles, predictive models or look-alike audiences. The User must also not subject data subjects to automated decision-making or Profiling that has legal or similarly significant effects.
Supporting quotations
(e) No Profiling. User must not process Personal Data for the purpose of evaluating, analyzing, or predicting the characteristics or behavior of data subjects ("Profiling"). This includes the creation of behavioral profiles, predictive models, or "look-alike" audiences. User must not subject data subjects to any automated decision-making or Profiling that produces legal or similarly significant effects.
Qualifications & exceptions
Profiling is defined in the clause as evaluating, analyzing or predicting characteristics or behavior.
Charges & Financial Obligations · Restriction or exception
Total Link Transaction value is capped per Documentation or written agreement, counting refunds and disputes
The total dollar value of all Link Transactions started by or through the User Agentic Agent, including refunds, reversals and disputes, is determined by Stripe Documentation or as the parties agree in writing (email is enough). The terms do not state the cap amount.
Supporting quotations
2.3 Transaction Cap.
The total dollar value of all Link Transactions (including refunds, reversals, and disputes) initiated by or through User Agentic Agent will be determined per Stripe Documentation or as agreed to in writing by the parties (email sufficient)..
Qualifications & exceptions
Counts refunds, reversals and disputes as well as purchases.
Email counts as written agreement.
Not stated here
The cap amount is not stated in this document; it sits in Documentation or a separate written agreement.
Charges & Financial Obligations · Permission or license
Stripe may suspend Link use once its Link Transaction Losses exceed USD $25,000, until a Definitive Agreement
When Stripe is liable as merchant of record under the Card Network Rules for certain transaction liabilities of Link Transactions started through the User Agentic Agent, or for funding a Link balance, and incurs more than USD $25,000 in Link Transaction Losses, Stripe may suspend or restrict the User's use of the Link Agent Wallet Services until the parties agree a Definitive Agreement. Link Transaction Losses are Stripe's losses from chargebacks, chargeback fees, fines, penalties, fraud, disputes, refunds or reversals on those transactions. A Definitive Agreement is one that includes any fees or agreed liability framework.
Supporting quotations
2.4 Loss Liability.
When Stripe is liable as merchant of record under the Card Network Rules for certain transaction liabilities associated with Link Transactions initiated through User Agentic Agent or funding of a custodial or non-custodial Link balance, including Link Transaction Losses, and incurs greater than USD $25,000 in Link Transaction Losses, Stripe may suspend or restrict User’s use of Link Agent Wallet Services until the parties have agreed to a Definitive Agreement.
“Link Transaction Losses” means losses Stripe incurs for chargebacks, chargeback fees, fines, penalties, fraud, disputes, refunds, or reversals arising as a result of Link Transactions initiated by or through User Agentic Agent.
“Definitive Agreement” means an agreement that includes any fees or agreed upon liability framework for the Link Agent Wallet Services.
Qualifications & exceptions
The USD $25,000 threshold counts Stripe's losses, not the User's.
Suspension or restriction continues until a Definitive Agreement is agreed.
Not stated here
The terms do not state what liability the User bears for Link Transaction Losses; they say only that a Definitive Agreement would set any liability framework.
Legal Rights & Agreement Rules · Restriction or exception
You are solely responsible for keeping your Link use and AI systems compliant with Law and Card Network Rules
The User is solely responsible for ensuring that (a) its use of Link and the Link Agent Wallet Services complies with Law and Card Network Rules; (b) its AI Systems, meaning its artificial intelligence agents, services and systems including the User Agentic Agent, comply with Law, including law on developing, deploying and running AI systems; and (c) it puts in place the notices, safeguards, human oversight and documentation Law requires for those AI Systems.
Supporting quotations
2.5 Compliance. (a) General Compliance. User will, and is solely responsible for ensuring that (a) its use of Link and the Link Agent Wallet Services complies with Law and Card Network Rules; (b) its artificial intelligence agents, services, and systems, including User Agentic Agent (collectively, “AI Systems”), comply with Law, including those governing the development, deployment and operation of artificial intelligence systems; and (c) it implements required notices, safeguards, human oversight, and documentation with respect to its AI Systems as required by Law.
Qualifications & exceptions
The notices, safeguards, human oversight and documentation duty applies as Law requires.
Not stated here
The terms do not name which AI laws apply.
Security & Safeguards · Restriction or exception
You and your service providers must meet PCI Standards for Mutual End User Data and give Stripe evidence on request
The User must comply with the PCI Standards, and must make sure its service providers that store, access or transmit Mutual End User Data comply too. When Stripe asks, the User must give Stripe evidence of its compliance. PCI Standards means PCI-DSS and the Payment Card Industry Software Security Framework (PCI-SSF), including successor standards.
Supporting quotations
(b) PCI Compliance. User must, and must ensure that User’s service providers that store, access, or transmit Mutual End User Data, comply with the PCI Standards. Upon Stripe’s request, User must provide Stripe with evidence of User’s compliance.
“PCI Standards” means PCI-DSS and the Payment Card Industry Software Security Framework (PCI-SSF), including successor standards, if any.
Qualifications & exceptions
Evidence is due on Stripe's request.
Standards include successor standards.
Account & Service Control · Permission or license
Stripe guarantees no Link Transaction, may decline risky ones without liability, and may suspend or end your use
Stripe does not guarantee that any Link Transaction started by or through a User Agentic Agent will succeed. Stripe and its Affiliates may decline, cancel or refuse to start any Link Transaction Stripe reasonably believes is unauthorized, fraudulent, illegal, or exposes Stripe, the User, third-party merchants or Mutual End Users to unacceptable risk, and Stripe is not liable to the User for that refusal. Separately, Stripe may suspend, restrict or end the User's use of the Link Agent Wallet Services, or a Mutual End User's access to Link through them, in whole or in part, including any feature, at any time for any reason in its sole discretion.
Supporting quotations
3.1 Link Transactions.
Stripe makes no guarantees that a Link Transaction initiated by or through a User Agentic Agent will be successful. Stripe and its Affiliates may decline, cancel, or refuse to initiate any Link Transaction that Stripe reasonably believes is unauthorized, fraudulent, illegal, or exposes Stripe, User, third-party merchants, or Mutual End Users to unacceptable risk. Stripe is not liable to User for this refusal. Stripe may suspend, restrict, or terminate User’s use of Link Agent Wallet Services or a Mutual End User’s access to Link through Link Agent Wallet Services (in whole or in part), including any feature or functionality, at any time for any reason in its sole discretion.
Qualifications & exceptions
Declining a transaction requires Stripe's reasonable belief of a listed risk.
Suspension or termination needs no reason and is in Stripe's sole discretion.
Charges & Financial Obligations · Permission or license
The services carry no additional cost today, but Stripe may apply or change fees, subject to any legally required notice
Stripe provides the Link Agent Wallet Services at no additional cost to the User, and fees for other Stripe Services still apply. Stripe reserves the right to apply or change fees for the Service, subject to any notice period the law requires before applying or changing fees, and to any applicable Taxes.
Supporting quotations
3.2 Fees.
Stripe provides the Services at no additional cost to User. Fees for use of other Stripe Services continue to apply. Stripe reserves the right to apply or change fees for the use of the Service, subject to any notice period required by Law before applying or changing fees, as well as any applicable Taxes.
Qualifications & exceptions
Any legally required notice period applies before a fee starts or changes.
Applicable Taxes are additional.
Not stated here
The terms do not state any notice period of their own.
Use & Processing · Company practice
You and Stripe are independent data controllers for Mutual End User data, each limited by Law and its own terms
The parties act as independent Data Controllers for Mutual End Users' Personal Data in connection with the Link Agent Wallet Services. Stripe may use that Personal Data only as Law and the Link End User Terms permit, and the User only as Law and the User End User Terms permit. The Link End User Terms govern a Mutual End User's use of Link and Stripe's use of their data; the User End User Terms govern a Customer's use of the User Agentic Agent and the User's use of their data.
Supporting quotations
Data Use.
For the avoidance of doubt, the parties act as independent Data Controllers with respect to Personal Data of a Mutual End User in association with the Link Agent Wallet Services. Stripe may only use that Personal Data to the extent permitted by Law and the Link End User Terms, and User may only use that Personal Data to the extent permitted by Law and the User End User Terms.
“User End User Terms” means the terms of service, data policies, and other published terms and policies that govern a Customer’s use of User Agentic Agent, and User’s use of the Customer’s Personal Data in connection therewith.
Qualifications & exceptions
Each party is limited by Law and by its own end user terms.
Not stated here
Neither set of end user terms is part of this saved text.
Legal Rights & Agreement Rules · Context
Definitions: Link (by reference to the Link Terms), Link Payment Method and Link End User Terms
“Link” is defined by the Link Terms on the Stripe Legal Page, which are not in this saved text. The Link Payment Method (Link PM) means presenting Link through a Stripe interface or APIs in the User's customer payment form so a Customer can pay with Link using supported payment methods, where the Transaction Payment Method type is identified as “Link”. The Link End User Terms are the published terms of service, data policies and other terms governing a Mutual End User's use of Link and Stripe's use of their Personal Data or information in connection with it.
Supporting quotations
“Link” is as defined in the Link Terms accessible from the Stripe Legal Page.
“Link Payment Method” or “Link PM” means presentment of Link via Stripe interface or Stripe APIs in the User’s customer payment form that allows a Customer to submit payment via Link using supported payment methods where the Transaction Payment Method type is identified as “Link”.
“Link End User Terms” means the terms of service, data policies, and other published terms and policies that govern a Mutual End User’s use of Link, and Stripe’s use of the Mutual End User’s Personal Data or information in connection therewith.
Not stated here
The Link Terms that define “Link” are not supplied.
Charges & Financial Obligations · Context
Definitions: Link Transaction, Link Transaction Losses and Definitive Agreement
A Link Transaction is a Transaction started via the User's Link integration. Link Transaction Losses are losses Stripe incurs for chargebacks, chargeback fees, fines, penalties, fraud, disputes, refunds or reversals arising from Link Transactions started by or through the User Agentic Agent. A Definitive Agreement is an agreement that includes any fees or agreed liability framework for the Link Agent Wallet Services.
Supporting quotations
“Link Transaction” means a Transaction initiated via User’s Link integration.
“Link Transaction Losses” means losses Stripe incurs for chargebacks, chargeback fees, fines, penalties, fraud, disputes, refunds, or reversals arising as a result of Link Transactions initiated by or through User Agentic Agent.
“Definitive Agreement” means an agreement that includes any fees or agreed upon liability framework for the Link Agent Wallet Services.
Qualifications & exceptions
Link Transaction Losses are measured as Stripe's own losses.
Data Access & Collection · Context
Definitions: User Agentic Agent, Mutual End User, Mutual End User Data and Link Agent Wallet Services
A User Agentic Agent is the User's agentic interface, AI-powered system or product that lets Mutual End Users start (or start on their behalf) a Link Transaction. A Mutual End User is a Customer with a Link account who authorizes the User Agentic Agent to connect to it. Mutual End User Data is the Mutual End User's name, email address, verification information, other information Stripe reasonably requests for verification, and associated metadata from the User's website. The Link Agent Wallet Services are the Services that let the User Agentic Agent start Link Transactions on a Mutual End User's behalf with the User or third-party merchants.
Supporting quotations
“User Agentic Agent” means a User agentic interface, artificial intelligence-powered system, or product that enables Mutual End Users to initiate (or initiate on their behalf) a Link Transaction.
“Mutual End User” means a Customer that has a Link account and authorizes User Agentic Agent to connect to Customer’s Link account.
“Mutual End User Data” means Mutual End User’s name, email address, verification information, other information Stripe reasonably requests for verification purposes, associated metadata from User’s website, and other information Stripe requests associated metadata from User’s website.
“Link Agent Wallet Services” means the Services that enable User Agentic Agent to initiate Link Transactions on behalf of the Mutual End User with User or third-party merchants.
Qualifications & exceptions
Mutual End User Data includes whatever further verification information Stripe reasonably requests.
Not stated here
The list of data is open-ended because of Stripe's right to request other verification information.
Legal Rights & Agreement Rules · Context
Definitions: Card Network (Visa, Mastercard, American Express, Discover) and Card Network Rules
A Card Network is a payment card network, including those run by Visa, Mastercard, American Express and Discover; the named networks are examples, not a closed list. Card Network Rules are the Payment Method Rules a Card Network publishes.
Supporting quotations
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
“Card Network Rules” means the Payment Method Rules published by a Card Network.
Qualifications & exceptions
The named networks are examples, not a complete list.
Not stated here
The Card Network Rules themselves are published by the networks and are not in this document.
Legal Rights & Agreement Rules · Context
Managed Payments Terms add to four other term sets and control in a conflict (modified Sept. 28, 2026)
These Stripe Managed Payments Terms, last modified September 28, 2026, supplement the General Terms, Stripe Financial Services Terms, Stripe Payments Terms and Stripe Connect Terms, which they incorporate by reference, and together with the Documentation govern the User's use of the Stripe Managed Payments Service. If they conflict with the Financial Services, Payments or Connect Terms, the Managed Payments Terms control as applied to this Service. Capitalized terms not defined here take their meaning from those other terms.
Supporting quotations
Last modified: September 28, 2026
These terms (“Stripe Managed Payments Terms”) supplement the General Terms, the Stripe Financial Services Terms, the Stripe Payments Terms, the Stripe Connect Terms, each of which are incorporated into these Stripe Managed Payments Terms by this reference, and, together with the Documentation, govern User’s use of the Stripe Managed Payments Service. If the Stripe Managed Payments Terms conflict with the Financial Services Terms, the Stripe Payments Terms, or the Stripe Connect Terms, then the Stripe Managed Payments Terms control as applied to the Stripe Managed Payments Service.
Qualifications & exceptions
The Managed Payments Terms control over the Financial Services, Payments and Connect Terms only as applied to the Managed Payments Service.
Not stated here
The text names the General Terms as supplemented but states the priority rule only against three of the four incorporated term sets.
Legal Rights & Agreement Rules · Company practice
Your Managed Payments agreement is with Sold through Link, LLC, which may freely assign it to Affiliates
The Stripe Managed Payments Service is provided by Stripe's Affiliate Sold through Link, LLC (SMP), and these terms create an agreement between the User and SMP for using the Service. The User agrees that SMP may freely assign and transfer any of its rights or obligations under these terms to its Affiliates.
Supporting quotations
The Stripe Managed Payments Service is provided by Stripe’s Affiliate, Sold through Link, LLC (“SMP”). These Stripe Managed Payments Terms create an agreement between User and SMP for use of the Stripe Managed Payments Service. User agrees that SMP may freely assign and transfer any of its rights or obligations under these Stripe Managed Payments Terms to its Affiliates.
Qualifications & exceptions
The assignment right is SMP's only; the clause gives the User no matching right.
Not stated here
The terms give no notice or consent requirement for an assignment.
Charges & Financial Obligations · Company practice
The service sells digital products via checkout, receipts, proceeds, post-sale support and Indirect Tax handling
The Stripe Managed Payments Service enables the sale of digital products to Customers by showing checkout pages, sending receipts, managing sales proceeds and post-sale support (such as disputes and transaction support), and calculating and remitting any applicable Indirect Taxes in certain jurisdictions, as described in the Documentation.
Supporting quotations
1.2 Description of Stripe Managed Payments Service.
The Stripe Managed Payments Service enables the sales of digital products to Customers by surfacing checkout pages to Customers, sending receipts, managing sales proceeds and post-sale support (e.g., disputes and transaction support), as well as calculating and remitting any applicable Indirect Taxes in certain jurisdictions, as described in the [Documentation](https://docs.stripe.com/payments/managed-payments/how-it-works).
Qualifications & exceptions
Indirect Tax calculation and remittance happens only in certain jurisdictions.
Not stated here
Which jurisdictions are covered is left to the Documentation, which is a linked page not in this text.
Charges & Financial Obligations · Company practice
SMP is merchant of record and sells on your behalf; you are bound by its actions; it is the Indirect Tax supplier
SMP provides the Managed Payments Service to the User as a Seller, not to the User's Customers, and is the merchant of record for Transactions through it. The User appoints and authorizes SMP to facilitate sales of the User's Product on the User's behalf and agrees to be bound by SMP's actions in those sales. SMP is not the seller of record, never has or receives possession of the Product, and does not book the revenue from the sale. For Indirect Tax purposes only, as further described in Section 4, the User agrees that SMP should be treated under applicable Laws as making or deemed to make the supply to the Customer, for example as an electronic interface operator, marketplace operator, commissionaire, agent or deemed supplier, or as the person responsible for determining, collecting, reporting and remitting Indirect Taxes.
Supporting quotations
2.1 Provision of Services by SMP to Seller.
(a) Merchant of Record. SMP provides the Stripe Managed Payments Service to User, as a Seller, and not to User’s Customers. SMP is the merchant of record for Transactions using the Stripe Managed Payments Service. User appoints and authorizes SMP to facilitate the sale of User’s Product on User’s behalf in accordance with these Stripe Managed Payments Terms, and User agrees to be bound by the actions of SMP in connection with the sale of User’s Product on User’s behalf. User agrees that SMP is not the seller of record, SMP does not have or receive possession of the Product, and SMP will not book the revenue from User’s sale of the Product to Customer. User acknowledges and agrees that, for Indirect Tax purposes only and as further described in Section 4 (Responsibility for Indirect Taxes on the Sales of Products), SMP should be treated under applicable Laws as making or deemed to make the supply of the Product to the Customer, as an electronic interface operator, marketplace operator, commissionaire, agent or deemed supplier, or as the person responsible for determining, collecting, reporting and remitting Indirect Taxes in respect of that supply.
“Indirect Taxes” means any applicable transaction taxes and duties imposed by any Governmental Authority, including sales and use tax, value-added tax (VAT), and goods and services tax (GST), or equivalent transaction taxes.
Qualifications & exceptions
The supplier treatment is for Indirect Tax purposes only.
SMP is merchant of record but not seller of record.
Not stated here
Section 4 on Indirect Tax responsibility sits in a later part of these terms.
Account & Service Control · Permission or license
SMP may change your Stripe Account on your behalf for payment methods, dispute evidence, fraud tools and data
To provide the Service, SMP and its Affiliates may change the User's Stripe Account on the User's behalf to (i) enable a payment method or adjust its settings for the Service, (ii) submit evidence for a Dispute on a Managed Payments Transaction, (iii) enable or configure fraud prevention and dispute management tools, such as dispute deflection and automated resolution, to keep risk and dispute levels acceptable, and (iv) delete, restrict access to or modify Customer information or Transaction data, as a Customer requests or Law requires. The User authorizes these changes.
Supporting quotations
(b) Changes to User's Stripe Account. As part of providing the Stripe Managed Payments Service to User, SMP and its Affiliates may need to make changes to User’s Stripe Account, on User’s behalf, (i) enable a payment method or adjust its settings for use with the Stripe Managed Payments Service, (ii) submit evidence in connection with a Dispute for a Stripe Managed Payments Service Transaction, (iii) enable or configure fraud prevention and dispute management tools (e.g., dispute deflection and automated resolution) to maintain acceptable risk and dispute levels, (iv) delete, restrict access to, or modify Customer information or Transaction data, as requested by a Customer or required by Law, in connection with a Stripe Managed Payments Service Transaction. User authorizes SMP and its Affiliates to make the changes described in this Section.
Qualifications & exceptions
Changes are made on the User's behalf and under the User's authorization.
Data deletion or modification is tied to a Customer request or a legal requirement.
Not stated here
Whether the User is notified of each change is not stated.
Charges & Financial Obligations · Company practice
You appoint SMP as your agent for funds, and settlement funds are pooled with other users' funds at Financial Providers
SMP may provide access to Stripe Payment Services to facilitate the User's sales. The User appoints SMP as its agent for the limited purpose of directing, receiving, holding and settling funds. All settlement funds that Stripe, SMP or Acquiring Affiliates receive for Transactions are combined with other users' settlement funds and held in one or more Pooled Accounts at one or more Financial Providers. A Pooled Account is a pooled account to which Transaction settlement funds are credited.
Supporting quotations
2.2 Provision of Services by Stripe to SMP; Pooled Accounts.
User appoints SMP as User’s agent for the limited purpose of directing, receiving, holding and settling funds under this Agreement.
All settlement funds that Stripe, SMP, or Acquiring Affiliates, as applicable, receive for Transactions are combined with settlement funds for other users and held in one or more Pooled Accounts at one or more Financial Providers.
“Pooled Account” means a pooled account to which Transaction settlement funds are credited.
Qualifications & exceptions
The agency is limited to directing, receiving, holding and settling funds.
Not stated here
The terms do not name the Financial Providers.
Charges & Financial Obligations · Company practice
Once an Acquiring Affiliate has the funds the Customer owes you nothing more; recourse is against Stripe or SMP
Once an Acquiring Affiliate receives funds for a Transaction, the Customer has no further obligation to pay the User for it, whether or not and whenever Stripe or its Affiliate settles those funds to the User. If Stripe or SMP does not settle funds due to the User, the User has recourse only against Stripe or SMP and not against the Customer. Stripe or SMP will promptly update the User's Stripe Account balance to reflect processed Transactions. Acquiring Affiliates are Stripe's Affiliates or Payment Method Acquirers identified in the Documentation that SMP may use to acquire Transactions for the Service.
Supporting quotations
Once an Acquiring Affiliate receives funds for a Transaction, the relevant Customer has no further obligation to make payments to User with respect to that Transaction, regardless of whether and when Stripe or its Affiliate (as applicable) settles those funds to User. If Stripe or SMP (as applicable) does not settle funds due to User under this Agreement, User will have recourse only against Stripe or SMP (as applicable) and not the relevant Customer.
Stripe or SMP (as applicable) will promptly update User’s Stripe Account balance to reflect processed Transactions.
“Acquiring Affiliates” means Stripe’s Affiliates or Payment Method Acquirers as identified in the Documentation which SMP may provide access to via the Stripe Payments Services to acquire Transactions in connection with the Stripe Managed Payments Service.
Qualifications & exceptions
The Customer's discharge does not depend on whether Stripe has settled the funds to the User.
Balance updates are promised promptly, not by a fixed deadline.
Not stated here
The Acquiring Affiliates are identified in the Documentation, which is not in this text.
Legal Rights & Agreement Rules · Restriction or exception
A receipt SMP gives a Customer as your agent is binding on you
If SMP, acting as the User's agent, gives the Customer a receipt for a Transaction, that receipt is binding on the User.
Supporting quotations
If, in the capacity as User’s agent, SMP provides a receipt for a Transaction to the applicable Customer, that receipt is binding on User.
Qualifications & exceptions
Applies to receipts SMP provides in its capacity as the User's agent.
Not stated here
The terms do not say what a receipt may contain or how the User can correct one.
Charges & Financial Obligations · Restriction or exception
Stripe may invest pooled funds, and you have no rights to the pooled account, its earnings, or to draw funds from it
Stripe and its Affiliates may invest funds held in a Pooled Account as described in the General Terms. The User has no rights to any Pooled Account or to earnings its funds generate, and is not entitled to draw funds from any Pooled Account.
Supporting quotations
Stripe and its Affiliates (as applicable) may invest funds held in a Pooled Account as described in the General Terms.
User has no rights to any Pooled Account, or earnings generated by funds held in any Pooled Account, and are not entitled to draw funds from any Pooled Account.
Qualifications & exceptions
Investment is as the General Terms describe.
Not stated here
The General Terms' investment rules are not repeated here.
Account & Service Control · Context
Stripe and its Affiliates may separately provide other Stripe services to Customers
Stripe and its Affiliates may separately provide other Stripe services to Customers of the User, in addition to the Managed Payments Service.
Supporting quotations
2.3 Provision of Services by Stripe to Customers.
Stripe and its Affiliates may separately provide other Stripe services to Customers.
Not stated here
The terms do not describe those other services or whether they involve Customer data from the User's sales.
Account & Service Control · Restriction or exception
The service covers only eligible Products you elect, and your account becomes a Connected Account of SMP
The Managed Payments Service applies to, and may be used only for, Transactions for eligible Products the User elects to sell through it. By using it, the User's Stripe Account is treated as a Connected Account to SMP as the Platform, and these terms incorporate the Connected Account Agreement by reference.
Supporting quotations
3.1 Use of the Service and Termination.
Stripe Managed Payments Service only applies to, and may only be used for, Transactions for eligible Products that User elects to sell via the Stripe Managed Payments Service. By using the Stripe Managed Payments Service, User’s Stripe Account is treated as a Connected Account to SMP as the Platform. These Stripe Managed Payments Terms incorporate by reference the Connected Account Agreement.
Qualifications & exceptions
Only eligible Products the User elects to sell are covered.
Not stated here
Which Products are eligible is not set out in this section.
Account & Service Control · Permission or license
SMP may suspend or end your use at any time, and may make you stop selling or offboard ineligible products
SMP reserves the right to suspend or terminate the User's use of the Service at any time. If SMP or its Affiliates determine the User's products are not eligible Products, they may (i) require the User to stop using the Service for the ineligible products, or (ii) offboard the ineligible products from the Service.
Supporting quotations
SMP reserves the right to suspend or terminate User’s use of the Stripe Managed Payments Service at any time. If SMP or its Affiliates determines that User’s products do not qualify as eligible Products, SMP and its Affiliates may (i) require User to stop using the Stripe Managed Payments Service for the ineligible products, or (ii) offboard the ineligible products from the Stripe Managed Payments Service.
Qualifications & exceptions
Suspension or termination is available at any time, without a stated reason or notice in this clause.
The ineligible-product remedies follow a determination by SMP or its Affiliates.
Not stated here
This clause states no notice period; other parts of the terms may add one.
Account & Service Control · Restriction or exception
You must clearly disclose subscription terms to Customers before or at checkout, including renewal and cancellation
For any Product sold on a subscription basis through the Service, the User must clearly and conspicuously disclose the subscription's terms to Customers before or at checkout: the amount and frequency of the charge, the term length, whether it automatically renews, the amount on renewal, any additional fees and costs, and a method for cancellation.
Supporting quotations
3.2 Subscriptions.
For any Product sold on a subscription basis via the Stripe Managed Payments Service, User must clearly and conspicuously disclose the terms of the subscription to Customers before or at checkout, including subscription amount and frequency of the charge, term length, whether the subscription automatically renews, the subscription amount upon renewal, any additional fees and costs related to the subscription, and a method for cancellation.
Qualifications & exceptions
Disclosure must be clear and conspicuous and made before or at checkout.
Account & Service Control · Restriction or exception
To have SMP manage existing subscriptions you need contract rights, an agency appointment and Customer notice
If the User elects to manage its existing Customer subscriptions through the Service, then from the date it starts and at all times during the Term the User must (a) have the contractual rights to assign or transfer those subscriptions to be managed through the Service and to appoint SMP to charge and collect the amounts owed; (b) have appointed SMP as its agent before SMP charges and collects on its behalf, and keep that appointment; and (c) give its Customers notice that SMP will be responsible for charging and collecting.
Supporting quotations
3.2 Subscriptions.
If User elects to manage its existing Customer subscriptions for Products through Stripe Managed Payments Service, User will, as of the date it starts using the Stripe Managed Payments Service and at all times during the Term:
(a) have the necessary contractual rights to assign or transfer existing Customer subscriptions to be managed through Stripe Managed Payments Service and to appoint SMP to charge and collect subscription amounts owed by Customers;
(b) have appointed SMP as User’s agent before SMP charges and collects subscription amounts on User’s behalf from User’s Customers, and will maintain that agency appointment; and
(c) will give notice to User’s Customers that SMP will be responsible for charging and collecting subscription amounts owed by Customers.
Qualifications & exceptions
Applies only if the User elects to manage existing subscriptions through the Service.
The duties apply from the start date and at all times during the Term.
Account & Service Control · Restriction or exception
Taking subscriptions back from SMP needs your own capability and timely Customer notice that SMP's role ends
If the User elects to stop having the Service manage Customer subscriptions so it can manage them directly, then from the date of its election the User must (x) have the contractual rights and capabilities to manage the subscriptions and charge and collect the amounts owed, and (y) give the affected Customers timely notice that SMP will no longer charge and collect for the sale of the User's Product, that there is no further relationship between SMP and the Customers, and that any related services from Stripe or its Affiliates to Customers will no longer be provided.
Supporting quotations
If User elects to stop managing Customer subscriptions for Products through Stripe Managed Payments Service to manage them directly, User will, as of the date of User’s election:
(x) have the necessary contractual rights and capabilities to manage the subscriptions and to charge and collect subscription amounts owed by Customers; and
(y) will give timely notice to the affected Customers that SMP will no longer charge and collect subscription amounts owed for the sale of User’s Product, that there is no further relationship between SMP and User’s Customers, and any services provided by Stripe or its Affiliates to Customers related to those subscriptions will no longer be provided.
Qualifications & exceptions
Applies only if the User elects to stop having the Service manage subscriptions.
Notice must be timely.
Charges & Financial Obligations · Permission or license
SMP may issue refunds within 60 days despite a stricter policy of yours, and its refund policy controls
SMP reserves the right to issue refunds within 60 days of a Customer's purchase through the Service, regardless of any more restrictive refund policy the User has set. The User's refund policy remains subject to the SMP refund policy at all times (the policy is on a linked page not in this text). If the two conflict, the SMP refund policy controls where the User's is more restrictive.
Supporting quotations
3.3 Refund Policy.
SMP reserves the right to issue refunds within 60 days of a Customer’s purchase of a Product via the Stripe Managed Payments Service regardless of any more restrictive refund policy User has set with its Customers. User’s refund policy remains subject to the SMP refund policy, located at [https://support.link.com/questions/sold-through-link-refunds](https://support.link.com/questions/sold-through-link-refunds), at all times. In the event of a conflict between the SMP refund policy and User’s refund policy, the SMP refund policy will control where User’s refund policy is more restrictive than the SMP refund policy.
Qualifications & exceptions
The 60-day refund right applies even where the User's policy is more restrictive.
The SMP policy wins only where the User's policy is more restrictive.
Not stated here
The SMP refund policy is on a linked page and is not supplied.
Charges & Financial Obligations · Restriction or exception
You are liable for legally required Refunds and all Disputes, refunds and Reversals, debited from you
If SMP must make a Refund by Law, including Law applicable to the Customer's location, the User is liable for the full amount regardless of any refund policy. The User, as Seller, is liable to SMP and its Affiliates for the full amount of any Disputes, refunds and Reversals resulting from its sale of Products through the Service. SMP or its Affiliates will debit those amounts from the User's Stripe Account balance or, where Law permits, its User Bank Account.
Supporting quotations
If SMP is required to make a Refund by Law, including Law applicable to Customer's location, User is liable for the full amount of the Refund regardless of any refund policy. User, as Seller, is liable to SMP and its Affiliates for the full amount of any Disputes, refunds, and Reversals resulting from User’s sale of Products using the Stripe Managed Payments Service. SMP or its Affiliates will debit the amount of any Disputes, refunds, and Reversals from User’s Stripe Account balance or, where permitted by Law, User’s User Bank Account.
Qualifications & exceptions
Bank account debits happen only where Law permits.
Liability covers the full amount regardless of the refund policy the User set.
Account & Service Control · Procedure
You get 48 hours to answer SMP's request about a sale, or SMP may refund the Customer without your input
The User has an opportunity to address Customer complaints and Disputes. If SMP asks the User for more information about a sale, the User may respond within 48 hours of the request with the information. If the User does not provide the information or a timely response, SMP may refund the payment to the Customer without the User's input.
Supporting quotations
3.4 Customer Disputes and Refunds.
(a) User Cooperation. User will have an opportunity to address Customer complaints and Disputes. If SMP contacts User for additional information about the sale of a Product, User has an opportunity to respond within 48 hours of the request and provide to SMP the requested information. If User does not provide the requested information or a timely response, SMP may refund the payment to the Customer without User’s input.
Qualifications & exceptions
The 48-hour window runs from the request.
Not stated here
The terms do not say how a refund made this way interacts with the User's liability for refunds.
Charges & Financial Obligations · Permission or license
SMP may switch on dispute prevention, deflection and resolution features for you, and you pay their fees
SMP may, at its discretion, enable and configure dispute prevention, deflection and resolution features on the User's behalf to manage the User's dispute rate and maintain the integrity of the Service. The User is responsible for fees on dispute management tools, including when enabled on its behalf, as described in the Documentation or on the Stripe Pricing Page.
Supporting quotations
(b) Dispute Rate Management. SMP may, at its discretion, enable and configure dispute prevention, deflection, and resolution features on User’s behalf to manage User’s dispute rate and maintain the integrity of the Stripe Managed Payments Service. User is responsible for any fees associated with dispute management tools, including when enabled on User’s behalf, as described in the relevant Documentation or on the Stripe Pricing Page.
Qualifications & exceptions
Enabling the tools is at SMP's discretion.
The User pays the fees even if SMP enabled the tools on its behalf.
Not stated here
Fee amounts are in the Documentation or Pricing Page, which are not in this text.
Sharing & Disclosure · Permission or license
You authorize Stripe and its Affiliates to give your User Information to Stripe's Financial Providers
The User authorizes Stripe and its Affiliates to provide User Information to Stripe's Financial Providers in connection with the User's use of the Stripe Managed Payments Service.
Supporting quotations
3.5 Seller Information.
User authorizes Stripe and its Affiliates to provide User Information to Stripe’s Financial Providers in connection with User’s use of the Stripe Managed Payments Service.
Qualifications & exceptions
Sharing is for use of the Managed Payments Service.
Not stated here
The terms do not list the Financial Providers or the information shared.
Charges & Financial Obligations · Company practice
The Payments Terms apply to you as Seller, SMP submits Transactions for you, and Amex conversion is off
The Stripe Payments Terms apply when the User uses the Managed Payments Service. Section 3 of those terms (Payment Methods and Transactions; Payment Method Rules and Payment Method Terms) is modified to apply to the User as the Seller, and any reference to Stripe Payments Services is replaced with the Managed Payments Service. References to submitting Transactions mean SMP submitting them on the User's behalf, and Section 3.5 of the Payments Terms (American Express Conversion, applicable only to the American Express Card Network) does not apply.
Supporting quotations
3.6 Payment Methods.
The Stripe Payments Terms apply when User uses the Stripe Managed Payments Service. Section 3 (“Payment Methods and Transactions; Payment Method Rules and Payment Method Terms”) of the Stripe Payments Terms are modified to apply to User as the Seller when using Stripe Managed Payments Service and any reference to Stripe Payments Services is replaced with the Stripe Managed Payments Service. For clarity, when using the Stripe Managed Payments Service, (a) references to submitting Transactions refers to SMP submitting Transactions on User’s behalf, and (b) Section 3.5 of the Stripe Payments Terms (“American Express Conversion – Only Applicable to the American Express Card Network”) does not apply.
Qualifications & exceptions
Section 3 of the Payments Terms applies as modified for the Seller.
Section 3.5 on American Express conversion does not apply.
Charges & Financial Obligations · Restriction or exception
You as Seller must meet payment method acceptance requirements unless Managed Payments already did so for you
The User, as Seller, is responsible for complying with the specific requirements for accepting and using the Payment Methods offered to Customers through the Managed Payments Service, unless the Service has already complied on the User's behalf, for example by providing a receipt that accurately describes each Transaction.
Supporting quotations
User, as Seller, is responsible for compliance with the specific requirements for acceptance and use of Payment Methods that are offered to Customers through User’s use of the Stripe Managed Payments Service, unless already complied with on User’s behalf by the Stripe Managed Payments Service (e.g., providing a receipt that accurately describes each Transaction).
Qualifications & exceptions
Excused only where the Service has already complied on the User's behalf.
Not stated here
The terms do not list which requirements the Service handles beyond the receipt example.
Charges & Financial Obligations · Restriction or exception
Stripe passes through acquirer, provider and Card Network costs and liabilities to you, and their decisions bind you
Stripe will pass through to the User, and the User is responsible for, (a) costs, fees, fines and charges imposed by a Payment Method Acquirer, Payment Method Provider or Card Network on the User's sale of Products through the Service, and (b) the liability allocated to SMP, acting for the User as Seller, from a decision by one of them about those sales. Any such decision is final and binding on the User.
Supporting quotations
3.7 Liability for Payment Methods.
(a) Pass-Throughs. Stripe will pass through to User and User is responsible for (a) any costs, fees, fines, and charges imposed by a Payment Method Acquirer, Payment Method Provider, or Card Network related to User’s sale of Products via the Stripe Managed Payments Service, and (b) the liability allocated to SMP (acting on User’s behalf as the Seller) from a decision made by a Payment Method Acquirer, Payment Method Provider, or Card Network related to User’s sale of Products via the Stripe Managed Payments Service. Any decision made by a Payment Method Acquirer, Payment Method Provider, or Card Network is final and binding on User.
Qualifications & exceptions
Covers both charges imposed and liability allocated to SMP acting for the User.
Decisions of the acquirer, provider or Card Network are final and binding on the User.
Not stated here
The amounts and the appeal routes, if any, are not stated here.
Charges & Financial Obligations · Restriction or exception
You may not charge a stored Payment Method that SMP authorized unless you get the Customer's own authorization
The User may have access to the Payment Method information a Customer used for Transactions through Managed Payments, but must not charge a Customer's stored Payment Method if SMP obtained the original authorization, unless the User gets its own authorization from the Customer in line with Law.
Supporting quotations
(b) Stored Payment Methods. User may have access to Payment Method information used by a Customer for Transactions using Stripe Managed Payments. User must not charge a Customer’s stored Payment Method if the original authorization was obtained by SMP, unless User obtains its own authorization from Customer in accordance with Law.
Qualifications & exceptions
Applies where SMP obtained the original authorization.
Charges & Financial Obligations · Permission or license
SMP may decline, cancel or refund any Transaction it reasonably suspects is risky, abnormal or in error
SMP may decline, cancel or refund any Transaction made through the Service at any time if it reasonably believes or suspects the Transaction (a) may be fraudulent or unlawful, (b) poses a security risk to Stripe or its Affiliates, (c) may be abnormal, such as an excessive order size, (d) may be made in error, (e) may be made in bad faith, (g) is likely to result in a Dispute, or (h) violates the Agreement, the Documentation or other Stripe terms or policies. The list as written skips item (f).
Supporting quotations
3.8 Transaction Integrity.
SMP may decline, cancel, or refund any Transaction made using Stripe Managed Payments Service at any time if SMP reasonably believes or suspects a Transaction (a) may be fraudulent or unlawful, (b) poses a security risk to Stripe or its Affiliates, (c) may be abnormal (e.g., excessive order size), (d) may be made in error, (e) may be made in bad faith, (g) is likely to result in a Dispute, or (h) is a violation of this Agreement, the Documentation, or other Stripe terms or policies.
Qualifications & exceptions
Requires SMP's reasonable belief or suspicion.
The listed grounds run (a) to (e) then (g) and (h), with no item (f) in the source.
Not stated here
The source has no item (f); the terms do not say whether one was dropped.
Charges & Financial Obligations · Company practice
SMP calculates, collects and remits Indirect Taxes in listed countries and is the liable supplier where Law treats it so
By using the Service, the User agrees SMP will calculate, collect, hold and remit Indirect Taxes on the sale of the Seller's Product to the relevant authorities in the countries identified in the Documentation. For Sellers in certain jurisdictions SMP does this only for cross-border sales, to Customers outside the Seller's country, and has no responsibility for Indirect Taxes on domestic sales. As local Law applies, the User appoints SMP to act as an electronic interface operator, marketplace operator, commissionaire or agent to facilitate supply to Customers for Indirect Tax purposes. Where Law treats SMP in that role as making the supply in its own name or as an intermediary, SMP is treated as the supplier or intermediary liable for the Indirect Taxes and is responsible for charging, collecting, reporting and remitting them. Indirect Taxes means transaction taxes and duties such as sales and use tax, VAT and GST.
Supporting quotations
4. Responsibility for Indirect Taxes on the Sales of Products.
4.1 Indirect Taxes Responsibility.
(a) SMP Tax Responsibility. By using the Stripe Managed Payments Service, User agrees SMP will calculate, collect, hold, and remit to the relevant Government Authorities Indirect Taxes on the sale of Seller’s Product in the countries identified in the Documentation. For Sellers located in certain jurisdictions, SMP will only calculate, collect, and remit Indirect Taxes on the cross-border sales of Seller’s Product (i.e. for sales to Customers outside of Seller’s country), and SMP will have no responsibility for Indirect Taxes on the domestic sales of Seller’s Product (i.e., for sales to Buyers in Seller’s own country). As applicable under local Law, User appoints SMP to act as an electronic interface operator, marketplace operator, commissionaire, or agent on User’s behalf to facilitate the supply of User’s Product to Customers for Indirect Tax purposes. User acknowledges that, in jurisdictions where SMP, as an electronic interface operator, marketplace operator, commissionaire, or agent, is treated by Law as making the supply in SMP’s own name or as an intermediary, SMP will be treated as the supplier or intermediary liable for Indirect Taxes, and will be responsible for charging, collecting, reporting and remitting those Indirect Taxes to the relevant Governmental Authority.
“Indirect Taxes” means any applicable transaction taxes and duties imposed by any Governmental Authority, including sales and use tax, value-added tax (VAT), and goods and services tax (GST), or equivalent transaction taxes.
Qualifications & exceptions
Coverage is limited to the countries identified in the Documentation.
In certain jurisdictions SMP covers cross-border sales only.
SMP's role as liable supplier applies where Law treats it that way.
Not stated here
The country list and the jurisdictions limited to cross-border sales are in the Documentation, which is not in this text.
Charges & Financial Obligations · Restriction or exception
You handle taxes where SMP does not, and SMP's invoices in your name are your responsibility to keep compliant
For Sellers in jurisdictions where SMP supports Indirect Taxes only on cross-border sales, the Seller is solely responsible for calculating, collecting, holding and remitting Indirect Taxes on domestic sales. For Customers in jurisdictions not identified in the Documentation, SMP is not responsible for Indirect Taxes and the Seller is solely responsible for all taxes as Law requires. For sales where SMP is not responsible for Indirect Taxes, SMP will issue an invoice to the Customer on the Seller's behalf in the Seller's name. The Seller, not SMP or its Affiliates, must make sure those invoices meet the Seller's legal and tax requirements, should configure invoice settings in the Stripe Dashboard, and should check whether additional third party services are needed to supplement the invoices.
Supporting quotations
(b) Seller Tax Responsibility and Customer Invoices. For Sellers located in jurisdictions where SMP only supports Indirect Taxes for cross-border sales of Seller’s Product, Seller is solely responsible for calculating, collecting, holding, and remitting Indirect Taxes to the relevant Government Authority on domestic sales of Seller’s Product. For Sellers with Customers located in jurisdictions not identified in the Documentation, SMP is not responsible for the calculation, collection, or remittance of Indirect Taxes on the sale of Seller’s Product, and Seller is solely responsible for the calculation, collection, and remittance of all taxes as required by Law. For those sales of Products using Managed Payments for which SMP is not responsible for the Indirect Taxes, SMP will issue an invoice to Customer on behalf of Seller in Seller’s name. Seller, and not SMP or its Affiliates, is responsible for ensuring that invoices issued by SMP in Seller’s name meet Seller’s legal and tax requirements. Seller should configure the invoice settings in the Stripe Dashboard and ensure the invoices comply with Law, including determining if the invoices need to be supplemented using additional third party services to meet Seller’s legal and tax requirements.
Qualifications & exceptions
Applies to domestic sales in cross-border-only jurisdictions and to Customers in jurisdictions not in the Documentation.
SMP issues the invoice but the Seller is responsible for its legal and tax compliance.
Not stated here
Which jurisdictions fall in each group depends on the Documentation, which is not supplied.
Charges & Financial Obligations · Restriction or exception
You repay SMP for Indirect Tax refunded to Customers that it cannot recover; later recoveries come back to you
The User must pay SMP for Indirect Tax refunded to Customers on a Managed Payments Transaction when SMP or its Affiliates must remit that tax to Governmental Authorities and cannot recover it from the authority. The User authorizes Stripe and its Affiliates to debit the User's Stripe Account balance to recover those refunded taxes. If Stripe or its Affiliates later recover the tax from the authority, they will refund the recovered amount to the User.
Supporting quotations
(c) Responsibility for Indirect Tax Refunded to Customers. User must pay SMP for any Indirect Tax that is refunded to Customers in connection with a Transaction using Stripe Managed Payments Service, if SMP or its Affiliates is required to remit the Indirect Tax amount to Governmental Authorities for that Transaction and is unable to recover the relevant Indirect Tax amounts from the Governmental Authority. User authorizes Stripe and its Affiliates to debit User’s Stripe Account balance and recover from User any Indirect Taxes refunded by Stripe and its Affiliates to User’s Customers, where SMP is required to remit those Indirect Taxes to, and is unable to recover those Indirect Taxes from, the relevant Governmental Authority. If Stripe or its Affiliates can recover those Indirect Taxes from the relevant Governmental Authority at a later date, Stripe or its Affiliates will refund the recovered amount to User.
Qualifications & exceptions
Applies only where SMP must remit the tax and cannot recover it from the Governmental Authority.
Later recoveries are refunded to the User.
Not stated here
No deadline is stated for refunding a later recovery.
Charges & Financial Obligations · Restriction or exception
Where you are deemed to supply SMP, the amount SMP pays you includes Indirect Tax and you may not charge more
In any jurisdiction where the User is deemed to supply the Product to SMP and SMP is deemed to supply it to the User's Customer, the amounts SMP pays the User for the Product include any Indirect Taxes on the deemed supply to SMP, and the User will not charge or recover any additional amount from SMP for that Indirect Tax.
Supporting quotations
(d) Tax Inclusive. In any jurisdiction where, User is deemed to make a supply of the Product to SMP and SMP is deemed to make a supply of the Product to User’s Customer:
(i) the amounts payable by SMP to the User for the Product are inclusive of any Indirect Taxes that apply to the deemed supply of the Product to SMP; and
(ii) User will not charge or recover any additional amount from SMP for that Indirect Tax.
Qualifications & exceptions
Applies only in jurisdictions with a deemed two-step supply.
Not stated here
Which jurisdictions have a deemed supply is not stated.
Account & Service Control · Company practice
SMP invoices and talks to Customers in its own name without disclosing it acts as your agent
The User acknowledges that SMP will communicate with and invoice the Customer in SMP's own name, without disclosing that it acts as the User's agent. A User that does not want SMP to act as its agent must not use the Managed Payments Service for those transactions.
Supporting quotations
(e) Undisclosed Agent. User acknowledges that SMP will communicate with and invoice the customer in SMP’s own name, without disclosing that SMP is acting as User’s agent. If User does not want SMP to act as its agent, User must not use Stripe Managed Payments Service for those transactions.
Qualifications & exceptions
The only stated alternative is not using the Service for those transactions.
Charges & Financial Obligations · Permission or license
If your Free Trials are taxable supplies, SMP may decide, collect, remit and recover the Indirect Tax from you
If the User offers Free Trials and one is deemed a taxable supply where SMP is treated as the party responsible for the Indirect Tax, the User authorizes SMP to (i) decide, in its reasonable discretion and based on Law, whether Indirect Tax is due on the Free Trials, (ii) charge, collect, withhold and remit Indirect Tax as Law requires, and (iii) charge or recover from the User the Indirect Tax attributable to its Free Trials. A Free Trial is free digital goods or services, trial periods, samples or promotional services.
Supporting quotations
(f) Free Trials Provided by User. If User offers Free Trials to User’s Customers and the Free Trial is deemed a taxable supply where SMP is treated as the party responsible for the Indirect Tax, User authorizes SMP to:
(i) determine, using SMP’s reasonable discretion and based on Law, whether Indirect Tax is due on User’s Free Trials;
(ii) charge, collect, withhold, and remit Indirect Tax in accordance with Law; and
(iii) charge or recover from the User the amount of any Indirect Tax attributable to User’s Free Trials.
“Free Trial” means the provision of free digital goods and/or services, trial periods, samples, or promotional services.
Qualifications & exceptions
Applies only where a Free Trial is deemed a taxable supply and SMP is the responsible party.
SMP decides using reasonable discretion based on Law.
Charges & Financial Obligations · Restriction or exception
You must reimburse SMP for Free Trial tax costs, which it may set off or debit, and give trial details on request
The User must promptly reimburse SMP on request for any Indirect Tax, interest, penalties or associated costs SMP has paid, is assessed or becomes liable for in relation to the User's Free Trials. SMP may, without limitation, set those amounts off against sums otherwise due to the User under the Agreement or debit the User's Stripe Account balance. On request the User must give SMP accurate and complete information on the nature, value and terms of any Free Trials.
Supporting quotations
User will promptly reimburse SMP, upon request, for any Indirect Tax, interest, penalties, or associated costs that SMP has paid, is assessed, or becomes liable for in relation to User’s Free Trials. SMP may, without limitation, set off such amounts against any sums otherwise payable or due to the User under this Agreement or debit User’s Stripe Account balance. Upon request, User must provide SMP with accurate and complete information regarding the nature, value, and terms of any Free Trials.
Qualifications & exceptions
Reimbursement is due promptly on SMP's request.
The set-off right is stated as without limitation.
Charges & Financial Obligations · Restriction or exception
You must give accurate product information; Stripe sets and may change tax rates, which is not tax advice
The User must give SMP accurate information about its products so eligibility for the Service can be determined. For each Product the User chooses to sell through the Service, the Service determines the product's taxability and tax rate. Stripe and its Affiliates may review and change the tax rate assigned to a Product at their discretion for supported Transactions, as the Documentation describes, and a change does not constitute tax advice. SMP is not responsible for calculating, collecting or remitting Indirect Taxes on products that do not meet the eligibility requirements in the Documentation, and the Seller is solely responsible for all Taxes on them as Law requires.
Supporting quotations
4.2 Product Eligibility and Tax Rates.
User must provide accurate information to SMP about its products to determine eligibility for the use of the Stripe Managed Payments Service. For each Product that User elects to sell via the Stripe Managed Payments Service the Stripe Managed Payments Service will determine the appropriate product taxability and tax rate. Stripe and its Affiliates reserve the right to review and change the tax rate assigned to a Product at its discretion for a Transaction using the Stripe Managed Payments Service that SMP supports for Indirect Tax purposes in accordance with the Documentation. User acknowledges and agrees that any change Stripe makes to a tax rate does not constitute tax advice. SMP is not responsible for the calculation, collection, or remittance of Indirect Taxes on the sale of any product that does not meet the eligibility requirements as described in the Documentation, and Seller is solely responsible for the calculation, collection, and remittance of all Taxes as required by Law.
Qualifications & exceptions
Stripe's right to change a tax rate is at its discretion.
SMP does not handle taxes on products that fail the eligibility requirements.
Not stated here
The eligibility requirements are in the Documentation, which is not in this text.
Legal Rights & Agreement Rules · Procedure
Tell Stripe within five days of tax authority correspondence and respond to the authority only after talking to Stripe
If the User receives correspondence from a Governmental Authority about SMP's Indirect Tax responsibilities under Section 4.1, the User must contact Stripe Support by the earlier of five calendar days after receipt or five business days before the response deadline. Stripe will endeavor to give the User information or supporting documents for the response, and the User must reasonably help Stripe review the matter. Stripe may require the User to ask the authority for an extension if the deadline is under five business days from Stripe's receipt. The User will respond to the authority only after discussing it with Stripe. A delay or failure to notify does not release Stripe from its Section 4.3 obligations, except to the extent Stripe was prejudiced.
Supporting quotations
4.3 Tax Authorities and Audits.
If User receives any correspondence from a Governmental Authority in connection with SMP’s Indirect Tax responsibilities as stated in Section 4.1 (Indirect Taxes Responsibility), User must (i) contact [Stripe Support](https://stripe.com/contact) by the earlier of (a) five calendar days after receipt of that correspondence or (b) five business days before the response deadline. After receipt of notification, Stripe will endeavor to provide User with information or supporting documentation to respond to the Government Authority and User must reasonably assist Stripe in its review of the matter. Stripe may require User to request an extension from a Governmental Authority if the response deadline is less than five business days from Stripe’s receipt of that correspondence. In any case, User will respond to the Government Authority only after engaging in discussion with Stripe. Any delay or failure to notify will not relieve Stripe of its obligations under this Section 4.3, except to the extent Stripe has been prejudiced by the delay or failure.
Qualifications & exceptions
The notice deadline is the earlier of two measures.
Stripe's obligations survive late notice except to the extent of prejudice to Stripe.
Not stated here
The terms do not describe what happens if the User responds to the authority without first talking to Stripe.
Charges & Financial Obligations · Restriction or exception
You pay other taxes from your sales, and Stripe may recoup any it becomes liable for from funds it owes you
The User is responsible for paying other Tax liabilities that arise from its sale of a Product through the Service. If Stripe becomes liable for any other Tax liabilities because of the User's use of the Service or these terms, excluding Taxes Stripe or SMP owes from charging Fees for the Service, the User authorizes Stripe to recoup the cost by deducting funds from amounts Stripe owes the User.
Supporting quotations
4.4 Responsibility for other Taxes.
User is responsible for payment of other Tax liabilities that arise from User’s sale of a Product via the Stripe Managed Payments Service. If Stripe becomes liable for any other Tax liabilities as a result of User’s use of Stripe Managed Payments Service or these Stripe Managed Payments Terms, excluding Tax liabilities owed by Stripe or SMP as a result of charging Fees for the Stripe Managed Payments Service, User authorizes Stripe to recoup the cost of other Tax liabilities by deducting funds from amounts Stripe owes to User.
Qualifications & exceptions
Excludes Tax liabilities Stripe or SMP owes from charging Fees for the Service.
Legal Rights & Agreement Rules · Company practice
For Tax Information Reports you know the nature of the payments best; Stripe is not the Form 1042-S withholding agent
For any Tax Information Reports, the User acknowledges and agrees it is best placed to determine the nature of the payments made in connection with its use of the Service. Under US tax law, in connection with the User's use of the Service, Stripe and its Affiliates are not the withholding agent for Form 1042-S purposes.
Supporting quotations
For any Tax Information Reports, User acknowledges and agrees that User is in the best position to determine the nature of the payments made in connection with User’s use of the Stripe Managed Payments Service. With respect to US tax law, in connection with User’s use of the Stripe Managed Payments Service, Stripe and its Affiliates are not the withholding agent for Form 1042-S purposes.
Qualifications & exceptions
The Form 1042-S statement is about US tax law.
Charges & Financial Obligations · Restriction or exception
You agree to self-billing for your deemed supply to SMP, accept SMP's invoices and must not send your own
For Tax purposes only, the User agrees to a self-billing arrangement for its deemed provision of the Product to SMP in jurisdictions where Law permits it, as the Documentation outlines. Where permitted, the User accepts all self-billed invoices SMP issues on its behalf and must not issue its own invoices to SMP or its Affiliates for those deemed sales. The User remains responsible for determining whether self-billing is permitted in its jurisdiction. If it is not, the User must inform SMP immediately through Stripe support and may, if Law requires, issue compliant Tax invoices for the deemed sales.
Supporting quotations
4.5. Responsibility for Invoicing.
This Section 4.5 applies for Tax purposes only. User agrees to a self-billing arrangement for User’s deemed provision of the Product to SMP in the jurisdictions where such an arrangement is permitted by Law as outlined in the Documentation. Where permitted, User agrees to accept all self-billed invoices issued by SMP on User’s behalf and User must not issue its own invoices to SMP or its Affiliates for the deemed sales of Product to SMP. User remains responsible for determining whether self-billing is permitted in User’s jurisdiction. If self-billing is not permitted in User’s jurisdiction, User must inform SMP immediately by contacting [Stripe support](https://stripe.com/contact) and may, if required by Law, issue compliant Tax invoices for all deemed sales of Product to SMP or its Affiliates.
Qualifications & exceptions
For Tax purposes only.
Applies only in jurisdictions where Law permits self-billing.
The User must tell SMP immediately if self-billing is not permitted.
Not stated here
The jurisdictions where self-billing is permitted are listed in the Documentation, which is not in this text.
Charges & Financial Obligations · Restriction or exception
You must review self-billed invoices, report errors, and keep SMP told of your Indirect Tax registration
The User must review the self-billed invoices in its Stripe Dashboard and tell SMP of any errors through Stripe support. The User must give SMP its Indirect Tax registration number, such as a VAT or GST number, and must immediately tell SMP in writing if the number changes, if the User stops being registered for Indirect Tax in any jurisdiction, or if its Indirect Tax status otherwise changes. Failing to do so may invalidate the self-billed invoices.
Supporting quotations
User must review the self-billed invoices in User’s Stripe Dashboard and must notify SMP of any errors by contacting [Stripe support](https://stripe.com/contact).
User must provide SMP its Indirect Tax registration number (e.g., VAT/GST number). User must immediately inform SMP in writing if (a) User’s Indirect Tax registration number changes, (b) User ceases to be registered for Indirect Tax purposes in any jurisdiction, or (c) User’s Indirect Tax status is otherwise altered. Failure to do so may result in the invalidation of the self-billed invoices.
Qualifications & exceptions
Changes must be reported immediately and in writing.
Failure may invalidate the self-billed invoices.
Not stated here
The terms set no deadline for reporting invoice errors.
Charges & Financial Obligations · User right or choice
You must supply the information for self-billed invoices and may opt out in writing, then invoice SMP yourself
The User is responsible for giving all the necessary and accurate information SMP needs to generate the self-billed invoices. The User may opt out of the self-billing arrangement by notifying Stripe in writing, and if it does it is responsible for providing SMP invoices for all deemed sales of the Product made to SMP.
Supporting quotations
User is responsible for providing all necessary and accurate information for SMP to generate the self-billed invoices. User may opt out of this self-billing arrangement by notifying Stripe in writing. If User opts out, then User is responsible for providing SMP invoices for all deemed sales of Product made by User to SMP.
Qualifications & exceptions
Opting out requires written notice to Stripe.
Not stated here
The terms do not say when an opt-out takes effect.
Charges & Financial Obligations · Company practice
Fees exclude Taxes; SMP may add or withhold Taxes on Fees and deduct them, unless you give an exemption certificate
Section 5 replaces section 7.3 (Taxes) of the General Terms, which is not part of this saved text. The Fees exclude all Taxes unless the Stripe Pricing Page or other documents expressly say otherwise. If Law requires SMP or its Affiliates to collect or withhold Taxes, they will do so as additional amounts to the Fees, deduct them from amounts owed to the User or charge the User if there are not enough such amounts, and pay them to the taxing authority. If the User is exempt or eligible for a reduced rate, it must give SMP a copy of the original qualifying certificate, and SMP will not deduct the Taxes the certificate covers. Failing to provide a valid VAT or GST identification number may lead to Taxes being assessed and deducted from the User's balance or invoiced.
Supporting quotations
5. Taxes on Fees.
(a) Taxes. This Section 5 (Taxes on Fees) replaces section 7.3 (Taxes) of the General Terms. The Fees exclude all Taxes, except as the Stripe Pricing Page or other documents expressly state to the contrary. If SMP or its Affiliates are required by Law to collect or withhold any Taxes, SMP or its Affiliates will collect or withhold such Taxes as additional amounts to the Fees and either deduct those Taxes from amounts otherwise owed to User or charge User for the additional Taxes if there are insufficient amounts owed to User from which to deduct the Taxes, and pay those Taxes to the appropriate taxing authority. If User is exempt from paying, or is otherwise eligible to pay a reduced rate on, those Taxes, User will provide to SMP a copy of the original certificate that satisfies applicable legal requirements attesting to User’s tax-exempt status or reduced rate eligibility, in which case SMP or its Affiliates will not deduct the Taxes that certificate covers. Failure to provide SMP a valid VAT or GST identification number may result in the assessment and applicability of Taxes, which will be deducted from User’s Stripe Account balance or Stripe may invoice User for those amounts.
Qualifications & exceptions
Exemption needs the original certificate meeting legal requirements.
A missing valid VAT or GST number can lead to Taxes being assessed.
Not stated here
General Terms section 7.3, which this replaces, is not supplied here.
Legal Rights & Agreement Rules · Restriction or exception
You must give accurate tax information when reasonably asked, and failing to is a material breach
The User must give accurate information about its tax affairs when SMP or its Affiliates reasonably ask, and must promptly tell SMP if any information Stripe prepopulates is inaccurate or incomplete. The User's failure to provide accurate, complete or up-to-date information or documentation when these terms or the Documentation require it is a material breach of the Managed Payments Terms.
Supporting quotations
(b) User Information. User must provide accurate information regarding User’s tax affairs as SMP or its Affiliates reasonably request, and must promptly notify SMP if any information that Stripe prepopulates is inaccurate or incomplete.
User’s failure to provide accurate, complete, or up‑to‑date information or documentation when required by these Stripe Managed Payments Terms or the Documentation is a material breach of these Stripe Managed Payments Terms.
Qualifications & exceptions
Applies to information SMP reasonably requests and to prepopulated information.
Not stated here
The terms do not say what remedies follow from the material breach.
Sharing & Disclosure · Permission or license
SMP may send tax documents to you and to Government Authorities and may file periodic informational returns
SMP or its Affiliates may send documents about transactions processed through the Services to the User and to any relevant Government Authority. Law may require them to file periodic informational returns with a Government Authority related to the User's use of the Services, and they may send tax-related information to the User electronically.
Supporting quotations
SMP or its Affiliates may send documents to User and any relevant Government Authority for transactions processed using the Services. Specifically, Law may require SMP or its Affiliates to file periodic informational returns with a Government Authority related to User’s use of the Services. SMP or its Affiliates may send tax-related information to User electronically.
Qualifications & exceptions
Filings are described as what Law may require.
Not stated here
The terms do not say which documents or what information go to the authority.
Use & Processing · Permission or license
Stripe includes SMP for privacy terms and may use Personal Data to run the service and ancillary activities
For the Privacy and Data Use section of the General Terms, references to Stripe also include SMP. By using the Service the User authorizes Stripe and its Affiliates to process Personal Data under applicable DP Law and the Data Processing Agreement. The User also authorizes them to use Personal Data, as Stripe determines, to provide the Service and for ancillary activities including customer support, order management, facilitating order fulfillment, managing tax remittance and ensuring legal compliance, in line with DP Law and the Data Processing Agreement.
Supporting quotations
6. Data Privacy.
6.1 Generally.
For purposes of the Privacy and Data Use section of the General Terms, references to Stripe also include SMP. By using the Stripe Managed Payments Service, User authorizes Stripe and its Affiliates to process Personal Data in accordance with applicable DP Law and the Data Processing Agreement. User also authorizes Stripe and its Affiliates to use Personal Data, as determined by Stripe, in connection with providing Stripe Managed Payments Service and for activities ancillary to the Stripe Managed Payments Service, including customer support, order management, facilitating order fulfillment, managing tax remittance, and ensuring compliance with applicable Law, in accordance with applicable DP Law and the Data Processing Agreement.
Qualifications & exceptions
Use is under applicable DP Law and the Data Processing Agreement.
Use covers the Service and ancillary activities, as Stripe determines.
Not stated here
The Data Processing Agreement and the General Terms' privacy section are not in this saved text.
Retention & Deletion · Company commitment
SMP honors valid Customer deletion requests in Stripe systems, tells you, and may let you review concerns
In line with applicable DP Law, SMP will honor valid deletion requests from Customers who bought through the Service. On a valid request, SMP manages deletion of the Customer's Personal Data within Stripe systems for SMP, including Customer Personal Data the User shared with Stripe and stored there. SMP will notify the User of the request and the actions taken, and will endeavor to give the User the chance to review the request with SMP if SMP has specific concerns or legal obligations in mind.
Supporting quotations
6.2 Customer Data Deletion.
In compliance with applicable DP Law, SMP will honor valid deletion requests from Customers who made a purchase through Stripe Managed Payments Service. Upon receiving a valid deletion request, SMP will manage the deletion of the Customer’s Personal Data within Stripe systems for SMP, including any Customer Personal Data User shared with Stripe and stored on Stripe systems. SMP will notify User of the deletion request and actions taken. SMP will endeavor to provide User the opportunity to review the request with SMP if SMP believes there are specific concerns or legal obligations.
Qualifications & exceptions
Applies to valid deletion requests under DP Law.
The chance to review the request is an endeavor, not a promise.
Not stated here
The terms do not state how quickly deletion happens.
Retention & Deletion · Restriction or exception
You handle deletion requests you receive directly and data you collect, and must cooperate and follow DP Law
SMP is not responsible for deletion requests the User receives directly from Customers, or for deleting Personal Data the User collects from Customers; the User must manage those requests. The User agrees to cooperate and to make sure any additional data it controls is handled in line with DP Law.
Supporting quotations
SMP is not responsible for managing any deletion requests that User receives directly from Customers or for the deletion of Personal Data that User collects from Customers. User is responsible for managing those deletion requests. User agrees to cooperate and ensure that any additional data User controls is handled in compliance with DP Law.
Qualifications & exceptions
Covers requests sent to the User directly and data the User itself collects.
Account & Service Control · Restriction or exception
Your Products must be lawful, non-infringing and defect-free, and your Customer contracts must match these terms
Before using the Service and at all times during the Term, the User will (a) make sure the goods or services it sells are Products, are not restricted for sale under applicable Law (for example export control laws), do not violate or infringe third-party rights such as IP Rights, and do not cause SMP to violate Law; (b) amend its Customer agreements as needed to comply with these terms; (c) make sure those agreements include the disclosures and links to Stripe's or its Affiliate's Customer terms that SMP and its Affiliates require; and (d) keep its Products free of defects while it controls them.
Supporting quotations
7. User Obligations.
Before using the Stripe Managed Payments Service, and at all times during the Term, User will:
(a) Ensure the goods or services for which User uses the Stripe Managed Payments Service are Products, and are not restricted for sale under any applicable Law (e.g., export control laws), do not violate or infringe any third-party rights (e.g., IP Rights), and do not cause SMP to violate any applicable Law;
(b) Make such amendments to User’s agreements with its Customers as are necessary to comply with these Stripe Managed Payments Terms;
(c) Ensure User’s agreements with Customers include all necessary disclosures and links to Stripe’s or its Affiliate’s Customer terms required by SMP and its Affiliates;
(d) Ensure User’s Products are free of defects while User has control over the Product;
Qualifications & exceptions
The duties apply before use and at all times during the Term.
The defect-free duty applies while the User has control over the Product.
Security & Safeguards · Restriction or exception
If your Product is a DORA ICT service sold into the EU, you must meet organizational resilience requirements
To the extent the User's Product is an ICT service within the meaning of DORA, and the User sells into the EU, the User must comply with organizational resilience requirements.
Supporting quotations
Before using the Stripe Managed Payments Service, and at all times during the Term, User will:
(e) To the extent User’s Product is an “ICT service” within the meaning of DORA, and if User sells into the EU, comply with organizational resilience requirements;
Qualifications & exceptions
Applies only to an ICT service within the meaning of DORA sold into the EU.
Not stated here
The terms do not say which resilience requirements apply.
Account & Service Control · Restriction or exception
You may not use the service to sell NFTs, cryptocurrency, virtual currency or similar digital assets
The User must not use the Managed Payments Service to sell non-fungible tokens, cryptocurrency, virtual currency or similar digital assets.
Supporting quotations
Before using the Stripe Managed Payments Service, and at all times during the Term, User will:
(f) Not use the Stripe Managed Payments Services to sell non-fungible tokens, cryptocurrency, virtual currency, and similar digital assets; and
Not stated here
The terms do not define similar digital assets.
Account & Service Control · Restriction or exception
No selling Prohibited or Restricted Business products, or dealing with such a business, without written approval
The User must not use the Service to sell Products on the Prohibited or Restricted Business List, conduct a Prohibited or Restricted Business, transact with one, or enable any individual or entity (including the User) to benefit from one, unless Stripe has pre-approved that business in writing.
Supporting quotations
Before using the Stripe Managed Payments Service, and at all times during the Term, User will:
(g) Not use the Stripe Managed Payments Service to sell Products listed on the Prohibited or Restricted Business List, conduct a Prohibited or Restricted Business, transact with any Prohibited or Restricted Business, or enable any individual or entity (including User) to benefit from any Prohibited or Restricted Business, unless Stripe has pre-approved the respective Prohibited or Restricted Business in writing.
Qualifications & exceptions
The only exception is Stripe's written pre-approval of the specific business.
Not stated here
The Prohibited or Restricted Business List is a separate document and is not supplied here.
Legal Rights & Agreement Rules · Restriction or exception
Stripe gives no legal, tax or accounting advice and is not liable for your Products or added legal and tax liabilities
The User acknowledges that Stripe and its Affiliates, including SMP, do not provide legal, tax or accounting advice as part of the Service. The User remains fully responsible for, and the Stripe Parties are not liable for, any losses, damages, costs, fines, fees or penalties related to (a) the User's Products, defects in them, its sales of Products to Customers, or a Customer's use, misuse or inability to use them, and (b) any additional legal, regulatory or Tax liabilities arising from the User's use of the Service.
Supporting quotations
8. Disclaimers.
User acknowledges that Stripe and its Affiliates, including SMP, do not provide legal, tax, or accounting advice as part of the Stripe Managed Payments Service. User remains fully responsible for, and the Stripe Parties are not liable for, any losses, damages, costs, fines, fees, or penalties related to:
(a) User’s Products, defects with User’s Products, User’s sale of Products to Customers, or a Customer’s use, misuse, or inability to use User’s Products; and
(b) any additional legal, regulatory, or Tax liabilities arising from User’s use of the Stripe Managed Payments Service.
Qualifications & exceptions
The disclaimer covers both product-related losses and additional legal, regulatory or Tax liabilities.
Legal Rights & Agreement Rules · Restriction or exception
You defend and indemnify the Stripe Parties against Claims about your Products, sales and Customers' use of them
The User will defend the Stripe Parties against, and indemnify them for Stripe Losses arising out of, Claims relating to (a) the User's Products, including Claims that they infringe or misappropriate the third party's rights such as IP Rights, (b) the User's sale of Products to Customers, or (c) Customers' use, misuse or inability to use the Products. Customers count as third parties for Claims under this section or the General Terms. Stripe Losses are the amounts awarded to the third party making a Claim, plus penalties, fines and third-party costs, including legal fees, paid by the Stripe Parties.
Supporting quotations
9. Indemnification.
User will defend the Stripe Parties against, and indemnify the Stripe Parties for Stripe Losses arising out of, any Claims relating to (a) User’s Products (including any Claims that User’s Products infringe on or misappropriate the rights, including IP Rights, of the third party making the Claim), (b) User’s sale of Products to Customers, or (c) Customers’ use, misuse, or inability to use User’s Products. For clarity, Customers are third parties for purposes of Claims under this section or under the General Terms.
“Stripe Losses” means all amounts awarded to the third party making a Claim, and all penalties, fines, and third-party costs (including legal fees) paid by the Stripe Parties.
Qualifications & exceptions
Includes a duty to defend as well as to indemnify.
Customers are third parties for Claims.
Not stated here
Whether any cap applies is not stated here.
Account & Service Control · Context
Definitions: Product (eligible digital product per the Documentation) and Seller
A Product is the eligible software as a service, digital good or digital product, as the Documentation describes, that the User, as Seller, makes available for sale to Customers through the Service. A Seller is the User using the Service to sell Product to Customers.
Supporting quotations
“Product” means the eligible software as a service, digital good, or digital product as described in the [Documentation](https://docs.stripe.com/payments/managed-payments/eligibility) that User, as Seller, makes available for sale to Customers via the Stripe Managed Payments Service.
“Seller” means the User using the Stripe Managed Payments Service to sell Product to Customers.
Qualifications & exceptions
Only items that meet the Documentation's eligibility description count as Products.
Not stated here
The eligibility rules are on a linked Documentation page and are not in this text.
Charges & Financial Obligations · Context
Definitions: Acquiring Affiliates, Free Trial and Indirect Tax
Acquiring Affiliates are Stripe's Affiliates or Payment Method Acquirers identified in the Documentation that SMP may use, through the Stripe Payments Services, to acquire Transactions for the Service. A Free Trial is the provision of free digital goods or services, trial periods, samples or promotional services. Indirect Tax means applicable transaction taxes and duties imposed by a Governmental Authority, including sales and use tax, VAT and GST or equivalent transaction taxes.
Supporting quotations
“Acquiring Affiliates” means Stripe’s Affiliates or Payment Method Acquirers as identified in the Documentation which SMP may provide access to via the Stripe Payments Services to acquire Transactions in connection with the Stripe Managed Payments Service.
“Free Trial” means the provision of free digital goods and/or services, trial periods, samples, or promotional services.
“Indirect Tax” or “Indirect Taxes" means any applicable transaction taxes and duties imposed by any Governmental Authority, including sales and use tax, value-added tax (VAT), and goods and services tax (GST), or equivalent transaction taxes.
Qualifications & exceptions
Indirect Tax uses “including”, so the listed taxes are examples.
Not stated here
The Acquiring Affiliates are named in the Documentation, which is not in this text.
Legal Rights & Agreement Rules · Context
Regional Terms apply to listed countries and prevail over the Managed Payments Terms in a conflict
The Regional Terms apply for the countries or regions listed below them, and if they conflict with the Managed Payments Terms the Regional Terms prevail. The first listed region is Australia: its Regional Terms apply for Users in Australia.
Supporting quotations
11. Regional Terms.
The following Regional Terms apply for the countries or regions below. If there is a conflict between the Stripe Managed Payments Terms and the Regional Terms, the Regional Terms prevail.
Australia.
The following Regional Terms apply for Users in Australia.
Qualifications & exceptions
The Regional Terms win in a conflict.
Not stated here
Terms for the other listed regions sit in later sections.
Account & Service Control · Permission or license
Australia: SMP may suspend or end your use at once on listed events, or at any time on 30 days' notice
For Users in Australia, the Managed Payments Service applies only to Transactions for eligible Products the User elects to sell, the User's Stripe Account is treated as a Connected Account to SMP as the Platform, and the Connected Account Agreement is incorporated. SMP may suspend or terminate the User's use (i) with immediate effect on notifying the User if an event listed in Section 10.1(b) (Suspension and Termination by Stripe) of the General Terms occurs, or (ii) at any time on 30 days' notice. If SMP or its Affiliates decide products are not eligible, they may require the User to stop using the Service for them or offboard them. This replaces the base clause's right to suspend or terminate at any time with a 30-day notice route.
Supporting quotations
11.1 Use of the Service and Termination.
Stripe Managed Payments Service will only apply to Transactions for eligible Products User elects to sell via the Stripe Managed Payments Service. By using the Stripe Managed Payments Service, User’s Stripe Account is treated as a Connected Account to SMP as the Platform. These Stripe Managed Payments Terms incorporate by reference the Connected Account Agreement. SMP reserves the right to suspend or terminate User’s use of the Stripe Managed Payments Service (i) with immediate effect upon notifying User if any event listed in Section 10.1(b) (Suspension and Termination by Stripe) of the General Terms occurs; or (ii) at any time upon 30 days’ notice to User. If SMP or its Affiliates determines that User’s products do not qualify as eligible Products, SMP and its Affiliates may (i) require User to stop using the Stripe Managed Payments Service for the ineligible products, or (ii) offboard the ineligible products from the Stripe Managed Payments Service.
Qualifications & exceptions
Immediate suspension needs a General Terms 10.1(b) event and notice to the User.
Otherwise 30 days' notice is required for the Australian Regional Terms.
Not stated here
General Terms section 10.1(b), which lists the events, is not part of this saved text.
Australia: your refund request is an instruction to Stripe Payment Australia Pty Ltd to start the refund
In Australia, in addition to the refund provisions of Section 3.3 (Refund Policy), if the Seller asks for a refund to be applied to a Transaction, that request is an instruction to Stripe Payment Australia Pty Ltd to start the process to refund the Transaction.
Supporting quotations
11.2 Refund Policy.
In addition to the provisions on Refunds in Section 3.3 (Refund Policy), if Seller requests a refund be applied to a Transaction, that request constitutes an instruction to Stripe Payment Australia Pty Ltd to initiate the process to refund the Transaction.
Qualifications & exceptions
Adds to Section 3.3 rather than replacing it.
Charges & Financial Obligations · Restriction or exception
Australia: you do not bear payment method costs and liability that arise from Stripe's negligence, fraud or misconduct
In Australia, a clause is added to the beginning of Section 3.7 (Liability for Payment Methods): “Except to the extent the costs, fees, fines, charges or liability arises out of Stripe's negligence, fraud or willful misconduct,”. The pass-through of acquirer, provider and Card Network costs and liabilities to the User therefore does not apply to the extent they arise from Stripe's negligence, fraud or willful misconduct.
Supporting quotations
11.3 Liability for Payment Methods.
In addition to the provisions on liability for Payment Methods in Section 3.7 (Liability for Payment Methods), the following clause is added to the beginning of Section 3.7: “Except to the extent the costs, fees, fines, charges or liability arises out of Stripe’s negligence, fraud or willful misconduct,”
Qualifications & exceptions
The carve-out is limited to the extent the cost or liability arises from Stripe's negligence, fraud or willful misconduct.
Legal Rights & Agreement Rules · User right or choice
Australia: Australian Consumer Law rights and guarantees that cannot be excluded are not excluded by this agreement
To the extent the User acquires goods or services from Stripe as a consumer within the meaning of the Australian Consumer Law, the User has rights and remedies, including consumer guarantee rights, that cannot be excluded, restricted or modified by agreement. Nothing in the Agreement excludes, restricts or modifies any implied condition, warranty or guarantee, or any right, remedy or liability under law, where doing so would contravene that law or make a term of the agreement void.
Supporting quotations
11.4 Disclaimers.
To the extent that User acquires goods or services from Stripe as a consumer within the meaning of the Australian Consumer Law as set out in the Competition and Consumer Act 2010 (Cth), User has certain rights and remedies (including consumer guarantee rights) that cannot be excluded, restricted or modified by agreement. Nothing in this Agreement operates to exclude, restrict or modify the application of any implied condition, warranty or guarantee, or the exercise of any right or remedy, or the imposition of any liability under law where to do so would: (a) contravene that law; or (b) cause any term of this agreement to be void.
Qualifications & exceptions
Applies only to the extent the User is a consumer within the meaning of the Australian Consumer Law.
Not stated here
Whether a business User counts as a consumer depends on the Australian Consumer Law, which is not supplied.
Legal Rights & Agreement Rules · Restriction or exception
Australia: no advice and no Stripe liability for your Products or added liabilities, except Stripe's fault
The User acknowledges Stripe and its Affiliates, including SMP, do not give legal, tax or accounting advice through the Service. Except to the extent a loss arises from Stripe's breach of the Agreement, negligence, fraud or willful misconduct, the User remains fully responsible for, and the Stripe Parties are not liable for, losses, damages, costs, fines, fees or penalties related to (a) the User's Products, their defects, its sales to Customers, or a Customer's use, misuse or inability to use them, and (b) additional legal, regulatory or Tax liabilities from using the Service. The base clause has no exception for Stripe's own fault.
Supporting quotations
User acknowledges that Stripe and its Affiliates, including SMP, do not provide legal, tax, or accounting advice as part of the Stripe Managed Payments Service. Except to the extent the loss arises out of Stripe’s breach of this Agreement, negligence, fraud or willful misconduct, User remains fully responsible for, and the Stripe Parties are not liable for, any losses, damages, costs, fines, fees, or penalties related to:
(a) User’s Products, defects with User’s Products, User’s sale of Products to Customers, or a Customer’s use, misuse, or inability to use User’s Products; and
(b) any additional legal, regulatory, or Tax liabilities arising from User’s use of the Stripe Managed Payments Service.
Qualifications & exceptions
The exception covers Stripe's breach of the Agreement, negligence, fraud or willful misconduct, to the extent the loss arises from them.
Legal Rights & Agreement Rules · Restriction or exception
Australia: your indemnity excludes Claims from Stripe's fault and extends to your fraud, gross negligence and breach
Except to the extent Claims arise from Stripe's breach of the Agreement, negligence, fraud or willful misconduct, the User will indemnify the Stripe Parties for Stripe Losses arising from Claims relating to (a) the User's Products, including infringement or misappropriation of third-party rights such as IP Rights, (b) its sales of Products to Customers, (c) Customers' use, misuse or inability to use the Products, (d) the User's fraud, gross negligence or willful misconduct related to the Service, or (e) the User's breach of these terms. Customers are third parties for Claims under Section 11.5. Compared with the base indemnity, this version does not mention a duty to defend and adds items (d) and (e).
Supporting quotations
11.5 Indemnification.
Except to the extent the Claims arise out of Stripe’s breach of this Agreement, negligence, fraud or willful misconduct, User will indemnify the Stripe Parties for Stripe Losses arising out of any Claims made relating to (a) User’s Products (including any Claims that User’s Products infringe on or misappropriate the rights, including IP Rights, of the third party making the Claim), (b) User’s sale of Products to Customers, (c) Customers’ use, misuse, or inability to use User’s Products, (d) User’s fraud, gross negligence, or willful misconduct related to use of the Stripe Managed Payments Service, or (e) User’s breach of these Stripe Managed Payments Terms. For clarity, Customers are third parties for purposes of Claims under this Section 11.5.
Qualifications & exceptions
The Stripe-fault exception applies to the extent Claims arise from Stripe's breach, negligence, fraud or willful misconduct.
Charges & Financial Obligations · Company practice
Australia: SMP collects and remits GST on your digital service sales to Australian customers
To the extent the User is established in Australia, the User agrees that SMP, as an electronic distribution platform under Australian GST Law, is responsible for collecting and remitting GST under s84-60 of the Australian GST Act on the User's sales of digital services to its customers in Australia.
Supporting quotations
11.6 Tax.
To the extent that User is established in Australia, User agrees, by way of entering into these Stripe Managed Payments Terms, that SMP, as an electronic distribution platform under Australian GST Law, will be responsible for collecting and remitting GST, under s84-60 of the Australian GST Act, on User’s sales of digital services to User’s customers in Australia.
Qualifications & exceptions
Applies to Users established in Australia and sales of digital services to customers in Australia.
Charges & Financial Obligations · Restriction or exception
Australia: you must not charge GST separately on SMP sales and remain responsible for GST outside the platform
The User must not charge or account for GST separately on Products provided through SMP to Australia-based Customers. The User remains responsible for GST on any supplies made outside the SMP platform and for its own compliance obligations under the Australian GST Act generally.
Supporting quotations
User must not charge or account for GST separately on the Products provided via SMP to User’s Australia-based Customers. User remains responsible for GST on any supplies made outside of the SMP platform, and for the User’s own compliance obligations under the Australian GST Act generally.
Qualifications & exceptions
The ban on separate GST applies to Products provided through SMP to Australia-based Customers.
Charges & Financial Obligations · Company practice
Canada: all retail payment activities are provided solely by Stripe Payments Canada, Ltd., an RPAA-registered provider
For Canada, all retail payment activities, as defined under the Retail Payment Activities Act (Canada) (RPAA), are provided solely by Stripe Payments Canada, Ltd., which is registered as a payment service provider under the RPAA.
Supporting quotations
Canada.
11.1 Retail Payment Activities.
All retail payment activities, as defined under the Retail Payment Activities Act (Canada) ("RPAA") are provided solely by Stripe Payments Canada, Ltd., which is registered as a payment service provider under the RPAA.
Qualifications & exceptions
Covers retail payment activities as the RPAA defines them.
Not stated here
The RPAA is an external law and is not supplied.
Legal Rights & Agreement Rules · Restriction or exception
Malaysia: Stripe disclaims all warranties and statutory guarantees on the service to the maximum extent allowed
For Users in Malaysia, except where these terms expressly state a “warranty”, and to the maximum extent Law permits, Stripe and its Affiliates make no express or implied warranties or statutory guarantees about (a) the Managed Payments Service or (b) their performance under the terms, and disclaim them all.
Supporting quotations
Malaysia.
11.1 Disclaimers.
Except when expressly stated as a “warranty” in these Stripe Managed Payments Terms, to the maximum extent permitted by Law, Stripe and its Affiliates do not make any, and disclaim all, express and implied warranties and statutory guarantees with respect to (a) the Stripe Managed Payments Service, and (b) Stripe’s and its Affiliates’ performance under these Stripe Managed Payments Service Terms.
Qualifications & exceptions
Disclaimer is to the maximum extent Law permits.
Does not apply where the terms expressly state a “warranty”.
Legal Rights & Agreement Rules · Restriction or exception
Malaysia: no advice, and no Stripe liability for your Products or added liabilities, except gross negligence or breach
The User acknowledges Stripe and its Affiliates, including SMP, do not give legal, tax or accounting advice through the Service. The User remains fully responsible for, and the Stripe Parties are not liable for (except due to the Stripe Parties' gross negligence or breach of contract), losses, damages, costs, fines, fees or penalties related to (a) the User's Products, their defects, its sales to Customers, or a Customer's use, misuse or inability to use them, and (b) additional legal, regulatory or Tax liabilities from using the Service.
Supporting quotations
User acknowledges that Stripe and its Affiliates, including SMP, do not provide legal, tax, or accounting advice as part of the Stripe Managed Payments Service. User remains fully responsible for, and the Stripe Parties are not liable for (except due to gross negligence or breach of contract by the Stripe Parties), any losses, damages, costs, fines, fees, or penalties related to:
(a) User’s Products, defects with User’s Products, User’s sale of Products to Customers, or a Customer’s use, misuse, or inability to use User’s Products; and
(b) any additional legal, regulatory, or Tax liabilities arising from User’s use of the Stripe Managed Payments Service.
Qualifications & exceptions
The exception covers the Stripe Parties' gross negligence or breach of contract.
Account & Service Control · Permission or license
New Zealand: SMP may suspend or end your use at once on listed events, or at any time on 30 days' notice
For Users in New Zealand, the Managed Payments Service applies only to Transactions for eligible Products the User elects to sell, the User's Stripe Account is treated as a Connected Account to SMP as the Platform, and the Connected Account Agreement is incorporated. SMP may suspend or terminate the User's use (i) with immediate effect on notifying the User if an event listed in Section 10.1(b) (Suspension and Termination by Stripe) of the General Terms occurs, or (ii) at any time on 30 days' notice. If SMP or its Affiliates decide products are not eligible, they may require the User to stop using the Service for them or offboard them.
Supporting quotations
The following Regional Terms apply for Users in New Zealand.
(a) Stripe Managed Payments Service will only apply to Transactions for eligible Products User elects to sell via the Stripe Managed Payments Service. By using the Stripe Managed Payments Service, User’s Stripe Account is treated as a Connected Account to SMP as the Platform. These Stripe Managed Payments Terms incorporate by reference the Connected Account Agreement. SMP reserves the right to suspend or terminate User’s use of the Stripe Managed Payments Service (i) with immediate effect upon notifying User if any event listed in Section 10.1(b) (Suspension and Termination by Stripe) of the General Terms occurs; or (ii) at any time upon 30 days’ notice to User. If SMP or its Affiliates determines that User’s products do not qualify as eligible Products, SMP and its Affiliates may (i) require User to stop using the Stripe Managed Payments Service for the ineligible products, or (ii) offboard the ineligible products from the Stripe Managed Payments Service.
Qualifications & exceptions
Immediate suspension needs a General Terms 10.1(b) event and notice to the User.
Otherwise 30 days' notice is required for the New Zealand Regional Terms.
Not stated here
General Terms section 10.1(b), which lists the events, is not part of this saved text.
Charges & Financial Obligations · Company practice
New Zealand: Stripe New Zealand Limited is the registered financial service provider and AML reporting entity
In New Zealand, Stripe New Zealand Limited is the registered financial service provider and AML reporting entity responsible for providing financial services connected with the Managed Payments Service, including managing the relevant means of payment and transferring and settling funds to the Seller, in line with these terms.
Supporting quotations
(b) Stripe New Zealand Limited is the registered financial service provider and AML reporting entity responsible for the provision of financial services in connection with the Stripe Managed Payments Service in New Zealand, including managing the relevant means of payment, and transferring and settling funds to the Seller, in accordance with these Stripe Managed Payments Terms.
Qualifications & exceptions
Responsibility is for financial services connected with the Service in New Zealand.
Charges & Financial Obligations · Restriction or exception
New Zealand: you do not bear payment method costs and liability that arise from Stripe's negligence, fraud or misconduct
In New Zealand, a clause is added to the beginning of Section 3.7 (Liability for Payment Methods): “Except to the extent the costs, fees, fines, charges or liability arises out of Stripe's negligence, fraud or willful misconduct,”. The pass-through of acquirer, provider and Card Network costs and liabilities to the User therefore does not apply to the extent they arise from Stripe's negligence, fraud or willful misconduct.
Supporting quotations
11.2 Liability for Payment Methods.
In addition to the provisions on liability for Payment Methods in Section 3.7 (Liability for Payment Methods), the following clause is added to the beginning of Section 3.7: “Except to the extent the costs, fees, fines, charges or liability arises out of Stripe’s negligence, fraud or willful misconduct,”
Qualifications & exceptions
The carve-out is limited to the extent the cost or liability arises from Stripe's negligence, fraud or willful misconduct.
Legal Rights & Agreement Rules · User right or choice
New Zealand: consumer rights and guarantees that cannot be excluded are not excluded by this agreement
To the extent the User acquires goods or services from Stripe as a consumer, the User has rights and remedies, including consumer guarantee rights, that cannot be excluded, restricted or modified by agreement. Nothing in the Agreement excludes, restricts or modifies any implied condition, warranty or guarantee, or any right, remedy or liability under law, where doing so would contravene that law or make a term of the agreement void.
Supporting quotations
11.3 Disclaimers.
To the extent that User acquires goods or services from Stripe as a consumer, User have certain rights and remedies (including consumer guarantee rights) that cannot be excluded, restricted or modified by agreement. Nothing in this Agreement operates to exclude, restrict or modify the application of any implied condition, warranty or guarantee, or the exercise of any right or remedy, or the imposition of any liability under law where to do so would: (a) contravene that law; or (b) cause any term of this agreement to be void.
Qualifications & exceptions
Applies only to the extent the User acquires goods or services from Stripe as a consumer.
Not stated here
The New Zealand clause does not name the consumer law it relies on, unlike the Australian clause.
Legal Rights & Agreement Rules · Restriction or exception
New Zealand: no advice and no Stripe liability for your Products or added liabilities, except Stripe's fault
The User acknowledges Stripe and its Affiliates, including SMP, do not give legal, tax or accounting advice through the Service. Except to the extent a loss arises from Stripe's breach of the Agreement, negligence, fraud or willful misconduct, the User remains fully responsible for, and the Stripe Parties are not liable for, losses, damages, costs, fines, fees or penalties related to (a) the User's Products, their defects, its sales to Customers, or a Customer's use, misuse or inability to use them, and (b) additional legal, regulatory or Tax liabilities from using the Service.
Supporting quotations
User acknowledges that Stripe and its Affiliates, including SMP, do not provide legal, tax, or accounting advice as part of the Stripe Managed Payments Service. Except to the extent the loss arises out of Stripe’s breach of this Agreement, negligence, fraud or willful misconduct, User remains fully responsible for, and the Stripe Parties are not liable for, any losses, damages, costs, fines, fees, or penalties related to:
(a) User’s Products, defects with User’s Products, User’s sale of Products to Customers, or a Customer’s use, misuse, or inability to use User’s Products; and
(b) any additional legal, regulatory, or Tax liabilities arising from User’s use of the Stripe Managed Payments Service.
Qualifications & exceptions
The exception covers Stripe's breach of the Agreement, negligence, fraud or willful misconduct, to the extent the loss arises from them.
Legal Rights & Agreement Rules · Restriction or exception
New Zealand: your indemnity excludes Claims from Stripe's fault and extends to your fraud, gross negligence and breach
Except to the extent Claims arise from Stripe's breach of the Agreement, negligence, fraud or willful misconduct, the User will indemnify the Stripe Parties for Stripe Losses arising from Claims relating to (a) the User's Products, including infringement or misappropriation of third-party rights such as IP Rights, (b) its sales of Products to Customers, (c) Customers' use, misuse or inability to use the Products, (d) the User's fraud, gross negligence or willful misconduct related to the Service, or (e) the User's breach of these terms. Customers are third parties for Claims under Section 11.4.
Supporting quotations
11.4 Indemnification.
Except to the extent the Claims arise out of Stripe’s breach of this Agreement, negligence, fraud or willful misconduct, User will indemnify the Stripe Parties for Stripe Losses arising out of any Claims made relating to (a) User’s Products (including any Claims that User’s Products infringe on or misappropriate the rights, including IP Rights, of the third party making the Claim), (b) User’s sale of Products to Customers, (c) Customers’ use, misuse, or inability to use User’s Products, (d) User’s fraud, gross negligence, or willful misconduct related to use of the Stripe Managed Payments Service, or (e) User’s breach of these Stripe Managed Payments Terms. For clarity, Customers are third parties for purposes of Claims under this Section 11.4.
Qualifications & exceptions
The Stripe-fault exception applies to the extent Claims arise from Stripe's breach, negligence, fraud or willful misconduct.
Not stated here
Whether any cap applies is not stated here.
Charges & Financial Obligations · Procedure
New Zealand: your refund request is an instruction to Stripe New Zealand Limited to start the refund
In New Zealand, in addition to the refund provisions of Section 3.3 (Refund Policy), if the Seller asks for a refund to be applied to a Transaction, that request is an instruction to Stripe New Zealand Limited to start the process to refund the Transaction.
Supporting quotations
11.5 Refund Policy.
In addition to the provisions on Refunds in Section 3.3 (Refund Policy), if Seller requests a refund be applied to a Transaction, that request constitutes an instruction to Stripe New Zealand Limited to initiate the process to refund the Transaction.
Qualifications & exceptions
Adds to Section 3.3 rather than replacing it.
Charges & Financial Obligations · Context
United States: Section 2.2 (pooled accounts) is deleted and replaced for US Users
The United States Regional Terms apply to Users in the United States. They amend the Managed Payments Terms by deleting Section 2.2 (Provision of Services by Stripe to SMP; Pooled Accounts) and replacing it with new wording, which begins with the section heading and continues in the next section of the document.
Supporting quotations
United States.
The following Regional Terms apply to Users in the United States.
Section 2.2 of the Stripe Managed Payments Terms is deleted and replaced with the following:
2.2 Provision of Services by Stripe to SMP; Pooled Accounts.
Qualifications & exceptions
Applies only to Users in the United States.
Not stated here
The replacement wording follows in the next part of the document and is not covered by this card.
Charges & Financial Obligations · Company practice
United States: you appoint SMP as your agent for funds, and settlement funds are pooled with other users' funds
For US Users, the replacement Section 2.2 says SMP may provide access to Stripe Payment Services to facilitate the User's sales, and the User appoints SMP as its agent for the limited purpose of directing, receiving, holding and settling funds. All settlement funds Stripe, SMP or Acquiring Affiliates receive for Transactions are combined with other users' settlement funds and held in one or more Pooled Accounts at one or more Financial Providers. A Pooled Account is a pooled account to which Transaction settlement funds are credited.
Supporting quotations
2.2 Provision of Services by Stripe to SMP; Pooled Accounts.
SMP may provide access to the Stripe Payment Services in order to facilitate User’s sale of Products to Customers. User appoints SMP as User’s agent for the limited purpose of directing, receiving, holding and settling funds under this Agreement. All settlement funds that Stripe, SMP, or Acquiring Affiliates, as applicable, receive for Transactions are combined with settlement funds for other users and held in one or more Pooled Accounts at one or more Financial Providers.
“Pooled Account” means a pooled account to which Transaction settlement funds are credited.
Qualifications & exceptions
The agency is limited to directing, receiving, holding and settling funds.
Not stated here
The terms do not name the Financial Providers.
Charges & Financial Obligations · Company practice
United States: after an Acquiring Affiliate gets the funds the Customer owes nothing; recourse is to Stripe, SMP or SPC
For US Users, once an Acquiring Affiliate receives funds for a Transaction, the Customer has no further obligation to pay the User for it, whether or not and whenever Stripe or its Affiliate settles the funds. If Stripe, SMP or SPC (as applicable) does not settle funds due to the User, the User has recourse only against Stripe, SMP or SPC and not the Customer. Stripe or SMP will promptly update the User's Stripe Account balance to reflect processed Transactions. Compared with the base clause, the US version adds SPC as a party the User can look to. Acquiring Affiliates are Stripe's Affiliates or Payment Method Acquirers identified in the Documentation that SMP may use to acquire Transactions.
Supporting quotations
Once an Acquiring Affiliate receives funds for a Transaction, the relevant Customer has no further obligation to make payments to User with respect to that Transaction, regardless of whether and when Stripe or its Affiliate (as applicable) settles those funds to User. If Stripe, SMP or SPC (as applicable) does not settle funds due to User under this Agreement, User will have recourse only against Stripe, SMP or SPC (as applicable) and not the relevant Customer. Stripe or SMP (as applicable) will promptly update User’s Stripe Account balance to reflect processed Transactions.
“Acquiring Affiliates” means Stripe’s Affiliates or Payment Method Acquirers as identified in the Documentation which SMP may provide access to via the Stripe Payments Services to acquire Transactions in connection with the Stripe Managed Payments Service.
Qualifications & exceptions
The Customer's discharge does not depend on whether Stripe has settled the funds to the User.
Balance updates are promised promptly, not by a fixed deadline.
Not stated here
SPC is not defined in this saved text for this section; the Acquiring Affiliates are identified in the Documentation, which is not supplied.
Charges & Financial Obligations · Restriction or exception
United States: SMP's receipts bind you, Stripe may invest pooled funds, and you have no rights to the pool
For US Users, a receipt SMP gives a Customer as the User's agent is binding on the User. Stripe and its Affiliates may invest funds held in a Pooled Account as described in the General Terms. The User has no rights to any Pooled Account or to earnings its funds generate, and is not entitled to draw funds from any Pooled Account.
Supporting quotations
If, in the capacity as User’s agent, SMP provides a receipt for a Transaction to the applicable Customer, that receipt is binding on User.
Stripe and its Affiliates (as applicable) may invest funds held in a Pooled Account as described in the General Terms. User has no rights to any Pooled Account, or earnings generated by funds held in any Pooled Account, and is not entitled to draw funds from any Pooled Account.
Qualifications & exceptions
Receipts bind the User only where SMP provides them as the User's agent.
Investment is as the General Terms describe.
Not stated here
The General Terms' investment rules are not repeated here.
Charges & Financial Obligations · Context
Next-Day Settlement Terms add to the General and Financial Services Terms (last modified September 28, 2026)
These Next-Day Settlement Terms, last modified September 28, 2026, supplement the General Terms and the Stripe Financial Services Terms and govern the User's use of the Next-Day Settlement Services. Capitalized terms not defined here take their meaning from those two sets of terms.
Supporting quotations
Last modified: September 28, 2026
These terms (“Next-Day Settlement Terms”) supplement the General Terms and the Stripe Financial Services Terms and govern User’s use of the Next-Day Settlement Services. Capitalized terms that are not defined in these Next-Day Settlement Terms have the meanings given to them in the General Terms or the Stripe Financial Services Terms.
Charges & Financial Obligations · Company commitment
Funds are made available within one business day net of Refunds, Disputes and amounts owed, unless delayed or withheld
Stripe will make Next-Day Settlement Transaction funds available to the User in an eligible Stripe Account, net of Refunds, Disputes, Reversals and other amounts owed to Stripe, within the Next-Day Settlement Period, which is one business day from successful capture. This does not apply if a Next-Day Settlement Delay occurs or Stripe exercises a right under the Agreement to withhold or delay the transfer.
Supporting quotations
2. Next-Day Settlement Timing.
Stripe will make Next-Day Settlement Transaction funds available to User in an eligible Stripe Account, net of Refunds, Disputes, Reversals and other amounts owed to Stripe within the Next-Day Settlement Period, unless a Next-Day Settlement Delay occurs, or Stripe exercises a right under the Agreement to withhold or delay the transfer.
“Next-Day Settlement Period” means the period of one business day from the date of the successful capture of the Next-Day Settlement Transaction.
Qualifications & exceptions
Funds are net of Refunds, Disputes, Reversals and other amounts owed to Stripe.
The commitment does not apply during a Next-Day Settlement Delay or where Stripe exercises a right to withhold or delay.
Charges & Financial Obligations · Restriction or exception
The service is available only for enabled payment methods, Stripe-designated currencies and enabled Stripe Accounts
The Next-Day Settlement Services are available only for (a) Next-Day Settlement Payment Methods, meaning Payment Methods Stripe has enabled for the User's use of the services, (b) currencies Stripe designates in the Documentation, and (c) eligible Stripe Accounts that Stripe has enabled for the services.
Supporting quotations
3. Next-Day Settlement Conditions.
The Next-Day Settlement Services are only available for: (a) Next-Day Settlement Payment Methods; (b) currencies designated by Stripe in the Documentation; and (c) eligible Stripe Accounts that Stripe has enabled for use of the Next-Day Settlement Services.
“Next-Day Settlement Payment Method” means a Payment Method that Stripe has enabled for User’s use of the Next-Day Settlement Services.
Qualifications & exceptions
All three conditions must hold.
Not stated here
The designated currencies are listed in the Documentation, which is not in this text.
Charges & Financial Obligations · Permission or license
Stripe may extend settlement for all International Transactions once they exceed 10% of your average daily volume
This applies only if Stripe has enabled the User to make International Transactions. If International Transactions on a day exceed 10% of the average daily Transaction volume Stripe processes for the User over the trailing four weeks, Stripe may extend the settlement period for all International Transactions to the default Payout Schedule for the Territory and Next-Day Settlement Payment Method, until the average daily volume over the trailing four weeks falls below that threshold. An International Transaction is one where the charge is presented in a different currency from the Territory's default currency.
Supporting quotations
4. International Transactions.
This section applies only if Stripe has enabled User to make International Transactions. If International Transactions on a given day exceed 10% of the average daily Transaction volume Stripe processes for User as measured during the trailing four-week period, Stripe may extend the Next-Day Settlement Period for all International Transactions to the default Payout Schedule for the applicable Territory and Next-Day Settlement Payment Method until the average daily Transaction volume processed for User during the trailing four-week period falls below that threshold.
“International Transaction” means a Transaction Stripe processes for User in which the charge is presented in a different currency to the default currency of the Territory.
Qualifications & exceptions
Applies only if Stripe has enabled International Transactions for the User.
The extension covers all International Transactions, not only the excess.
Not stated here
The terms do not say how the 10% test relates to the day's volume when volumes are measured, or how soon Stripe applies an extension.
Account & Service Control · User right or choice
You may end the service in the Dashboard at any time; it takes effect next business day and default payout speed applies
The User may terminate its use of the Next-Day Settlement Services for an eligible Stripe Account at any time in the Stripe Dashboard. Termination takes effect on the next business day. After that, Transaction funds are settled to the Stripe Account at the default Payout Speed for the applicable Payment Method.
Supporting quotations
5. Termination of the Next-Day Settlement Services.
User may terminate its use of the Next-Day Settlement Services in respect of an eligible Stripe Account at any time in the Stripe Dashboard. Termination will become effective on the next business day. Following termination of the Next-Day Settlement Services, settlement of Transaction funds to the Stripe Account will be made in accordance with the default Payout Speed for the applicable Payment Method.
Qualifications & exceptions
Termination is per eligible Stripe Account.
Charges & Financial Obligations · Restriction or exception
Next-Day Settlement Delays include outages, wrong details, fraud screening, Financial Provider failure and bank limits
A Next-Day Settlement Delay is a delay to a Next-Day Settlement caused by (a) unavailability of a Financial Provider, Governmental Authority, telecommunications provider or internet service provider; (b) incorrect information, such as a bank account number, given to Stripe; (c) the User's equipment, software or technology; (d) a Force Majeure Event; (e) fraud or sanction screening required or requested by Stripe, its Financial Providers or recipient banks; (f) a Financial Provider's delay or failure to settle to Stripe, including from default, insolvency or bankruptcy; or (g) the recipient bank not being directly integrated with Stripe's clearing system, or the type of account not being supported, such as savings, money market, investment, multi-currency, foreign or correspondent accounts.
Supporting quotations
“Next-Day Settlement Delay” means a delay to a Next-Day Settlement caused by: (a) the unavailability of a Financial Provider, Governmental Authority, telecommunications provider, or internet service provider; (b) incorrect information, such as a bank account number, provided to Stripe; (c) User’s equipment, software, or other technology; (d) a Force Majeure Event; (e) fraud or sanction screening as required or requested by Stripe, its Financial Providers, or recipient banks; (f) a delay or failure of a Financial Provider to settle a Transaction to Stripe, including as a result of a Financial Provider’s default, insolvency, or bankruptcy; or (g) the recipient bank not being directly integrated with the clearing system used by Stripe or the type of recipient bank account not being supported by Stripe (e.g., a savings account, money market or investment account, multi-currency account, or foreign or correspondent account).
Qualifications & exceptions
During a delay the one-business-day timing does not apply.
Not stated here
The terms do not say how long a delay may last.
Charges & Financial Obligations · Context
Definitions: Next-Day Settlement, Services, Transaction, Payment Method and Territory
Next-Day Settlement is settlement of Next-Day Settlement Transaction funds to an eligible Stripe Account within one business day, and the Next-Day Settlement Services are the Services that let the User do that. A Next-Day Settlement Transaction is a transaction request on a Next-Day Settlement Payment Method, started through the Stripe Technology, by which Stripe is directed to capture funds for or from a payer's account for a payment from a Customer to the User, and it includes the authorization, settlement and any Disputes, Refunds and Reversals. Territory means the location of the User's Stripe Account or Accounts.
Supporting quotations
“Next-Day Settlement” means the settlement of Next-Day Settlement Transaction funds to an eligible Stripe Account within one business day.
“Next-Day Settlement Services” means the Services that enable User to make a Next-Day Settlement.
“Next-Day Settlement Transaction” means a Next-Day Settlement Payment Method transaction request initiated via the Stripe Technology through which Stripe is directed to capture funds for or from a payer’s associated account with respect to a payment from a Customer to User, and includes the authorization, settlement, and if applicable, Disputes, Refunds, and Reversals with respect to that Next-Day Settlement Payment Method transaction request.
“Territory” means the location of User’s Stripe Account(s).
Use & Processing · Context
Orchestrated Services Terms add to the General Terms (last modified September 28, 2026)
These Stripe Orchestrated Services Terms, last modified September 28, 2026, supplement the General Terms, which they incorporate by reference, and govern use of the Stripe Orchestrated Services. Capitalized terms not defined here take their General Terms meaning.
Supporting quotations
Last modified: September 28, 2026
These terms (“Stripe Orchestrated Services Terms”) supplement the General Terms which are incorporated into these terms by this reference, and govern the use of the Stripe Orchestrated Services. Capitalized terms that are not defined in these terms have the same meanings given to them in the General Terms.
Security & Safeguards · Restriction or exception
You must evidence and check each Third-Party PSP's PCI and AML and Sanctions compliance, and report failures at once
For each Third-Party PSP, meaning the User's or its Affiliate's third-party payment services provider to which the User routes Orchestrated Data, the User must (i) give Stripe evidence of its PCI-DSS compliance on request, annually; (ii) list it as a third-party service provider in the User's PCI attestation of compliance; (iii) immediately tell Stripe if it learns the PSP is not complying with PCI-DSS or is otherwise failing to safeguard the Orchestrated Data; and (v) on request, validate its compliance with AML and Sanctions Law annually.
Supporting quotations
(a) Ensuring Third-Party PSP Compliance. User must:
(i) provide Stripe with evidence of each Third-Party PSP’s compliance with PCI-DSS upon Stripe’s request, on an annual basis;
(ii) list each Third-Party PSP as User's third-party service provider in User's PCI attestation of compliance;
(iii) immediately notify Stripe if User becomes aware that a Third-Party PSP is not complying with PCI-DSS or is otherwise failing to safeguard the Orchestrated Data;
(v) upon request, validate each Third-Party PSP’s compliance with AML and Sanctions Law on an annual basis;
“Third-Party PSP” means User or User's Affiliate’s third-party payment services provider (such as a provider of payments processing, payments orchestration services, or token management services) to whom User directly or indirectly routes Orchestrated Data.
“AML and Sanctions Law” means all applicable anti-money laundering and sanctions laws, rules, regulations and other binding requirements of any Governmental Authority with jurisdiction in the United States, or with jurisdiction over the Stripe Orchestrated Services, Stripe or its Affiliates, User or its Affiliates, or a Third Party PSP, as applicable.
Qualifications & exceptions
Evidence and validation are due on request and on an annual basis.
Notice of non-compliance must be immediate.
Sharing & Disclosure · Restriction or exception
On request you must give Stripe information about Third-Party PSPs and your transactions with them
On request, the User must (iv) give Stripe information about a Third-Party PSP that Stripe determines it needs to comply with Law or meet its obligations to the User, the User's Customers, Stripe's users and Financial Providers, and (vi) to the extent Law permits, give Stripe information about transactions with Third-Party PSPs through the Orchestrated Services that Stripe determines it needs for investigations, administrative inquiries, legal requirements, audits, and demands or inquiries from consumers, merchants or Third-Party PSPs.
Supporting quotations
(a) Ensuring Third-Party PSP Compliance. User must:
(iv) upon request, provide Stripe with information about a Third-Party PSP that Stripe determines is necessary to enable Stripe to comply with Law or otherwise fulfill its obligations to User, User's Customers, Stripe’s users, and Stripe’s Financial Providers;
(vi) upon request and to the extent permitted by Law, User must provide Stripe with information about transactions with Third-Party PSPs using the Orchestrated Services that Stripe determines is necessary to enable Stripe to comply with any investigations, administrative inquiries, legal requirements, audits, and demands or inquiries from consumers, merchants, or Third-Party PSPs;
Qualifications & exceptions
Stripe determines what information is necessary.
Transaction information is subject to what Law permits.
Security & Safeguards · Restriction or exception
You must immediately disable a Third-Party PSP Stripe flags as restricted and not use non-compliant PSPs
The User must (vii) immediately disable any User-hosted Third-Party PSP integration if Stripe, in its sole discretion, notifies it that the PSP is a Restricted Third-Party PSP, and (viii) not use the Orchestrated Services with any Third-Party PSP that does not comply with Law (including AML and Sanctions Law) and data security standards imposed by Law or Financial Providers (including PCI-DSS), or that is listed as prohibited in the Documentation. A Restricted Third-Party PSP is one the User may not integrate with, as the Documentation describes and Stripe may update.
Supporting quotations
(a) Ensuring Third-Party PSP Compliance. User must:
(vii) immediately disable any User-hosted Third-Party PSP integration if Stripe, in its sole discretion, notifies User that the Third-Party PSP is a Restricted Third-Party PSP;
(viii) not use the Stripe Orchestrated Services with any Third Party PSP that does not comply with Law (including AML and Sanctions Law) and data security standards imposed by Law or Financial Providers (including PCI-DSS), or are otherwise listed as prohibited in the Documentation.
“Restricted Third-Party PSP” means a Third-Party PSP with which User may not integrate in relation to User’s use of the Stripe Orchestrated Services, as described in the Documentation and as may be updated by Stripe from time to time.
Qualifications & exceptions
Restricted status is Stripe's sole-discretion decision and can change over time.
Not stated here
The Documentation's lists of restricted and prohibited PSPs are not supplied.
Charges & Financial Obligations · Restriction or exception
Custom Payment Methods must be shown as selected and any Stripe flags as prohibited must be removed at once
For Custom Payment Methods, the User must (i) make sure its Customers are shown the Custom Payment Method they select, and (ii) immediately remove any Custom Payment Method Stripe tells it is prohibited. A Custom Payment Method is a third-party payment method not supported by the User's Stripe integration, configured to process transactions outside Stripe, that Stripe permits the User to integrate with the Orchestrated Services as the Documentation describes.
Supporting quotations
(b) Custom Payment Methods. User must:
(i) ensure that User’s Customers are presented with the Custom Payment Method they select; and
(ii) immediately remove any Custom Payment Method that Stripe notifies User is prohibited.
“Custom Payment Method” means a third-party payment method not supported by a User’s Stripe integration configured to process transactions outside of Stripe that Stripe permits User to integrate with User’s use of the Stripe Orchestrated Services, as described in the Documentation.
Qualifications & exceptions
Removal must be immediate once Stripe notifies the User.
Not stated here
Which Custom Payment Methods are prohibited is for Stripe to notify; no list is given here.
Use & Processing · Restriction or exception
Input Data you give Stripe must be accurate, complete and current, and supplied after payment where required
The User must (i) make sure Orchestrated Input Data is accurate, complete and current, and (ii) promptly give Stripe Orchestrated Input Data after a payment is processed where the Documentation requires. Orchestrated Input Data is any data the User gives Stripe so Stripe can perform the Orchestrated Services, including third party data in a Standalone 3DS request.
Supporting quotations
(c) Data. User must:
(i) ensure that Orchestrated Input Data is accurate, complete, and current;
(ii) promptly provide Stripe with Orchestrated Input Data after a payment is processed where required in the Documentation;
“Orchestrated Input Data” means any data provided by User to Stripe to enable Stripe to perform the Orchestrated Services, including (i) any third party data included in a Standalone 3DS request as described in the Documentation or otherwise envisaged by the Stripe Orchestrated Services, including without limitation acquirer BIN, merchant ID, and requestor ID and (ii) the results of previously-provided Orchestrated Input Data, which may include accuracy rate, outcome of the payment, User’s decision to process or decline the transaction, updates to the payment status, dispute rate, and dispute code, among other things.
Qualifications & exceptions
Post-payment delivery applies where the Documentation requires it.
Not stated here
The Documentation's requirements are not supplied.
Use & Processing · Restriction or exception
Output Data may not be used to train substitute models, be reverse engineered, or be used for marketing
The User must not (iii) use Orchestrated Output Data to develop, test, validate, train, enhance or deploy machine learning models or algorithms that substitute for or are substantially similar to the Services; (iv) modify it, create derivative works from it, disassemble, decompile or otherwise reverse engineer it, or try to derive source code or underlying structure, ideas or algorithms from it; or (v) use it for marketing purposes. Orchestrated Output Data is data the User receives through the Orchestrated Services that a proprietary Stripe model produced.
Supporting quotations
(c) Data. User must:
(iii) not use the Orchestrated Output Data to develop, test, validate, train, enhance, or deploy any machine learning models or algorithms that are a substitute for, or substantially similar to, the Services;
(iv) not modify, create derivative works from, disassemble, decompile, or otherwise reverse engineer or attempt to derive any source code or underlying structure, ideas, or algorithms from the Orchestrated Output Data; and
(v) not use the Orchestrated Output Data for marketing purposes.
“Orchestrated Output Data” means any data User receives through the Stripe Orchestrated Services which has been produced by a proprietary Stripe model.
Qualifications & exceptions
Applies to Orchestrated Output Data produced by a proprietary Stripe model.
Account & Service Control · Restriction or exception
You (or your Affiliate) must keep an agreement with each Third-Party PSP
The User, or if applicable its Affiliate, must maintain a Third-Party-PSP Agreement with each Third-Party PSP. That is a service agreement between the User (or its Affiliate) and the PSP governing routing, processing, settlement or other ancillary services for payment card transactions accessed through the Orchestrated Services.
Supporting quotations
(d) General Obligations.
(i) User (or if applicable, User’s Affiliate) must maintain a Third-Party-PSP Agreement with each Third Party PSP.
“Third-Party-PSP Agreement” means a service agreement between User (or if applicable, a User’s Affiliate) and a Third-Party PSP governing the routing, processing, settlement, or other ancillary services, for payment card transactions, which are being accessed in connection with the Stripe Orchestrated Services.
Use & Processing · Restriction or exception
You must hold the rights, consents and Customer disclosures that let Stripe lawfully process Orchestrated Data
The User must obtain and maintain all necessary rights, consents, approvals and authorizations, and give Customers all disclosures required, so that Stripe and its Affiliates can lawfully (i) provide the Orchestrated Services; (ii) store and use the User's Security Credentials (its or its Affiliate's API license keys and other credentials for Third-Party PSPs), related data and any Orchestrated Input Data as the Agreement and Documentation describe; and (iii) collect, use, retain and disclose the Orchestrated Data Stripe sends or receives, as the Agreement, Stripe's Privacy Policy and the Documentation describe. Orchestrated Data is data the User sends to or receives from Stripe through the services, including Third-Party PSP response data Stripe receives on the User's behalf, and may include Personal Data.
Supporting quotations
(d) General Obligations.
(ii) User must obtain and maintain all necessary rights, consents, approvals, and authorizations, and provide all disclosures to Customers, as required to enable Stripe and its Affiliates to lawfully: (i) provide the Stripe Orchestrated Services; (ii) store and use User's Security Credentials and any related data, and any Orchestrated Input Data as described in the Agreement and in the Documentation; and (iii) collect, use, retain and disclose the Orchestrated Data Stripe sends or receives in connection with the Stripe Orchestrated Services, as the Agreement, Stripe’s Privacy Policy and the Documentation describe.
“Security Credentials” means User's (or if applicable, User's Affiliate’s) API license keys and other security credentials for Third-Party PSPs.
“Orchestrated Data” means data that User sends to or receives from Stripe using the Stripe Orchestrated Services, which include response data that Stripe receives from Third-Party PSPs on User’s behalf, and may include Orchestrated Output Data, Orchestrated Input Data, and Personal Data.
Qualifications & exceptions
The duty is framed as what Stripe needs to lawfully do its processing.
Not stated here
The Privacy Policy and Documentation are linked and not supplied.
Security & Safeguards · Restriction or exception
You must use the services only within third-party agreements, payment method rules and data security standards
The User must use the Orchestrated Services only in line with all applicable (i) agreements with and obligations to relevant third parties, including Third-Party PSPs; (ii) guidelines, bylaws, rules and regulations of Payment Method providers, including Card Network Rules; and (iii) data security standards imposed by Law, Financial Providers and Payment Method Rules, including PCI-DSS and EMVCo 3DS specifications as applicable.
Supporting quotations
(d) General Obligations.
(iii) User must only use the Orchestrated Services in accordance with all applicable: (i) agreements with and obligations owed to relevant third parties (including Third Party PSPs); (ii) guidelines, bylaws, rules and regulations maintained by the Payment Method providers (including Card Network Rules); and (iii) data security standards imposed by Law, Financial Providers, and Payment Method Rules (including PCI-DSS and EMVCo 3DS specifications, as applicable).
Qualifications & exceptions
EMVCo 3DS specifications apply as applicable.
Legal Rights & Agreement Rules · Restriction or exception
Affiliate merchants must be identified on request, bound by the Agreement and screened for AML and sanctions risk
If the User uses the Orchestrated Services for Orchestrated Transactions where the merchant is a User Affiliate or a Sub-user of one, the User must (i) on request promptly tell Stripe the merchant's identity; (ii) make sure the merchant is bound by and will comply with the Agreement as if references to User were references to it; and (iii) have enough controls to ensure none of those transactions involve goods or services prohibited under AML and Sanctions Law or benefit Sanctioned Persons. Sanctioned Persons are people or entities subject to sanctions under AML and Sanctions Law, including those on an applicable sanctions list (such as those identified by the US Office of Foreign Asset Control and the European Commission), those owned or controlled by a listed person, and those ordinarily resident in a jurisdiction the Stripe Restricted Business List identifies as high risk.
Supporting quotations
(d) General Obligations.
(iv) If User is using the Stripe Orchestrated Services in connection with Orchestrated Transactions where the merchant is a User Affiliate or a Sub-user of a User Affiliate, then User must: (i) upon request, promptly notify Stripe of the identity of that merchant; (ii) ensure that merchant is subject to and will comply with the terms of the Agreement as if references to “User” were references to that merchant; and (iii) have sufficient controls in place to ensure that none of those Orchestrated Transactions (A) involve goods or services prohibited under AML and Sanctions Law, and (B) are for the benefit of Sanctioned Persons.
“Sanctioned Persons” means people or entities that are subject to sanctions (e.g., prohibitions or asset freezes) under AML and Sanctions Law, including if they are (a) on an applicable sanctions list, such as the sanctions lists identified by the United States Office of Foreign Asset Control and the European Commission; (b) owned or controlled by a person on an applicable sanctions list; or (c) ordinarily resident in a jurisdiction identified as high risk in the Stripe Restricted Business List (located on the Stripe website).
Qualifications & exceptions
Applies where the merchant is a User Affiliate or a Sub-user of a User Affiliate.
Not stated here
The Stripe Restricted Business List, which identifies high-risk jurisdictions, is on the Stripe website and is not supplied here.
Account & Service Control · Restriction or exception
You may not integrate Restricted PSPs or Methods, or tell anyone Stripe is the payment processor
The User must not (a) integrate with Restricted Third-Party PSPs or Restricted Custom Payment Methods; (b) represent that Stripe acts as the payment processor for transactions where Stripe provides Orchestration Services rather than Payment Services; or (c) misrepresent to anyone that Stripe is the payment processor of the Orchestrated Transactions.
Supporting quotations
2.2 Services Restrictions.
User must not:
(a) integrate with Restricted Third-Party PSPs or Restricted Custom Payment Methods;
(b) represent that Stripe acts as the payment processor in connection with any transactions for which Stripe provides Stripe Orchestration Services rather than Stripe Payment Services; or
(c) misrepresent to anyone that Stripe is the payment processor of the Orchestrated Transactions.
Not stated here
Restricted Custom Payment Methods are not defined in the text read for this section.
Account & Service Control · Restriction or exception
You may not say or imply Stripe is the payment processor of Orchestrated Transactions
The User must not represent that Stripe acts as the payment processor for transactions where Stripe provides Orchestration Services rather than Payment Services, and must not misrepresent to anyone that Stripe is the payment processor of the Orchestrated Transactions.
Supporting quotations
(b) represent that Stripe acts as the payment processor in connection with any transactions for which Stripe provides Stripe Orchestration Services rather than Stripe Payment Services; or
(c) misrepresent to anyone that Stripe is the payment processor of the Orchestrated Transactions.
Account & Service Control · Permission or license
Stripe may add or remove Restricted Custom Payment Methods and Restricted Third-Party PSPs at any time
Stripe may, at any time, add or remove Restricted Custom Payment Methods or Restricted Third-Party PSPs. The User may not integrate with those on the restricted lists, so the set of allowed integrations can change without the User's agreement.
Supporting quotations
3. Stripe’s Rights.
Stripe may, at any time, add or remove Restricted Custom Payment Methods or Restricted Third-Party PSPs.
Qualifications & exceptions
Stripe may change the restricted lists at any time.
Not stated here
The terms give no notice period for changes to the restricted lists.
Content & IP Rights · Company practice
Stripe processes Orchestrated Data under the Agreement and owns the IP rights in Orchestrated Output Data
Stripe will process Orchestrated Data in accordance with the Agreement. As between the parties, Stripe owns all IP Rights in and to the Orchestrated Output Data, which is data the User receives through the Orchestrated Services that a proprietary Stripe model produced. Orchestrated Data is data the User sends to or receives from Stripe through the services, including Third-Party PSP response data Stripe receives on the User's behalf.
Supporting quotations
4. Data Use.
4.1 Stripe’s Processing.
Stripe will process Orchestrated Data in accordance with the Agreement. As between the parties, Stripe owns all IP Rights in and to the Orchestrated Output Data.
“Orchestrated Output Data” means any data User receives through the Stripe Orchestrated Services which has been produced by a proprietary Stripe model.
“Orchestrated Data” means data that User sends to or receives from Stripe using the Stripe Orchestrated Services, which include response data that Stripe receives from Third-Party PSPs on User’s behalf, and may include Orchestrated Output Data, Orchestrated Input Data, and Personal Data.
Qualifications & exceptions
Ownership is as between the parties.
Sharing & Disclosure · Permission or license
You authorize Stripe to transfer Output Data to you or your chosen PSP, and must help Stripe meet legal duties
The User authorizes Stripe to transfer Orchestrated Output Data to the User or to the Third-Party PSP the User designates through the Orchestrated Services. On Stripe's request, the User will help Stripe comply with its legal obligations, which may include responding to requests from data subjects or a Governmental Authority.
Supporting quotations
4.2 Transfer and Custody of Orchestrated Output Data.
User authorizes Stripe to transfer Orchestrated Output Data to User or to the Third-Party PSP User designates via the Stripe Orchestrated Services. Upon Stripe’s request, User will assist Stripe in complying with its obligations under Law, which assistance may include responding to requests by data subjects or a Governmental Authority.
Qualifications & exceptions
Assistance is on Stripe's request.
Not stated here
The terms do not say who is the custodian of the data once transferred, unlike the parallel data pipeline clause.
Content & IP Rights · Restriction or exception
Payment Method Marks need rights, lawful use, no alteration without permission and no use for another provider
If the User uses any trademark, name, logo, icon, design element or other identifier of a payment method (a Payment Method Mark) with the Orchestrated Services, the User must, and must make sure third parties, (a) obtain and keep all necessary rights to use it, (b) not use it in violation of Law or of the payment method provider's terms or obligations, including Marks Usage terms, (c) not alter or modify it unless the User has written permission, and (d) not use one provider's Payment Method Mark to identify a different provider.
Supporting quotations
5. Marks requirements.
If User uses any trademark, name, logo, icon, design element, or anything else used to identify a payment method (a “Payment Method Mark”) in connection with the Stripe Orchestrated Services, User must (and must ensure that third parties):
(a) obtain and maintain all necessary rights to use the Payment Method Mark (including in connection with the Stripe Orchestrated Services);
(b) not use the Payment Method Mark in violation of any Law, or any terms or obligations imposed by the payment method provider (including any Marks Usage terms);
(c) not alter or modify the Payment Method Mark (unless User has written permission to do so); and
(d) not use the Payment Method Mark of a payment method provider to identify a different payment method provider.
Qualifications & exceptions
The duties extend to third parties the User deals with.
Alteration needs written permission.
Legal Rights & Agreement Rules · Restriction or exception
Stripe disclaims responsibility for your third-party integrations, agreements, PSP processing and Custom Payment Methods
Stripe disclaims all responsibility and liability for (a) the User's integration to any third party including a Third-Party PSP; (b) the terms and upkeep of agreements with third parties, including Third-Party-PSP Agreements; (c) completion or processing of any transactions by a Third-Party PSP, including authentication, order confirmation, reconciliation, charges, refunds, disputes, settlements or funds flows; (e) the operation and support of Custom Payment Methods; (i) any other aspect of a Third-Party PSP's services or failure to provide them, which the Third-Party-PSP Agreements govern; and (l) other acts and omissions of Third-Party PSPs, including a PSP that stops letting the User reach its services through the Orchestrated Services.
Supporting quotations
6. Disclaimers.
Stripe disclaims all responsibility and liability for:
(a) User’s integration to any third party including any Third-Party PSP;
(b) the terms and maintenance of agreements with any third party including Third-Party-PSP Agreements;
(c) completion or processing of any transactions by any Third-Party PSP including, for example, authentication requirements or methods, order confirmation, reconciliation of orders, any charges, refunds, disputes, settlements, or funds flows;
(e) the operation and support of Custom Payment Methods;
(i) any other aspect of Third-Party PSPs’ provision of, or failure to provide, its services; which in all cases are governed by the Third-Party-PSP Agreements;
(l) any other acts and omissions by Third-Party PSPs, including Third-Party PSPs that cease to allow User to access their services using the Orchestrated Services.
“Third-Party PSP” means User or User's Affiliate’s third-party payment services provider (such as a provider of payments processing, payments orchestration services, or token management services) to whom User directly or indirectly routes Orchestrated Data.
Qualifications & exceptions
Third-Party PSP matters are governed by the Third-Party-PSP Agreements.
Legal Rights & Agreement Rules · Restriction or exception
Stripe disclaims responsibility for the accuracy of information it relies on and for others' copies and use of data
Stripe disclaims responsibility and liability for (d) the accuracy of information the User, a Third-Party PSP, a Governmental Authority or another third party gives Stripe that Stripe relies on. The User agrees inaccurate information may cause the services to produce inaccurate Orchestrated Data, and Stripe is not responsible for inaccuracies, errors or omissions in it. Stripe also disclaims (j) Third-Party PSPs' use or disclosure of Orchestrated Data, which the Third-Party-PSP Agreements and the PSPs' privacy policies (if any) govern, and (k) any copy of Orchestrated Data the User or a Third-Party PSP makes, including how it is stored, used or disclosed.
Supporting quotations
6. Disclaimers.
Stripe disclaims all responsibility and liability for:
(d) the accuracy of information User, any Third-Party PSP, any Governmental Authority, or other third party provides to Stripe that Stripe relies on to provide the Orchestrated Services. User agrees that inaccurate information may cause the Orchestrated Services to generate inaccurate Orchestrated Data, and Stripe is not responsible for any inaccuracies, errors, or omissions in the Orchestrated Data;
(j) Third-Party PSPs’ use or disclosure of any Orchestrated Data, which are governed by the Third-Party PSP Agreements and the Third-Party PSPs’ privacy policies (if any);
(k) any copy of the Orchestrated Data that User or the Third-Party PSP makes, including how it is stored, used, or disclosed; and
Qualifications & exceptions
The accuracy disclaimer covers inputs from the User, PSPs, authorities and other third parties.
Not stated here
The terms do not say whether a Third-Party PSP has a privacy policy.
Charges & Financial Obligations · Restriction or exception
Stripe disclaims responsibility for disputes, refunds, fraud losses, funds movement and authentication choices
Stripe disclaims all responsibility and liability for (f) disputes, refunds, reversals and any other losses on Orchestrated Transactions, including losses from fraud; (g) any movement of funds related to Orchestrated Transactions; and (h) deciding whether Customer authentication is required for an Orchestrated Transaction under Law or Card Network requirements and, if so, which method to use.
Supporting quotations
6. Disclaimers.
Stripe disclaims all responsibility and liability for:
(f) disputes, refunds, reversals, and any other losses on Orchestrated Transactions, including losses due to fraud;
(g) any movement of funds related to Orchestrated Transactions;
(h) determining whether Customer authentication is required for any Orchestrated Transaction under Law or Card Network requirements, and if so, which authentication method to apply;
Qualifications & exceptions
Covers losses from fraud on Orchestrated Transactions.
Legal Rights & Agreement Rules · Restriction or exception
You defend and indemnify the Stripe Parties for Claims from Third-Party PSP or Custom Payment Method Provider failures
The User will (a) defend the Stripe Parties against Claims arising from a failure by a Custom Payment Method Provider or Third-Party PSP to (i) comply with Law, Payment Method provider rules including Card Network Rules, data security standards, or its agreements with or obligations to the User, Sub-users, Customers or others, or (ii) protect Orchestrated Data given to it, and (b) indemnify the Stripe Parties for all Stripe Losses arising from or relating to those Claims, under the indemnification provisions of the General Terms. Sub-users are users of the User's or its Affiliate's platform services that the user entity has enabled to accept card payments.
Supporting quotations
7. Indemnification.
User will (a) defend the Stripe Parties from any Claims arising from a failure by a Custom Payment Method Provider or Third-Party PSP to: (i) comply with Law, Payment Method provider rules (including Card Network Rules), data security standards, or any of its agreements with or obligations to User, Sub-users, Customers, or any other party, or (ii) protect Orchestrated Data provided to the Custom Payment Method provider or Third-Party PSP, as applicable; and (b) indemnify the Stripe Parties for all Stripe Losses arising out of or relating to those Claims, in each case in accordance with the indemnification provisions in the General Terms.
“Sub-users” means the users of User's or User's Affiliate’s platform services that the applicable user entity has enabled to accept card payments.
Qualifications & exceptions
Applies to failures by a Custom Payment Method Provider or Third-Party PSP.
Operates in line with the General Terms' indemnification provisions.
Not stated here
The General Terms' indemnification provisions are not supplied here.
Legal Rights & Agreement Rules · Context
Definitions: AML and Sanctions Law, Connected Account and Custom Payment Method
AML and Sanctions Law means applicable anti-money laundering and sanctions laws and other binding requirements of any Governmental Authority with jurisdiction in the United States, or over the Orchestrated Services, Stripe or its Affiliates, the User or its Affiliates, or a Third Party PSP, as applicable. A Connected Account is either a Platform User with a Stripe Account onboarded to a Stripe Connect Platform through the Stripe Connect Services, or a Payout Recipient. A Custom Payment Method is a third-party payment method not supported by the User's Stripe integration, configured to process transactions outside Stripe, that Stripe permits the User to integrate as the Documentation describes.
Supporting quotations
“AML and Sanctions Law” means all applicable anti-money laundering and sanctions laws, rules, regulations and other binding requirements of any Governmental Authority with jurisdiction in the United States, or with jurisdiction over the Stripe Orchestrated Services, Stripe or its Affiliates, User or its Affiliates, or a Third Party PSP, as applicable.
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
“Custom Payment Method” means a third-party payment method not supported by a User’s Stripe integration configured to process transactions outside of Stripe that Stripe permits User to integrate with User’s use of the Stripe Orchestrated Services, as described in the Documentation.
Not stated here
The Documentation that describes Custom Payment Methods is not supplied.
Legal Rights & Agreement Rules · Context
Definitions: Card Network (Visa, Mastercard, American Express, Discover) and Card Network Rules
A Card Network is a payment card network, including those run by Visa, Mastercard, American Express and Discover; the named networks are examples. Card Network Rules are the Payment Method Rules a Card Network publishes.
Supporting quotations
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
“Card Network Rules” means the Payment Method Rules published by a Card Network.
Qualifications & exceptions
The named networks are examples, not a complete list.
Not stated here
The Card Network Rules themselves are published by the networks and are not in this document.
Use & Processing · Context
Definitions: Orchestrated Data, Orchestrated Input Data and Orchestrated Output Data
Orchestrated Data is data the User sends to or receives from Stripe using the Orchestrated Services, including response data Stripe receives from Third-Party PSPs on the User's behalf, and it may include Output Data, Input Data and Personal Data. Orchestrated Input Data is any data the User gives Stripe so it can perform the services, including third party data in a Standalone 3DS request (such as acquirer BIN, merchant ID and requestor ID) and results of previously provided Input Data (such as accuracy rate, payment outcome, the User's decision to process or decline, payment status updates, dispute rate and dispute code), among other things. Orchestrated Output Data is data the User receives through the services that a proprietary Stripe model produced.
Supporting quotations
“Orchestrated Data” means data that User sends to or receives from Stripe using the Stripe Orchestrated Services, which include response data that Stripe receives from Third-Party PSPs on User’s behalf, and may include Orchestrated Output Data, Orchestrated Input Data, and Personal Data.
“Orchestrated Input Data” means any data provided by User to Stripe to enable Stripe to perform the Orchestrated Services, including (i) any third party data included in a Standalone 3DS request as described in the Documentation or otherwise envisaged by the Stripe Orchestrated Services, including without limitation acquirer BIN, merchant ID, and requestor ID and (ii) the results of previously-provided Orchestrated Input Data, which may include accuracy rate, outcome of the payment, User’s decision to process or decline the transaction, updates to the payment status, dispute rate, and dispute code, among other things.
“Orchestrated Output Data” means any data User receives through the Stripe Orchestrated Services which has been produced by a proprietary Stripe model.
Qualifications & exceptions
Input Data includes “among other things”, so the examples are not exhaustive.
Orchestrated Data may include Personal Data.
Use & Processing · Context
Definitions: Orchestrated Services, Third-Party PSP and its agreement, Sub-users and Security Credentials
The Stripe Orchestrated Services let the User (a) receive Output Data from Stripe for specified purposes, (b) send certain Orchestrated Data to Third-Party PSPs, (c) capture and store Orchestrated Data from Third-Party PSPs, (d) send User Input Data to Stripe, and (e) otherwise carry out certain activities related to its business and transactions processed through Custom Payment Methods or Third-Party PSPs. A Third-Party PSP is the User's or its Affiliate's third-party payment services provider, such as a provider of payments processing, orchestration or token management, to which the User routes Orchestrated Data directly or indirectly. A Third-Party-PSP Agreement is the service agreement with it governing routing, processing, settlement or ancillary services. Sub-users are users of the User's or its Affiliate's platform services whom the user entity has enabled to accept card payments. Security Credentials are the User's (or Affiliate's) API license keys and other credentials for Third-Party PSPs.
Supporting quotations
“Stripe Orchestrated Services” means the Services that enable User to (a) receive Output Data from Stripe for specified purposes; (b) send certain Orchestrated Data to Third-Party PSPs; (c) capture and store Orchestrated Data from Third-Party PSPs; (d) send the User Input Data to Stripe; and (e) otherwise conduct certain activities related to User’s business and transactions processed through Custom Payment Methods or Third-Party PSPs.
“Third-Party PSP” means User or User's Affiliate’s third-party payment services provider (such as a provider of payments processing, payments orchestration services, or token management services) to whom User directly or indirectly routes Orchestrated Data.
“Third-Party-PSP Agreement” means a service agreement between User (or if applicable, a User’s Affiliate) and a Third-Party PSP governing the routing, processing, settlement, or other ancillary services, for payment card transactions, which are being accessed in connection with the Stripe Orchestrated Services.
“Sub-users” means the users of User's or User's Affiliate’s platform services that the applicable user entity has enabled to accept card payments.
“Security Credentials” means User's (or if applicable, User's Affiliate’s) API license keys and other security credentials for Third-Party PSPs.
Account & Service Control · Context
Definitions: Restricted Custom Payment Method and Restricted Third-Party PSP, set by Documentation and updates
A Restricted Custom Payment Method is a third-party payment method the User is prohibited from accepting with the Orchestrated Services, as the Documentation describes and Stripe may update from time to time. A Restricted Third-Party PSP is a Third-Party PSP the User may not integrate with in relation to the services, on the same basis. Both restrictions can change when Stripe updates the Documentation. A Custom Payment Method is a third-party payment method not supported by the User's Stripe integration, configured to process transactions outside Stripe, that Stripe permits the User to integrate.
Supporting quotations
“Restricted Custom Payment Method” means a third-party payment method User is prohibited from accepting in connection with User’s use of the Stripe Orchestrated Services, as described in the Documentation and as may be updated by Stripe from time to time.
“Restricted Third-Party PSP” means a Third-Party PSP with which User may not integrate in relation to User’s use of the Stripe Orchestrated Services, as described in the Documentation and as may be updated by Stripe from time to time.
“Custom Payment Method” means a third-party payment method not supported by a User’s Stripe integration configured to process transactions outside of Stripe that Stripe permits User to integrate with User’s use of the Stripe Orchestrated Services, as described in the Documentation.
Qualifications & exceptions
Both lists can change when Stripe updates the Documentation.
Not stated here
The Documentation's lists are not supplied here.
Legal Rights & Agreement Rules · Context
Definitions: Sanctioned Persons, AML and Sanctions Law and PCI-DSS
Sanctioned Persons are people or entities subject to sanctions under AML and Sanctions Law, including those on an applicable sanctions list (such as lists identified by the US Office of Foreign Asset Control and the European Commission), those owned or controlled by a listed person, and those ordinarily resident in a jurisdiction the Stripe Restricted Business List identifies as high risk. AML and Sanctions Law covers applicable anti-money laundering and sanctions laws and other binding requirements of any Governmental Authority with jurisdiction in the United States, or over the Orchestrated Services, Stripe or its Affiliates, the User or its Affiliates, or a Third Party PSP. PCI-DSS is the Payment Card Industry Data Security Standard.
Supporting quotations
“Sanctioned Persons” means people or entities that are subject to sanctions (e.g., prohibitions or asset freezes) under AML and Sanctions Law, including if they are (a) on an applicable sanctions list, such as the sanctions lists identified by the United States Office of Foreign Asset Control and the European Commission; (b) owned or controlled by a person on an applicable sanctions list; or (c) ordinarily resident in a jurisdiction identified as high risk in the Stripe Restricted Business List (located on the Stripe website).
“AML and Sanctions Law” means all applicable anti-money laundering and sanctions laws, rules, regulations and other binding requirements of any Governmental Authority with jurisdiction in the United States, or with jurisdiction over the Stripe Orchestrated Services, Stripe or its Affiliates, User or its Affiliates, or a Third Party PSP, as applicable.
“PCI-DSS” means the Payment Card Industry Data Security Standard.
Qualifications & exceptions
The Sanctioned Persons definition is not limited to listed names; it reaches owned or controlled entities and residents of high-risk jurisdictions.
Not stated here
The Stripe Restricted Business List is on the Stripe website and is not supplied here.
Legal Rights & Agreement Rules · Context
Definition: Stripe Losses cover awards, penalties, fines and third-party costs including legal fees
Stripe Losses means all amounts awarded to the third party making a Claim, and all penalties, fines and third-party costs, including legal fees, paid by the Stripe Parties.
Supporting quotations
“Stripe Losses” means all amounts awarded to the third party making a Claim, and all penalties, fines, and third-party costs (including legal fees) paid by the Stripe Parties.
Account & Service Control · Context
Organizations Terms add to the General Terms and bind each Organization Account (last modified Nov. 18, 2025)
These Stripe Organizations Terms, last modified November 18, 2025, supplement the General Terms and govern the use of the Stripe Organizations Services, and each Stripe Account that is an Organization Account is bound by them. Capitalized terms not defined here take their General Terms meaning. An Organization Account is a Stripe Account included in an Organization, and the Organizations Services are designed to let the User join one or more Affiliate Stripe Accounts together in an Organization.
Supporting quotations
Last modified: November 18, 2025
These terms (“Stripe Organizations Terms”) supplement the General Terms and govern the use of the Stripe Organizations Services. Each Stripe Account that is an Organization Account is bound by these Stripe Organization Terms. Capitalized terms that are not defined in these Stripe Organizations Terms have the same meanings given to them in the General Terms.
“Organization Account” means a Stripe Account that is included in an Organization.
“Stripe Organizations Services” means the Service that is designed to enable User to join one or more Affiliate Stripe Accounts together in an Organization.
Qualifications & exceptions
Each Organization Account is bound, not only the one that signed up.
Account & Service Control · Restriction or exception
An account can join only one Organization, members must be Affiliates, and you must leave after a Change of Control
Each Stripe Account can be in only one Organization at a time, and all accounts in an Organization must be Affiliates. If the User experiences a Change of Control and its Organization Account is no longer an Affiliate of the other users in the Organization, the User must immediately remove its account from the Organization.
Supporting quotations
2. Conditions of Use.
Each Stripe Account can only join one Organization at any time. All Stripe Accounts within an Organization must be Affiliates. If User experiences a Change of Control and User’s Organization Account is no longer an Affiliate of the other Stripe users in the Organization, then User must immediately remove its Organization Account from the Organization.
Qualifications & exceptions
Removal after a Change of Control applies where the account is no longer an Affiliate of the others.
Account & Service Control · Permission or license
Stripe may remove an Organization Account at any time if it is not an Affiliate or is in breach
Stripe may, at its discretion and at any time, remove an Organization Account from an Organization if it determines the account is not an Affiliate of the other Organization Accounts, or is in violation of the Agreement or the Organizations Terms.
Supporting quotations
3. Stripe Rights.
Stripe may remove, at its discretion and at any time, an Organization Account from an Organization if Stripe determines that an Organization Account is not an Affiliate of the other Organization Accounts, or is in violation of the Agreement or these Stripe Organization Terms.
Qualifications & exceptions
Requires Stripe's determination of non-affiliation or violation, but removal is at its discretion.
Sharing & Disclosure · Permission or license
By joining, you authorize sharing your account data and wide administration of your account by Organization entities
By joining an Organization, the User authorizes (a) Stripe to share the User's account data with other Organization Accounts in the Organization; (b) people with authority to act for individual Organization Accounts to do so through the Organization; and (c) all other legal entities of the Organization Accounts in the same Organization to enable paid features or other paid Services for the Organization, to add or remove other Affiliate Stripe Accounts, and to access, share, delete and modify the User's Organization Account data, based on the administration roles the User sets for that account.
Supporting quotations
4. Administration of Organization.
By joining an Organization, User authorizes (a) Stripe to share User’s account data with other Organization Accounts in User’s Organization; (b) those individuals with authority to act on behalf of individual Organization Accounts, to do so through the Organization; and (c) all other legal entities of the Organization Accounts that are part of the same Organization to enable paid features or other paid Services for the Organization, to add or remove other Affiliate Stripe Accounts in the Organization, and to access, share, delete and modify the account data of User’s Organization Account based on administration roles that User sets for that Stripe Account.
Qualifications & exceptions
Access by other entities follows the administration roles the User sets for that account.
Not stated here
The terms do not say which account data is shared.
Sharing & Disclosure · Restriction or exception
You must hold notices and consents for sharing Personal Data in the Organization and stop third-party misuse
The User must have given all notices and obtained, and keep throughout the Term, all rights and consents from the people concerned, including all Customers, that Stripe needs to lawfully disclose Personal Data to other Organization Accounts in the Organization. The User must not enable or allow any third party to access or use its Organization Account, or any data including Personal Data tied to any Organization Account in the Organization, in a way that breaks Law, including Law that applies to the User or to other Organization Accounts.
Supporting quotations
5. Sharing of Data.
User must have provided all notices and obtained all rights and consents from applicable individuals, including from all Customers, and maintain such rights and consents throughout the Term, necessary to permit Stripe to lawfully disclose Personal Data to other Organization Accounts in User’s Organization. User must not enable or allow any third party to access or use (a) User’s Organization Account, or (b) any data including Personal Data associated with any Organization Account in User’s Organization, in a manner that violates Law, including Law applicable to User or to other Organization Accounts in User’s Organization.
Qualifications & exceptions
Consents must be maintained throughout the Term.
Legal Rights & Agreement Rules · Restriction or exception
You are jointly and severally liable with the other Organization entities for all Organizations Services activity
While the User's Stripe Account is part of an Organization, the User is jointly and severally liable with the other legal entities whose Stripe Accounts are in the same Organization for all activity related to use of the Organizations Services, including any features or other Services the Organization uses.
Supporting quotations
6. Liability of Organization Accounts.
While User’s Stripe Account is part of an Organization, User is jointly and severally liable with the other legal entities whose Stripe Accounts are part of the same Organization as User’s Organization Accounts for all activity related to use of Stripe Organizations Services, including for any features or other Services used by the Organization.
Qualifications & exceptions
Liability is joint and several, so Stripe could look to the User for the whole amount.
Applies while the User's account is in the Organization.
Not stated here
The terms do not say whether liability continues for activity before the User leaves.
Sharing & Disclosure · Permission or license
Preview Customer and Payment Method Sharing lets your CPM Information be shared with other Organization Accounts
Section 7, a Preview feature, applies only if the User uses the Customer and Payment Method Sharing feature. If the User enables it for its Organization, the User's CPM Information can be shared with the other Organization Accounts. CPM Information is Customer account information including name, contact information, billing information, tax ID, loyalty program information and the Customer's payment methods saved to the Customer profile. The feature lets the User share that information of its Organization Accounts with other Organization Accounts in the Organization.
Supporting quotations
7. Customer and Payment Method Sharing (Preview).
7.1 Customer and Payment Method Sharing.
This section applies only if User uses the Customer and Payment Method Sharing feature of Stripe Organizations Services.
7.2 Permitted Use.
If User enables Customer and Payment Method Sharing for User’s Organization, User’s CPM Information can be shared with the other Organization Accounts in User’s Organization.
“Customer and Payment Method Information” (or “CPM Information”) means Customer account information including Customer name, Customer contact information, Customer billing information, Customer tax ID, Customer loyalty program information, and Customer’s payment methods saved to the Customer profile.
“Customer and Payment Method Sharing” means the feature that enables User to share Customer Payment Method Information of User’s Organization Accounts with other Organization Accounts in User’s Organization.
Qualifications & exceptions
Applies only if the User uses the feature.
The feature is in Preview.
Sharing & Disclosure · Restriction or exception
Before enabling sharing you must give notices and get the consents Law requires for CPM Information
Before enabling Customer and Payment Method Sharing, the User must give all necessary notices and obtain all necessary rights and consents from the people concerned, as Law requires, before sharing CPM Information with other Organization Accounts in its Organization.
Supporting quotations
7.3 Conditions of Use.
Before enabling Customer and Payment Method Sharing, User must provide all necessary notices and obtain all necessary rights and consents from applicable individuals, as required by Law, before sharing CPM Information with other Organization Accounts in User’s Organization.
Qualifications & exceptions
Must be done before enabling.
Sharing & Disclosure · Restriction or exception
Sharing CPM Information is all or nothing, only Stripe can disable it, and disabling may cost you access to it
The User agrees that (a) if it enables sharing, all of its CPM Information is shared with other Organization Accounts that have also enabled sharing, and CPM Information cannot be segregated or shared in part; and (b) once enabled, the feature can be disabled only by Stripe. If it is disabled, the User may lose access to all CPM Information.
Supporting quotations
User agrees that:
(a) if User enables sharing of User’s CPM Information with User’s Organization, then all of User’s CPM Information is shared with other Organization Accounts that have also enabled sharing CPM Information. CPM Information cannot be segregated and shared in part; and
(b) once enabled, Customer and Payment Method Sharing can only be disabled by Stripe.
If Customer and Payment Method Sharing is disabled, User may lose access to all CPM Information.
Qualifications & exceptions
Sharing cannot be partial.
Only Stripe can turn the feature off once enabled.
Not stated here
The terms do not say whether information already shared can be recalled from other accounts.
Account & Service Control · Permission or license
Sharing is for Stripe-approved Organizations; Stripe may disable it, change fees or end it at any time
Customer and Payment Method Sharing is only available for Organizations Stripe approves. Stripe may disable it for any Organization or any Organization Account, and disclaims all liability for disabling it after the User has enabled or used it. Stripe may apply or change fees for the feature, subject to any notice period Law requires and any applicable Taxes, and may discontinue the feature at any time.
Supporting quotations
7.4 Stripe’s Rights.
Customer and Payment Method Sharing is only available for Organizations approved by Stripe. Stripe reserves the right to disable Customer and Payment Method Sharing for any Organization or for any Organization Account in an Organization. Stripe disclaims all liability for disabling Customer and Payment Method Sharing after User has enabled or used the feature. Stripe reserves the right to apply or change fees for the Customer and Payment Method Sharing feature, subject to any notice period required by Law before applying or changing fees, as well as any applicable Taxes. Stripe reserves the right to discontinue offering the Customer and Payment Method Sharing feature at any time.
Qualifications & exceptions
Fee changes are subject to any legally required notice period.
Stripe's liability for disabling the feature is disclaimed.
Not stated here
The terms do not state any notice period of their own.
Account & Service Control · Context
Definitions: Organization (two or more Affiliate accounts), Organization Account and Organizations Services
An Organization is a group of two or more of the User's or its Affiliates' Stripe Accounts that the User joins together through the Stripe Organization Services. An Organization Account is a Stripe Account included in an Organization. The Stripe Organizations Services are the Service designed to let the User join one or more Affiliate Stripe Accounts together in an Organization.
Supporting quotations
“Organization” means a group of two or more of User’s or User’s Affiliates’ Stripe Accounts that User joins together via the Stripe Organization Services.
“Organization Account” means a Stripe Account that is included in an Organization.
“Stripe Organizations Services” means the Service that is designed to enable User to join one or more Affiliate Stripe Accounts together in an Organization.
Qualifications & exceptions
An Organization needs at least two accounts.
Account & Service Control · Context
Professional Services Terms add to the General Terms for Order Form purchases (last modified Sept. 28, 2026)
These Stripe Professional Services Terms, last modified September 28, 2026, supplement the General Terms, govern the use of the Stripe Professional Services, and apply to the User's purchase of those services under a Professional Services Order Form. That is an order form or statement of work for the services signed between the User and Stripe. Capitalized terms not defined here take their General Terms meaning.
Supporting quotations
Last modified: September 28, 2026
These terms (“Stripe Professional Services Terms”) supplement the General Terms, govern the use of the Stripe Professional Services, and apply to User’s purchase of Stripe Professional Services under a Professional Services Order Form. Capitalized terms that are not defined in these Stripe Professional Services Terms have the same meanings given to them in the General Terms.
“Professional Services Order Form” means an order form or statement of work for Stripe Professional Services executed between User and Stripe.
Qualifications & exceptions
Applies to purchases made under a Professional Services Order Form.
Account & Service Control · Company practice
The services you get are described in the Order Form, the Data Sheet and on the Stripe Website
The specific Stripe Professional Services Stripe will provide are described on the Professional Services Order Form, the Professional Services Data Sheet and the Stripe Website. The Data Sheet is the document the Order Form references with a detailed description of the services. The terms themselves do not list the services.
Supporting quotations
2.1 Service Description.
The specific Stripe Professional Services that Stripe will provide to User is described on the Professional Services Order Form, Professional Services Data Sheet and Stripe Website.
“Professional Services Data Sheet” means the document referenced in the Professional Services Order Form containing a detailed description of the Stripe Professional Services.
Qualifications & exceptions
Scope comes from three sources, including a website page that can change.
Not stated here
The Order Form, Data Sheet and website content are not part of this saved text.
Account & Service Control · Procedure
The start date is agreed within 10 days or set by you on 30 days' notice, and Stripe's duty ends one year after signing
Within 10 days after the Order Form is signed, the parties will seek to agree a Project Start Date. If they do not, the User may choose one by giving Stripe at least 30 days' notice of its proposed date. Whatever the start date, Stripe's obligation to provide the services ends one year after the Order Form is executed.
Supporting quotations
2.2 Project Start Date.
Within 10 days after the Professional Services Order Form is executed, the parties will seek to agree on a date when Stripe will start providing the Stripe Professional Services to User (“Project Start Date”). If the parties do not agree on a Project Start Date within that time period, User may select a Project Start Date by providing Stripe with at least 30 days’ notice of User’s proposed Project Start Date. Notwithstanding the Project Start Date, Stripe’s obligation to provide the Stripe Professional Services to User ends one year after the Professional Services Order Form is executed.
Qualifications & exceptions
The User's own date needs at least 30 days' notice.
The one-year end date runs from execution of the Order Form, not from the start date.
Not stated here
The terms do not say what happens to fees if the services cannot be completed within the one year.
Account & Service Control · Company practice
Services are provided remotely, during business hours on business days, unless agreed otherwise
Unless the parties agree otherwise, including in the Order Form or Data Sheet, Stripe will provide the Professional Services (a) on a remote or virtual basis and (b) during business hours on business days.
Supporting quotations
2.3 Delivery of Services.
Unless the parties otherwise agree (including in the Professional Services Order Form or Professional Services Data Sheet), Stripe will provide Stripe Professional Services (a) on a remote or virtual basis, and (b) during business hours on business days.
Qualifications & exceptions
The parties can agree differently in the Order Form or Data Sheet.
Not stated here
Business hours are not defined in this section.
Account & Service Control · Procedure
Services are deemed accepted unless you object within 10 days of Stripe's completion notice
Stripe will give the User a completion notice for completed services. Unless the User objects by notifying Stripe within 10 days of the notice, the services are deemed accepted when Stripe provides the notice. If the User objects, the parties will cooperate in good faith to resolve it.
Supporting quotations
2.4 Acceptance of Services.
Stripe will provide User with a completion notice for the completed Stripe Professional Services, and unless User objects to the completion notice by notifying Stripe within 10 days of the completion notice, the Stripe Professional Services will be deemed accepted by User when Stripe provides the completion notice. If User raises an objection, the parties will cooperate in good faith to resolve it.
Qualifications & exceptions
Acceptance is deemed from the date of the notice, not the end of the 10 days.
Charges & Financial Obligations · Company practice
The fees are stated in the Order Form, the Data Sheet and on the Stripe Website
The fees for the Professional Services are described on the Professional Services Order Form, the Professional Services Data Sheet and the Stripe Website. The fees are the amounts the Order Form states, and the terms themselves do not give amounts.
Supporting quotations
3. Fees and Expenses.
3.1 Professional Services Fees and Expenses.
The fees for Stripe Professional Services are described on the Professional Services Order Form, Professional Services Data Sheet and Stripe Website.
“Professional Services Fees” means the fees for the Stripe Professional Services stated in a Professional Services Order Form.
Qualifications & exceptions
Fee information comes from three sources, including a website page that can change.
Not stated here
Fee amounts are not in this saved text.
Charges & Financial Obligations · Restriction or exception
You must pay the fees and approved expenses and bear the consequences if you are slow to approve expenses
The User must pay the Professional Services Fees and all approved Professional Services Expenses, which are costs Stripe and its subcontractors incur delivering the services. Stripe will seek the User's approval before Stripe or its subcontractors incur expenses, including before required travel. If the User does not promptly approve expenses, Stripe's ability to provide the services may be adversely affected and the User is responsible for the consequences, including delays or termination of the services.
Supporting quotations
3.2 Liability for Fees and Expenses.
User must pay the Professional Services Fees, and all approved Professional Services Expenses. Stripe will seek User’s approval for Professional Services Expenses before Stripe or its subcontractors incur them, including prior to making any required travel. If User does not promptly approve Professional Services Expenses, Stripe’s ability to provide the Stripe Professional Services may be adversely impacted and User is responsible for any consequences, including delays or termination of the Stripe Professional Services.
“Professional Services Expenses” means costs and expenses Stripe and its subcontractors incur in connection with the delivery of the Stripe Professional Services.
Qualifications & exceptions
Expenses are payable only once approved.
Slow approval can lead to delay or termination, for which the User is responsible.
Charges & Financial Obligations · Restriction or exception
Fees and expenses are payable in full and non-refundable even if you stop early or the Order Form ends early
Stripe will collect the Professional Services Fees and Expenses as the General Terms describe. They are payable in full and are non-refundable regardless of whether (a) the User asks Stripe to stop before the services are fully delivered, (b) Stripe cannot provide the services because the User did not meet its obligations, or (c) the Order Form is terminated before full delivery for a reason other than Stripe's uncured material breach.
Supporting quotations
3.3 Collection of Fees and Expenses.
Stripe will collect Professional Services Fees and Professional Services Expenses as described in the General Terms. The Professional Services Fees and Professional Services Expenses are payable by User in full and are non-refundable, regardless of whether: (a) User requests that Stripe stop providing the Stripe Professional Services before they are delivered in full; (b) Stripe is unable to provide the Stripe Professional Services due to User's failure to fulfill User's obligations under this Agreement; or (c) the Professional Services Order Form is terminated before the Stripe Professional Services are fully delivered for a reason other than Stripe’s uncured material breach.
Qualifications & exceptions
The only stated route out is Stripe's uncured material breach of the Order Form.
Legal Rights & Agreement Rules · Restriction or exception
Sample Codes are provided "as is", with all warranties disclaimed and no liability for losses from them
Stripe may provide sample codes, snippets and programming examples showing features of the Stripe Technology (Sample Codes) as part of the services. They are provided “AS IS” and “AS AVAILABLE”. To the maximum extent Law permits, Stripe disclaims all express and implied warranties and statutory guarantees about Sample Codes, and Stripe and its Affiliates are not liable for losses, damages or costs the User or others may suffer from them. Sample Codes count as Documentation for the Agreement.
Supporting quotations
4. Sample Codes.
Stripe may, as part of Stripe Professional Services, provide sample codes, snippets, and programming examples illustrating various features of the Stripe Technology (collectively, “Sample Codes”). Stripe provides Sample Codes “AS IS” and “AS AVAILABLE”. To the maximum extent permitted by Law, Stripe does not make any, and expressly disclaims all, express and implied warranties and statutory guarantees with respect to Sample Codes. Stripe and its Affiliates are not liable for any losses, damages, or costs that User or others may suffer arising out of or relating to Sample Codes. Sample Codes are Documentation for purposes of this Agreement.
Qualifications & exceptions
Disclaimer is to the maximum extent Law permits.
Account & Service Control · Restriction or exception
You must appoint a point of contact with authority and a senior project sponsor
The User must (a) appoint a person to act as its main point of contact for the services, with authority to act for the User and to coordinate its employees, contractors and agents to meet its obligations, and (b) appoint a senior leader as project sponsor, responsible for providing the resources needed for project management and for resolving escalated issues.
Supporting quotations
5. User Commitments and Obligations.
User must:
(a) appoint a person to act as User’s main point of contact with respect to the Stripe Professional Services who will have the authority to act on User’s behalf and coordinate User’s employees, contractors and agents to meet User’s obligations under these Stripe Professional Services Terms;
(b) appoint a senior leader within User’s organization as a project sponsor to be responsible for providing necessary resources for successful project management and resolving any escalated issues;
Account & Service Control · Restriction or exception
You must hold requirements steady after the plan is agreed, respond promptly and keep your team available
The User must (c) not change technical and operational requirements after the parties agree a project plan as the Data Sheet contemplates; (d) respond promptly to Stripe's requests for direction, information, documentation (including test plans, testing environments and a description of its systems architecture), approvals, authorizations or decisions reasonably needed to provide the services; and (e) make all User team members, including engineering and operational personnel and subject matter experts, available throughout the project to carry out their tasks in a timely way.
Supporting quotations
User must:
(c) not change technical and operational requirements after the parties agree on a project plan as contemplated in the Professional Services Data Sheet;
(d) respond promptly to any request from Stripe to provide direction, information, documentation (including test plans, relevant testing environments (if applicable), and a description of User’s systems architecture), approvals, authorizations, or decisions that are reasonably necessary for Stripe to provide the Stripe Professional Services in accordance with this Agreement;
(e) make all User team members, including engineering and operational personnel, subject matter experts and other key personnel, available throughout the project to execute their required tasks in a timely fashion;
Qualifications & exceptions
The requirements freeze applies after the project plan is agreed.
Information requests must be reasonably necessary for the services.
Not stated here
The terms do not say what follows if requirements change anyway.
Account & Service Control · Restriction or exception
You must keep your team available and complete your project obligations within agreed timeframes
The User must (e) make all User team members, including engineering and operational personnel, subject matter experts and other key personnel, available throughout the project to carry out their tasks in a timely way, and (f) cooperate with Stripe and complete its obligations for the project within agreed timeframes.
Supporting quotations
(e) make all User team members, including engineering and operational personnel, subject matter experts and other key personnel, available throughout the project to execute their required tasks in a timely fashion;
(f) cooperate with Stripe and complete User’s obligations in relation to the project within agreed upon timeframes; and
Qualifications & exceptions
Applies throughout the project.
Not stated here
The terms do not say what follows if the User misses a timeframe.
Account & Service Control · Restriction or exception
You must give each Stripe Project Team member developer-level access to your Stripe Account
The User must give each Stripe Project Team member developer-level access to the User's Stripe Account during the term of the Professional Services Order Form. The Stripe Project Team is the subcontractors and Stripe employees performing the services.
Supporting quotations
(g) provide each Stripe Project Team member (as defined below) with developer-level access to User’s Stripe Account during the term of the Professional Services Order Form.
(together with Stripe employees performing the Stripe Professional Services, if any, the “Stripe Project Team”)
Qualifications & exceptions
Access lasts for the term of the Order Form.
Not stated here
The terms do not say what developer-level access allows, or how it is ended or monitored.
Account & Service Control · Company practice
Stripe may use subcontractors and remains responsible to you for performing its obligations
Stripe may engage subcontractors to perform all or part of the Professional Services, and together with any Stripe employees doing the work they are the Stripe Project Team. Stripe remains responsible to the User for performing its obligations under these terms, the Data Sheet and the Order Form.
Supporting quotations
6. Subcontractors.
Stripe may engage subcontractors to perform all or part of the Stripe Professional Services (together with Stripe employees performing the Stripe Professional Services, if any, the “Stripe Project Team”). Stripe will remain responsible to User for performing its obligations under and in accordance with these Stripe Professional Services Terms, Professional Services Data Sheet and Professional Services Order Form.
Not stated here
The terms do not say whether the User is told which subcontractors are used.
Legal Rights & Agreement Rules · Restriction or exception
Stripe does not warrant its advice suits your business, and you decide whether to act on it
Stripe does not represent or warrant that its or its subcontractors' advice or recommendations will suit the User's business. Stripe does not have access to all relevant information about the business, and its advice rests on assumptions and on information the User provides. The User is responsible for deciding whether to act on any advice or recommendation.
Supporting quotations
7. Disclaimer.
Stripe does not represent or warrant that any advice or recommendations made by Stripe, or its subcontractors, will be appropriate for User’s business. Stripe does not have access to all relevant information about User’s business, and its advice and recommendations will be based on certain assumptions and in reliance on information User provides in connection with this Agreement. User is responsible for determining whether to act upon any advice or recommendations Stripe or its subcontractors make.
Qualifications & exceptions
Advice rests on assumptions and on information the User provides.
Legal Rights & Agreement Rules · Restriction or exception
Stripe gives no legal or compliance advice; you own the integration work and your own legal assessment
Stripe does not provide legal or compliance advice. The User is responsible for all integration work and for making its own assessment of whether its use of the Professional Services meets applicable legal and regulatory requirements.
Supporting quotations
Stripe does not provide legal or compliance advice. User is responsible for all integration work and for making User’s own assessment of whether User’s use of the Stripe Professional Services meets applicable legal and regulatory requirements.
Content & IP Rights · Restriction or exception
All non-public information that Stripe or its project team discloses is Stripe's Confidential Information
All non-public information disclosed by a Stripe Entity or the Stripe Project Team in connection with the Professional Services is Stripe's Confidential Information. This clause covers Stripe's information only; it does not say how information the User discloses is treated.
Supporting quotations
8. Confidentiality.
All non-public information disclosed by a Stripe Entity or the Stripe Project Team in connection with the Stripe Professional Services is Stripe’s Confidential Information.
Qualifications & exceptions
Covers non-public information disclosed in connection with the Professional Services.
Not stated here
Treatment of the User's own information is not addressed in this clause.
Charges & Financial Obligations · Context
Definitions: Professional Services Data Sheet, Order Form, Fees and Expenses
The Professional Services Data Sheet is the document the Order Form references with a detailed description of the services. The Order Form is an order form or statement of work for the services signed between the User and Stripe. Professional Services Fees are the fees stated in an Order Form. Professional Services Expenses are costs and expenses Stripe and its subcontractors incur delivering the services.
Supporting quotations
“Professional Services Data Sheet” means the document referenced in the Professional Services Order Form containing a detailed description of the Stripe Professional Services.
“Professional Services Order Form” means an order form or statement of work for Stripe Professional Services executed between User and Stripe.
“Professional Services Fees” means the fees for the Stripe Professional Services stated in a Professional Services Order Form.
“Professional Services Expenses” means costs and expenses Stripe and its subcontractors incur in connection with the delivery of the Stripe Professional Services.
Account & Service Control · Context
Definition: Stripe Professional Services are advisory and consulting services set out in the Order Form and Data Sheet
Stripe Professional Services means the advisory and consulting services Stripe or its subcontractors provide, as described on the Order Form, the Data Sheet and the Stripe Website.
Supporting quotations
“Stripe Professional Services” means the advisory and consulting services provided by Stripe or its subcontractors as described on the Professional Services Order Form, Professional Services Data Sheet, and Stripe Website.
Security & Safeguards · Context
Radar Terms add to the General Terms and incorporate Payments and Orchestrated Terms (last modified Sept. 28, 2026)
These Stripe Radar Terms, last modified September 28, 2026, supplement the General Terms and, together with the Stripe Payments Terms (as applicable) and the Stripe Orchestrated Services Terms (as applicable to the Stripe Radar API Service), which they incorporate by reference, govern the use of the Stripe Radar Services and Stripe Radar Data. Capitalized terms not defined here take their meaning from those three sets of terms.
Supporting quotations
Last modified: September 28, 2026
These terms (“Stripe Radar Terms”) supplement the General Terms and, together with the Stripe Payments Terms (as applicable), and the Stripe Orchestrated Services Terms (as applicable to use of the Stripe Radar API Service), which are incorporated into these Stripe Radar Terms by this reference govern the use of the Stripe Radar Services and Stripe Radar Data. Capitalized terms that are not defined in these Stripe Radar Terms have the same meanings given to them in the General Terms, Stripe Payments Terms, and the Stripe Orchestrated Services Terms.
Qualifications & exceptions
The Payments Terms and Orchestrated Services Terms apply as applicable.
Account & Service Control · Company practice
Radar Services may be on by default, and you must contact Stripe to disable them
The Stripe Radar Services may be enabled by default. A User that does not want to use them must contact Stripe to disable them.
Supporting quotations
2. Stripe Radar Services on by Default.
The Stripe Radar Services may be enabled by default. If User does not wish to use these Services, User must [contact Stripe](https://stripe.com/contact) to disable them.
Qualifications & exceptions
Enablement by default is a possibility (“may”).
Not stated here
The terms do not say how quickly Stripe disables the services once asked.
Security & Safeguards · Restriction or exception
You may use Radar only to detect and block fraud, and Radar for Platforms only to investigate Connected Accounts
The User may use the Stripe Radar Services and Radar Data only (a) to help detect and block actual or potential fraud and unauthorized Transactions in connection with the Services, and (b) for the Stripe Radar API Service only, to help detect and block fraud and unauthorized transactions related to its transactions processed through Third-Party PSPs. The User may use the Radar for Platforms Service to help detect and investigate whether Connected Accounts may be engaging in actual or potential fraudulent behavior, in connection with the Services. The Radar API Service lets the User send Orchestrated Input Data to Stripe and access the Radar Services and Orchestrated Output Data.
Supporting quotations
3. Permitted Use.
User may use the Stripe Radar Services and Stripe Radar Data only:
(a) to help detect and block actual or potential fraud and unauthorized Transactions, in each case in connection with the Services; and
(b) in the case of the Stripe Radar API Service only, to help detect and block actual or potential fraud and unauthorized transactions in each case related to User’s transactions processed through Third-Party PSPs.
User may use the Radar for Platforms Service to help detect and investigate whether Connected Accounts may be engaging in actual or potential fraudulent behavior, in each case in connection with the Services.
“Stripe Radar API Service” means the Services, including an API, that (a) provide User with a means of sending to Stripe the Orchestrated Input Data and access to the Stripe Radar Services and the Orchestrated Output Data, and (b) is designed to enable User to help detect and prevent actual or potential fraud, or unauthorized transactions, related to User’s business and transactions processed through other payment service providers.
“Stripe Radar for Platforms Service” means the Services that are designed to enable User to help detect and investigate whether Connected Accounts may be engaging in actual or potential fraudulent behavior, in each case in connection with the Services.
Qualifications & exceptions
Third-Party PSP transactions are covered only for the Radar API Service.
Radar for Platforms is limited to fraud detection and investigation about Connected Accounts.
Use & Processing · Restriction or exception
No use of Radar for credit, insurance, housing or employment decisions, discrimination or adverse action
The User must not, and must not let any third party, use the Radar Services or Radar Data (a) as a factor in deciding anyone's eligibility for credit, insurance, housing or employment, or in a way that could make Stripe a consumer reporting agency or make the Radar Data a consumer report under the FCRA (as applicable); or (e) to discriminate on race, gender or other protected characteristics, or to take any adverse action as the FCRA describes it (as applicable).
Supporting quotations
4. Services Restrictions.
User must not, and must not enable or allow any third party to:
(a) use the Stripe Radar Services or Stripe Radar Data as a factor in determining a person’s eligibility for credit, insurance, housing or employment, or in any way that could cause Stripe to be a “consumer reporting agency” or cause the Stripe Radar Data to constitute a “consumer report,” in each case as described in the FCRA (as applicable);
(e) use the Stripe Radar Services or Stripe Radar Data to discriminate based on race, gender, or other protected characteristics, or take any “adverse action” as that term is described in the FCRA (as applicable);
Qualifications & exceptions
The FCRA references apply only as applicable.
The ban reaches third parties the User enables or allows.
Sharing & Disclosure · Restriction or exception
No selling, sharing, disclosing, downloading or storing Radar Data
The User must not, and must not let a third party, (b) sell, rent, transfer, make available or communicate Radar Data orally or by other means, with “sell” as the CCPA defines it where applicable, or (c) disclose, download or store Radar Data. Disclosure is allowed where Law requires it or the Agreement otherwise permits it.
Supporting quotations
User must not, and must not enable or allow any third party to:
(b) sell, rent, transfer, make available, or communicate orally or through other means Stripe Radar Data (including as the term “sell” is defined in the CCPA, as applicable);
(c) disclose (except as Law requires or this Agreement otherwise permits), download or store Stripe Radar Data;
Qualifications & exceptions
Disclosure is allowed where Law requires it or the Agreement otherwise permits.
The ban reaches third parties the User enables or allows.
Use & Processing · Restriction or exception
No building competing models or products, marketing use, or evaluating transactions outside the Services
The User must not, and must not let a third party, (d) use the Radar Services or Data to develop, test, validate, train, enhance or deploy machine learning models or algorithms that substitute for or are substantially similar to the Services, or to develop or commercially offer any security or fraud detection product or service; (f) use them for marketing purposes; or (h) except as Section 3 permits, use them to evaluate transactions not processed through the Services. Section 3 permits use for the User's transactions processed through Third-Party PSPs, for the Radar API Service only.
Supporting quotations
User must not, and must not enable or allow any third party to:
(d) use the Stripe Radar Services or Stripe Radar Data to: (i) develop, test, validate, train, enhance or deploy any machine learning models or algorithms that are a substitute for, or substantially similar to, the Services; or (ii) otherwise directly or indirectly develop or otherwise make available on a commercial basis any security or fraud detection product or service;
(f) use the Stripe Radar Services or Stripe Radar Data for marketing purposes;
(h) except as Section 3 of the Stripe Radar Terms permits, use the Stripe Radar Services or Stripe Radar Data to evaluate transactions not processed through the Services.
3. Permitted Use.
Qualifications & exceptions
The evaluation ban has an exception for what Section 3 permits.
Use & Processing · Restriction or exception
Radar for Platforms: no test data use, and not the sole input into decisions about Connected Accounts
The User must not use the Stripe Radar for Platforms Service (i) for any purpose not tied to a live Transaction, such as test or dummy Account Features, or (ii) as the sole input into any decision-making process, such as automated decision-making or profiling, the User applies when deciding to begin, cease or refrain from a business relationship with any Connected Account. Account Features means Stripe's merchant level fraud protection system.
Supporting quotations
User must not, and must not enable or allow any third party to:
(g) use the Stripe Radar for Platforms Service: (i) for any purpose not associated with a live Transaction (e.g. test or dummy Account Features); or (ii) as the sole input into any decision making process (e.g. automated decision making, profiling) User applies when deciding to begin engaging, cease engaging, or refrain from engaging in a business relationship with any Connected Accounts; or
“Account Features” means Stripe’s merchant level fraud protection system.
Qualifications & exceptions
Applies to the Radar for Platforms Service only.
Legal Rights & Agreement Rules · Restriction or exception
You are solely responsible for how you use Radar and for the decisions and actions you take
The User is solely responsible for its use of the Radar Services and Radar Data, and for the decisions it makes and actions it takes in connection with them.
Supporting quotations
5.1 Responsibility for Decisions.
(a) Use of the Stripe Radar Services and Stripe Radar Data. User is solely responsible for User’s use of the Stripe Radar Services and Stripe Radar Data, as well as the decisions User makes and the actions User takes in connection with the Stripe Radar Services and Stripe Radar Data.
Use & Processing · Restriction or exception
You choose your Radar rules, added rules may slow settlement, and Stripe may change rules without notice
The User is solely responsible for choosing which rules, default or custom, it uses with the Radar Services. Choosing to add and use additional rules may lengthen settlement times for applicable Transactions. Without further notice to the User, Stripe may make general or specific changes to the rules that may alter the Radar Services.
Supporting quotations
(b) Stripe Radar Services Rules. User is solely responsible for choosing which rules (default or custom) User uses with the Stripe Radar Services. User’s choice to input and use additional rules with the Stripe Radar Services may result in longer settlement times for applicable Transactions. Without further notice to User, Stripe may make general or specific changes to the rules that may alter the Stripe Radar Services.
Qualifications & exceptions
Longer settlement is a possibility tied to added rules.
Stripe's rule changes need no further notice.
Not stated here
The terms give no figure for how much longer settlement may take.
Use & Processing · Restriction or exception
You must offer Connected Accounts human review and pass on reported Radar for Platforms errors to Stripe
The User will give Connected Accounts the chance to seek human review of any decision where the Radar for Platforms Service was an input. If a Connected Account gives the User additional information that the User believes shows imprecision, inaccuracies or errors in the Service or its operation, the User will give Stripe that information in the manner the Documentation prescribes.
Supporting quotations
(c) Connected Accounts. User will provide Connected Accounts with the opportunity to seek human review of any decisions User makes where the Stripe Radar for Platforms Service was used as an input into that decision. If a Connected Account provides User with any additional information that indicates what User believes to be imprecision, inaccuracies, or errors in the Stripe Radar for Platforms Service and/or in the operation of the Stripe Radar for Platforms Service, User will provide Stripe with this additional information in a manner prescribed in the Documentation.
Qualifications & exceptions
Applies to decisions where Radar for Platforms was used as an input.
Not stated here
The Documentation's prescribed manner is not supplied.
Use & Processing · Company practice
Radar Scores are snapshots that do not auto-update, built from data on transactions through Stripe services
Each Radar Score is based on data available to the Radar Services when it is generated and does not automatically update when that data later changes. A Radar Score is a numerical risk score or level for a transaction, Connected Account or other related activity. The Radar Services use data from transactions processed through the Stripe services, which may include the User's Transactions.
Supporting quotations
5.2 Disclaimers.
(a) Radar Scores. Each Radar Score is based on data available to the Stripe Radar Services at the time it is generated, and the Radar Score does not auto-update to reflect a subsequent change to data that was used to generate that Radar Score.
(b) Data from Transactions. The Stripe Radar Services use data from transactions processed through the Stripe services, which may include User Transactions.
“Radar Score” means a numerical risk score or level associated with a transaction, Connected Account, or other related activity that the Stripe Radar Services provides.
Qualifications & exceptions
A score reflects the data available at the time it was generated.
Not stated here
The terms do not say how often scores are regenerated.
Legal Rights & Agreement Rules · Restriction or exception
Radar Data is not advice, and Stripe is not liable for fraud, wrongly blocked sales or data accuracy
The Radar Data is not legal or compliance advice, or advice on whether the User should go ahead with a transaction with another person. Stripe is not liable for losses, damages, costs, fines, fees or penalties relating to (i) fraudulent Transactions and other fraud, including by third party payment service providers; (ii) non-fraudulent transactions the Radar Services may block; or (iii) the accuracy or inaccuracy of the Radar Data, and any actions the User or Stripe takes based on it.
Supporting quotations
5.2 Disclaimers.
(c) Nature of Stripe Radar Data. The Stripe Radar Data does not constitute legal or compliance advice, or advice as to whether User should proceed with a transaction with another person.
(d) Stripe Liability. Stripe is not liable for any losses, damages, costs, fines, fees, or penalties relating to (i) fraudulent Transactions and other fraudulent activity, including fraudulent activity untaken by third party payment service providers; (ii) non-fraudulent transactions that may be blocked by the Stripe Radar Services; or (iii) the accuracy (or inaccuracy) of the Stripe Radar Data, and any actions that User or Stripe may take based on the Stripe Radar Data.
Qualifications & exceptions
The liability disclaimer covers actions taken by either the User or Stripe based on the Radar Data.
Not stated here
Whether other parts of the Agreement limit or restore any of these disclaimers is not stated here.
Legal Rights & Agreement Rules · Restriction or exception
Stripe is not liable for fraud, wrongly blocked transactions, or the accuracy of Radar Data and actions based on it
Stripe is not liable for losses, damages, costs, fines, fees or penalties relating to (i) fraudulent Transactions and other fraudulent activity, including fraud by third party payment service providers; (ii) non-fraudulent transactions the Radar Services may block; or (iii) the accuracy or inaccuracy of the Radar Data, and any actions the User or Stripe may take based on the Radar Data.
Supporting quotations
(d) Stripe Liability. Stripe is not liable for any losses, damages, costs, fines, fees, or penalties relating to (i) fraudulent Transactions and other fraudulent activity, including fraudulent activity untaken by third party payment service providers; (ii) non-fraudulent transactions that may be blocked by the Stripe Radar Services; or (iii) the accuracy (or inaccuracy) of the Stripe Radar Data, and any actions that User or Stripe may take based on the Stripe Radar Data.
(c) Nature of Stripe Radar Data. The Stripe Radar Data does not constitute legal or compliance advice, or advice as to whether User should proceed with a transaction with another person.
Qualifications & exceptions
Covers actions by either the User or Stripe based on Radar Data.
Not stated here
Whether other parts of the Agreement limit or restore this disclaimer is not stated here.
Data Access & Collection · Company practice
Stripe collects device and activity signals and may share them with other Stripe users; you must disclose this
In providing the Radar Services, Stripe collects and uses, and may make available to other Stripe users, information about device characteristics and customer activity indicators that may help Stripe users detect and block actual or potential fraud. The User affirms that its Privacy Policy fully discloses to Customers these types of data collection and use, including sharing the data with Stripe and Stripe using it. More information is in the Documentation under “Advanced Fraud Protection” and in Stripe's Privacy Policy.
Supporting quotations
6. Additional Terms Regarding Personal Data and Compliance.
6.1 Privacy Disclosures.
In providing the Stripe Radar Services, Stripe collects, uses and may make available to other Stripe users information regarding device characteristics and customer activity indicators that may help Stripe users detect and block actual or potential fraud. User affirms that User’s Privacy Policy fully discloses to Customers these types of data collection and use, including sharing this data with Stripe and Stripe using this data. More information is available under the topic “Advanced Fraud Protection” in the Documentation and in Stripe's [Privacy Policy](https://stripe.com/privacy).
Qualifications & exceptions
Sharing with other Stripe users is a possibility (“may”).
Not stated here
The Documentation topic and Stripe's Privacy Policy are linked and not supplied.
Data Access & Collection · User right or choice
You may add Stripe's example wording to your Privacy Policy if it lacks a disclosure to this effect
The User may choose to add Stripe's suggested wording to its Privacy Policy if the policy does not already include a disclosure to this effect. The wording says the business uses Stripe for payment, analytics and other business services, and that Stripe collects transaction and personally identifying information it analyzes and uses to operate and improve its services, including for fraud detection, with a link to Stripe's privacy policy.
Supporting quotations
6.2 Example Disclosure.
User may choose to add the following to User’s Privacy Policy if it does not already include a disclosure to this effect:
“We use Stripe for payment, analytics, and other business services. Stripe collects transaction and personally identifying information, which it analyzes and uses to operate and improve the services it provides to us, including for fraud detection. User can learn more about Stripe and read its privacy policy [here](https://stripe.com/privacy).”
Qualifications & exceptions
Adding the wording is optional.
Not stated here
Whether the example wording alone satisfies the User's duty to disclose is not stated.
Account & Service Control · Restriction or exception
You must answer Stripe's compliance information requests within 14 days, or Stripe may suspend or end Radar access
Within 14 days after Stripe's request, the User must give the information and documentation Stripe asks for to ensure the User complies with the Radar Terms. Stripe may suspend or terminate the User's access to the Radar Services immediately on notice if the User fails to provide it.
Supporting quotations
6.3 Requests for Compliance Information.
Within 14 days after Stripe’s request, User must provide information and documentation that Stripe requests for the purpose of ensuring User’s compliance with these Stripe Radar Terms. Stripe may suspend or terminate User’s access to the Stripe Radar Services immediately upon notice to User if User fails to provide information or documentation Stripe requests under this Section 6.3.
Qualifications & exceptions
The 14 days run from Stripe's request.
Suspension or termination is immediate on notice.
Retention & Deletion · Restriction or exception
Radar Data is Stripe Data: delete it on termination or request, though you may keep copies Law requires
Radar Data is Stripe Data under the Agreement. The User must promptly delete or destroy all Radar Data in its possession or control received through the Radar Services (a) when the Radar Terms end and (b) at any time Stripe asks. The User may keep copies if Law requires.
Supporting quotations
7. Stripe Radar Data.
Stripe Radar Data is Stripe Data for the purposes of this Agreement. User must promptly delete or destroy all Stripe Radar Data in User’s possession or control that User received in connection with the Stripe Radar Services (a) upon termination of these Stripe Radar Terms; and (b) at any time upon Stripe’s request. User may retain copies of Stripe Radar Data, if required by Law.
Qualifications & exceptions
The retention exception applies if Law requires it.
Not stated here
Unlike the parallel fraud tools clause, this one does not limit use of retained copies.
Use & Processing · Context
Definitions: Radar Score, Radar Data, Radar Services, Radar API Service and Radar for Platforms Service
A Radar Score is a numerical risk score or level for a transaction, Connected Account or other activity that the Radar Services provide. Radar Data is the Radar Scores and other data the User receives through the Radar Services and, as applicable, the Orchestrated Services. The Radar Services are the Services designed to let the User detect and evaluate the risk that a transaction, Connected Account or other activity is fraudulent. The Radar API Service includes an API through which the User sends Stripe Orchestrated Input Data and accesses the Radar Services and Orchestrated Output Data, to help detect and prevent fraud or unauthorized transactions in its business processed through other payment service providers. The Radar for Platforms Service helps detect and investigate whether Connected Accounts may be engaging in fraud.
Supporting quotations
“Radar Score” means a numerical risk score or level associated with a transaction, Connected Account, or other related activity that the Stripe Radar Services provides.
“Stripe Radar Data” means the Radar Scores and other data User receives through the Stripe Radar Services, and the Stripe Orchestrated Services (as applicable).
“Stripe Radar Services” means the Services that are designed to enable User to detect and evaluate the risk that a transaction, Connected Account, or other related activity is fraudulent.
“Stripe Radar API Service” means the Services, including an API, that (a) provide User with a means of sending to Stripe the Orchestrated Input Data and access to the Stripe Radar Services and the Orchestrated Output Data, and (b) is designed to enable User to help detect and prevent actual or potential fraud, or unauthorized transactions, related to User’s business and transactions processed through other payment service providers.
“Stripe Radar for Platforms Service” means the Services that are designed to enable User to help detect and investigate whether Connected Accounts may be engaging in actual or potential fraudulent behavior, in each case in connection with the Services.
“Orchestrated Input Data” means any data provided by User to Stripe to enable Stripe to perform the Orchestrated Services, including (i) any third party data included in a Standalone 3DS request as described in the Documentation or otherwise envisaged by the Stripe Orchestrated Services, including without limitation acquirer BIN, merchant ID, and requestor ID and (ii) the results of previously-provided Orchestrated Input Data, which may include accuracy rate, outcome of the payment, User’s decision to process or decline the transaction, updates to the payment status, dispute rate, and dispute code, among other things.
“Orchestrated Output Data” means any data User receives through the Stripe Orchestrated Services which has been produced by a proprietary Stripe model.
Use & Processing · Context
Definitions: Account Features and Connected Account
Account Features means Stripe's merchant level fraud protection system. A Connected Account is either a Platform User with a Stripe Account onboarded to a Stripe Connect Platform through the Stripe Connect Services, or a Payout Recipient.
Supporting quotations
“Account Features” means Stripe’s merchant level fraud protection system.
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
Legal Rights & Agreement Rules · Context
Definitions: CCPA and FCRA, with the statute citations as written in the source
CCPA means the California Consumer Privacy Act of 2018, Cal. Civ. Code Sections 1798.100-1798.199. FCRA is defined as the Fair Credit Reporting Act and the Equal Credit Opportunity Act, and the source cites the same “15 U.S.C. Section 1681, et seq.” for both. This explanation reports the citations as written and does not resolve the laws.
Supporting quotations
“CCPA” means California Consumer Privacy Act of 2018, Cal. Civ. Code Sections 1798.100-1798.199.
“FCRA” means Fair Credit Reporting Act, 15 U.S.C. Section 1681, et seq. and Equal Credit Opportunity Act, 15 U.S.C. Section 1681, et seq.
Qualifications & exceptions
The FCRA definition names two Acts but gives one identical citation for both, as written in the source.
Not stated here
The cited statutes are not supplied; the repeated FCRA citation is left as written.
Charges & Financial Obligations · Context
Revenue Recognition Terms add to the General Terms (last modified November 18, 2025)
These RevRec Terms, last modified November 18, 2025, supplement the General Terms and govern the use of the Stripe Revenue Recognition Services and RevRec Data. Capitalized terms not defined here take their General Terms meaning. The Services automate revenue recognition and reporting, and RevRec Data is data the Services generate, organize or otherwise analyze.
Supporting quotations
Last modified: November 18, 2025
These terms (“RevRec Terms”) supplement the General Terms and govern the use of the Stripe Revenue Recognition Services and RevRec Data. Capitalized terms that are not defined in these terms have the same meanings given to them in the General Terms.
“RevRec Data” means data generated by, organized by or otherwise analyzed by Stripe Revenue Recognition Services.
“Stripe Revenue Recognition Services” means Services that enable a User to automate revenue recognition and reporting.
Charges & Financial Obligations · Restriction or exception
You are solely responsible for configuring the service and for the accuracy and legality of RevRec Data
The User is responsible for configuring the Revenue Recognition Services for its needs and to comply with Law. It is solely responsible for the accuracy, quality and legality of RevRec Data, including deciding whether the data is accurate, meets relevant standards or regulations, or is otherwise enough for its purposes. The User must not, and must make sure its Connected Accounts (if applicable) do not, use the Services in connection with Protected Health Information.
Supporting quotations
2. Use of the RevRec Services.
User is responsible for configuring Stripe Revenue Recognition Services for its needs and to comply with Law. User is solely responsible for the accuracy, quality, and legality of RevRec Data, including determining whether the RevRec Data is accurate, compliant with relevant standards or regulations, or otherwise sufficient for User’s purposes. User must not, and must ensure that its Connected Accounts (if applicable) do not, use the Stripe Revenue Recognition Services in connection with Protected Health Information.
Qualifications & exceptions
The Protected Health Information ban extends to the User's Connected Accounts, if applicable.
Not stated here
Protected Health Information is not defined in this document.
Sharing & Disclosure · Company practice
By enabling Third-Party Services you accept that RevRec Data may flow between them and Stripe
By enabling the Third-Party Services, the User understands that RevRec Data may flow between the Third-Party Services and Stripe.
Supporting quotations
3. Third-Party Services.
By enabling the Third-Party Services, User understands that RevRec Data may flow between the Third-Party Services and Stripe.
Qualifications & exceptions
Data flow is a possibility (“may”) once the User enables the Third-Party Services.
Not stated here
Which Third-Party Services are meant and what data they receive is not stated in this section.
Account & Service Control · Context
Definition: Connected Account (a Platform User onboarded to a Stripe Connect Platform, or a Payout Recipient)
A Connected Account is either a Platform User with a Stripe Account onboarded to a Stripe Connect Platform through the Stripe Connect Services, or a Payout Recipient.
Supporting quotations
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
Charges & Financial Obligations · Context
Stablecoin Treasury Terms add to the General and Financial Services Terms; Preview Services (modified Sept. 28, 2026)
These Stripe Stablecoin Treasury Terms, last modified September 28, 2026, supplement the General Terms and, together with the Stripe Financial Services Terms, which they incorporate by reference, govern the User's use of the Stripe Stablecoin Treasury Services (formerly Stablecoin Financial Accounts). Capitalized terms not defined here take their meaning from those two sets of terms. The services are Preview Services.
These terms ("Stripe Stablecoin Treasury Terms") supplement the General Terms and, together with the Stripe Financial Services Terms which are incorporated into these Stripe Stablecoin Treasury Terms by this reference, govern User's use of the Stripe Stablecoin Treasury Services. Capitalized terms that are not defined in these Stripe Stablecoin Treasury Terms have the same meanings given to them in the General Terms or the Stripe Financial Services Terms. The Stripe Stablecoin Treasury Services are Preview Services.
Qualifications & exceptions
The services are Preview Services.
Not stated here
What Preview status changes for the User is set by other parts of the General Terms.
Charges & Financial Obligations · Company practice
The service lets you hold funds with the Stablecoin Partner; Stripe does not convert, hold or transfer Stablecoin
The Stripe Stablecoin Treasury Services let the User hold funds with the Stablecoin Partner and access and use the Stablecoin Partner Services. Stripe does not convert, hold custody of or transfer any Stablecoin as part of its services. They are the user interface, data transmission, user support and related technology services that let the User reach the Stablecoin Partner Services. Because they require the Stablecoin Partner Services to be performed, the User's use of Stripe's services is also its simultaneous access to and use of the Stablecoin Partner Services.
Supporting quotations
2. Stablecoin Treasury Services.
2.1 Overview; Stripe's Rights and Obligations.
The Stripe Stablecoin Treasury Services enable User to hold funds with the Stablecoin Partner, and access and use the Stablecoin Partner Services. Stripe does not convert, hold custody of, or transfer any Stablecoin as a component of the Stripe Stablecoin Treasury Services.
Because the Stripe Stablecoin Treasury Services necessarily involve and require the performance of Stablecoin Partner Services, User's use of the Stripe Stablecoin Treasury Services constitutes User's simultaneous access to and use of the Stablecoin Partner Services.
"Stripe Stablecoin Treasury Services" means the user interface, data transmission, user support, and related technology services that enable User to access and use the Stablecoin Partner Services.
Qualifications & exceptions
Stripe's role is the interface and related technology services, not custody or conversion.
Using Stripe's services counts as using the Stablecoin Partner Services at the same time.
Account & Service Control · Permission or license
Stripe may add or restrict access to particular Stablecoin or fiat denominations or transaction types at any time
Stripe may add or restrict access in the User's Stripe Account to particular denominations of Stablecoin or fiat currency, or types of Stablecoin Partner Transactions, at any time.
Supporting quotations
Stripe may add or restrict access in User's Stripe Account to particular denominations of Stablecoin or fiat currency, or types of Stablecoin Partner Transactions, at any time.
Qualifications & exceptions
Available at any time.
Not stated here
The terms give no notice period for changes.
Charges & Financial Obligations · Restriction or exception
The Stablecoin Partner is a Financial Provider, you are bound by its terms, and Stripe may add or remove partners
The Stablecoin Partner is a Financial Provider, and the Stablecoin Partner Terms, which govern its rights and obligations in carrying out the User's Stablecoin Partner Transactions, are Financial Provider Terms. By using the services the User agrees to be bound by the applicable Stablecoin Partner Terms as well as these terms. Stripe will identify the applicable Stablecoin Partner during onboarding and may add or remove Stablecoin Partners in its sole discretion.
Supporting quotations
2.2 Stablecoin Partner.
The Stablecoin Partner is a Financial Provider, and the Stablecoin Partner Terms, which govern the Stablecoin Partner's rights and obligations with respect to performing User's Stablecoin Partner Transactions, are Financial Provider Terms. By using the Stripe Stablecoin Treasury Services, User agrees to be bound by the applicable Stablecoin Partner Terms in addition to these Stripe Stablecoin Treasury Terms. Stripe will identify the applicable Stablecoin Partner to User during the onboarding process for the Stripe Stablecoin Treasury Services, and Stripe may add or remove Stablecoin Partners in its sole discretion.
Qualifications & exceptions
Stripe may change partners in its sole discretion.
Not stated here
The Stablecoin Partner Terms are not part of this saved text.
Account & Service Control · Restriction or exception
To use the Partner Services you must be located and incorporated in a supported place and follow Partner Terms
To access and use the Stablecoin Partner Services the User must (a) be located and incorporated in a jurisdiction that Stripe and the Stablecoin Partner support for the services; (b) accept the applicable Stablecoin Partner Terms; and (c) comply with them at all times. The Stablecoin Partner may add or remove supported Stablecoins and fiat currencies, as its Partner Terms provide, at any time.
Supporting quotations
To access and use the Stablecoin Partner Services, User must (a) be located and incorporated in a jurisdiction that Stripe and the Stablecoin Partner support in connection with the Stripe Stablecoin Treasury Services; (b) accept the applicable Stablecoin Partner Terms; and (c) comply with the applicable Stablecoin Partner Terms at all times. The Stablecoin Partner may add or remove supported Stablecoins and fiat currencies as provided in its Stablecoin Partner Terms, at any time.
Qualifications & exceptions
All three conditions apply.
The Partner may change supported currencies at any time.
Not stated here
The supported jurisdictions are not listed in these terms.
Legal Rights & Agreement Rules · Restriction or exception
Stripe is not liable for suspensions, your errors, Partner rejections, Partner insolvency or irreversible transactions
To the extent Law permits, Stripe is not liable to the User for losses, damages or costs from (a) suspension, termination or interruption of the Stablecoin Treasury Services or the Stablecoin Partner Services; (b) the User giving incorrect information on a Stablecoin Partner Transaction; (c) the User or a third party trying to start a transaction the Partner does not support; (d) the Partner rejecting a transaction for any reason; (e) the Partner rejecting, delaying or failing to complete a Stablecoin Payout Transaction for any reason; (f) the Partner's default, insolvency or bankruptcy; or (g) the irreversibility of any Stablecoin Partner Transaction, including an exchange of fiat for Stablecoin that cannot be unwound once the Partner starts it. A Stablecoin Partner Transaction is a Stablecoin or fiat transmission, exchange, custody or other transaction requested or executed through the Partner Services.
Supporting quotations
2.3 Disclaimer.
To the extent Law permits, Stripe is not liable to User for any losses, damages, or costs resulting from: (a) the suspension or termination of, or interruptions to, the Stripe Stablecoin Treasury Services or the Stablecoin Partner Services; (b) User providing incorrect information in connection with a Stablecoin Partner Transaction; (c) User or any third party attempting to initiate a Stablecoin Partner Transaction that is not supported by the Stablecoin Partner; (d) the Stablecoin Partner rejecting a Stablecoin Partner Transaction, for any reason; (e) the Stablecoin Partner rejecting, delaying, or failing to complete a Stablecoin Payout Transaction for any reason; (f) the Stablecoin Partner’s default, insolvency, or bankruptcy; or (g) the irreversibility of any Stablecoin Partner Transaction, including any exchange of fiat currency for Stablecoin that cannot be unwound once initiated by the Stablecoin Partner.
“Stablecoin Partner Transaction” means a Stablecoin or fiat currency transmission, exchange, custody, or other transaction that is requested or executed via the Stablecoin Partner Services.
Qualifications & exceptions
The disclaimer applies to the extent Law permits.
Covers the Partner's insolvency and the irreversibility of transactions.
Charges & Financial Obligations · Permission or license
After a Depeg Event, Stripe and the Partner may immediately suspend, or continue at the prevailing market exchange rate
If a Depeg Event occurs, Stripe and the Stablecoin Partner may immediately (a) suspend the services for the affected Stablecoin, including new exchanges of fiat for that Stablecoin, or (b) continue providing the services for it at its prevailing Stablecoin-to-fiat market exchange rate. A Depeg Event is any occurrence where Stripe or the Partner determines, in its sole discretion, that a Stablecoin's price has failed to keep its intended peg to the fiat value it is linked to.
Supporting quotations
2.4 Depeg Event.
If a Depeg Event occurs, Stripe and the Stablecoin Partner may immediately (a) suspend the Stripe Stablecoin Treasury Services with respect to the affected Stablecoin, including suspending any new exchanges of fiat currency for the affected Stablecoin; or (b) continue providing the Stripe Stablecoin Treasury Services with respect to the affected Stablecoin at its prevailing Stablecoin-to-fiat market exchange rate.
“Depeg Event” means any occurrence where Stripe or the Stablecoin Partner determines, in its sole discretion, that the price of a Stablecoin has failed to maintain its intended peg to the fiat value to which it is linked.
Qualifications & exceptions
Whether a Depeg Event has happened is decided by Stripe or the Partner in its sole discretion.
Action can be immediate.
Legal Rights & Agreement Rules · Restriction or exception
Value held during a Depeg Event is set by the Partner Terms, and Stripe is not liable for depeg losses
The value of Stablecoin held in custody with the Stablecoin Partner during a Depeg Event is governed solely by the Stablecoin Partner Terms. Stripe is not liable to the User for losses, damages or costs from a Depeg Event, or from actions Stripe or the Partner takes in connection with one, including any difference between the exchange rate when the User accepts payment in Stablecoin and the rate at which the Partner executes the exchange, if it chooses to do so.
Supporting quotations
The value of Stablecoin held in custody with the Stablecoin Partner during a Depeg Event is governed solely by the Stablecoin Partner Terms. Stripe is not liable to User for any losses, damages, or costs arising from a Depeg Event, or any actions taken by Stripe or the Stablecoin Partner in connection with a Depeg Event, including any difference between the exchange rate applicable at the time User accepts payment in Stablecoin and the rate at which the Stablecoin Partner executes the exchange, if it chooses to do so.
Qualifications & exceptions
Exchange rate differences are covered by the disclaimer.
Not stated here
The Stablecoin Partner Terms that govern value are not supplied.
Charges & Financial Obligations · Restriction or exception
Stablecoin transactions may be taxed, and Stripe does not assess, collect, report or remit your Taxes or give advice
Transactions in Stablecoin may be subject to Taxes. The User acknowledges that tax Laws for Stablecoin transactions may be uncertain and evolving, and that it is not Stripe's responsibility to assess, collect, report or remit Taxes the User owes from (a) using the Stablecoin Treasury Services, (b) using the Stablecoin Partner Services, or (c) any other transactions with a Stablecoin Partner. Stripe does not provide investment or tax advice.
Supporting quotations
3. Taxes.
Transactions in Stablecoin may be subject to Taxes. User acknowledges that tax Laws applicable to Stablecoin transactions may be uncertain and evolving, and that it is not Stripe's responsibility to assess, collect, report, or remit any Taxes owed by User arising from: (a) the use of the Stripe Stablecoin Treasury Services; (b) the use of the Stablecoin Partner Services; or (c) any other transactions User may enter into with a Stablecoin Partner. Stripe does not provide investment or tax advice.
Qualifications & exceptions
Tax law for Stablecoin transactions is described as uncertain and evolving.
Sharing & Disclosure · Company practice
Stripe may file tax information reports and send you copies, and the Stablecoin Partner may report separately
Stripe may be required to submit tax information reports to tax authorities about these transactions and may send the User a copy. Law may require Stripe to file periodic informational returns with taxing authorities about the User's use of the services, and Stripe may send tax-related information to the User electronically. The Stablecoin Partner may also have independent tax reporting obligations for Stablecoin Partner Transactions, as its Partner Terms describe.
Supporting quotations
Stripe may be required to submit tax information reports to tax authorities regarding these transactions and may send User a copy of such tax information. Specifically, Law may require Stripe to file periodic informational returns with taxing authorities related to User's use of the Stripe Stablecoin Treasury Services, and Stripe may send tax-related information electronically to User. The Stablecoin Partner may also have independent tax reporting obligations with respect to Stablecoin Partner Transactions, as described in the applicable Stablecoin Partner Terms.
Qualifications & exceptions
Filings are described as what Law may require.
Not stated here
The terms do not say what information goes to tax authorities.
Sharing & Disclosure · Permission or license
You authorize Stripe and its Affiliates to share your information and Personal Data with the Stablecoin Partner
The User authorizes Stripe and its Affiliates to share information about the User, including Personal Data, with the Stablecoin Partner as necessary to let the User access and use the Stripe Stablecoin Treasury Services and the Stablecoin Partner Services.
Supporting quotations
4. Privacy.
User authorizes Stripe and its Affiliates to share information about User, including Personal Data, with the Stablecoin Partner as necessary to enable User to access and use the Stripe Stablecoin Treasury Services and the Stablecoin Partner Services.
Qualifications & exceptions
Sharing is limited to what is necessary to let the User use the services.
Not stated here
The terms do not list the categories of information shared.
Use & Processing · Restriction or exception
Where Law requires, you must tell your customers and counterparties that the Stablecoin Partner may process their data
Where Law requires, the User must make sure its customers and counterparties are told that it uses Stripe and the Stablecoin Partner for Stablecoin-related services, and that their data may be processed by the Stablecoin Partner under the Partner's privacy policy, as made available in the applicable Stablecoin Partner Terms.
Supporting quotations
User must ensure that, where required by Law, User's customers and counterparties are informed that User uses Stripe and the Stablecoin Partner in connection with Stablecoin-related services, and that their data may be processed by the Stablecoin Partner in accordance with the Stablecoin Partner's privacy policy, as made available in the applicable Stablecoin Partner Terms.
Qualifications & exceptions
Applies where Law requires the notice.
Not stated here
The Stablecoin Partner's privacy policy is in the Partner Terms and is not supplied.
Charges & Financial Obligations · Context
Definitions: Stablecoin (fiat-backed cryptocurrency a Partner supports) and Depeg Event
A Stablecoin is any fiat-backed cryptocurrency supported by a Stablecoin Partner, which may be updated from time to time as the Stablecoin Partner Terms and the Documentation state. A Depeg Event is any occurrence where Stripe or the Stablecoin Partner determines, in its sole discretion, that a Stablecoin's price has failed to maintain its intended peg to the fiat value it is linked to.
Supporting quotations
5. Definitions.
"Stablecoin" means any fiat-backed cryptocurrency supported by a Stablecoin Partner, which may be updated from time to time as stated in the applicable Stablecoin Partner Terms and the Documentation.
“Depeg Event” means any occurrence where Stripe or the Stablecoin Partner determines, in its sole discretion, that the price of a Stablecoin has failed to maintain its intended peg to the fiat value to which it is linked.
“Depeg Event” means any occurrence where Stripe or the Stablecoin Partner determines, in its sole discretion, that the price of a Stablecoin has failed to maintain its intended peg to the fiat value to which it is linked.
Qualifications & exceptions
The list of supported Stablecoins can change over time.
A Depeg Event turns on Stripe's or the Partner's own determination.
A Stablecoin Partner is an entity, which may be a Stripe Affiliate or a third party, that provides Stablecoin-related services to the User, including exchange, custody, transmission or payout of Stablecoin, under the Stablecoin Partner Terms. Stablecoin Partner Services may include creating and maintaining accounts and wallet addresses for the User, exchanging Stablecoins and fiat, custody, transmission or payout of Stablecoins to designated wallets, and other Stablecoin-related services the Partner offers from time to time. Stablecoin Partner Terms are the terms that govern the Partner's provision of those services and the User's use of them, and they may be updated from time to time. A Stablecoin Partner Transaction is a Stablecoin or fiat transmission, exchange, custody or other transaction requested or executed through the Partner Services. The Stripe Stablecoin Treasury Services are the user interface, data transmission, user support and related technology services that let the User reach the Partner Services.
Supporting quotations
"Stablecoin Partner" means an entity, which may be a Stripe Affiliate or a third party, that provides Stablecoin-related services to User, including the exchange, custody, transmission, or payout of Stablecoin, under the applicable Stablecoin Partner Terms.
"Stablecoin Partner Services" means any services provided by a Stablecoin Partner to User in connection with Stripe's Stablecoin-related Services, which may include: (a) the creation and maintenance of accounts and associated wallet addresses for User; (b) the exchange or conversion of Stablecoins to fiat currency and vice versa; (c) the custody of Stablecoins; (d) the transmission or payout of Stablecoins to designated wallet addresses; and (e) such other Stablecoin-related services as the Stablecoin Partner may offer from time to time, as described in the applicable Stablecoin Partner Terms.
"Stablecoin Partner Terms" means the terms that govern the Stablecoin Partner's provision, and User's access to and use of, the Stablecoin Partner Services, and which may be updated from time to time.
“Stablecoin Partner Transaction” means a Stablecoin or fiat currency transmission, exchange, custody, or other transaction that is requested or executed via the Stablecoin Partner Services.
"Stripe Stablecoin Treasury Services" means the user interface, data transmission, user support, and related technology services that enable User to access and use the Stablecoin Partner Services.
Qualifications & exceptions
The Partner Terms and the range of Partner Services can change over time.
Not stated here
The Partner Terms are not part of this saved text.
Legal Rights & Agreement Rules · Context
Regional Terms apply for the listed countries and prevail over the Stablecoin Treasury Terms in a conflict
The Regional Terms apply for the countries or regions listed below them, and if they conflict with the Stablecoin Treasury Terms the Regional Terms prevail.
Supporting quotations
6. Regional Terms.
The following Regional Terms apply for the countries or regions below. If there is a conflict between the Stripe Stablecoin Treasury Terms and the Regional Terms, the Regional Terms prevail.
Qualifications & exceptions
The Regional Terms win in a conflict.
Charges & Financial Obligations · Company practice
United States: Bridge Building Inc is the Stablecoin Partner, and its Bridge terms are the Partner Terms
For Users in the United States, Bridge Building Inc is the Stablecoin Partner that provides Stablecoin Partner Services. The Bridge terms on or accessible from the Stablecoin Partner Terms section of the Stripe Legal Page are the Stablecoin Partner Terms that apply to Users in the United States.
Supporting quotations
United States.
The following Regional Terms apply for Users in the United States.
6.1 Stablecoin Partner.
Bridge Building Inc is the Stablecoin Partner that provides Stablecoin Partner Services in the United States. The Bridge terms located on or accessible from the Stablecoin Partner Terms section of the Stripe Legal Page are the Stablecoin Partner Terms applicable to Users in the United States.
Qualifications & exceptions
Applies to Users in the United States.
Not stated here
The Bridge terms are linked from the Stripe Legal Page and are not supplied here.
Charges & Financial Obligations · Company practice
Outside the US, UK and EEA: Bridge Building Limited is the Stablecoin Partner and its Bridge terms apply
The Regional Terms for countries outside the United States, United Kingdom and European Economic Area prevail over the Stablecoin Treasury Terms in a conflict. For Users there, Bridge Building Limited is the Stablecoin Partner that provides Stablecoin Partner Services, and the Bridge terms on or accessible from the Stablecoin Partner Terms section of the Stripe Legal Page are the Stablecoin Partner Terms that apply.
Supporting quotations
Territories Outside the United States.
The following Regional Terms apply for countries that are outside the United States, United Kingdom, and European Economic Area. If there is a conflict between the Stripe Stablecoin Treasury Terms and the Regional Terms, the Regional Terms prevail.
6.1 Stablecoin Partner.
Bridge Building Limited is the Stablecoin Partner that provides Stablecoin Partner Services outside the United States, European Economic Area, and United Kingdom. The Bridge terms located on or accessible from the Stablecoin Partner Terms section of the Stripe Legal Page are the Stablecoin Partner Terms applicable to Users outside the United States, European Economic Area, and United Kingdom.
Qualifications & exceptions
Applies to countries outside the United States, United Kingdom and European Economic Area.
Not stated here
The Bridge terms are linked from the Stripe Legal Page and are not supplied here.
Use & Processing · Company practice
Outside the US, UK and EEA: Stripe Global Technology, LLC provides the services; the DPA treats you as in the Americas
For Users outside the United States, European Economic Area and United Kingdom, the Stablecoin Treasury Services are provided by Stripe Global Technology, LLC, and references to Stripe in these terms mean that entity for these services. For purposes of the Data Processing Agreement, the User is treated as if its Stripe Account were located in North or South America.
Supporting quotations
6.2 Modifications.
For Users outside the United States, European Economic Area, and United Kingdom, the Stripe Stablecoin Treasury Services are provided by Stripe Global Technology, LLC. References to "Stripe" in these Stripe Stablecoin Treasury Terms mean Stripe Global Technology, LLC with respect to the Stripe Stablecoin Treasury Services. However, for purposes of the Data Processing Agreement, User will be treated as if its Stripe Account were located in North or South America.
Qualifications & exceptions
Applies to Users outside the United States, European Economic Area and United Kingdom.
The Americas treatment applies for the Data Processing Agreement only.
Charges & Financial Obligations · Context
Stripe Tax Terms add to the General Terms (last modified September 28, 2026)
These Stripe Tax Terms, last modified September 28, 2026, supplement the General Terms and govern the use of the Stripe Tax Services. Capitalized terms not defined here take their General Terms meaning. The Stripe Tax Services are the Services and Partner Services on indirect taxes that Stripe makes available, including Tax Registration, Validation, Calculation and Filing Services.
Supporting quotations
Last modified: September 28, 2026
These terms (“Stripe Tax Terms”) supplement the General Terms and govern the use of the Stripe Tax Services. Capitalized terms that are not defined in these Stripe Tax Terms have the same meanings given to them in the General Terms.
“Stripe Tax Services” means the Services and Partner Services relating to indirect taxes that Stripe makes available to User, including Tax Registration Services, Tax Validation Services, Tax Calculation Services, and Tax Filing Services.
Qualifications & exceptions
The Stripe Tax Services include both Services and Partner Services.
Legal Rights & Agreement Rules · Restriction or exception
Some Tax Services are Partner Services provided at your own risk, which Stripe does not endorse and disclaims
Some of the Stripe Tax Services are provided directly by Stripe and some are Partner Services. Stripe gives access to Partner Services for the User's convenience only, does not approve or endorse them, and disclaims all responsibility and liability for the User's use of them, which is at the User's own risk. Partner Services are not Services. The User may be required to create an account with a Tax Partner, which is a third-party provider of Partner Services, and agree to its terms and privacy policy.
Supporting quotations
2. Provision of Services.
2.1 Partner Services.
Some of the Stripe Tax Services are provided directly by Stripe and some are Partner Services. Stripe provides User access to Partner Services for User’s convenience only and Stripe does not approve or endorse Partner Services. User’s access and use of Partner Services is at User’s own risk and Stripe disclaims all responsibility and liability for User’s use of Partner Services. Partner Services are not Services. User may be required to create an account with a Tax Partner and agree to its terms and privacy policy for use of the Partner Services.
“Tax Partner” means a third-party service provider of Partner Services.
Qualifications & exceptions
Use of Partner Services is at the User's own risk.
The User may have to accept the Tax Partner's own terms and privacy policy.
Not stated here
The Tax Partner terms and privacy policies are not supplied, except the two TaxJar links.
Charges & Financial Obligations · Restriction or exception
Stripe fees apply to Partner Services, and you must respond promptly to the Tax Partner's requests
Stripe fees apply to Partner Services the User accesses through the Services. The User's obligation to pay fees and Stripe's rights to collect fees under the Agreement apply to Partner Services. When using Partner Services, the User must respond in a timely manner to the Tax Partner's requests for additional information or documentation.
Supporting quotations
Stripe fees apply to Partner Services that User accesses via the Services. User’s obligation to pay fees and Stripe’s rights to collect fees under this Agreement apply to Partner Services. When using the Partner Services, User must respond in a timely manner to the Tax Partner’s requests for additional information or documentation in connection with the Partner Services.
Qualifications & exceptions
Fees are charged by Stripe even though Partner Services are not Services.
Not stated here
The terms do not state the fee amounts.
Legal Rights & Agreement Rules · Restriction or exception
TaxJar is a Tax Partner, and using its services means accepting its Terms of Service and privacy policy
For these terms, TPS Unlimited, Inc, dba TaxJar, is deemed a Tax Partner and may provide Partner Services. The User's use of TaxJar services with the Stripe Tax Services is its acceptance of the TaxJar Terms of Service and acknowledgement of the TaxJar Privacy Policy, which are at the TaxJar links in the definitions.
Supporting quotations
2.2 Use of TaxJar.
For purposes of these Stripe Tax Terms, TPS Unlimited, Inc, dba TaxJar (“TaxJar”), is deemed a Tax Partner and may provide Partner Services. User’s use of TaxJar services in connection with Stripe Tax Services constitutes User’s acceptance of the TaxJar Terms of Service and acknowledgement of the TaxJar Privacy Policy.
“TaxJar Terms of Service” means TaxJar’s terms of service located at [https://www.taxjar.com/terms-of-service](https://www.taxjar.com/terms-of-service).
“TaxJar Privacy Policy” means TaxJar’s privacy policy located at [https://www.taxjar.com/privacy](https://www.taxjar.com/privacy).
Qualifications & exceptions
Acceptance follows from use of the TaxJar services.
Not stated here
The TaxJar terms and privacy policy are linked and not supplied.
Charges & Financial Obligations · Company practice
A subcontractor may be legally required to add remittance services on its own terms; Stripe does not provide them
When a subcontractor provides the Stripe Tax Services for Stripe in certain countries, Law may require the subcontractor to provide remittance services too. For those additional services, the subcontractor's terms and fees apply, and Stripe is not providing them.
Supporting quotations
2.3 Subcontractors.
(a) Subcontractors of Stripe Tax Services. When a subcontractor is providing the Stripe Tax Services on behalf of Stripe, in certain countries, the subcontractor may be required by Law to also provide remittance services. For those additional services, the subcontractor’s terms and fees will apply, and Stripe is not provisioning any such additional services.
Qualifications & exceptions
Applies in certain countries where Law requires remittance services.
Not stated here
The countries and the subcontractor's terms and fees are not stated.
Use & Processing · Company practice
Global VAT Compliance B.V. may process Personal Data as an independent controller under its own privacy policy
When Global VAT Compliance B.V. (GVC) acts as a subcontractor of the Stripe Tax Services, it may process Personal Data as an independent Data Controller to meet its obligations under Law, in line with GVC's privacy policy.
Supporting quotations
(b) GVC. When Global VAT Compliance B.V. (“GVC”) is acting as a subcontractor of Stripe Tax Services, GVC may process Personal Data as an independent Data Controller in order to comply with GVC’s obligations under Law, in accordance with [GVC’s Privacy Policy](https://www.globalvatcompliance.com/privacy-policy/).
Qualifications & exceptions
Applies when GVC is acting as a subcontractor of Stripe Tax Services.
Processing is to comply with GVC's obligations under Law.
Not stated here
GVC's privacy policy is linked and not supplied.
Account & Service Control · Permission or license
For non-Partner services you give Stripe a limited power of attorney and let it access your government tax account
For Stripe Tax Services that are not Partner Services, the User (i) grants Stripe, and where applicable its subcontractors, a limited power of attorney and appoints them as its attorney-in-fact and agent, with full power and authority to do all required activities as the User could itself, and (ii) authorizes them to access the User's tax account with a Governmental Authority using its Tax Information and act on its behalf.
Supporting quotations
2.4 Agent; Power of Attorney.
For Stripe Tax Services that are not Partner Services, User (i) grants Stripe (and if applicable, Stripe’s subcontractors) a limited power of attorney and appoints Stripe (and if applicable, Stripe’s subcontractors) as its attorney-in-fact and agent, with the full power and authority to perform all required activities as User could otherwise do itself or in person; and (ii) authorizes Stripe (and if applicable, Stripe’s subcontractors) to access User’s tax account with a Governmental Authority using its Tax Information and act on User’s behalf.
Qualifications & exceptions
Applies to Stripe Tax Services that are not Partner Services.
The power is described as limited, but covers all required activities.
Not stated here
The terms do not define the limits of the power of attorney.
Charges & Financial Obligations · Restriction or exception
You are solely responsible for the accuracy and completeness of the tax information you give Stripe
The User acknowledges the Stripe Tax Services rely on the accuracy and completeness of the information it provides, including Tax Information, and that it is solely responsible for it. Inaccurate or incomplete information may mean Stripe cannot provide some or all of the services, cause the services to generate inaccurate Stripe Tax Data, or cause inaccurate or incomplete tax calculations, Tax Registrations or Tax Filings. Stripe Tax Data is data and reporting the User receives through the services.
Supporting quotations
3. User’s Obligations.
3.1 Information and Documentation.
(a) Accuracy of Tax Information. User acknowledges that the Stripe Tax Services rely on the accuracy and completeness of information, including Tax Information, User provides to Stripe, and User is solely responsible for the accuracy and completeness of all information. Inaccurate or incomplete information may (i) result in Stripe not being able to provide some or all of the Stripe Tax Services; (ii) cause the Stripe Tax Services to generate inaccurate Stripe Tax Data; or (iii) cause inaccurate or incomplete tax calculations, Tax Registrations, or Tax Filings.
“Stripe Tax Data” means data and reporting User receives through the Stripe Tax Services.
Account & Service Control · Restriction or exception
You must give requested information within Stripe's timeframes and sign any extra documents or powers of attorney
The User must (i) promptly give Stripe, within the timeframes Stripe specifies, all information and documentation Stripe reasonably requests in connection with the Stripe Tax Services, and (ii) sign, and legalize where required, any additional documents Stripe requires to provide the services, including additional powers of attorney or authorizations a Governmental Authority requires.
Supporting quotations
(b) Additional Information Required. User must (i) promptly provide Stripe, within the timeframes that Stripe specifies, all information and documentation that Stripe reasonably requests in connection with the Stripe Tax Services; and (ii) sign, and legalize (where required), any additional documents Stripe requires to provide the Stripe Tax Services, including any additional powers of attorney or authorizations required by a Governmental Authority for Stripe to provide the Stripe Tax Services.
Qualifications & exceptions
Requests must be reasonable.
Timeframes are those Stripe specifies.
Account & Service Control · Restriction or exception
Your Tax Representative must be authorized to act at all times, and you must prove it on request
The User must make sure its Tax Representative, an individual using the Stripe Tax Services on its behalf, is authorized at all times during the Term to provide the Tax Information, submit a Tax Registration and approve Tax Filings for it. At Stripe's request the User must give further information or documents showing the Tax Representative's authority.
Supporting quotations
3.2 Authorization.
User must ensure that User’s Tax Representative is authorized to provide the Tax Information, submit a Tax Registration, and approve Tax Filings on User’s behalf at all times during the Term. At Stripe’s request, User must provide additional information or documentation demonstrating User’s Tax Representative’s authority.
“Tax Representative” means an individual using the Stripe Tax Services on User’s behalf.
Qualifications & exceptions
Authorization is required at all times during the Term.
Charges & Financial Obligations · Restriction or exception
You must review draft Tax Filings, pay registration and filing fees and penalties, and remit the related taxes
The User must (a) review all draft Tax Filings, or information used to prepare them, for accuracy and completeness and promptly tell Stripe of corrections or additional information within Stripe's timeframe; (b) pay all fees, costs and penalties the relevant Governmental Authorities require for each Tax Registration and Tax Filing; and (c) timely remit payment of any other taxes or fees tied to each Tax Filing.
Supporting quotations
3.3 Filing and Registration.
User must:
(a) review all draft Tax Filings or information that will be used to prepare and file a Tax Filing for accuracy and completeness and promptly notify Stripe of any corrections or additional information within the timeframe Stripe specifies;
(b) pay all associated fees, costs, and penalties that the relevant Governmental Authorities require for each Tax Registration and Tax Filing; and
(c) timely remit the payment of any other taxes or fees associated with each Tax Filing.
Qualifications & exceptions
Corrections must be notified within the timeframe Stripe specifies.
Charges & Financial Obligations · Company practice
Stripe does not audit your Tax Information, and a draft Tax Filing is deemed approved at approval or the deadline
Stripe will not independently audit or verify the Tax Information or any draft Tax Filing. After the earlier of (i) the User's approval or (ii) an approval deadline passing, the draft Tax Filing is deemed approved and Stripe will submit it on the User's behalf.
Supporting quotations
Stripe will not independently audit or verify the Tax Information or any draft Tax Filing. After the earlier of (i) User’s approval; or (ii) an approval deadline being passed, the draft Tax Filing will be deemed approved and Stripe will submit the Tax Filing on User's behalf.
Qualifications & exceptions
Approval is deemed when a deadline passes without action.
Stripe does not independently verify Tax Information.
Not stated here
The approval deadline is not stated in these terms.
Charges & Financial Obligations · Restriction or exception
You alone are responsible for your own tax policies and tax reporting positions
The User is solely responsible for its own tax policies and tax reporting positions.
Supporting quotations
3.4 User’s Tax Policies.
User is solely responsible for its own tax policies and tax reporting positions.
Charges & Financial Obligations · Restriction or exception
Stripe Tax Data rests on Stripe's interpretations of Law, and you must check they suit your circumstances
The Stripe Tax Data the User receives may be based on Stripe's interpretations of Law. The User must validate that Stripe's interpretations are appropriate for its circumstances.
Supporting quotations
4. Stripe Tax Data.
4.1 Limitations on Reporting.
User may receive Stripe Tax Data through the Stripe Tax Services that is based on Stripe’s interpretations of Law. User must validate that Stripe’s interpretations are appropriate for its circumstances.
Qualifications & exceptions
The data may be based on Stripe's interpretations rather than certain legal answers.
Retention & Deletion · Restriction or exception
Stripe Tax Data is Stripe Data, and you must keep copies for the period Law requires
Stripe Tax Data is Stripe Data for the purposes of the Agreement. The User is responsible for retaining copies of Stripe Tax Data for the time period Law requires.
Supporting quotations
4.2 Stripe Tax Data.
Stripe Tax Data is Stripe Data for purposes of this Agreement. User is responsible for retaining copies of Stripe Tax Data for the time period required by Law.
Qualifications & exceptions
The retention period is whatever Law requires.
Legal Rights & Agreement Rules · Company practice
Stripe provides no fiscal representation, but a subcontractor may act as your fiscal representative where required
Stripe does not provide fiscal representation. Where Law or a Governmental Authority requires fiscal representation for the Stripe Tax Services, a subcontractor engaged by Stripe may act as fiscal representative for the User. The User may have to sign additional documents for that arrangement, including authorizations or agreements the relevant Governmental Authority requires.
Supporting quotations
5. Service Restrictions.
5.1 Fiscal Representation.
Stripe does not provide fiscal representation. Where Law or a Governmental Authority requires fiscal representation in connection with the Stripe Tax Services, a subcontractor engaged by Stripe may act as fiscal representative on User's behalf. User may be required to execute additional documents in connection with any such fiscal representation arrangement, including any authorizations or agreements required by the relevant Governmental Authority.
Qualifications & exceptions
Applies where Law or a Governmental Authority requires fiscal representation.
Not stated here
The terms do not say who pays for the representation.
Use & Processing · Restriction or exception
You and your Connected Accounts may not use Stripe Tax with Protected Health Information
The User must not, and must make sure its Connected Accounts (if applicable) do not, use the Stripe Tax Services in connection with Protected Health Information.
Supporting quotations
5.2 Protected Health Information.
User must not, and must ensure that its Connected Accounts (if applicable) do not, use the Stripe Tax Services in connection with Protected Health Information.
Qualifications & exceptions
The ban extends to the User's Connected Accounts, if applicable.
Not stated here
Protected Health Information is not defined in this document.
Legal Rights & Agreement Rules · Restriction or exception
Stripe gives no legal, tax or accounting advice or audit support, and the tools are for convenience only
The User acknowledges Stripe does not provide legal, tax or accounting advice, and the Stripe Tax Services do not include audit support. The services are automated software tools provided strictly for the User's convenience. The User is solely responsible for its own due diligence and for seeking qualified legal, tax and accounting professionals. All information, forms and materials provided with the services are for informational and educational purposes only.
Supporting quotations
6. Disclaimer.
6.1 No Tax Advice or Audit Support.
User acknowledges that Stripe does not provide legal, tax or accounting advice, and that the Stripe Tax Services do not include audit support. The Stripe Tax Services are automated software tools provided strictly for User’s convenience. User is solely responsible for conducting its own due diligence and seeking the assistance of qualified legal, tax, and accounting professionals. All information, forms, and materials provided in connection with the Stripe Tax Services are provided to User for informational and educational purposes only.
Legal Rights & Agreement Rules · Restriction or exception
Third-party data feeds may lag, go down or be inaccurate, and Stripe disclaims availability and real-time accuracy
The User acknowledges the Stripe Tax Services rely on integrations with third party data sources and governmental databases, which may be subject to latency, downtime or inaccuracies. Stripe disclaims all liability for continuous availability, latency maximums or real-time accuracy of third-party data feeds used to generate Stripe Tax Data.
Supporting quotations
6.2 Third Party Data Sources.
User acknowledges that Stripe Tax Services rely on integrations with third party data sources and governmental databases, which may be subject to latency, downtime, or inaccuracies. Stripe disclaims all liability with respect to continuous availability, latency maximums, or real-time accuracy of third-party data feeds used to generate Stripe Tax Data.
Legal Rights & Agreement Rules · Restriction or exception
You stay responsible, and Stripe disclaims liability, for your tax compliance, fines, back-taxes and added obligations
The User remains fully responsible for, and the Stripe Parties disclaim all liability for, (a) the User's fulfillment of its obligations under Law, including Taxes; (b) the accuracy of the Stripe Tax Services, and the User's obligation to pay any fine, penalty, back-taxes or other sanction a Governmental Authority imposes as a result of using them; (c) the User's action or failure to act because of directions or recommendations related to the services; and (d) additional tax or legal obligations the services may trigger, such as requirements to register for income tax, franchise tax, or other local, state, federal or international tax obligations.
Supporting quotations
6.3. Additional Disclaimers.
User remains fully responsible for, and Stripe Parties disclaim all liability with respect to:
(a) User’s fulfillment of its obligations under Law, including with respect to Taxes;
(b) the accuracy of the Stripe Tax Services, and User’s obligation to pay any fine, penalty, back-taxes, or other sanction imposed by a Governmental Authority as a result of the use of the Stripe Tax Services;
(c) User’s action, or failure to act, as a result of any directions or recommendations User receives related to the Stripe Tax Services; and
(d) additional tax or legal obligations that the Stripe Tax Services may trigger, such as requirements to register for income tax, franchise tax, or other local, state, federal, or international tax obligations.
Qualifications & exceptions
Covers fines, penalties and back-taxes imposed because of the use of the services.
Data Access & Collection · Context
Definition: Tax Information covers business, owner, login credential, banking and transaction details
Tax Information means all information a Governmental Authority requires to legally register, collect, file and remit Taxes on taxable goods and services, and that is needed to provide the Stripe Tax Services, including (a) information on the User's business, products and operations; (b) information on its company representatives, directors, officers and equity owners; (c) passwords, usernames, PINs, tax registration numbers and other log-in information; (d) banking information; and (e) transaction information. “Including” means the list is not exhaustive.
Supporting quotations
“Tax Information” means all information required by a relevant Governmental Authority to legally register, collect, file, and remit Taxes on taxable goods and services, and necessary to provide the Stripe Tax Services, including (a) information relating to User’s business, products and operations; (b) information relating to User’s company representatives, directors, officers and equity owners; (c) passwords, usernames, PINs, tax registration numbers and other log-in information; (d) banking information; and (e) transaction information.
Qualifications & exceptions
The list is not exhaustive.
The definition includes login credentials and banking information.
Charges & Financial Obligations · Context
Definitions: Tax Registration, Tax Filing, and the Registration, Filing, Calculation and Validation Services
A Tax Registration is the User's requested enrollment with the relevant Governmental Authority that enables collecting, reporting and remitting Taxes on its sales. A Tax Filing is a tax return the User asks to have prepared and submitted to the appropriate Governmental Authority. Tax Registration Services and Tax Filing Services are the Services or Partner Services that let the User complete a Registration or a Filing. Tax Calculation Services determine and calculate the Taxes due, if any, on the User's sales, and Tax Validation Services automate verification of User or Customer tax identification numbers or tax-exempt status.
Supporting quotations
“Tax Registration” means User’s requested enrollment with the relevant Governmental Authority, enabling the collection, reporting, and remittance of Taxes associated with the sale of goods or provision of services to Customers.
“Tax Filing” means a tax return that User requests to be prepared and submitted to the appropriate Governmental Authority, arising from the sale of goods or provision of services to Customers.
“Tax Registration Services” means the Services or Partner Services that enable User to complete a Tax Registration.
“Tax Filing Services” means the Services or Partner Services that enable User to complete a Tax Filing.
“Tax Calculation Services” means the Services that enable User to determine and calculate the amount, if any, of certain Taxes due in connection with User’s sale of goods or provision of services to Customers.
“Tax Validation Services” means the Services that enable automated verification of User or Customer tax identification numbers or tax-exempt status.
Charges & Financial Obligations · Context
Definitions: Partner Services, Tax Partner, Tax Data and Services, Tax Representative, TaxJar documents
Partner Services are products or services provided by a Tax Partner, which Stripe enables the User to access through the Services (excluding subcontractor services) and for which Stripe and the provider have agreed Stripe fees apply. A Tax Partner is a third-party provider of Partner Services. Stripe Tax Data is data and reporting received through the Stripe Tax Services, which are the Services and Partner Services on indirect taxes Stripe makes available. A Tax Representative is an individual using the services on the User's behalf. The TaxJar Privacy Policy and Terms of Service are TaxJar's documents at the linked addresses. A Connected Account is either a Platform User onboarded to a Stripe Connect Platform or a Payout Recipient.
Supporting quotations
“Partner Services” means a product or service provided by a Tax Partner which Stripe enables User to access via the Services (excluding any subcontractor services) and for which Stripe and the third party service provider have agreed that Stripe fees apply.
“Tax Partner” means a third-party service provider of Partner Services.
“Stripe Tax Data” means data and reporting User receives through the Stripe Tax Services.
“Stripe Tax Services” means the Services and Partner Services relating to indirect taxes that Stripe makes available to User, including Tax Registration Services, Tax Validation Services, Tax Calculation Services, and Tax Filing Services.
“Tax Representative” means an individual using the Stripe Tax Services on User’s behalf.
“TaxJar Privacy Policy” means TaxJar’s privacy policy located at [https://www.taxjar.com/privacy](https://www.taxjar.com/privacy).
“TaxJar Terms of Service” means TaxJar’s terms of service located at [https://www.taxjar.com/terms-of-service](https://www.taxjar.com/terms-of-service).
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
Not stated here
The TaxJar documents are linked and not supplied.
Charges & Financial Obligations · Context
Definitions: Tax Registration Services, Tax Validation Services and Tax Representative
Tax Registration Services are the Services or Partner Services that let the User complete a Tax Registration. Tax Validation Services are the Services that automate verification of User or Customer tax identification numbers or tax-exempt status. A Tax Representative is an individual using the Stripe Tax Services on the User's behalf.
Supporting quotations
“Tax Registration Services” means the Services or Partner Services that enable User to complete a Tax Registration.
“Tax Validation Services” means the Services that enable automated verification of User or Customer tax identification numbers or tax-exempt status.
“Tax Representative” means an individual using the Stripe Tax Services on User’s behalf.
Charges & Financial Obligations · Context
Terminal Terms add to the General and Financial Services Terms (last modified November 18, 2025)
These Stripe Terminal Terms, last modified November 18, 2025, supplement the General Terms and, together with the Stripe Financial Services Terms, which they incorporate by reference, govern the use of the Stripe Terminal Services. Capitalized terms not defined here take their meaning from those two sets of terms. The Terminal Services are the Stripe Payments Services for Transactions processed using a Stripe Terminal Product, with related services and features. A Stripe Terminal Product is a device or other hardware (such as a point-of-sale device, accessory, component or spare part) that a Stripe Entity or an authorized distributor or reseller supplies to the User, and Stripe Terminal Software is the Terminal Device Software and the Terminal SDK.
Supporting quotations
Last modified: November 18, 2025
These terms (“Stripe Terminal Terms”) supplement the General Terms and, together with the Stripe Financial Services Terms which are incorporated into these Stripe Terminal Terms by this reference, govern the use of the Stripe Terminal Services. Capitalized terms that are not defined in these Stripe Terminal Terms have the same meanings given to them in the General Terms and the Stripe Financial Services Terms.
“Stripe Terminal Services” means the Stripe Payments Services for Transactions processed using a Stripe Terminal Product, together with related services and features as described in the Stripe Terminal Documentation and on the Stripe Website.
“Stripe Terminal Product” means a device, instrument, piece of equipment, or other hardware that (a) a Stripe Entity or a third-party distributor or reseller authorized by a Stripe Entity supplies to User, which may be a physical Point of Sale (POS) device, accessory, component, or spare part, and the Terminal Device Software installed on that hardware product; or (b) Stripe approves for use to access the Stripe Terminal Services or the Stripe Technology, or to operate the Stripe Terminal Software.
“Stripe Terminal Software” means the Terminal Device Software and Terminal SDK.
Not stated here
The definition of Stripe Terminal Product continues beyond the part read in this section.
Content & IP Rights · Restriction or exception
Using Terminal Products binds you to the Terminal Device EULA, which governs the Terminal Device Software
Certain Stripe Terminal Products need the Terminal Device Software installed to work. By using them, the User agrees to be bound by the Terminal Device EULA, which governs its use of that software. The EULA is the Terminal Device Software License Agreement for end users, and its terms are incorporated into the Agreement by reference.
Certain Stripe Terminal Products require the Terminal Device Software to be installed on them to function. By using the Stripe Terminal Products, User agrees to be bound by the [Terminal Device EULA](https://stripe.com/legal/terminal-device-eula), which governs User’s use of the Terminal Device Software.
“Terminal Device EULA” means the Terminal Device Software License Agreement for end users, the terms of which are incorporated into this Agreement by this reference.
Qualifications & exceptions
Applies to Terminal Products that need the Terminal Device Software.
Not stated here
The Terminal Device EULA is a linked document and is not supplied.
Content & IP Rights · Restriction or exception
You may use the Terminal SDK only with Terminal Products and Services, and not under licenses that open Stripe's code
If the User accesses the Stripe Terminal Services using the Terminal SDK, it must not, and must not let a third party, (a) use the Terminal SDK other than with the Stripe Terminal Products and Services, or (b) use the Terminal SDK in a way that would subject it or any part of it to license terms that seek to require any Stripe Terminal Service or Product to be licensed to or shared with a third party in source code form, with rights to make derivative works, or with rights to redistribute at no charge. The Terminal SDK is Stripe Technology software code distributed under the MIT license, with a test environment and documentation.
Supporting quotations
2.2 Use of Terminal SDK.
If User accesses the Stripe Terminal Services using the Terminal SDK, then User must not, and must not enable or allow any third party to:
(a) use the Terminal SDK other than in conjunction with the Stripe Terminal Products and Stripe Terminal Services, or
(b) use the Terminal SDK in any way that would subject it, or any part of it, to license terms that seek to require any Stripe Terminal Service or Stripe Terminal Product to be licensed to (or shared with) any third party in source code form, with rights to make derivative works, or with rights to redistribute at no charge.
“Terminal SDK” means the software code that is Stripe Technology and is distributed under the MIT license, test environment, and associated documentation, as described in the Stripe Terminal Documentation and which Stripe makes available at [https://github.com/stripe](https://github.com/stripe), including iOS, Android and JavaScript versions, and including all Updates.
Qualifications & exceptions
Applies if the User accesses the services using the Terminal SDK.
Security & Safeguards · Restriction or exception
You must keep the Terminal Device Software up to date by installing Updates as the EULA requires
The User must keep the Terminal Device Software up to date by installing Updates as the Terminal Device EULA requires.
Supporting quotations
2.3 Updates to Terminal Device Software.
User must keep the Terminal Device Software up to date by installing Updates as the Terminal Device EULA requires.
Not stated here
What the EULA requires, and how fast, is in the EULA, which is not supplied.
Account & Service Control · Context
References to Documentation mean Stripe Terminal Documentation for Terminal Services, Software and Products
References to Documentation in the Agreement are read as references to Stripe Terminal Documentation for the Stripe Terminal Services, Software and Products. Stripe Terminal Documentation is the Documentation plus other documentation Stripe makes available, including by email, about those services, software or products.
Supporting quotations
2.4 Stripe Terminal Documentation.
References to Documentation in this Agreement will be read as references to Stripe Terminal Documentation, with respect to the Stripe Terminal Services, Stripe Terminal Software and Stripe Terminal Products.
“Stripe Terminal Documentation” means the Documentation, along with other documentation that Stripe makes available to User (including via email), relating to the Stripe Terminal Services, Stripe Terminal Software, or Stripe Terminal Products.
Qualifications & exceptions
Documentation can include material Stripe sends by email.
Account & Service Control · Restriction or exception
You may use the Terminal Services only in compliance with the Terminal Purchase Terms and this Agreement
The User may use the Stripe Terminal Services only in compliance with the Terminal Purchase Terms, if applicable, and the Agreement. The Terminal Purchase Terms are the agreement under which a Stripe Entity supplies the Terminal Products the User is using.
Supporting quotations
3. Use of the Stripe Terminal Services.
3.1 General.
User may only use the Stripe Terminal Services in compliance with the Terminal Purchase Terms, if applicable, and this Agreement.
“Terminal Purchase Terms” means the agreement under which a Stripe Entity supplies the Stripe Terminal Products that User is using.
Qualifications & exceptions
Terminal Purchase Terms apply if applicable.
Not stated here
The Terminal Purchase Terms are a separate agreement and are not supplied.
Charges & Financial Obligations · Restriction or exception
Stripe is not liable for losses from using a Terminal Product in offline mode, including failed or declined transactions
Stripe and its Affiliates are not liable for any losses the User incurs from using a Stripe Terminal Product in “offline mode”, including losses from being unable to complete a Transaction, whether because there is a processing error or the Transaction is declined for any reason once the product leaves offline mode.
Supporting quotations
3.2 Failed Transactions.
Stripe and its Affiliates will not be liable for any losses User incurs in connection with User's use of a Stripe Terminal Product in "offline mode", including any losses arising in connection with User's inability to successfully complete a Transaction (i.e. there is an error in processing the attempted Transaction, or the Transaction is declined for any reason once the Stripe Terminal Product is taken out of "offline mode").
Qualifications & exceptions
Covers declines that happen after the product is taken out of offline mode.
Content & IP Rights · Restriction or exception
Using Apps on Devices also binds you to the Stripe Apps Developer Agreement
Section 4 applies if the User uses Apps on Devices, the application management and distribution service and developer tools Stripe provides to deploy Stripe Apps on Stripe Terminal Products. By using Apps on Devices the User also agrees to be bound by the Stripe Apps Developer Agreement, which is accessible from the Stripe Legal Page.
Supporting quotations
4. Stripe Apps on Devices.
4.1 Apps on Devices.
This Section 4 applies if User uses Apps on Devices. By using Apps on Devices, User also agrees to be bound by the [Stripe Apps Developer Agreement](https://stripe.com/legal/app-developer-agreement).
“Apps on Devices” means the application management and distribution service and developer tools provided by Stripe that enable User to deploy Stripe Apps on Stripe Terminal Products.
“Stripe Apps Developer Agreement” means the [Stripe Apps Developer Agreement](https://stripe.com/legal/app-developer-agreement) accessible from the Stripe Legal Page.
Qualifications & exceptions
Applies only if the User uses Apps on Devices.
Not stated here
The Stripe Apps Developer Agreement is a separate linked document and is not supplied.
Content & IP Rights · Permission or license
Stripe grants a limited, revocable, non-transferable license to use Apps on Devices for point-of-sale Stripe Apps
Stripe, or its Affiliates as applicable, grants the User a limited, revocable, royalty-free, non-exclusive, non-transferable, non-sublicensable license to use Apps on Devices to develop and use Stripe Apps on Stripe Terminal Products in connection with a point-of-sale solution.
Supporting quotations
4.2 License Grant.
Stripe (or its Affiliates, as applicable) grants User a limited, revocable, royalty-free, non-exclusive, non-transferable, non-sublicensable license to use Apps on Devices to develop and use Stripe Apps on Stripe Terminal Products in connection with a point-of-sale solution.
Qualifications & exceptions
The license is revocable, non-exclusive, non-transferable and non-sublicensable.
Limited to point-of-sale use on Stripe Terminal Products.
Content & IP Rights · Restriction or exception
You must follow the Apps Developer Agreement and hold the rights for Stripe to deploy and distribute your Apps
The User must comply with the Stripe Apps Developer Agreement and must obtain and keep all consents, authorizations, licenses and other rights and permissions needed to deploy and use Stripe Apps, and to let Stripe deploy, copy, use and distribute Stripe Apps in connection with Apps on Devices.
Supporting quotations
4.3 Stripe App Developer Agreement.
User must comply with the [Stripe Apps Developer Agreement](https://stripe.com/legal/app-developer-agreement), and User must obtain and maintain all necessary consents, authorizations, licenses, and all other rights and permissions necessary to deploy and use Stripe Apps, and to allow Stripe to deploy, copy, use, and distribute Stripe Apps in connection with Apps on Devices.
Legal Rights & Agreement Rules · Restriction or exception
Stripe does not test your Stripe Apps or answer for failures from improper use; you must keep them compatible
Stripe is not responsible for (a) testing Stripe Apps for any purpose, including interoperability with the Terminal Products they run on, or testing firmware or other software on those products, or (b) any failure of the Terminal Services that results from improper use of a Stripe App. The User is responsible for implementing all updates to its Stripe Apps needed to keep them compatible with the Terminal Services.
Supporting quotations
4.4 Responsibility for Testing and Updates.
Stripe will not be responsible for (a) testing Stripe Apps for any purpose, including for interoperability with the Stripe Terminal Products on which they are deployed, or testing any firmware or other software applications or services running on the Stripe Terminal Products; or (b) any failure of the Stripe Terminal Services that results from the improper use of a Stripe App. User is responsible for implementing all updates to Stripe Apps that are needed to ensure compatibility with the Stripe Terminal Services.
Account & Service Control · Permission or license
Stripe need not monitor your Stripe App but may review or test it at any time and require accurate information about you
Stripe is not obligated to monitor the User's Stripe App or its content, but may at any time review or test it for compliance with Law, the Agreement, the Stripe Apps Developer Agreement or other terms that apply to the User's relationship with Stripe. Stripe may require the User to provide information about itself, such as identification or contact details, as part of submitting its Stripe App and its continued use of Apps on Devices. The User must make sure all information it gives Stripe is and stays accurate, complete and up to date.
Supporting quotations
4.5 Monitoring and Compliance.
Stripe is not obligated to monitor User’s Stripe App or its content, but Stripe may at any time review or test User’s Stripe App for compliance with Law, this Agreement, the Stripe Apps Developer Agreement, or any other terms that apply to User’s relationship with Stripe. Stripe may require User to provide information about itself (such as identification or contact details) as a part of User’s Stripe App’s submission to, and User’s continued use of, Apps on Devices. User must ensure that all information User provides to Stripe is and will always be accurate, complete, and up to date.
Qualifications & exceptions
Reviews and tests may happen at any time.
Account & Service Control · Permission or license
Stripe may act against your Stripe App at its sole discretion if it infringes, breaks Law, offends or risks liability
Notwithstanding anything else in the Agreement, if Stripe decides at its sole discretion that any portion of the User's Stripe App, or its use of Stripe Apps on Terminal Products, (a) violates the IP Rights or other rights of a third party; (b) violates Law or is subject to an injunction; (c) is pornographic, obscene, malicious, offensive or otherwise violates the Agreement, the Apps Developer Agreement or Stripe's Prohibited and Restricted Business List; (d) is likely to cause liability for Stripe or any third party; or (e) impairs the user experience of Stripe Apps on Devices or Stripe Apps, then the remedies follow in the next section of the document.
Supporting quotations
4.6 Services Restrictions.
Notwithstanding anything to the contrary in this Agreement, if Stripe determines at its sole discretion that any portion of User’s Stripe App, or User’s use of Stripe Apps on the Stripe Terminal Products:
(a) violates the IP Rights or any other rights of a third party;
(b) violates Law or is subject to an injunction;
(c) is pornographic, obscene, malicious, offensive or otherwise violates this Agreement, the Stripe Apps Developer Agreement, or Stripe's Prohibited and Restricted Business List;
(d) is likely to cause liability for Stripe or any third party;
(e) impair the user experience of Stripe Apps on Devices or Stripe Apps; or
Qualifications & exceptions
Each ground depends on Stripe's sole-discretion determination.
The actions Stripe may take are set out in the following block, carded with the next section.
Not stated here
The remedies for these grounds are not covered by this card.
Account & Service Control · Permission or license
Stripe may reject, disable or suspend a defective or experience-impairing Stripe App and require fixes
Stripe's sole-discretion grounds for acting on a Stripe App include (e) impairing the user experience of Stripe Apps on Devices or Stripe Apps, and (f) being defective or improperly functioning so that it is not compatible with the Terminal Services, affects end users' use of them, or affects the integrity of Stripe's servers. If any ground applies, then in addition to all its other remedies, Stripe may (a) reject, disable or suspend the App from being used, and (b) ask the User to update, modify or fix the affected component or use. Apps on Devices is the service and developer tools Stripe provides to deploy Stripe Apps on Terminal Products.
Supporting quotations
(e) impair the user experience of Stripe Apps on Devices or Stripe Apps; or
(f) is defective or improperly functioning such that it is: (i) not compatible with the Stripe Terminal Services; (ii) impacts end users’ use of the Stripe Terminal Services; or (iii) affects the integrity of Stripe’s servers,
then in addition to all other remedies available to Stripe, Stripe may take one or more of the following actions:
(a) reject, disable or suspend User’s Stripe App from being used; and
(b) request that User updates, modifies, or remediates User’s Stripe App to rectify the affected component or usage of User’s Stripe App.
“Apps on Devices” means the application management and distribution service and developer tools provided by Stripe that enable User to deploy Stripe Apps on Stripe Terminal Products.
Qualifications & exceptions
Remedies are in addition to all of Stripe's other remedies.
The actions can be taken on one or more of the listed options.
Not stated here
The terms give no notice or cure period before an App is disabled.
Data Access & Collection · Context
The On-Reader Forms section applies only if you use them; they show text and collect input on reader screens
Section 5 applies only if the User uses On-Reader Forms. On-Reader Forms are functionality that lets the User display pre-built interfaces on Terminal reader screens to show customized text to Customers, let Customers choose from buttons with customized text, or collect and store Customer input text and signature images.
Supporting quotations
5. Stripe On-Reader Forms.
5.1 On-Reader Forms.
This Section 5 applies if User uses On-Reader Forms.
“On-Reader Forms” means functionality that allows User to display pre-built user interfaces on Stripe Terminal Product reader device screens that may be used to (a) display customized text to User’s Customers, (b) solicit Customer selection from buttons displaying customized text, or (c) collect and store Customer input text information and signature images.
Qualifications & exceptions
Applies only if the User uses On-Reader Forms.
Content & IP Rights · Permission or license
You grant Stripe a worldwide, non-exclusive, royalty-free license to On-Reader Forms Content during the Term
Stripe may permit the User to upload or publish Content through the Terminal Services or the Terminal SDK in connection with On-Reader Forms. The User grants Stripe, or its Affiliates as applicable, a worldwide, limited-term, non-exclusive, royalty-free license during the Term to use that Content to facilitate Stripe's provision of On-Reader Forms.
Supporting quotations
5.2 Content License.
Stripe may permit User to upload or publish Content via the Stripe Terminal Services or Terminal SDK, in connection with User’s use of On-Reader Forms. User grants Stripe (or its Affiliates, as applicable) a worldwide, limited-term, non-exclusive, and royalty-free license during the Term to use this Content to facilitate Stripe’s provision of On-Reader Forms.
“Terminal SDK” means the software code that is Stripe Technology and is distributed under the MIT license, test environment, and associated documentation, as described in the Stripe Terminal Documentation and which Stripe makes available at [https://github.com/stripe](https://github.com/stripe), including iOS, Android and JavaScript versions, and including all Updates.
Qualifications & exceptions
The license lasts for the Term and is for providing On-Reader Forms.
Data Access & Collection · Restriction or exception
You must hold rights in your Content and must not collect health information or card account details on readers
The User must obtain and keep all rights and consents needed for its use of Content with On-Reader Forms and to grant Stripe the Section 5.2 license. During the Term the User must not use On-Reader Forms to collect or store (i) protected health information as defined under HIPAA and its implementing regulations, or (ii) Payment Method Account Details.
Supporting quotations
5.3 Consents.
User must obtain and maintain all necessary rights and consents applicable to User’s use of Content in connection with On-Reader Forms and to grant Stripe the license under Section 5.2. During the Term, User must not use On-Reader Forms to collect or store (i) protected health information (as defined under the Health Insurance Portability and Accountability Act of 1996, as amended from time to time, and its implementing regulations); or (ii) Payment Method Account Details.
Qualifications & exceptions
The collection ban applies throughout the Term.
Legal Rights & Agreement Rules · Restriction or exception
You are fully responsible for the validity of contracts and notices made through On-Reader Forms
If the User uses On-Reader Forms to enter into contracts with, or give notices to, its Customers, the User is fully responsible for the legal validity and enforceability of those contracts or notices. Stripe and its Affiliates are not liable to the User or its Customers for any losses, damages or costs arising from the User's use of On-Reader Forms.
Supporting quotations
5.4 Responsibility for Contracts and Notices.
If User uses On-Reader Forms to (a) enter into contracts with, or (b) provide notices to User’s Customers, User is fully responsible for ensuring the legal validity and enforceability of such contracts or notices. Stripe and its Affiliates are not liable to User or User’s Customers for any losses, damages, or costs arising out of or in relation to User’s use of On-Reader Forms.
Qualifications & exceptions
Applies where the User uses On-Reader Forms for contracts or notices.
Charges & Financial Obligations · Company practice
Dynamic Currency Conversion (Preview): Stripe supplies only a technical service to you and may restrict access
Section 6 applies if the User uses Dynamic Currency Conversion, which is functionality Stripe may make available through the Terminal Services so the User can offer currency conversion to Customers on certain Card Network Transactions in supported currencies on supported Terminal Products. When Stripe makes it available, Stripe provides a technical service only to the User and does not offer or provide any service to Customers. Stripe may restrict access until it is satisfied the User's use meets the requirements stated in the section.
Supporting quotations
6. Stripe Dynamic Currency Conversion (Preview).
6.1 Dynamic Currency Conversion.
This Section 6 applies if User uses Dynamic Currency Conversion. User acknowledges that when Stripe makes Dynamic Currency Conversion available to User, Stripe is providing a technical service only to User to enable User to offer Dynamic Currency Conversion to its Customers, and Stripe is not offering or providing any service to Customers. Stripe reserves the right to restrict access to Dynamic Currency Conversion until Stripe is satisfied that User’s use of Dynamic Currency Conversion meets the requirements stated below.
“Dynamic Currency Conversion” means functionality Stripe may make available via the Stripe Terminal Services that allows User to offer dynamic currency conversion to its Customers on certain Card Network Transactions in supported currencies via supported Stripe Terminal Products, as described in the Stripe Terminal Documentation.
“Stripe Terminal Services” means the Stripe Payments Services for Transactions processed using a Stripe Terminal Product, together with related services and features as described in the Stripe Terminal Documentation and on the Stripe Website.
Qualifications & exceptions
The feature is in Preview.
Applies only if the User uses Dynamic Currency Conversion.
Charges & Financial Obligations · Restriction or exception
DCC: no use outside Terminal Services, no offers outside business sales, and no claim it is a Card Network service
The User must not (a) use Dynamic Currency Conversion except with the Stripe Terminal Services; (b) offer conversion optionality to Customers except in connection with accepting payments for goods or services in its business; or (c) represent, explicitly or implicitly, at any point in the Dynamic Currency Conversion Transaction process that its use of it is a service provided by the relevant Card Network.
Supporting quotations
6.2 Services Restrictions.
User must not:
(a) use Dynamic Currency Conversion except in conjunction with the Stripe Terminal Services;
(b) offer conversion optionality to its Customers except in connection with its acceptance of payments made in exchange for goods or services in connection with its business; or
(c) represent, either explicitly or implicitly, any point during the Dynamic Currency Conversion Transaction process that their use of Dynamic Currency Conversion is a service provided by the relevant Card Network.
Charges & Financial Obligations · Company practice
DCC: exchange rates may differ from Stripe's sources, currencies can change without notice, and it is not an FX service
The exchange rates made available to the User through Dynamic Currency Conversion may differ from the rates Stripe obtains from its service providers or public sources. Stripe may add or remove supported currencies at any time without notice. For any individual Customer transaction, Stripe may apply a different exchange rate than the Currency Exchange Rate when it settles the funds to the User's Stripe Account or issues Refunds. The User acknowledges that Dynamic Currency Conversion does not provide (a) the supply of foreign currencies by Stripe or (b) a foreign currency exchange or similar service.
Supporting quotations
6.3 Currencies and Exchange Rates.
The currency exchange rates made available to User as part of Dynamic Currency Conversion may differ from the currency exchange rates Stripe obtains from its service providers or publicly available resources. Stripe reserves the right to add or remove Dynamic Currency Conversion supported currencies at any time without notice. With respect to any individual Customer transaction, Stripe may choose to apply a different exchange rate than the Currency Exchange Rate when Stripe settles the resulting funds to User’s Stripe Account, or when issuing Refunds. User acknowledges and agrees that Dynamic Currency Conversion does not provide: (a) the supply of foreign currencies by Stripe; or (b) a foreign currency exchange or similar service.
Qualifications & exceptions
Stripe may apply a different rate at settlement or on Refunds.
Currency changes need no notice.
Not stated here
The terms do not say how large a difference in rates may be.
Charges & Financial Obligations · Restriction or exception
DCC: you must give Customers the required information, including any markup, and a free choice to accept or decline
The User must (a) give Customers all necessary information about its use of Dynamic Currency Conversion as Law or Payment Method Rules require, in the form (including durable medium, as applicable) and manner required, including that the service may include a User-imposed markup on the prevailing exchange rate; and (b) make sure Customers are offered a free choice to accept or decline the conversion and that it is not used to convert a Transaction to a Customer's card currency without first getting the Customer's agreement on the information properly given.
Supporting quotations
6.4 User Obligations.
User must:
(a) provide Customers with all necessary information relating to its use of Dynamic Currency Conversion as required by Law or Payment Method Rules, in the form (including durable medium, as applicable) and manner required, including that this service may include a User-imposed markup on the prevailing currency exchange rate; and
(b) ensure Customers are offered a free choice to accept or decline the conversion option and that Dynamic Currency Conversion is not used to convert a Transaction to a Customer’s card currency without first obtaining the Customer’s agreement on the basis of the information duly provided;
Qualifications & exceptions
Information must be given in the form and manner Law or Payment Method Rules require.
Legal Rights & Agreement Rules · Restriction or exception
DCC: you stay responsible; Stripe disclaims liability for compliance, rate accuracy, bank fees and your actions
The User remains fully responsible for, and Stripe disclaims all liability for, (a) the User's fulfilment of its obligations under Law and Payment Method Rules, including its use of Dynamic Currency Conversion; (b) the accuracy of the prices Dynamic Currency Conversion shows to the User and its Customers and of the exchange rates it uses; (c) any fees charged to the User or its Customers by the User's bank or another financial institution; and (d) the User's action or failure to act because of directions or recommendations related to it.
Supporting quotations
6.5 Disclaimer.
User remains fully responsible for, and Stripe disclaims all liability with respect to:
(a) User’s fulfilment of its obligations under Law and Payment Method Rules, including with respect to its use of Dynamic Currency Conversion;
(b) the accuracy of the prices Dynamic Currency Conversion presents to User and its Customers, and the currency exchange rates Dynamic Currency Conversion uses and applies;
(c) any fees charged to User or its Customers by User’s bank or any other applicable financial institution; and
(d) User’s action, or failure to act, as a result of any directions or recommendations User receives related to Dynamic Currency Conversion.
Charges & Financial Obligations · Context
Definitions: Card Network, Currency Exchange Rate and Refund
A Card Network is a payment card network, including those run by Visa, Mastercard, American Express and Discover; the named networks are examples. The Currency Exchange Rate is the Stripe-determined rate applied during a Customer transaction to convert prices of goods and services into the Customer's local currency. A Refund is an instruction the User starts to return funds, in full or in part, to a Customer for a processed Transaction.
Supporting quotations
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
“Currency Exchange Rate” means the Stripe-determined currency exchange rate applied during a Customer transaction to convert the prices of goods and services into Customer’s local currency.
“Refund” means an instruction User initiates to provide a full or partial return of funds to a Customer for a processed Transaction.
Qualifications & exceptions
The named Card Networks are examples, not a complete list.
The Currency Exchange Rate is determined by Stripe.
A Stripe Terminal Product is a device or other hardware that a Stripe Entity or an authorized distributor or reseller supplies to the User (such as a POS device, accessory, component or spare part) together with its installed Terminal Device Software, or that Stripe approves for use to access the Terminal Services or Stripe Technology or to run the Terminal Software. Stripe Terminal Services are the Stripe Payments Services for Transactions processed using a Terminal Product, with related services and features described in the Terminal Documentation and on the Stripe Website. Stripe Terminal Software is the Terminal Device Software and the Terminal SDK, and Terminal Device Software takes its meaning from the Terminal Device EULA. Stripe Terminal Documentation is the Documentation plus other documentation Stripe makes available, including by email.
Supporting quotations
“Stripe Terminal Product” means a device, instrument, piece of equipment, or other hardware that (a) a Stripe Entity or a third-party distributor or reseller authorized by a Stripe Entity supplies to User, which may be a physical Point of Sale (POS) device, accessory, component, or spare part, and the Terminal Device Software installed on that hardware product; or (b) Stripe approves for use to access the Stripe Terminal Services or the Stripe Technology, or to operate the Stripe Terminal Software.
“Stripe Terminal Services” means the Stripe Payments Services for Transactions processed using a Stripe Terminal Product, together with related services and features as described in the Stripe Terminal Documentation and on the Stripe Website.
“Stripe Terminal Software” means the Terminal Device Software and Terminal SDK.
“Stripe Terminal Documentation” means the Documentation, along with other documentation that Stripe makes available to User (including via email), relating to the Stripe Terminal Services, Stripe Terminal Software, or Stripe Terminal Products.
“Terminal Device Software” has the meaning given to it in the Terminal Device EULA.
Qualifications & exceptions
A Terminal Product can also be hardware Stripe approves for use, not only hardware supplied to the User.
Not stated here
The meaning of Terminal Device Software is in the Terminal Device EULA, which is not supplied.
The Terminal Device EULA is the Terminal Device Software License Agreement for end users, with terms incorporated into the Agreement by reference. The Terminal Purchase Terms are the agreement under which a Stripe Entity supplies the Terminal Products the User is using. The Terminal SDK is software code that is Stripe Technology, distributed under the MIT license with a test environment and associated documentation as the Terminal Documentation describes, available from Stripe's GitHub, including iOS, Android and JavaScript versions and all Updates.
Supporting quotations
“Terminal Device EULA” means the Terminal Device Software License Agreement for end users, the terms of which are incorporated into this Agreement by this reference.
“Terminal Purchase Terms” means the agreement under which a Stripe Entity supplies the Stripe Terminal Products that User is using.
“Terminal SDK” means the software code that is Stripe Technology and is distributed under the MIT license, test environment, and associated documentation, as described in the Stripe Terminal Documentation and which Stripe makes available at [https://github.com/stripe](https://github.com/stripe), including iOS, Android and JavaScript versions, and including all Updates.
Qualifications & exceptions
The Terminal SDK is described as distributed under the MIT license.
Not stated here
The EULA and Purchase Terms are separate documents and are not supplied.
Content & IP Rights · Context
Definitions: Apps on Devices, Stripe App, Stripe Apps Developer Agreement and Platform Services
Apps on Devices is the application management and distribution service and developer tools Stripe provides to let the User deploy Stripe Apps on Terminal Products. A Stripe App takes its meaning from the Stripe Apps Developer Agreement, which is accessible from the Stripe Legal Page. Platform Services are the products and services Platform Users receive from a Stripe Connect Platform, whether or not fees are charged, such as web development, customer support or hosting.
Supporting quotations
“Apps on Devices” means the application management and distribution service and developer tools provided by Stripe that enable User to deploy Stripe Apps on Stripe Terminal Products.
“Stripe App” has the meaning given to that term in the [Stripe Apps Developer Agreement](https://stripe.com/legal/app-developer-agreement).
“Stripe Apps Developer Agreement” means the [Stripe Apps Developer Agreement](https://stripe.com/legal/app-developer-agreement) accessible from the Stripe Legal Page.
“Platform Services” means the products and services that Platform Users receive from a Stripe Connect Platform, regardless of whether fees are charged (e.g., web development, customer support or hosting services).
Not stated here
The meaning of Stripe App is in the Developer Agreement, which is not supplied.
Charges & Financial Obligations · Context
Definitions: Dynamic Currency Conversion, On-Reader Forms and Payment Method Account Details
Dynamic Currency Conversion is functionality Stripe may make available through the Terminal Services that lets the User offer currency conversion to Customers on certain Card Network Transactions in supported currencies on supported Terminal Products. On-Reader Forms let the User show pre-built interfaces on reader screens to display customized text, let Customers pick from buttons, or collect and store Customer input text and signature images. Payment Method Account Details are the Customer's payment method account details that the PCI Standards require to be protected, which may include the name and, for cards, the account number, expiration date and card verification value or similar security code.
Supporting quotations
“Dynamic Currency Conversion” means functionality Stripe may make available via the Stripe Terminal Services that allows User to offer dynamic currency conversion to its Customers on certain Card Network Transactions in supported currencies via supported Stripe Terminal Products, as described in the Stripe Terminal Documentation.
“On-Reader Forms” means functionality that allows User to display pre-built user interfaces on Stripe Terminal Product reader device screens that may be used to (a) display customized text to User’s Customers, (b) solicit Customer selection from buttons displaying customized text, or (c) collect and store Customer input text information and signature images.
“Payment Method Account Details” means the Payment Method account details for a Customer that the PCI Standards require to be protected, which may include the Customer’s name, and with respect to credit and debit cards, the Customer’s account number, card expiration date, and card verification value or similar security code.
Charges & Financial Obligations · Context
Terminal-Platform Terms apply to Stripe Connect Platforms, adding to three other term sets (modified Nov. 18, 2025)
These Stripe Terminal Terms for platforms, last modified November 18, 2025, supplement the General Terms and, together with the Stripe Financial Services Terms and the Stripe Connect Infrastructure Terms, which they incorporate by reference, govern use of the Stripe Terminal Services if the User is a Stripe Connect Platform. Capitalized terms not defined here take their meaning from those three sets of terms. The Terminal Services, Products and Software have the same meanings as in the version for non-platform Users: the Stripe Payments Services for Transactions processed using a Terminal Product, hardware supplied or approved by Stripe, and the Terminal Device Software and Terminal SDK.
Supporting quotations
Last modified: November 18, 2025
These terms (“Stripe Terminal Terms”) supplement the General Terms and, together with the Stripe Financial Services Terms and the Stripe Connect Infrastructure Terms each of which are incorporated into these Stripe Terminal Terms by this reference, govern the use of the Stripe Terminal Services if User is a Stripe Connect Platform. Capitalized terms that are not defined in these Stripe Terminal Terms have the same meanings given to them in the General Terms, the Stripe Financial Services Terms, and the Stripe Connect Infrastructure Terms.
“Stripe Terminal Services” means the Stripe Payments Services for Transactions processed using a Stripe Terminal Product, together with related services and features as described in the Stripe Terminal Documentation and on the Stripe Website.
“Stripe Terminal Product” means a device, instrument, piece of equipment, or other hardware that (a) a Stripe Entity or a third-party distributor or reseller authorized by a Stripe Entity supplies to User, which may be a physical Point of Sale (POS) device, accessory, component, or spare part, and the Terminal Device Software installed on that hardware product; or (b) Stripe approves for use to access the Stripe Terminal Services or the Stripe Technology, or to operate the Stripe Terminal Software.
“Stripe Terminal Software” means the Terminal Device Software and Terminal SDK.
Qualifications & exceptions
Applies if the User is a Stripe Connect Platform.
Content & IP Rights · Restriction or exception
Using Terminal Products binds you to the Terminal Device EULA, which governs the Terminal Device Software
Certain Stripe Terminal Products need the Terminal Device Software installed to work. By using them, the User agrees to be bound by the Terminal Device EULA, which governs its use of that software. The EULA is the Terminal Device Software License Agreement for end users, incorporated into the Agreement by reference.
Certain Stripe Terminal Products require the Terminal Device Software to be installed on them to function. By using the Stripe Terminal Products, User agrees to be bound by the [Terminal Device EULA](https://stripe.com/legal/terminal-device-eula), which governs User’s use of the Terminal Device Software.
“Terminal Device EULA” means the Terminal Device Software License Agreement for end users, the terms of which are incorporated into this Agreement by this reference.
Qualifications & exceptions
Applies to Terminal Products that need the Terminal Device Software.
Not stated here
The Terminal Device EULA is a linked document and is not supplied.
Content & IP Rights · Restriction or exception
You may use the Terminal SDK only with Terminal Products and Services, and not under licenses that open Stripe's code
If the User accesses the Terminal Services using the Terminal SDK, it must not, and must not let a third party, (a) use the SDK other than with the Stripe Terminal Products and Services, or (b) use it in a way that would subject it or any part of it to license terms that seek to require any Terminal Service or Product to be licensed to or shared with a third party in source code form, with rights to make derivative works, or with rights to redistribute at no charge.
Supporting quotations
2.2 Use of Terminal SDK.
If User accesses the Stripe Terminal Services using the Terminal SDK, then User must not, and must not enable or allow any third party to:
(a) use the Terminal SDK other than in conjunction with the Stripe Terminal Products and Stripe Terminal Services, or
(b) use the Terminal SDK in any way that would subject it, or any part of it, to license terms that seek to require any Stripe Terminal Service or Stripe Terminal Product to be licensed to (or shared with) any third party in source code form, with rights to make derivative works, or with rights to redistribute at no charge.
“Terminal SDK” means the software code that is Stripe Technology and is distributed under the MIT license, test environment, and associated documentation, as described in the Stripe Terminal Documentation and which Stripe makes available at [https://github.com/stripe](https://github.com/stripe), including iOS, Android and JavaScript versions, and including all Updates.
Qualifications & exceptions
Applies if the User accesses the services using the Terminal SDK.
Security & Safeguards · Restriction or exception
You must keep the Terminal Device Software up to date by installing Updates as the EULA requires
The User must keep the Terminal Device Software up to date by installing Updates as the Terminal Device EULA requires.
Supporting quotations
2.3 Updates to Terminal Device Software.
User must keep the Terminal Device Software up to date by installing Updates as the Terminal Device EULA requires.
Not stated here
What the EULA requires, and how fast, is in the EULA, which is not supplied.
Security & Safeguards · Company practice
Terminal Software Updates are mandatory unless Stripe says optional, and Stripe notifies you of those it does not push
Section 2.4 applies if the User manages or controls its Connected Accounts' access to or use of the Stripe Terminal Software in connection with the Platform Services. Stripe, or the software's licensor, may from time to time make Updates available. An Update is mandatory unless Stripe designates it as optional or discretionary. Stripe will notify the User of each mandatory Update it does not push directly to the User's Connected Accounts.
Supporting quotations
2.4 Updates to Stripe Terminal Software for Connected Accounts.
This Section 2.4 applies if User manages or controls its Connected Accounts’ access to or use of the Stripe Terminal Software in connection with the Platform Services. Stripe, or the licensor of the Stripe Terminal Software, may from time to time make available Updates to the Stripe Terminal Software. An Update is mandatory unless Stripe designates it as optional or discretionary. Stripe will notify User of each mandatory Update that it does not push directly to User’s Connected Accounts.
Qualifications & exceptions
Applies if the User manages or controls its Connected Accounts' access to the Terminal Software.
Mandatory is the default for an Update.
Security & Safeguards · Restriction or exception
You must pass update notices to Connected Accounts at once and ensure mandatory Updates are installed in time
On receiving an Update notice from Stripe, the User must immediately tell its Connected Accounts that use the Terminal Services (a) about the Update; (b) whether it is mandatory, optional or discretionary; (c) for a mandatory Update, the installation deadline; and (d) that they may not be able to keep using the Terminal Services if they do not install the mandatory Update by the deadline. The User must make sure its Connected Accounts install each mandatory Update by the date or within the period stated in the notice or, if none is stated, no later than 30 days after Stripe's notice.
Supporting quotations
Upon receipt of an Update notice from Stripe, User must immediately notify User’s Connected Accounts that use the Stripe Terminal Services (a) of the Update; (b) whether the Update is mandatory, optional or discretionary; (c) if the Update is mandatory, the deadline for installing the Update; and (d) that they may not be able to continue using the Stripe Terminal Services if they do not install the mandatory Update by the deadline. User must ensure that User’s Connected Accounts install each mandatory Update by the date or within the time period stated in the notice; or, if there is no date or period stated in the notice, then no later than 30 days after the date of Stripe’s notice.
Qualifications & exceptions
Notice to Connected Accounts must be immediate.
The default installation window is 30 days from Stripe's notice.
Account & Service Control · Context
References to Documentation mean Stripe Terminal Documentation for Terminal Services, Software and Products
References to Documentation in the Agreement are read as references to Stripe Terminal Documentation for the Terminal Services, Software and Products. Stripe Terminal Documentation includes other documentation Stripe makes available, including by email.
Supporting quotations
2.5 Stripe Terminal Documentation.
References to Documentation in this Agreement will be read as references to Stripe Terminal Documentation, with respect to the Stripe Terminal Services, Stripe Terminal Software and Stripe Terminal Products.
“Stripe Terminal Documentation” means the Documentation, along with other documentation that Stripe makes available to User (including via email), relating to the Stripe Terminal Services, Stripe Terminal Software, or Stripe Terminal Products.
Qualifications & exceptions
Documentation can include material Stripe sends by email.
Account & Service Control · Restriction or exception
You may use the Terminal Services only in compliance with the Terminal Purchase Terms and this Agreement
The User may use the Stripe Terminal Services only in compliance with the Terminal Purchase Terms, if applicable, and the Agreement. The Terminal Purchase Terms are the agreement under which a Stripe Entity supplies the Terminal Products the User is using.
Supporting quotations
3. Use of the Stripe Terminal Services.
3.1 General.
User may only use the Stripe Terminal Services in compliance with the Terminal Purchase Terms, if applicable, and this Agreement.
“Terminal Purchase Terms” means the agreement under which a Stripe Entity supplies the Stripe Terminal Products that User is using.
Qualifications & exceptions
Terminal Purchase Terms apply if applicable.
Not stated here
The Terminal Purchase Terms are a separate agreement and are not supplied.
Charges & Financial Obligations · Restriction or exception
Stripe is not liable for losses from using a Terminal Product in offline mode, including failed or declined transactions
Stripe and its Affiliates are not liable for any losses the User incurs from using a Stripe Terminal Product in “offline mode”, including losses from being unable to complete a Transaction, whether because there is a processing error or the Transaction is declined for any reason once the product leaves offline mode.
Supporting quotations
3.2 Failed Transactions.
Stripe and its Affiliates will not be liable for any losses User incurs in connection with User's use of a Stripe Terminal Product in "offline mode", including any losses arising in connection with User's inability to successfully complete a Transaction (i.e. there is an error in processing the attempted Transaction, or the Transaction is declined for any reason once the Stripe Terminal Product is taken out of "offline mode")
Qualifications & exceptions
Covers declines that happen after the product is taken out of offline mode.
Charges & Financial Obligations · Restriction or exception
Tap to Pay on iPhone for your Connected Accounts is subject to Apple's platform terms, which you must keep confidential
As part of the Terminal Services, Stripe may enable the User to use Tap to Pay on iPhone, as the Documentation describes, so its Connected Accounts can accept Transactions on a compatible Apple product. The User's use is subject to, and the User agrees to comply with and treat as confidential, the Apple Acceptance Platform User Terms and Conditions.
Supporting quotations
3.3 Tap to Pay on iPhone.
As part of the Stripe Terminal Services, Stripe may enable User to use Tap to Pay on iPhone (as described in the Documentation) to allow User’s Connected Accounts to accept Transactions on a compatible Apple product. User’s use of Tap to Pay on iPhone is subject to, and User agrees to comply with, and treat as confidential, these [Apple Acceptance Platform User Terms and Conditions](https://stripe.com/legal/apple-acceptance-platform).
Qualifications & exceptions
Stripe may enable the feature; it is not promised.
Not stated here
The Apple terms are a linked document and are not supplied.
Account & Service Control · Company practice
These Terminal Terms end automatically if the Stripe Connect Terms end for any reason
These Stripe Terminal Terms automatically terminate if the Stripe Connect Terms terminate for any reason.
Supporting quotations
4. Termination.
These Stripe Terminal Terms automatically terminate if the Stripe Connect Terms terminate for any reason.
Qualifications & exceptions
Termination follows the Connect Terms for any reason.
Content & IP Rights · Permission or license
Using Apps on Devices binds you to the Apps Developer Agreement, with a limited, revocable, non-transferable license
Section 5 applies if the User uses Apps on Devices, the service and developer tools for deploying Stripe Apps on Terminal Products. By using it, the User also agrees to be bound by the Stripe Apps Developer Agreement. Stripe, or its Affiliates as applicable, grants the User a limited, revocable, royalty-free, non-exclusive, non-transferable, non-sublicensable license to use Apps on Devices to develop and use Stripe Apps on Terminal Products in connection with a point-of-sale solution.
Supporting quotations
5. Stripe Apps on Devices.
5.1 Apps on Devices.
This Section 5 applies if User uses Apps on Devices. By using Apps on Devices, User also agrees to be bound by the [Stripe Apps Developer Agreement](https://stripe.com/legal/app-developer-agreement).
5.2 License Grant.
Stripe (or its Affiliates, as applicable) grants User a limited, revocable, royalty-free, non-exclusive, non-transferable, non-sublicensable license to use Apps on Devices to develop and use Stripe Apps on Stripe Terminal Products in connection with a point-of-sale solution.
“Apps on Devices” means the application management and distribution service and developer tools provided by Stripe that enable User to deploy Stripe Apps on Stripe Terminal Products.
“Stripe Apps Developer Agreement” means the [Stripe Apps Developer Agreement](https://stripe.com/legal/app-developer-agreement) accessible from the Stripe Legal Page.
Qualifications & exceptions
Applies only if the User uses Apps on Devices.
The license is revocable and limited to point-of-sale use.
Not stated here
The Stripe Apps Developer Agreement is a linked document and is not supplied.
Content & IP Rights · Restriction or exception
You must follow the Apps Developer Agreement and hold the rights for Stripe to deploy and distribute your Apps
The User must comply with the Stripe Apps Developer Agreement and must obtain and keep all consents, authorizations, licenses and other rights and permissions needed to deploy and use Stripe Apps, and to let Stripe deploy, copy, use and distribute Stripe Apps in connection with Apps on Devices.
Supporting quotations
5.3 Stripe App Developer Agreement.
User must comply with the [Stripe Apps Developer Agreement](https://stripe.com/legal/app-developer-agreement), and User must obtain and maintain all necessary consents, authorizations, licenses, and all other rights and permissions necessary to deploy and use Stripe Apps, and to allow Stripe to deploy, copy, use, and distribute Stripe Apps in connection with Apps on Devices.
“Stripe Apps Developer Agreement” means the [Stripe Apps Developer Agreement](https://stripe.com/legal/app-developer-agreement) accessible from the Stripe Legal Page.
Not stated here
The Stripe Apps Developer Agreement is a linked document and is not supplied.
Legal Rights & Agreement Rules · Restriction or exception
Stripe does not test your Stripe Apps or answer for failures from improper use; you must keep them compatible
Stripe is not responsible for (a) testing Stripe Apps for any purpose, including interoperability with the Terminal Products they run on, or testing firmware or other software on those products, or (b) any failure of the Terminal Services that results from improper use of a Stripe App. The User is responsible for implementing all updates to its Stripe Apps needed to keep them compatible with the Terminal Services.
Supporting quotations
5.4 Responsibility for Testing and Updates.
Stripe will not be responsible for (a) testing Stripe Apps for any purpose, including for interoperability with the Stripe Terminal Products on which they are deployed, or testing any firmware or other software applications or services running on the Stripe Terminal Products; or (b) any failure of the Stripe Terminal Services that results from the improper use of a Stripe App. User is responsible for implementing all updates to Stripe Apps that are needed to ensure compatibility with the Stripe Terminal Services.
Account & Service Control · Permission or license
Stripe need not monitor your Stripe App but may review or test it at any time and require accurate information
Stripe is not obligated to monitor the User's Stripe App or its content, but may at any time review or test it for compliance with Law, the Agreement, the Stripe Apps Developer Agreement or other terms that apply to the User's relationship with Stripe. Stripe may require the User to give information about itself, such as identification or contact details, as part of submitting its Stripe App and its continued use of Apps on Devices. The User must make sure all information it gives Stripe is and stays accurate, complete and up to date.
Supporting quotations
5.5 Monitoring and Compliance.
Stripe is not obligated to monitor User’s Stripe App or its content, but Stripe may at any time review or test User’s Stripe App for compliance with Law, this Agreement, the Stripe Apps Developer Agreement, or any other terms that apply to User’s relationship with Stripe. Stripe may require User to provide information about itself (such as identification or contact details) as a part of User’s Stripe App’s submission to, and User’s continued use of, Apps on Devices. User must ensure that all information User provides to Stripe is and will always be accurate, complete and up to date.
Qualifications & exceptions
Reviews and tests may happen at any time.
Account & Service Control · Permission or license
Stripe may reject, disable or suspend your Stripe App at its sole discretion on listed grounds and require fixes
Notwithstanding anything else in the Agreement, if Stripe decides at its sole discretion that any portion of the User's Stripe App, or its use of Stripe Apps on Terminal Products, (a) violates the IP Rights or other rights of a third party; (b) violates Law or is subject to an injunction; (c) is pornographic, obscene, malicious, offensive or otherwise violates the Agreement, the Apps Developer Agreement or Stripe's Prohibited and Restricted Business List; (d) is likely to cause liability for Stripe or any third party; (e) impairs the user experience of Stripe Apps on Devices or Stripe Apps; or (f) is defective or improperly functioning so that it is not compatible with the Terminal Services, affects end users' use of them, or affects the integrity of Stripe's servers, then in addition to all its other remedies Stripe may (a) reject, disable or suspend the App from being used and (b) ask the User to update, modify or fix the affected component or use.
Supporting quotations
5.6 Services Restrictions.
Notwithstanding anything to the contrary in this Agreement, if Stripe determines at its sole discretion that any portion of User’s Stripe App, or User’s use of Stripe Apps on the Stripe Terminal Products:
(a) violates the IP Rights or any other rights of a third party;
(b) violates Law or is subject to an injunction;
(c) is pornographic, obscene, malicious, offensive or otherwise violates this Agreement, the Stripe Apps Developer Agreement, or Stripe's Prohibited and Restricted Business List;
(d) is likely to cause liability for Stripe or any third party;
(e) impair the user experience of Stripe Apps on Devices or Stripe Apps; or
(f) is defective or improperly functioning such that it is: (i) not compatible with the Stripe Terminal Services; (ii) impacts end users’ use of the Stripe Terminal Services; or (iii) affects the integrity of Stripe’s servers,
then in addition to all other remedies available to Stripe, Stripe may take one or more of the following actions:
(a) reject, disable or suspend User’s Stripe App from being used; and
(b) request that User updates, modifies or remediates User’s Stripe App to rectify the affected component or usage of User’s Stripe App.
Qualifications & exceptions
Each ground depends on Stripe's sole-discretion determination.
Remedies are in addition to all of Stripe's other remedies.
Not stated here
The terms give no notice or cure period before an App is disabled.
Content & IP Rights · Permission or license
The On-Reader Forms section applies only if you use them, and you license Stripe your Content for the Term
Section 6 applies only if the User uses On-Reader Forms, which let it show pre-built interfaces on Terminal reader screens to display customized text, let Customers pick from buttons, or collect and store Customer input text and signature images. Stripe may permit the User to upload or publish Content through the Terminal Services or the Terminal SDK for On-Reader Forms, and the User grants Stripe, or its Affiliates as applicable, a worldwide, limited-term, non-exclusive, royalty-free license during the Term to use that Content to facilitate On-Reader Forms.
Supporting quotations
6. Stripe On-Reader Forms.
6.1 On-Reader Forms.
This Section 6 applies if User uses On-Reader Forms.
6.2 Content License.
Stripe may permit User to upload or publish Content via the Stripe Terminal Services or Terminal SDK, in connection with User’s use of On-Reader Forms. User grants Stripe (or its Affiliates, as applicable) a worldwide, limited-term, non-exclusive, and royalty-free license during the Term to use this Content to facilitate Stripe’s provision of On-Reader Forms.
“On-Reader Forms” means functionality that allows User to display pre-built user interfaces on Stripe Terminal Product reader device screens that may be used to (a) display customized text to User’s Customers, (b) solicit Customer selection from buttons displaying customized text, or (c) collect and store Customer input text information and signature images.
“Terminal SDK” means the software code that is Stripe Technology and is distributed under the MIT license, test environment, and associated documentation, as described in the Stripe Terminal Documentation and which Stripe makes available at [https://github.com/stripe](https://github.com/stripe), including iOS, Android and JavaScript versions, and including all Updates.
Qualifications & exceptions
Applies only if the User uses On-Reader Forms.
The license lasts for the Term and is for providing On-Reader Forms.
Data Access & Collection · Restriction or exception
You must hold rights in your Content and must not collect health information or card account details on readers
The User must obtain and keep all rights and consents needed for its use of Content with On-Reader Forms and to grant Stripe the Section 6.2 license. During the Term the User must not use On-Reader Forms to collect or store (i) protected health information as defined under HIPAA and its implementing regulations, or (ii) Payment Method Account Details.
Supporting quotations
6.3 Consents.
User must obtain and maintain all necessary rights and consents applicable to User’s use of Content in connection with On-Reader Forms and to grant Stripe the license under Section 6.2. During the Term, User must not use On-Reader Forms to collect or store (i) protected health information (as defined under the Health Insurance Portability and Accountability Act of 1996, as amended from time to time, and its implementing regulations); or (ii) Payment Method Account Details.
Qualifications & exceptions
The collection ban applies throughout the Term.
Legal Rights & Agreement Rules · Restriction or exception
You are fully responsible for the validity of contracts and notices made through On-Reader Forms
If the User uses On-Reader Forms to enter into contracts with, or give notices to, its Customers, the User is fully responsible for the legal validity and enforceability of those contracts or notices. Stripe and its Affiliates are not liable to the User or its Customers for any losses, damages or costs arising from the User's use of On-Reader Forms.
Supporting quotations
6.4 Responsibility for Contracts and Notices.
If User uses On-Reader Forms to (a) enter into contracts with, or (b) provide notices to User’s Customers, User is fully responsible for ensuring the legal validity and enforceability of such contracts or notices. Stripe and its Affiliates are not liable to User or User’s Customers for any losses, damages, or costs arising out of or in relation to User’s use of On-Reader Forms.
Qualifications & exceptions
Applies where the User uses On-Reader Forms for contracts or notices.
Charges & Financial Obligations · Company practice
Dynamic Currency Conversion (Preview): Stripe supplies only a technical service to you and your Connected Accounts
Section 7 applies if the User uses Dynamic Currency Conversion. When Stripe makes it available to the User and its Connected Accounts, Stripe provides a technical service only to them, so they can offer it to their Customers, and Stripe does not offer or provide any service to Customers. Stripe may restrict access until it is satisfied the User's use meets the requirements stated in the section. Dynamic Currency Conversion is functionality available through the Terminal Services for certain Card Network Transactions in supported currencies on supported Terminal Products.
Supporting quotations
7. Stripe Dynamic Currency Conversion (Preview).
7.1 Dynamic Currency Conversion.
This Section 7 applies if User uses Dynamic Currency Conversion. User acknowledges that when Stripe makes Dynamic Currency Conversion available to User and its Connected Accounts, Stripe is providing a technical service only to User and its Connected Accounts to enable User and its Connected Accounts to offer Dynamic Currency Conversion to their Customers, and Stripe is not offering or providing any service to Customers. Stripe reserves the right to restrict access to Dynamic Currency Conversion until Stripe is satisfied that User’s use of Dynamic Currency Conversion meets the requirements stated below.
“Dynamic Currency Conversion” means functionality Stripe may make available via the Stripe Terminal Services that allows User to offer dynamic currency conversion to its Customers on certain Card Network Transactions in supported currencies via supported Stripe Terminal Products, as described in the Stripe Terminal Documentation.
“Stripe Terminal Services” means the Stripe Payments Services for Transactions processed using a Stripe Terminal Product, together with related services and features as described in the Stripe Terminal Documentation and on the Stripe Website.
Qualifications & exceptions
The feature is in Preview.
Applies only if the User uses Dynamic Currency Conversion.
Charges & Financial Obligations · Restriction or exception
DCC: you and your Connected Accounts may not use it outside Terminal Services or claim it is a Card Network service
The User and its Connected Accounts must not (a) use Dynamic Currency Conversion except with the Stripe Terminal Services; (b) offer conversion optionality to Customers except in connection with accepting payments for goods or services in their business; or (c) represent, explicitly or implicitly, at any point in the Dynamic Currency Conversion Transaction process that their use of it is a service provided by the relevant Card Network.
Supporting quotations
7.2 Services Restrictions.
User and its Connected Accounts must not:
(a) use Dynamic Currency Conversion except in conjunction with the Stripe Terminal Services;
(b) offer conversion optionality to its Customers except in connection with its acceptance of payments made in exchange for goods or services in connection with its business; or
(c) represent, either explicitly or implicitly, at any point during the Dynamic Currency Conversion Transaction process that their use of Dynamic Currency Conversion is a service provided by the relevant Card Network.
Qualifications & exceptions
The restrictions bind the User's Connected Accounts as well as the User.
Charges & Financial Obligations · Restriction or exception
DCC: no conversion offers outside your business sales, and no claim that it is a Card Network service
The User and its Connected Accounts must not offer conversion optionality to Customers except in connection with accepting payments for goods or services in their business, and must not represent, explicitly or implicitly, at any point in the Dynamic Currency Conversion Transaction process that their use of it is a service provided by the relevant Card Network.
Supporting quotations
(b) offer conversion optionality to its Customers except in connection with its acceptance of payments made in exchange for goods or services in connection with its business; or
(c) represent, either explicitly or implicitly, at any point during the Dynamic Currency Conversion Transaction process that their use of Dynamic Currency Conversion is a service provided by the relevant Card Network.
Qualifications & exceptions
The restrictions bind the User's Connected Accounts as well as the User.
Charges & Financial Obligations · Company practice
DCC: exchange rates may differ from Stripe's sources, currencies can change without notice, and it is not an FX service
The exchange rates made available to the User and its Connected Accounts through Dynamic Currency Conversion may differ from the rates Stripe obtains from its service providers or public sources. Stripe may add or remove supported currencies at any time without notice. For any individual Customer transaction, Stripe may apply a different exchange rate than the Currency Exchange Rate when it settles the funds to the User's Stripe Account or issues Refunds. The User acknowledges that it does not provide (a) the supply of foreign currencies by Stripe or (b) a foreign currency exchange or similar service.
Supporting quotations
7.3 Currencies and Exchange Rates.
The currency exchange rates made available to User and its Connected Accounts as part of Dynamic Currency Conversion may differ from the currency exchange rates Stripe obtains from its service providers or publicly available resources. Stripe reserves the right to add or remove Dynamic Currency Conversion supported currencies at any time without notice. With respect to any individual Customer transaction, Stripe may choose to apply a different exchange rate than the Currency Exchange Rate when Stripe settles the resulting funds to User’s Stripe Account, or when issuing Refunds. User acknowledges and agrees that Dynamic Currency Conversion does not provide: (a) the supply of foreign currencies by Stripe; or (b) a foreign currency exchange or similar service.
Qualifications & exceptions
Stripe may apply a different rate at settlement or on Refunds.
Currency changes need no notice.
Not stated here
The terms do not say how large a difference in rates may be.
Charges & Financial Obligations · Restriction or exception
DCC: you must give Customers the required information, including any markup, and a free choice to accept or decline
The User must (a) give Customers all necessary information about its use of Dynamic Currency Conversion as Law or Payment Method Rules require, in the form (including durable medium, as applicable) and manner required, including that the service may include a User-imposed markup on the prevailing exchange rate; and (b) make sure Customers are offered a free choice to accept or decline the conversion and that it is not used to convert a Transaction to a Customer's card currency without first getting the Customer's agreement on the information properly given.
Supporting quotations
7.4 User Obligations.
User must:
(a) provide Customers with all necessary information relating to its use of Dynamic Currency Conversion as required by Law or Payment Method Rules, in the form (including durable medium, as applicable) and manner required, including that this service may include a User-imposed markup on the prevailing currency exchange rate; and
(b) ensure Customers are offered a free choice to accept or decline the conversion option and that Dynamic Currency Conversion is not used to convert a Transaction to a Customer’s card currency without first obtaining the Customer’s agreement on the basis of the information duly provided;
Qualifications & exceptions
Information must be given in the form and manner Law or Payment Method Rules require.
Legal Rights & Agreement Rules · Restriction or exception
DCC: you stay responsible; Stripe disclaims liability for compliance, rate accuracy, bank fees and your actions
The User remains fully responsible for, and Stripe disclaims all liability for, (a) the User's fulfilment of its obligations under Law and Payment Method Rules, including its use of Dynamic Currency Conversion; (b) the accuracy of the prices Dynamic Currency Conversion shows to the User and its Customers and of the exchange rates it uses; (c) any fees charged to the User or its Customers by the User's bank or another financial institution; and (d) the User's action or failure to act because of directions or recommendations related to it.
Supporting quotations
7.5 Disclaimer.
User remains fully responsible for, and Stripe disclaims all liability with respect to:
(a) User’s fulfilment of its obligations under Law and Payment Method Rules, including with respect to its use of Dynamic Currency Conversion;
(b) the accuracy of the prices Dynamic Currency Conversion presents to User and its Customers, and the currency exchange rates Dynamic Currency Conversion uses and applies;
(c) any fees charged to User or its Customers by User’s bank or any other applicable financial institution; and
(d) User’s action, or failure to act, as a result of any directions or recommendations User receives related to Dynamic Currency Conversion.
Content & IP Rights · Context
Definitions: Apps on Devices, Stripe App and Stripe Apps Developer Agreement
Apps on Devices is the application management and distribution service and developer tools Stripe provides to let the User deploy Stripe Apps on Terminal Products. A Stripe App takes its meaning from the Stripe Apps Developer Agreement, which is accessible from the Stripe Legal Page.
Supporting quotations
8. Definitions.
“Apps on Devices” means the application management and distribution service and developer tools provided by Stripe that enable User to deploy Stripe Apps on Stripe Terminal Products.
“Stripe App” has the meaning given to that term in the [Stripe Apps Developer Agreement](https://stripe.com/legal/app-developer-agreement).
“Stripe Apps Developer Agreement” means the [Stripe Apps Developer Agreement](https://stripe.com/legal/app-developer-agreement) accessible from the Stripe Legal Page.
Not stated here
The meaning of Stripe App is in the Developer Agreement, which is not supplied.
Charges & Financial Obligations · Context
Definitions: Card Network, Connected Account, Currency Exchange Rate and Refund
A Card Network is a payment card network, including those run by Visa, Mastercard, American Express and Discover; the named networks are examples. A Connected Account is either a Platform User with a Stripe Account onboarded to a Stripe Connect Platform through the Stripe Connect Services, or a Payout Recipient. The Currency Exchange Rate is the Stripe-determined rate applied during a Customer transaction to convert prices into the Customer's local currency. A Refund is an instruction the User starts to return funds, in full or in part, to a Customer for a processed Transaction.
Supporting quotations
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
“Currency Exchange Rate” means the Stripe-determined currency exchange rate applied during a Customer transaction to convert the prices of goods and services into Customer’s local currency.
“Refund” means an instruction User initiates to provide a full or partial return of funds to a Customer for a processed Transaction.
Qualifications & exceptions
The named Card Networks are examples, not a complete list.
Charges & Financial Obligations · Context
Definitions: Dynamic Currency Conversion, On-Reader Forms and Payment Method Account Details
Dynamic Currency Conversion is functionality Stripe may make available through the Terminal Services that lets the User offer currency conversion to Customers on certain Card Network Transactions in supported currencies on supported Terminal Products. On-Reader Forms let the User show pre-built interfaces on reader screens to display customized text, let Customers pick from buttons, or collect and store Customer input text and signature images. Payment Method Account Details are the Customer's payment method account details that the PCI Standards require to be protected, which may include the name and, for cards, the account number, expiration date and card verification value or similar security code.
Supporting quotations
“Dynamic Currency Conversion” means functionality Stripe may make available via the Stripe Terminal Services that allows User to offer dynamic currency conversion to its Customers on certain Card Network Transactions in supported currencies via supported Stripe Terminal Products, as described in the Stripe Terminal Documentation.
“On-Reader Forms” means functionality that allows User to display pre-built user interfaces on Stripe Terminal Product reader device screens that may be used to (a) display customized text to User’s Customers, (b) solicit Customer selection from buttons displaying customized text, or (c) collect and store Customer input text information and signature images.
“Payment Method Account Details” means the Payment Method account details for a Customer that the PCI Standards require to be protected, which may include the Customer’s name, and with respect to credit and debit cards, the Customer’s account number, card expiration date, and card verification value or similar security code.
Charges & Financial Obligations · Context
Definitions: Stripe Terminal Documentation and Stripe Terminal Product
Stripe Terminal Documentation is the Documentation plus other documentation Stripe makes available, including by email, about the Terminal Services, Software or Products. A Stripe Terminal Product is a device or other hardware that a Stripe Entity or an authorized distributor or reseller supplies to the User (such as a POS device, accessory, component or spare part) together with its installed Terminal Device Software, or that Stripe approves for use to access the Terminal Services or Stripe Technology or to run the Terminal Software.
Supporting quotations
“Stripe Terminal Documentation” means the Documentation, along with other documentation that Stripe makes available to User (including via email), relating to the Stripe Terminal Services, Stripe Terminal Software, or Stripe Terminal Products.
“Stripe Terminal Product” means a device, instrument, piece of equipment, or other hardware that (a) a Stripe Entity or a third-party distributor or reseller authorized by a Stripe Entity supplies to User, which may be a physical Point of Sale (POS) device, accessory, component, or spare part, and the Terminal Device Software installed on that hardware product; or (b) Stripe approves for use to access the Stripe Terminal Services or the Stripe Technology, or to operate the Stripe Terminal Software.
Qualifications & exceptions
A Terminal Product can also be hardware Stripe approves for use, not only hardware supplied to the User.
Stripe Terminal Services are the Stripe Payments Services for Transactions processed using a Terminal Product, with related services and features described in the Terminal Documentation and on the Stripe Website. Stripe Terminal Software is the Terminal Device Software and the Terminal SDK, and Terminal Device Software takes its meaning from the Terminal Device EULA. The Terminal Device EULA is the Terminal Device Software License Agreement for end users, incorporated into the Agreement by reference. The Terminal Purchase Terms are the agreement under which a Stripe Entity supplies the Terminal Products the User is using. The Terminal SDK is software code that is Stripe Technology, distributed under the MIT license with a test environment and documentation, available from Stripe's GitHub, including iOS, Android and JavaScript versions and all Updates.
Supporting quotations
“Stripe Terminal Services” means the Stripe Payments Services for Transactions processed using a Stripe Terminal Product, together with related services and features as described in the Stripe Terminal Documentation and on the Stripe Website.
“Stripe Terminal Software” means the Terminal Device Software and Terminal SDK.
“Terminal Device EULA” means the Terminal Device Software License Agreement for end users, the terms of which are incorporated into this Agreement by this reference.
“Terminal Device Software” has the meaning given to it in the Terminal Device EULA.
“Terminal Purchase Terms” means the agreement under which a Stripe Entity supplies the Stripe Terminal Products that User is using.
“Terminal SDK” means the software code that is Stripe Technology and is distributed under the MIT license, test environment, and associated documentation, as described in the Stripe Terminal Documentation and which Stripe makes available at [https://github.com/stripe](https://github.com/stripe), including iOS, Android and JavaScript versions, and including all Updates.
Qualifications & exceptions
The Terminal SDK is described as distributed under the MIT license.
Not stated here
The EULA and Purchase Terms are separate documents and are not supplied.
Charges & Financial Obligations · Context
Treasury Terms add to the General and Financial Services Terms, with Regional Terms by your Account Country
These Stripe Treasury Terms (formerly Financial Accounts), last updated September 28, 2026, supplement the General Terms and, together with the Stripe Financial Services Terms, which they incorporate by reference, govern the use of the Stripe Treasury Services. The Regional Terms in Section 11 apply based on the User's Stripe Account Country. Capitalized terms not defined here take their meaning from the General Terms or the Financial Services Terms.
Supporting quotations
Last updated: September 28, 2026
1.1 Operation of These Terms.
These terms (“Stripe Treasury Terms”) supplement the General Terms and, together with the Stripe Financial Services Terms which are incorporated into these Stripe Treasury Terms by this reference, govern the use of the Stripe Treasury Services. The Regional Terms in Section 11 (Regional Terms) of these Stripe Treasury Terms apply based on User’s Stripe Account Country. Capitalized terms that are not defined in these terms have the same meanings given to them in the General Terms or the Stripe Financial Services Terms.
Qualifications & exceptions
Which Regional Terms apply depends on the User's Stripe Account Country.
Charges & Financial Obligations · Restriction or exception
Treasury lets you make, accept and store fiat funds if you reside in the User Territory; no stablecoin
The Stripe Treasury Services let the User make or accept Financial Account Transactions and store funds. The User must reside in the User Territory to use them: for the United States this means the US and its territories and protectorates (excluding the Northern Mariana Islands, US Virgin Islands and Guam), and for the United Kingdom, the UK. The services are limited to fiat currency and do not include custody, exchange, transmission or payout of Stablecoin or any other digital asset. Stablecoin-related services are governed by the Stablecoin Treasury Terms, the Stripe Global Payouts Stablecoin Terms and the Stablecoin Partner Terms, as applicable. A Financial Account Transaction is an Inbound or Outbound Transaction.
Supporting quotations
1.2 Description of Stripe Treasury Services.
The Stripe Treasury Services enable User to make or accept Financial Account Transactions and store funds. User must reside in the User Territory in order to use the Stripe Treasury Services. For the avoidance of doubt, the Stripe Treasury Services are limited to fiat currency services. The Stripe Treasury Services do not include the custody, exchange, transmission, or payout of Stablecoin or any other digital asset. All Stablecoin-related services are governed by the Stablecoin Treasury Terms, the Stripe Global Payouts Stablecoin Terms, and the Stablecoin Partner Terms, as applicable.
“Financial Account Transaction” means an Inbound Transaction or an Outbound Transaction.
“User Territory” means the United States and its territories and protectorates (excluding the Northern Mariana Islands, US Virgin Islands, and Guam).
“User Territory” means the United Kingdom.
Qualifications & exceptions
Residence in the User Territory is required.
Limited to fiat currency.
Not stated here
User Territory is defined separately in the regional definitions for each region read here.
Data Access & Collection · Permission or license
You authorize RSP and the Treasury Bank to obtain credit and personal information about you and your owners
The User authorizes RSP, the regulated services provider of the Treasury Services, and the Treasury Bank to obtain information about it from their service providers and other third parties, including credit reporting agencies and information bureaus, and if required must authorize and direct those third parties to compile and provide it. The information may include the User's name, addresses, credit history and other data, including Personal Data, about the User, its representatives and its owners. The Treasury Bank is a bank at which Stripe maintains User funds for the services.
Supporting quotations
2.1 Authority to Conduct Checks.
User authorizes RSP and the Treasury Bank to obtain information about User from their service providers and other third parties, including credit reporting agencies and information bureaus. If required, User must authorize and direct these third parties to compile and provide this information to RSP or the Treasury Bank, as applicable. User agrees that this information may include User’s name, addresses, credit history, and other data (including Personal Data) about User, User’s representatives, and User’s owners.
“RSP” means the regulated services provider of the Stripe Treasury Services.
“Treasury Bank” means a bank at which Stripe maintains User funds in connection with the Stripe Treasury Services.
Qualifications & exceptions
Covers information about the User's representatives and owners as well as the User.
Not stated here
The list of data is open-ended (“other data”).
Charges & Financial Obligations · Restriction or exception
You must provide Financial Account Transaction information on request, and Stripe may limit use until satisfied
If Stripe asks, the User must give information about a Financial Account Transaction, including the source of funds. Stripe may prohibit, disable or limit the User's use of the Stripe Treasury Services until it is satisfied it has enough information about each Financial Account Transaction or other use of the services.
Supporting quotations
2.2 Information Provided to Stripe.
(a) Financial Account Transactions. User must, if requested by Stripe, provide information about a Financial Account Transaction, including the source of funds. Stripe may prohibit, disable, or limit User’s use of the Stripe Treasury Services until Stripe is satisfied that it has received sufficient information relating to each Financial Account Transaction or other use of the Stripe Treasury Services.
Qualifications & exceptions
Applies if Stripe requests the information.
Not stated here
The terms do not say how long Stripe may take to be satisfied.
Charges & Financial Obligations · Restriction or exception
You are responsible for accurate payment instructions and must promptly report errors or unauthorized transactions
The User is responsible for giving accurate and complete payment instructions, and for checking the accuracy and completeness of any payment instructions and details it gives for a Financial Account Transaction. If the User believes there is an error in a Financial Account Transaction, or an unauthorized one has occurred, it must promptly notify Stripe and give all information Stripe requests.
Supporting quotations
(b) Payment Instructions. User is responsible for providing accurate and complete payment instructions, and for verifying the accuracy and completeness of any payment instructions and details that User provides in respect of a Financial Account Transaction.
(c) Errors. If User believes that there is an error in a Financial Account Transaction, or an unauthorized Financial Account Transaction has occurred, User must promptly notify Stripe and provide all information requested by Stripe.
Qualifications & exceptions
Notice of errors must be prompt.
Not stated here
The terms give no fixed deadline for reporting errors.
Charges & Financial Obligations · Restriction or exception
You acknowledge RSP is not a bank, the Financial Account is not a deposit account, and RSP acts as your agent
The User acknowledges that (a) RSP and its Affiliates are not banks; (b) the Financial Account is not a demand deposit (checking) account, savings account or other asset or bank account with RSP, its Affiliates, a Treasury Bank or its Affiliates; (c) RSP acts as the User's agent for the Financial Account; (d) RSP selects the Treasury Bank through which the Financial Account is created; (e) RSP makes no representation about the sufficiency of the Treasury Bank's capitalization; and (f) RSP may appoint Stripe as its agent or service provider to exercise its rights and perform its obligations, other than for regulated services.
Supporting quotations
2.3 Acknowledgments.
User acknowledges that:
(a) RSP and its Affiliates are not banks;
(b) the Financial Account is not a demand deposit (checking) account, savings account, or other asset or bank account with RSP, an Affiliate of RSP, a Treasury Bank, or an Affiliate of a Treasury Bank;
(c) RSP will act as User’s agent with respect to the Financial Account;
(d) RSP will select the Treasury Bank through which User’s Financial Account is created;
(e) RSP makes no representation about the sufficiency of the capitalization of the Treasury Bank where User’s funds are held; and
(f) RSP may appoint Stripe as its agent or service provider to exercise its rights and perform its obligations under these Stripe Treasury Terms, other than with respect to regulated services.
Qualifications & exceptions
RSP chooses the Treasury Bank, not the User.
Appointment of Stripe does not extend to regulated services.
Security & Safeguards · Restriction or exception
A VBAN may be used only with Treasury; you must secure it, and Stripe is not liable for your use or disclosure of it
Unless Stripe agrees otherwise in writing, a VBAN issued for the Treasury Services may be used only with them. The User must keep the VBAN secure and prevent misuse. Stripe, its Affiliates and Stripe's Financial Providers are not liable for losses, damages or costs from the User's use or disclosure of the VBAN. The User acknowledges that a VBAN is not an account at a Treasury Bank. A VBAN is the virtual account number tied to the Financial Account, provisioned by a Treasury Bank.
Supporting quotations
2.4 Use of VBANs.
Unless otherwise agreed in writing by Stripe, any VBAN issued for the Stripe Treasury Services must only be used in connection with the Stripe Treasury Services. User must maintain the security of the VBAN and prevent its misuse. Stripe, its Affiliates, and Stripe’s Financial Providers will not be liable for any losses, damages, or costs arising out of or related to User’s use or disclosure of the VBAN. User acknowledges that a VBAN is not an account at a Treasury Bank.
“VBAN” means the virtual account number associated with User’s Financial Account that is provisioned by a Treasury Bank.
Qualifications & exceptions
Other use needs Stripe's written agreement.
Charges & Financial Obligations · Company practice
Available Balance adds pending provisional credits and subtracts Transaction Holds when checking if funds are available
Solely to decide whether funds are available for a Financial Account Transaction, the Available Balance is (a) increased by pending provisionally credited Financial Account Transactions (excluding pending returns) in the User's Financial Account and (b) decreased by Transaction Holds on funds in it. The User can view its Available Balance on the Stripe Dashboard.
Supporting quotations
3. Financial Account Transactions.
3.1 Available Balance.
Solely for the purpose of determining whether funds are available for a Financial Account Transaction, the Available Balance is (a) increased by the amount of any pending provisionally credited Financial Account Transactions (excluding pending returns) in User’s Financial Account; and (b) decreased by the amount of Transaction Holds on funds in User’s Financial Account. User can view User’s Available Balance on the Stripe Dashboard.
Qualifications & exceptions
Applies solely to determining whether funds are available for a transaction.
Pending returns are excluded from the increase.
Charges & Financial Obligations · Company practice
You add funds through Stripe's funding mechanisms, and Stripe counts them only once actually received
The User may add funds to a Financial Account through the funding mechanisms Stripe makes available. Stripe is not responsible for any funds transferred, and will not record them as available in a Financial Account, until Stripe actually receives them. Financial Account Transactions and the Available Balance can be viewed in the User's Stripe Dashboard.
Supporting quotations
3.2 Adding Funds to User’s Financial Account.
(a) How to Add Funds. User may add funds into a Financial Account via the funding mechanisms Stripe makes available. Stripe is not responsible for any funds transferred, and will not record them as available in a Financial Account, until actually received by Stripe. Financial Account Transactions and Available Balance are available to view in User’s Stripe Dashboard.
Qualifications & exceptions
Funds are available only after Stripe actually receives them.
Charges & Financial Obligations · Permission or license
You authorize RSP as your agent; Outbound Transactions are deducted at once; Stripe may retry or split them
The User authorizes RSP to act as its agent to make any Financial Account Transaction it requests. Stripe deducts the amount of each Outbound Transaction the User starts from the Available Balance even if the transaction has not yet completed. If a transaction cannot be completed, Stripe may retry it or complete it in multiple transactions, and if it still cannot be completed Stripe will notify the User. RSP may endorse any credit Financial Account Transaction the User presents to be added to the account, and if there is a qualified endorsement RSP may place the User's unqualified endorsement on it. An Outbound Transaction is an Outbound Payment, Outbound Transfer or other fiat entry that subtracts from the Available Balance and that Stripe may permit in its sole discretion.
Supporting quotations
(b) Authorization. User authorizes RSP to act as User’s agent to make any Financial Account Transaction requested by User. Stripe will deduct the amount of each Outbound Transaction that User initiates from the Available Balance even if the transaction has not yet been completed. If an initiated Financial Account Transaction cannot be completed, Stripe may retry the Financial Account Transaction, or complete the Financial Account Transaction in multiple transactions. If that Financial Account Transaction still cannot be completed, Stripe will notify User. RSP may endorse any credit Financial Account Transaction that User presents to be added to User’s Financial Account. If there is a qualified endorsement on a credit Financial Account Transaction, RSP may place User’s unqualified endorsement on the credit Financial Account Transaction.
“Outbound Transaction” means an Outbound Payment, Outbound Transfer, or any other fiat currency entry or transaction that subtracts from the Available Balance that Stripe may permit from time to time in its sole discretion.
Qualifications & exceptions
Deduction happens even before the transaction completes.
Stripe may complete a transaction in multiple parts.
Not stated here
The terms do not say when a deducted amount is returned if a transaction fails.
Charges & Financial Obligations · Permission or license
RSP follows documented timelines unless delayed or withheld, and Stripe may place Transaction Holds above your balance
RSP will make a Financial Account Transaction within the time periods in the Documentation unless (i) a Financial Account Transaction Delay occurs, (ii) Stripe exercises a right under the Agreement, or (iii) Law permits withholding or delaying it. Stripe may place a Transaction Hold, a restriction on funds availability or on the User's ability to transact, if it reasonably doubts it can collect amounts owed to it, is concerned about fraud or misconduct (including for new accounts or large transactions), is concerned about Financial Account Regulatory Requirements, or for any other reason the Agreement or those requirements permit. A hold may be for more than the User's Available Balance.
Supporting quotations
3.3 Timing of Financial Account Transactions.
(a) Timing. RSP will make a Financial Account Transaction in accordance with the time periods stated in the Documentation unless (i) a Financial Account Transaction Delay occurs, (ii) Stripe exercises a right under the Agreement, or (iii) as permitted by Law to withhold or delay the Financial Account Transaction.
(b) Transaction Hold. Stripe may place a Transaction Hold on Financial Account Transactions (i) if Stripe reasonably doubts that it can collect the amounts owed to Stripe; (ii) if Stripe is concerned about potential fraud or other misconduct, including for new Financial Accounts or large Financial Account Transactions; (iii) if Stripe is concerned about compliance with Financial Account Regulatory Requirements; or (iv) for any other reason permitted by the Agreement or Financial Account Regulatory Requirements. Stripe may place a Transaction Hold for more than User’s Available Balance.
“Financial Account Transaction Delay” means a delay of a Financial Account Transaction caused by (a) the unavailability of, or delay by, a Financial Provider (including a Card Network or clearing network), Governmental Authority, telecommunications provider, or internet service provider, including as a result of a Financial Provider’s default, insolvency, or bankruptcy; (b) incorrect information, such as a bank account number, provided to Stripe; (c) User’s equipment, software, or other technology; (d) a Force Majeure Event; (e) fraud or sanction screening required or requested by Stripe, its Financial Providers, or recipient banks; or (f) the recipient bank not being directly integrated with the clearing system used by Stripe or the type of recipient bank account not being supported by Stripe (e.g. a savings account, money market or investment account, multi-currency account, or foreign or correspondent account).
“Transaction Hold” means a restriction on the availability of funds in a Financial Account or on User’s ability to effect a Financial Account Transaction that Stripe places as a result of delayed funds availability, Legal Process, or other circumstances as determined by Stripe in its sole discretion.
Qualifications & exceptions
Timing depends on the Documentation, which is not supplied.
A Transaction Hold can exceed the Available Balance.
Not stated here
The Documentation's time periods are not in this text.
Charges & Financial Obligations · Restriction or exception
An Outbound Transaction cannot be cancelled or reversed, and you cannot send more than your Available Balance
An Outbound Transaction extinguishes any payout liability Stripe may have for the payout amount. Once an Outbound Transaction has started it cannot be cancelled or reversed, and Stripe may not be able to, and has no obligation to try to, retrieve funds sent. If Stripe can retrieve them, it may charge the User the retrieval costs. The User may not start an Outbound Transaction larger than the Available Balance of its Financial Account.
Supporting quotations
3.4 Outbound Transaction Initiation.
An Outbound Transaction extinguishes any payout liability that Stripe may have in respect of the payout amount. User acknowledges that once an Outbound Transaction has commenced, it cannot be cancelled or reversed, and Stripe may not be able to (and is under no obligation to attempt to) retrieve funds sent via an Outbound Transaction. If Stripe is able to retrieve the funds, then Stripe may charge User the costs incurred for that retrieval. User may not initiate an Outbound Transaction that is greater than the Available Balance of User’s Financial Account.
Qualifications & exceptions
Stripe has no obligation to attempt retrieval.
Retrieval costs may be charged to the User.
Charges & Financial Obligations · Permission or license
RSP may refuse a transaction made by an unpermitted method or lacking required information
RSP may refuse any Financial Account Transaction (a) made by a method RSP does not specifically permit for the User's Financial Account, or (b) that does not include all the information RSP or the Treasury Bank require.
Supporting quotations
3.5 RSP’s Right to Refuse.
RSP may refuse any Financial Account Transaction (a) by any method that RSP does not specifically permit for User’s Financial Account; or (b) that does not include all information RSP or the Treasury Bank require.
Not stated here
The permitted methods and required information are not listed here.
Charges & Financial Obligations · Permission or license
RSP sets Cut-Off Times and may change them immediately without notice
RSP sets Cut-Off Times for various Financial Account Transactions and gives them to the User through the Stripe Dashboard or otherwise in writing. RSP may change a Cut-Off Time from time to time, effective immediately and without notice to the User. The User may contact RSP at any time to verify the Cut-Off Time. A Cut-Off Time is the time on a business day by which RSP must receive an instruction or request for it to be processed the same day.
Supporting quotations
3.6 Cut-Off Times.
RSP establishes Cut-Off Times for various Financial Account Transactions and RSP will provide those Cut-Off Times to User through the Stripe Dashboard or otherwise in writing. RSP may change the Cut-Off Time from time to time. Any change to the Cut-Off Time will be effective immediately and without notice to User. User may contact RSP at any time to verify the Cut-Off Time.
“Cut-Off Time” means the time on a business day by which RSP must receive an instruction or Financial Account Transaction request in order to process that instruction or request on the same day.
Qualifications & exceptions
Changes take effect immediately and without notice.
Charges & Financial Obligations · Restriction or exception
There is no overdraft feature, and you must promptly fund any negative balance
There is no overdraft feature for the User's Financial Account. If the account has a negative balance, the User must promptly transfer enough funds in the applicable Supported Currency into it to make the balance positive.
Supporting quotations
3.7 No Overdraft Features.
There is no overdraft feature associated with User’s Financial Account. If User’s Financial Account has a negative balance, User must promptly transfer sufficient funds in the applicable Supported Currency into the Financial Account to render the balance positive.
Qualifications & exceptions
Funding must be prompt.
Not stated here
The terms give no fixed deadline for covering a negative balance.
Charges & Financial Obligations · User right or choice
You can stop a scheduled or preauthorized transaction by instructing Stripe within the documented timeframe
To stop a scheduled or preauthorized Financial Account Transaction, the User must give Stripe instructions within the timeframe specified in the Documentation. If the User scheduled or preauthorized the transaction through the Stripe Dashboard, it may change or cancel it there as the Documentation describes.
Supporting quotations
3.8 User’s Right to Stop Payment.
If User wishes to stop any scheduled or preauthorized Financial Account Transaction from User’s Financial Account, then User must give Stripe instructions to do so within the timeframe specified in the Documentation. If User scheduled or preauthorized the Financial Account Transaction via the Stripe Dashboard, then User may change or cancel the Financial Account Transaction via the Stripe Dashboard as described in the Documentation.
Qualifications & exceptions
The timeframe is set in the Documentation.
Not stated here
The timeframe is in the Documentation, which is not supplied.
Charges & Financial Obligations · Restriction or exception
You are responsible for all transactions, authorized or not; Stripe disclaims liability for failures and lost funds
To the extent Law permits, the User is responsible for all Financial Account Transactions on its Financial Account, whether or not authorized. To the maximum extent Law permits, the Stripe Parties are not liable to the User, its Affiliates or any third party for losses, damages or costs from (a) a failed transaction, including RSP refusing or declining it or a failure from circumstances outside RSP's control; (b) RSP completing a transaction or acting in reliance on incorrect or incomplete information; or (c) any correspondent bank's negligence or failure, or funds lost in transit.
Supporting quotations
3.9 Liability Related to Financial Account Transactions.
To the extent permitted by Law, User is responsible for all Financial Account Transactions on User’s Financial Account, whether or not they are authorized. To the maximum extent permitted by Law, the Stripe Parties will not be liable to User, User’s Affiliates, or any third party for any losses, damages, or costs arising out of or relating to:
(a) a failed Financial Account Transaction on User’s Financial Account, including if RSP decides to refuse to pay or decline any Financial Account Transaction or if a Financial Account Transaction fails due to circumstances outside of RSP’s control;
(b) RSP completing a Financial Account Transaction or otherwise acting in reliance upon any incorrect or incomplete information provided or made available to RSP; or
(c) any correspondent bank’s negligence or failure, or funds lost in transit.
Qualifications & exceptions
Responsibility for unauthorized transactions applies to the extent Law permits.
The disclaimer applies to the maximum extent Law permits.
Account & Service Control · Permission or license
RSP may decline, delay, freeze or reverse transactions, restrict access, and remove funds pending investigation
RSP may decline, delay, freeze or reverse a Financial Account Transaction or part of one, restrict access to the User's Financial Account or its information, or remove funds from the account to hold them pending investigation, to protect the User, RSP or RSP's Affiliates, or to comply with Financial Account Regulatory Requirements or other legal obligations.
Supporting quotations
4. Restricting or Closing User’s Financial Account.
4.1 Restricting User’s Financial Account.
RSP may decline, delay, freeze, or reverse a Financial Account Transaction or part of a Financial Account Transaction, restrict access to User’s Financial Account or information on User’s Financial Account, or remove funds from User’s Financial Account to hold them pending investigation to protect User, RSP, or RSP’s Affiliates, or to comply with Financial Account Regulatory Requirements or other legal obligations.
Qualifications & exceptions
Actions are tied to protection or legal compliance.
Not stated here
The terms give no notice period before RSP acts.
Account & Service Control · Permission or license
RSP may move your information to a replacement Financial Account and move custodial accounts to another institution
RSP may transfer the User's documentation and information, including Personal Data, to a replacement Financial Account and account number, including if the account is reported as compromised or RSP reasonably believes it is necessary to protect its security. RSP may also move its Custodial Accounts, and therefore the User's Financial Account, to a different financial institution. A Custodial Account is a custodial account RSP maintains in its own name at the Treasury Bank for the benefit of all accountholders using the Treasury Services.
Supporting quotations
4.2 Replacement Financial Account.
RSP may transfer User’s documentation and information (including Personal Data) to a replacement Financial Account and account number, including if User’s Financial Account is reported as compromised, or if RSP reasonably believes it is necessary to protect User’s Financial Account’s security. RSP may move RSP’s Custodial Accounts (and therefore User’s Financial Account) to a different financial institution.
“Custodial Account” means a custodial account that RSP maintains, in its name, at the Treasury Bank, for the benefit of all accountholders using the Stripe Treasury Services.
Qualifications & exceptions
Moving information is tied to compromise or security protection.
Moving Custodial Accounts has no stated condition.
Not stated here
The terms do not require notice before a move.
Account & Service Control · Permission or license
RSP may close your account any time on notice; you may close it by notice; RSP may require you to withdraw the balance
RSP may close the User's Financial Account at any time for any reason on notice to the User. The User may close it at any time by notifying Stripe. If the balance is above $0, after RSP deducts fees, expenses, claims and other deductions it may make, RSP may require the User to withdraw the remaining balance before closing.
Supporting quotations
4.3 Closing User’s Financial Account.
(a) By RSP. RSP may close User’s Financial Account at any time for any reason upon notice to User.
(b) By User. User may close User’s Financial Account at any time by giving notice to Stripe. If User’s account balance is greater than $0, after RSP deducts fees, expenses, claims, and other deductions that RSP has the right to make, RSP may require User to withdraw the remaining balance before RSP closes User’s Financial Account.
Qualifications & exceptions
RSP's closing right needs notice but no reason.
RSP may require withdrawal of any remaining balance first.
Not stated here
No notice period is stated for RSP's closure.
Account & Service Control · Restriction or exception
RSP may keep an account open for pending transactions, overdrafts or Legal Process, and owes no duty after closure
RSP need not close the account at the User's request if (i) there are pending Financial Account Transactions, (ii) there is an overdraft, or (iii) the account is subject to Legal Process. In those cases RSP may restrict the account against all future withdrawals, other than those made under Legal Process, until pending transactions are paid or returned, the balance is no longer negative and any legal restriction is released. After closure, RSP has no obligation to accept funds into the account, process transactions on the User's behalf, or satisfy outstanding payment demands, but may reopen the account if it receives funds payable to it.
Supporting quotations
(c) RSP Can Keep Financial Account Open. RSP is not required to close User’s Financial Account at User’s request if (i) User has pending Financial Account Transactions; (ii) there is an overdraft on User’s Financial Account; or (iii) User’s Financial Account is subject to Legal Process. In those cases, RSP may restrict User’s Financial Account against all future withdrawals, other than those made under Legal Process, until pending Financial Account Transactions are paid or returned, the account balance is no longer negative, and any legal restriction has been released.
(d) Consequences of Closing User’s Financial Account. After User’s Financial Account is closed, RSP has no obligation to accept funds into User’s Financial Account, process Financial Account Transactions through the Financial Account on User’s behalf, or satisfy any outstanding demands for payment. But, RSP may reopen User’s Financial Account if RSP receives funds payable to User’s Financial Account.
Qualifications & exceptions
The right to keep the account open applies in three listed cases.
Charges & Financial Obligations · Restriction or exception
You are responsible for paying, withholding and reporting Taxes for yourself and your Recipients
The User is responsible for paying or withholding any applicable Taxes and for completing any Tax reporting for itself and, if required, on behalf of its Recipients, in connection with the Stripe Treasury Services.
Supporting quotations
5. Taxes and Currency Conversion.
5.1 Taxes.
User is responsible for the payment or withholding of any applicable Taxes and the completion of any Tax reporting for User and on behalf of User’s Recipient, if required, in connection with the Stripe Treasury Services.
Qualifications & exceptions
Covers Tax reporting on behalf of Recipients, if required.
Charges & Financial Obligations · Company practice
Currency conversion rates follow the Documentation, and quoted payout amounts and fees are estimates
If a requested Financial Account Transaction needs a currency conversion, the exchange rate is determined as stated in the Documentation. Where conversion is part of a transaction, quoted payout amounts and associated fees are estimates that may change with the exchange rate when the conversion happens.
Supporting quotations
5.2 Currency Conversion.
If a requested Financial Account Transaction requires a currency conversion, then the exchange rate used for that conversion will be determined as stated in the Documentation. Where currency conversion is part of a Financial Account Transaction, any quoted payout amounts and associated fees are estimates, and may fluctuate based on changes in the exchange rate that applies when the currency conversion takes place.
Qualifications & exceptions
Quoted amounts and fees are estimates.
Not stated here
The rate is set by the Documentation, which is not supplied.
Sharing & Disclosure · Permission or license
You authorize Stripe to share your information with third parties, including Financial Providers, for listed purposes
The User authorizes Stripe and its Affiliates to share, unless Financial Account Regulatory Requirements prohibit it, information including Personal Data about the User, its Financial Account, Recipients and Financial Account Transactions with third parties, including Financial Providers: (a) to let the User open the account and complete transactions; (b) to provision VBANs; (c) to investigate any claim the User makes; (d) to comply with Financial Account Regulatory Requirements; (e) to comply with an arbitration order; or (f) as otherwise disclosed or permitted by the Treasury Terms, Stripe's Privacy Policy or the Agreement.
Supporting quotations
6. Permitted Privacy and Data Use.
User authorizes Stripe and its Affiliates to share, unless prohibited by Financial Account Regulatory Requirements, information, including Personal Data, about User, User’s Financial Account, Recipients, and Financial Account Transactions, with third parties (including our Financial Providers): (a) to enable User to open the Financial Account and complete Financial Account Transactions; (b) for the provisioning of VBANs; (c) in connection with investigating any claim User makes; (d) to comply with Financial Account Regulatory Requirements; (e) to comply with an arbitration order; or (f) as otherwise disclosed or permitted by these Stripe Treasury Terms, Stripe’s Privacy Policy, or the Agreement.
Qualifications & exceptions
Sharing is subject to a legal prohibition if one applies.
Item (f) allows sharing wherever the Privacy Policy or Agreement permits.
Not stated here
Stripe's Privacy Policy is linked and not supplied.
Legal Rights & Agreement Rules · Restriction or exception
No payments outside the Transaction Territory, no transfer services for third parties, and no criminal proceeds
The User must (a) not use the Financial Account to send payments to, or receive payments from, any bank or financial institution account outside the Transaction Territory, meaning any location Stripe makes available from time to time for transactions; (b) make sure its use of the services and performance of its obligations comply with all Financial Account Regulatory Requirements; (c) not use the Financial Account to provide funds transfer services to third parties; and (d) make sure no funds transferred into its Financial Account are proceeds of criminal activity.
Supporting quotations
7. User Restrictions and Obligations.
User must:
(a) not use the Financial Account to send any payment to any bank or financial institution account outside of the Transaction Territory or to receive any payment from any account located outside the Transaction Territory;
(b) ensure that User’s use of the Stripe Treasury Services and performance of User’s obligations under these Stripe Treasury Terms comply with all Financial Account Regulatory Requirements;
(c) not use the Financial Account to provide funds transfer services to third parties; and
(d) ensure that no funds transferred into User’s Financial Account are proceeds from any criminal activity.
“Transaction Territory” means any location that Stripe may make available from time to time for Financial Account Transactions.
Qualifications & exceptions
The Transaction Territory is whatever Stripe makes available from time to time.
Legal Rights & Agreement Rules · Restriction or exception
Where Law voids liability limits for missed stop-payments or forged signatures, liability is capped at face value
To the extent Financial Account Regulatory Requirements invalidate or make unenforceable limits or exclusions of liability of RSP and its Affiliates for failing to stop payment on a Financial Account Transaction, or paying one bearing an unauthorized or forged signature or endorsement, the Stripe Parties' aggregate liability for those circumstances is limited to the face value of the Financial Account Transaction.
Supporting quotations
8. Limitation of Liability.
To the extent that Financial Account Regulatory Requirements invalidate or render unenforceable any limitations or exclusions of liability of RSP and its Affiliates under this Agreement with respect to failing to stop payment on a Financial Account Transaction, or paying a Financial Account Transaction bearing an unauthorized or forged signature or endorsement, then the Stripe Parties’ aggregate liability with respect to those circumstances will be limited to the face value of the Financial Account Transaction.
Qualifications & exceptions
Applies only to the extent regulatory requirements invalidate other limits.
Legal Rights & Agreement Rules · Restriction or exception
Stripe offers no service levels for the Treasury Services
Stripe does not offer service levels for the Stripe Treasury Services, so no uptime or availability commitment is made in these terms.
Supporting quotations
9. Disclaimers.
9.1 Availability.
Stripe does not offer service levels for the Stripe Treasury Services.
Charges & Financial Obligations · Restriction or exception
Transactions may go to the wrong account if you give Stripe inaccurate or incomplete information
The User acknowledges that Financial Account Transactions may be sent to the wrong account if it gives Stripe inaccurate or incomplete information, including because of compromise or fraud.
Supporting quotations
9.2 Reliance.
User acknowledges that Financial Account Transactions may be sent to the wrong account if User provides Stripe with inaccurate or incomplete information (including due to compromise or fraud).
Qualifications & exceptions
Includes errors caused by compromise or fraud.
Charges & Financial Obligations · Context
Definitions: ACH Network, Available Balance, Balance Transfer and Card Network
The ACH Network is the automated clearinghouse payment network that Nacha's member organizations control and manage. The Available Balance is the amount of funds available in the Financial Account. A Balance Transfer is a transfer from the User's own Stripe Account payments balance to its Financial Account under the Treasury Terms. A Card Network is a payment card network, including those run by Visa, Mastercard, American Express and Discover; the named networks are examples.
Supporting quotations
10. Definitions.
“ACH Network” means the automated clearinghouse payment network that the member organizations of Nacha control and manage.
“Available Balance” means the amount of funds available in the Financial Account.
“Balance Transfer” means a transfer from User’s own Stripe Account payments balance, to User’s Financial Account, in accordance with the Stripe Treasury Terms.
“Card Network” means a payment card network, including the network operated by each of Visa, Mastercard, American Express, and Discover.
Qualifications & exceptions
The named Card Networks are examples, not a complete list.
Charges & Financial Obligations · Context
Definitions: Financial Account, Treasury Services, RSP, Treasury Bank, Custodial Account and VBAN
The Financial Account is the Stripe Account Stripe provides as part of the Treasury Services. The Stripe Treasury Services let the User access a Financial Account, fund it with a Received Credit or Balance Transfer, make Outbound Transactions and engage in other permitted Financial Account Transactions, all limited to fiat currency, as the Documentation describes. RSP is the regulated services provider of the services. The Treasury Bank is a bank at which Stripe maintains User funds. A Custodial Account is a custodial account RSP maintains in its own name at the Treasury Bank for the benefit of all accountholders using the services. A VBAN is the virtual account number tied to the User's Financial Account, provisioned by a Treasury Bank.
Supporting quotations
“Financial Account” means the Stripe Account that Stripe provides to User as part of the Stripe Treasury Services.
“Stripe Treasury Services” means the Services that enable User to (a) access a Financial Account; (b) fund a Financial Account with a Received Credit or with a Balance Transfer; (c) make Outbound Transactions; and (d) engage in other permitted Financial Account Transactions (in each case limited to fiat currency transactions) as further described in the Documentation.
“RSP” means the regulated services provider of the Stripe Treasury Services.
“Treasury Bank” means a bank at which Stripe maintains User funds in connection with the Stripe Treasury Services.
“Custodial Account” means a custodial account that RSP maintains, in its name, at the Treasury Bank, for the benefit of all accountholders using the Stripe Treasury Services.
“VBAN” means the virtual account number associated with User’s Financial Account that is provisioned by a Treasury Bank.
Qualifications & exceptions
Services are limited to fiat currency transactions.
The Custodial Account is held in RSP's name for all accountholders together.
A Financial Account Regulatory Requirement is Law and the rules of the electronic funds transfer networks the Treasury Services use. Legal Process is a writ of attachment, lien, levy, subpoena, warrant or other legal order. A Transaction Hold is a restriction on the availability of funds in a Financial Account or on the User's ability to make a transaction that Stripe places because of delayed funds availability, Legal Process or other circumstances Stripe determines in its sole discretion. The Transaction Territory is any location Stripe may make available from time to time for transactions. A Cut-Off Time is the time on a business day by which RSP must receive an instruction or request to process it the same day.
Supporting quotations
“Financial Account Regulatory Requirement” means Law and the rules of the electronic funds transfer networks the Stripe Treasury Services use.
“Legal Process” means a writ of attachment, lien, levy, subpoena, warrant, or other legal order.
“Transaction Hold” means a restriction on the availability of funds in a Financial Account or on User’s ability to effect a Financial Account Transaction that Stripe places as a result of delayed funds availability, Legal Process, or other circumstances as determined by Stripe in its sole discretion.
“Transaction Territory” means any location that Stripe may make available from time to time for Financial Account Transactions.
“Cut-Off Time” means the time on a business day by which RSP must receive an instruction or Financial Account Transaction request in order to process that instruction or request on the same day.
Qualifications & exceptions
A Transaction Hold can rest on circumstances Stripe determines in its sole discretion.
The Transaction Territory can change over time.
Charges & Financial Obligations · Context
Definitions: Financial Account Transaction, Inbound and Outbound Transactions, Received Credit, Recipient
A Financial Account Transaction is an Inbound Transaction or an Outbound Transaction. An Inbound Transaction is any Received Credit, Balance Transfer or other entry that increases the Available Balance, which Stripe may permit from time to time in its discretion. A Received Credit is funds added in a Supported Currency from an external bank account by bank transfer, domestic wire or other supported funding methods. A Balance Transfer moves funds from the User's own Stripe Account payments balance to its Financial Account. An Outbound Transaction is an Outbound Payment, Outbound Transfer or other fiat entry that subtracts from the Available Balance and that Stripe may permit in its sole discretion. An Outbound Payment is a fiat payment from the Financial Account to a Recipient, and an Outbound Transfer is a fiat transfer to the User's own external account. A Recipient is a third party in a Transaction Territory receiving a fiat payment or transfer. A Supported Currency is one the Treasury Services support as Stripe communicates.
Supporting quotations
“Financial Account Transaction” means an Inbound Transaction or an Outbound Transaction.
“Inbound Transaction” means any Received Credit, Balance Transfer, or any other entry or transaction that increases the Available Balance, that Stripe may permit from time to time, in its discretion.
“Received Credit” means the funds added to a Financial Account in a Supported Currency from an external bank account via the bank transfer, domestic wire, or other supported funding methods.
“Balance Transfer” means a transfer from User’s own Stripe Account payments balance, to User’s Financial Account, in accordance with the Stripe Treasury Terms.
“Outbound Transaction” means an Outbound Payment, Outbound Transfer, or any other fiat currency entry or transaction that subtracts from the Available Balance that Stripe may permit from time to time in its sole discretion.
“Outbound Payment” means a fiat currency payment from the Financial Account to a Recipient.
“Outbound Transfer” means a fiat currency transfer from the Financial Account to User’s own external bank, financial institution account, or other account User designates.
“Recipient” means a third party located in a Transaction Territory, that receives a fiat currency payment or transfer from User's Financial Account.
“Supported Currency” means a currency supported under the Stripe Treasury Services as communicated to User by Stripe.
Qualifications & exceptions
Stripe permits other entries in its discretion or sole discretion.
Charges & Financial Obligations · Restriction or exception
Definition: a Financial Account Transaction Delay includes outages, wrong details, fraud screening and unsupported banks
A Financial Account Transaction Delay is a delay caused by (a) unavailability of, or delay by, a Financial Provider (including a Card Network or clearing network), Governmental Authority, telecommunications provider or internet service provider, including from a Financial Provider's default, insolvency or bankruptcy; (b) incorrect information, such as a bank account number, given to Stripe; (c) the User's equipment, software or technology; (d) a Force Majeure Event; (e) fraud or sanction screening required or requested by Stripe, its Financial Providers or recipient banks; or (f) the recipient bank not being directly integrated with Stripe's clearing system, or the type of account not being supported, such as savings, money market, investment, multi-currency, foreign or correspondent accounts.
Supporting quotations
“Financial Account Transaction Delay” means a delay of a Financial Account Transaction caused by (a) the unavailability of, or delay by, a Financial Provider (including a Card Network or clearing network), Governmental Authority, telecommunications provider, or internet service provider, including as a result of a Financial Provider’s default, insolvency, or bankruptcy; (b) incorrect information, such as a bank account number, provided to Stripe; (c) User’s equipment, software, or other technology; (d) a Force Majeure Event; (e) fraud or sanction screening required or requested by Stripe, its Financial Providers, or recipient banks; or (f) the recipient bank not being directly integrated with the clearing system used by Stripe or the type of recipient bank account not being supported by Stripe (e.g. a savings account, money market or investment account, multi-currency account, or foreign or correspondent account).
Qualifications & exceptions
During such a delay RSP is not bound by the documented time periods.
Not stated here
The terms do not say how long a delay may last.
Legal Rights & Agreement Rules · Context
Definitions: Nacha, the Nacha Operating Rules, Entry and Originator
Nacha is the National Automated Clearinghouse Association. The Nacha Operating Rules are the rules Nacha publishes that govern automated clearing house transactions on the ACH Network, available at the Nacha rules website. Entry and Originator take the meanings given in the Nacha Operating Rules.
Supporting quotations
“Nacha” means the National Automated Clearinghouse Association.
“Nacha Operating Rules” means the rules Nacha publishes that govern automated clearing house transactions on the ACH Network, located at [www.nachaoperatingrulesonline.org](http://www.nachaoperatingrulesonline.org).
“Entry” has the meaning given to it in the Nacha Operating Rules.
“Originator” has the meaning given to it in the Nacha Operating Rules.
Not stated here
The Nacha Operating Rules are published externally and are not supplied here.
Legal Rights & Agreement Rules · Context
Definitions: ERISA, IRS Code, FDIC and FDIC Insurance
ERISA means the Employee Retirement Income Security Act of 1974, 29 U.S.C. Chapt. 18, and the IRS Code means the Internal Revenue Code, 26 U.S.C. Title 26. FDIC means the Federal Deposit Insurance Corporation, and FDIC Insurance means deposit insurance that covers certain types of accounts at FDIC-insured banks. These definitions only name the laws and insurance; they do not say whether the Financial Account has FDIC Insurance.
Supporting quotations
“ERISA” means the Employee Retirement Income Security Act of 1974, 29 U.S.C. Chapt. 18.
“IRS Code” means Internal Revenue Code, 26 U.S.C. Title 26.
“FDIC” means Federal Deposit Insurance Corporation.
“FDIC Insurance” means deposit insurance that covers certain types of accounts at FDIC-insured banks.
Qualifications & exceptions
The definitions do not state that the Financial Account is FDIC insured.
Not stated here
Whether any FDIC Insurance applies to funds in a Financial Account is not stated in these definitions.
Charges & Financial Obligations · Context
Definitions: Stablecoin, Stablecoin Partner and Stablecoin Partner Terms
A Stablecoin is any fiat-backed cryptocurrency supported by a Stablecoin Partner, which may be updated from time to time as the Partner Terms and the Documentation state. A Stablecoin Partner is an entity, which may be a Stripe Affiliate or a third party, that provides Stablecoin-related services to the User, including exchange, custody, transmission or payout, under the Stablecoin Partner Terms. The Stablecoin Partner Terms govern the Partner's provision of services and the User's access to them, and may be updated from time to time. The Treasury Services themselves do not cover Stablecoin.
Supporting quotations
“Stablecoin” means any fiat-backed cryptocurrency supported by a Stablecoin Partner, which may be updated from time to time as stated in the applicable Stablecoin Partner Terms and the Documentation.
“Stablecoin Partner” means an entity, which may be a Stripe Affiliate or a third party, that provides Stablecoin-related services to User, including the exchange, custody, transmission, or payout of Stablecoin, under the applicable Stablecoin Partner Terms.
“Stablecoin Partner Terms” means the terms that govern the Stablecoin Partner's provision, and User's access to and use of, the Stablecoin Partner Services, and which may be updated from time to time.
Qualifications & exceptions
The supported Stablecoins and the Partner Terms can change over time.
Not stated here
The Partner Terms are not part of this text.
Legal Rights & Agreement Rules · Context
Regional Terms apply for the listed countries and prevail over the Treasury Terms; the first listed is the United States
The Regional Terms apply for the countries listed below them, and if they conflict with the Stripe Treasury Terms the Regional Terms prevail. The first listed country is the United States, and its Regional Terms apply for Users in the United States.
Supporting quotations
11. Regional Terms.
The following Regional Terms apply for the countries below. If there is a conflict between the Stripe Treasury Terms and the Regional Terms, the Regional Terms prevail.
United States.
The following Regional Terms apply for Users in the United States.
Qualifications & exceptions
The Regional Terms win in a conflict.
Charges & Financial Obligations · Company practice
United States: Treasury includes money transmission by RSP, a licensed transmitter, meaning Stripe Payments Company
For US Users, the Stripe Treasury Services include money transmission services provided by RSP, which is a licensed money transmitter and registered money services business as defined under the Financial Account Regulatory Requirements. Each reference to RSP in the Treasury Terms means Stripe Payments Company.
Supporting quotations
11.1 Regulated Services.
Stripe Treasury Services include money transmission services provided by RSP, and RSP is a licensed money transmitter and registered money services business, as defined under the Financial Account Regulatory Requirements. Each reference to “RSP” in these Stripe Treasury Terms means Stripe Payments Company.
Qualifications & exceptions
Applies to Users in the United States.
Charges & Financial Obligations · Company practice
United States: RSP holds your funds in a Custodial Account, you earn no interest unless Stripe says so
RSP will hold the funds shown in a Financial Account in a Custodial Account and will control those funds. Section 3.1 (Holding of Funds) of the Stripe Financial Services Terms, and any similar section, does not apply to funds eligible for pass-through FDIC Insurance held in the Custodial Accounts, and Stripe has no rights to any interest earned on funds held in them. Unless Stripe advises otherwise, the User will not earn interest on funds in its Financial Account. A Custodial Account is a custodial account RSP maintains in its own name at the Treasury Bank for the benefit of all accountholders.
Supporting quotations
11.2 Custodial Account; FDIC Insurance.
RSP will hold the funds represented in a Financial Account in a Custodial Account and will have control over those funds. Section 3.1 (Holding of Funds) of the Stripe Financial Services Terms and any similar section in the Agreement will not apply to funds that are eligible for pass-through FDIC Insurance and are held in the Custodial Accounts, and Stripe has no rights to any interest earned on funds held in those accounts. Unless Stripe advises User otherwise, User will not earn interest on funds in User’s Financial Account.
“Custodial Account” means a custodial account that RSP maintains, in its name, at the Treasury Bank, for the benefit of all accountholders using the Stripe Treasury Services.
Qualifications & exceptions
Section 3.1 is disapplied only for funds eligible for pass-through FDIC Insurance in the Custodial Accounts.
The User earns no interest unless Stripe advises otherwise.
Charges & Financial Obligations · Company commitment
United States: USD funds are expected to be eligible for pass-through FDIC Insurance, with conditions and limits
Funds held in USD in a Custodial Account, other than an Insurance Ineligible Custodial Account, are expected to be eligible for pass-through FDIC Insurance up to the then-current per depositor limit. Coverage depends on determinations the FDIC makes when the Treasury Bank goes into receivership or other insolvency. The per depositor limit applies to the total of all funds the User has on deposit with the relevant Treasury Bank as beneficial owner, including other accounts there. Insurance applies only to funds that have settled in a Financial Account, not to provisionally credited or pending funds. Stripe may earn a fee from the Treasury Bank in connection with the services. FDIC Insurance is deposit insurance covering certain accounts at FDIC-insured banks, and Insurance Ineligible Custodial Accounts are those the Documentation specifies as not eligible.
Supporting quotations
Funds held in USD in a Custodial Account (other than an Insurance Ineligible Custodial Account) are expected to be eligible for pass-through FDIC Insurance, up to the then-current per depositor limit. FDIC Insurance coverage is contingent on determinations FDIC makes at the time the Treasury Bank goes into receivership or other form of insolvency. The FDIC Insurance per depositor limit applies to the aggregate of all funds that User has on deposit with the relevant Treasury Bank as beneficial owner, including all funds in another account with the Treasury Bank. FDIC Insurance applies only to funds that have settled in a Financial Account and does not apply to funds that are provisionally credited to a Financial Account or that are pending but not yet settled. Stripe may earn a fee from the Treasury Bank in connection with the Stripe Treasury Services.
“FDIC” means Federal Deposit Insurance Corporation.
“FDIC Insurance” means deposit insurance that covers certain types of accounts at FDIC-insured banks.
“Insurance Ineligible Custodial Account” means the Custodial Accounts specified in the Documentation as not eligible for pass-through FDIC insurance.
Qualifications & exceptions
Eligibility is an expectation, not a guarantee.
Coverage depends on FDIC determinations at the time of insolvency.
The per depositor limit counts all the User's funds at the same Treasury Bank.
Pending or provisionally credited funds are not covered.
Not stated here
The list of Insurance Ineligible Custodial Accounts is in the Documentation, which is not supplied.
Charges & Financial Obligations · Restriction or exception
United States: you are the Originator of your ACH Entries and must get consents and keep data secure, or risk suspension
Under the Nacha Operating Rules, the User is the Originator of the Entries it originates through its Financial Account. It must (a) get the consent of each payor and payee, in line with the Nacha Operating Rules, before originating an Entry over the ACH Network to debit or credit their account, and (b) keep secure the integrity of all information it collects in making an Entry. RSP may suspend the User's access to the ACH Network if an Entry the User originates leads to a dispute or an unauthorized Financial Account Transaction.
Supporting quotations
11.3 ACH Access.
(a) Origination. Under the Nacha Operating Rules, User is the Originator of the Entries User originates via User’s Financial Account. User must (a) obtain the consent of each of User’s payors and payees in compliance with the Nacha Operating Rules before originating an Entry over the ACH Network to debit or credit their account; and (b) maintain the security and integrity of all information User collects in the course of making an Entry. RSP may suspend User’s access to the ACH Network if User originates an Entry that results in a dispute or unauthorized Financial Account Transaction.
“Nacha Operating Rules” means the rules Nacha publishes that govern automated clearing house transactions on the ACH Network, located at [www.nachaoperatingrulesonline.org](http://www.nachaoperatingrulesonline.org).
Qualifications & exceptions
Suspension of ACH access can follow an Entry that results in a dispute or unauthorized transaction.
Not stated here
The Nacha Operating Rules are published externally and are not supplied here.
Charges & Financial Obligations · Restriction or exception
United States: ACH credit Entries follow New York law and are provisional; no Nested Third Party Sender role
The User's rights and obligations for any credit Entry sent over the ACH Network are governed by New York law. Credit the recipient's financial institution gives for a credit Entry is provisional until that institution has received final settlement through a Federal Reserve Bank or otherwise received payment under Section 4A-403(a) of Article 4A of the New York Uniform Commercial Code. If it does not receive payment, it may take a refund from the recipient, and the User will not be considered to have paid the credit Entry to the recipient. The User must not originate Entries as a Nested Third Party Sender, as defined in the Nacha Operating Rules, through its Financial Account.
Supporting quotations
(b) Credit Entries. User’s rights and obligations concerning any credit Entry transmitted via the ACH Network are governed by, and construed in accordance with, the laws of the State of New York. Credit given to the recipient by the recipient’s financial institution for any such credit Entry will be provisional until the recipient’s financial institution has received final settlement through a Federal Reserve Bank or otherwise has received payment as provided for in Section 4A-403(a) of Article 4A of the Uniform Commercial Code as enacted in the State of New York. If the recipient’s financial institution does not receive such payment for the credit Entry, the recipient’s financial institution is entitled to a refund from the recipient in the amount of the credit to the recipient’s account, and User will not be considered to have paid the amount of the credit Entry to the recipient. User must not originate Entries as a Nested Third Party Sender (as defined in the Nacha Operating Rules) through User’s Financial Account.
Qualifications & exceptions
Credit to the recipient is provisional until final settlement.
Not stated here
Article 4A of the UCC and the Nacha definition of Nested Third Party Sender are external and not supplied here.
Legal Rights & Agreement Rules · Restriction or exception
United States: you represent and warrant that you do not lend funds or deliver property for ERISA or IRS Code plans
The User represents on the date it first uses the Treasury Services, and warrants at all times during use, that it does not lend funds to its Financial Account or otherwise deliver property to Stripe on behalf of (a) an “employee benefit plan” under Section 3(3) of ERISA; (b) a “plan” under Section 4975(e)(1) of the IRS Code; (c) an entity whose assets are “plan assets” subject to Title I of ERISA or Section 4974 of the IRS Code, by reason of Section 3(42) of ERISA, U.S. Department of Labor Regulation 29 C.F.R. Section 25.10.3-101 or otherwise; or (d) a “governmental plan”, or another plan (or an entity whose assets are considered to include the assets of one) subject to any Law or restriction substantively similar to Section 406 of ERISA or Section 4975 of the IRS Code. ERISA is the Employee Retirement Income Security Act of 1974 and the IRS Code is the Internal Revenue Code. The statute citations are given as written in the source and are not resolved here.
Supporting quotations
11.4 Compliance with ERISA.
User represents on the date User first uses the Stripe Treasury Services, and warrants at all times during User’s use of the Stripe Treasury Services, that User does not lend funds to User’s Financial Account or otherwise deliver property to Stripe on behalf of:
(a) an “employee benefit plan” within the meaning of Section 3(3) of ERISA;
(b) a “plan” within the meaning of Section 4975(e)(1) of the IRS Code;
(c) an entity whose underlying assets constitute “plan assets” subject to Title I of ERISA or Section 4974 of the IRS Code by reason of Section 3(42) of ERISA, U.S. Department of Labor Regulation 29 C.F.R. Section 25.10.3-101 or otherwise; or
(d) a “governmental plan” (as defined in ERISA or the IRS Code) or another type of plan (or an entity whose assets are considered to include the assets of a governmental plan or other plan) that is subject to any Law or restriction that is substantively similar or of similar effect to Section 406 of ERISA or Section 4975 of the IRS Code.
“ERISA” means the Employee Retirement Income Security Act of 1974, 29 U.S.C. Chapt. 18.
“IRS Code” means Internal Revenue Code, 26 U.S.C. Title 26.
Qualifications & exceptions
The warranty applies at all times during use of the services.
The legal citations are reported as written in the source.
Not stated here
The cited ERISA and IRS Code provisions are not supplied.
Charges & Financial Obligations · Restriction or exception
United States: RSP may rely on the routing and account number you give, even if it names a different person
RSP and anyone else involved in a Financial Account Transaction may rely on the routing number and account number the User gives in a transfer instruction. If the instruction names a different person from the account owner identified by the number, RSP and anyone else handling it may still rely exclusively on the number.
Supporting quotations
11.5 Account Numbers.
RSP and any other person involved in the Financial Account Transaction may rely on the routing number and account number that User provides when giving a transfer instruction. If the transfer instruction identifies a different person from the account owner identified by the number, RSP and any other person that handles the instruction may still rely exclusively on the number.
Qualifications & exceptions
Reliance on the number is exclusive even where the named person differs.
Charges & Financial Obligations · Context
United States definitions: Insurance Ineligible Custodial Account and User Territory
For the United States, an Insurance Ineligible Custodial Account is one of the Custodial Accounts the Documentation specifies as not eligible for pass-through FDIC insurance. The User Territory means the United States and its territories and protectorates, excluding the Northern Mariana Islands, US Virgin Islands and Guam.
Supporting quotations
11.6. Definitions.
“Insurance Ineligible Custodial Account” means the Custodial Accounts specified in the Documentation as not eligible for pass-through FDIC insurance.
“User Territory” means the United States and its territories and protectorates (excluding the Northern Mariana Islands, US Virgin Islands, and Guam).
Qualifications & exceptions
The User Territory excludes three named territories.
Not stated here
The Documentation's list of ineligible Custodial Accounts is not supplied.
Charges & Financial Obligations · Restriction or exception
United Kingdom: you must report errors and unauthorized transactions immediately and no later than 13 months
The Regional Terms apply for Users in the United Kingdom. For them, Section 2.2(c) (Errors) is replaced: if the User believes there is an error in a Financial Account Transaction, or that an unauthorized one has occurred, it must notify Stripe and give all information Stripe requests immediately and without undue delay, and no later than 13 months from the date the transaction appears on its Financial Account. The base clause required only prompt notice and gave no outer limit.
Supporting quotations
United Kingdom.
The following Regional Terms apply for Users in the United Kingdom.
11.1 Modifications.
(a) Section 2.2(c) (Errors) is replaced with the following clause: “If User believes that there is an error in a Financial Account Transaction, or an unauthorized Financial Account Transaction has occurred, User must notify Stripe and provide all information requested by Stripe immediately and without undue delay, and no later than 13 months from the date that Financial Account Transaction appears on User’s Financial Account.”
Qualifications & exceptions
Applies to Users in the United Kingdom.
The 13 months run from the date the transaction appears on the account.
Charges & Financial Obligations · Permission or license
United Kingdom: Stripe PSP may hold a settled transaction's amount while a forgery or improper-payment claim is resolved
For UK Users, Section 3.3(b) (Transaction Hold) is replaced: if, after final settlement of a Financial Account Transaction, the User or a third party claims it was altered, contained a forged or unauthorized signature or endorsement, or was not properly payable for any reason, Stripe PSP may place a Transaction Hold for the amount of that transaction on the User's Financial Account until the claim is finally investigated and resolved. A Transaction Hold is a restriction on the availability of funds or on the User's ability to transact that Stripe places because of delayed funds availability, Legal Process or other circumstances it determines in its sole discretion.
Supporting quotations
(b) Section 3.3(b) (Transaction Hold) is replaced with the following clause: “If after final settlement of any Financial Account Transaction, User or any third party asserts a claim alleging that the Financial Account Transaction was altered, contained a forged or unauthorized signature or endorsement, or was not properly payable for any reason, then Stripe PSP may place a Transaction Hold for the amount of the Financial Account Transaction from User’s Financial Account until the claim is finally investigated and resolved.”
“Transaction Hold” means a restriction on the availability of funds in a Financial Account or on User’s ability to effect a Financial Account Transaction that Stripe places as a result of delayed funds availability, Legal Process, or other circumstances as determined by Stripe in its sole discretion.
Qualifications & exceptions
The hold lasts until the claim is finally investigated and resolved.
Not stated here
No time limit for the investigation is stated.
Charges & Financial Obligations · Company practice
United Kingdom: once made, an Outbound Transaction is a redemption of E-money at par with its value
For UK Users, Section 3.4 (Outbound Transaction Initiation) gets an added closing clause: once the Outbound Transaction is made, this results in a redemption of E-money on par with the value of that Outbound Transaction. An Outbound Transaction is an Outbound Payment, Outbound Transfer or other fiat entry that subtracts from the Available Balance and that Stripe may permit in its sole discretion.
Supporting quotations
(c) Section 3.4 (Outbound Transaction Initiation) is modified by adding the following clause to the end of Section 3.4: “Once the Outbound Transaction is made, this will result in a redemption of E-money on par with the value of that Outbound Transaction.”
“Outbound Transaction” means an Outbound Payment, Outbound Transfer, or any other fiat currency entry or transaction that subtracts from the Available Balance that Stripe may permit from time to time in its sole discretion.
Qualifications & exceptions
Applies to Users in the United Kingdom.
Charges & Financial Obligations · Company practice
United Kingdom: your Financial Account is an E-money account issued by Stripe PSP, and RSP means Stripe Payments UK Ltd
For UK Users, the Financial Account is an E-money account, Stripe PSP issues the E-money held in it, and each reference to RSP in the Treasury Terms means Stripe Payments UK Ltd. E-money here means electronic money as defined in the Electronic Money Regulations 2011 (SI 2011/99), as the E-money Services section of the document sets out.
Supporting quotations
11.2. E-Money Issuer.
User’s Financial Account is an E-money account. Stripe PSP is the issuer of the E-money held in User’s Financial Account. Each reference to “RSP” in these Stripe Treasury Terms means Stripe Payments UK Ltd.
Depending on User’s location and, if applicable, User’s Connected Accounts’ locations, Stripe may offer E-money Services to User. “E-money” means electronic money as defined in the Electronic Money Regulations 2011 (SI 2011/99). The terms in this section only apply if Stripe provides E-money Services to User. User may use the Services to purchase E-money from Stripe, to send and receive E-money, and, if applicable, to transfer E-money to and from Connected Accounts. User will not receive any earnings from E-money that Stripe issues or holds. As the provider of Regulated Financial Services, Stripe PSP will be the only Stripe party liable to User for issuing, redeeming and transferring E-Money. If Stripe PSP issues E-money to User, Stripe PSP will safeguard funds received from User in exchange for that E-money according to Law. User may use the Stripe Technology to redeem E-money Stripe PSP holds for User for par value.
Qualifications & exceptions
Applies to Users in the United Kingdom.
Not stated here
The Electronic Money Regulations 2011 are external and not supplied.
Charges & Financial Obligations · User right or choice
United Kingdom: Stripe reimburses unauthorized transactions, but you bear the first £35 if you should have been aware
For UK Users, Stripe will reimburse the User for any unauthorized Financial Account Transaction where Stripe determines the User did not authorize the underlying transaction, except that the User is liable for the first £35 of any unauthorized transaction where Stripe reasonably believes the User should have been aware of the unauthorized use.
Supporting quotations
11.3 Transaction Management.
(a) Liability for Unauthorized Transactions. Stripe will reimburse User for any unauthorized Financial Account Transaction where Stripe determines that User has not authorized the underlying Financial Account Transaction, provided that User will be liable for the first £35 of any unauthorized Financial Account Transaction where Stripe reasonably believes User should have been aware of the unauthorized use.
Qualifications & exceptions
Reimbursement depends on Stripe's determination that the User did not authorize the transaction.
The £35 share applies only where Stripe reasonably believes the User should have been aware.
Charges & Financial Obligations · Restriction or exception
United Kingdom: no reimbursement if you misused the account, were grossly negligent, left it insecure or did not report
Stripe is not liable for an unauthorized transaction where (a) the User used a Financial Account for an Unauthorized Purpose or with intent or gross negligence, or failed to use it in line with the Treasury Terms, including by not taking all reasonable steps to keep account credentials and the devices it uses secure and confidential at all times; or (b) the User failed to notify Stripe of the unauthorized use immediately. An Unauthorized Purpose is a fraudulent or illegal purpose, a consumer, personal or household purpose, or any purpose unrelated to the Treasury Services.
Supporting quotations
However, Stripe will not be liable for any unauthorized transaction where (a) User used a Financial Account for an Unauthorized Purpose or with intent or gross negligence, failed to use the Financial Account in accordance with these Stripe Treasury Terms, including to take all reasonable steps to keep account credentials and the devices on which User accesses User’s Financial Account secure and confidential at all times; or (b) User failed to immediately notify Stripe of the unauthorized use.
“Unauthorized Purpose” means (a) a fraudulent or illegal purpose; (b) a consumer, personal, or household purpose; and (c) any purpose unrelated to the Stripe Treasury Services.
Qualifications & exceptions
Either ground (a) or (b) removes Stripe's liability.
Consumer, personal or household use counts as an Unauthorized Purpose.
Charges & Financial Obligations · Permission or license
United Kingdom: Stripe may recoup a reimbursement if the transaction proves duly authorized and correctly executed
If Stripe reimburses the User for an unauthorized or incorrectly executed Financial Account Transaction and later determines it was duly authorized and correctly executed, Stripe may recoup or set off an amount equal to the reimbursement from the User's Financial Account.
Supporting quotations
If Stripe reimburses User for an unauthorized or incorrectly executed Financial Account Transaction and subsequently determines that the relevant Financial Account Transaction was duly authorized and correctly executed, Stripe may recoup or set off an amount equal to that reimbursed amount from User’s Financial Account.
Qualifications & exceptions
Applies after Stripe determines the transaction was authorized and correctly executed.
Charges & Financial Obligations · User right or choice
United Kingdom: Stripe reimburses authorized push payment scams as regulations require, and you must report them at once
Stripe will reimburse the User for relevant Financial Account Transactions as and when required to comply with the Financial Account Regulatory Requirements on authorized push payment scams. If the User believes it has been the subject of such a scam, it must report the transactions immediately through the Stripe Dashboard.
Supporting quotations
(b) Reimbursements of Authorized Push Payments. Stripe will reimburse User for relevant Financial Account Transactions as and when required to comply with the Financial Account Regulatory Requirements relating to authorized push payment scams. If User believes that User has been subject to an authorized push payment scam, User must immediately report any such Financial Account Transactions through the Stripe Dashboard.
Qualifications & exceptions
Reimbursement is as and when the Regulatory Requirements require.
Reporting must be immediate and through the Stripe Dashboard.
Not stated here
The Regulatory Requirements that set the amounts and conditions are not supplied.
Charges & Financial Obligations · Context
United Kingdom definitions: Unauthorized Purpose and User Territory (the United Kingdom)
An Unauthorized Purpose is a fraudulent or illegal purpose, a consumer, personal or household purpose, or any purpose unrelated to the Stripe Treasury Services. For UK Users, the User Territory means the United Kingdom.
Supporting quotations
11.4 Definitions.
“Unauthorized Purpose” means (a) a fraudulent or illegal purpose; (b) a consumer, personal, or household purpose; and (c) any purpose unrelated to the Stripe Treasury Services.
“User Territory” means the United Kingdom.
Qualifications & exceptions
An Unauthorized Purpose includes consumer, personal or household purposes.
Charges & Financial Obligations · Context
Treasury for Platforms Accountholder Terms add to three other term sets (last modified September 28, 2026)
These Stripe Treasury for Platforms Accountholder Terms, last modified September 28, 2026, supplement the General Terms and, together with the Stripe Financial Services Terms and the Stripe Treasury Terms, which they incorporate by reference, govern the use of the Treasury for Platforms Services as a Treasury for Platforms Accountholder. If the User is a Stripe Connect Platform using the services for its own business purposes, the terms apply to it as an Accountholder and references to the Stripe Connect Platform also refer to the User. A Treasury for Platforms Accountholder is a Connected Account, or a Connect Platform using the services for its own business purpose, that has completed the onboarding requirements.
Supporting quotations
Last modified: September 28, 2026
These terms (“Stripe Treasury for Platforms Accountholder Terms”) supplement the General Terms, and together with the Stripe Financial Services Terms and the Stripe Treasury Terms, each of which are incorporated into these terms by this reference, govern the use of the Stripe Treasury for Platforms Services as a Stripe Treasury for Platforms Accountholder. Capitalized terms that are not defined in these terms have the same meanings given to them in the General Terms, the Stripe Financial Services Terms, or the Stripe Treasury Terms. If User is a Stripe Connect Platform using the Stripe Treasury for Platforms Services for User’s own business purposes, these Stripe Treasury for Platforms Accountholder Terms apply to User as a Stripe Treasury for Platforms Accountholder, and references to “Stripe Connect Platform” in these terms are also references to User.
“Stripe Treasury for Platforms Accountholder” means a Connected Account, or Stripe Connect Platform using the Stripe Treasury for Platforms Services for User’s own business purpose, who has successfully completed the onboarding requirements in the Stripe Treasury for Platforms Dashboard.
Qualifications & exceptions
A Connect Platform using the services for its own business is treated as an Accountholder.
Not stated here
The onboarding requirements are in the part of the definition not shown in this section.
Legal Rights & Agreement Rules · Context
On a conflict these terms rank first, then the Treasury Terms, Financial Services Terms and General Terms
If a term in the Accountholder Terms conflicts with a term incorporated into them, then unless a lower-ranking term expressly says otherwise, the order of precedence is (a) the Accountholder Terms, (b) the Stripe Treasury Terms, (c) the Stripe Financial Services Terms and (d) the General Terms.
Supporting quotations
1.2 Order of Precedence.
If any term in these Stripe Treasury for Platforms Accountholder Terms conflicts with a term or terms incorporated by reference into these terms, then unless terms of lower precedence expressly state to the contrary, the order of precedence is: (a) these Stripe Treasury for Platforms Accountholder Terms; (b) the Stripe Treasury Terms; (c) the Stripe Financial Services Terms; and (d) the General Terms.
Qualifications & exceptions
A lower-ranking term can win only if it expressly says so.
Charges & Financial Obligations · Restriction or exception
Treasury for Platforms is money transmission; you must reside in its Territory and may fund and transfer by ACH or wire
The Treasury for Platforms Services are money transmission services, and RSP is a licensed money transmitter and registered money services business as defined under the Financial Accounts Regulatory Requirements. The User must reside in the Treasury for Platforms Territory (the United States and Puerto Rico, or other jurisdictions Stripe permits as the Documentation describes) to use them. The User's Stripe Connect Platform provides access, if applicable. Subject to those requirements, the User and its Authorized Users can (a) add funds to the Financial Account by ACH, wire transfer and other supported funding methods and (b) transfer funds out to any account that can receive ACH or wire transfers at any financial institution. The services let an Accountholder create and maintain a Financial Account in which it can store, spend and manage funds.
Supporting quotations
2. Use of the Stripe Treasury for Platforms Services.
2.1 Scope.
Stripe Treasury for Platforms Services are money transmission services, and RSP is a licensed money transmitter and registered money services business, as defined under the Financial Accounts Regulatory Requirements. User must reside in the Stripe Treasury for Platforms Territory to use the Stripe Treasury for Platforms Services. User’s Stripe Connect Platform will provide User access to the Stripe Treasury for Platforms Services (if applicable). Subject to the Financial Accounts Regulatory Requirements and these Stripe Treasury for Platforms Accountholder Terms, User and User’s Treasury for Platforms Authorized Users will be able to (a) add funds to User’s Financial Account via ACH, wire transfer, and other supported funding methods; and (b) transfer funds from User’s Financial Account to any account able to receive ACH or wire transfers at any financial institution.
“Stripe Treasury for Platforms Territory” means the United States and Puerto Rico, or such other jurisdictions Stripe permits, as further described in the Documentation.
“Stripe Treasury for Platforms Services” means the Services that enable a Treasury for Platforms Accountholder to create and maintain a Financial Account where the Treasury for Platforms Accountholder can (a) store, spend, and manage funds; and (b) make electronic payments and funds transfers to and from that account.
Qualifications & exceptions
Residence in the Territory is required.
Other jurisdictions apply only if Stripe permits them.
Not stated here
The Territory is described here for the US version; other versions have their own Territory definitions.
Account & Service Control · Restriction or exception
Your use may be subject to additional terms from your Stripe Connect Platform, provided when you request access
The User acknowledges that its use of the Treasury for Platforms Services may be subject to additional terms specific to its Stripe Connect Platform, which the platform will provide when the User requests access to the services.
Supporting quotations
2.2 Acknowledgment.
User acknowledges that User’s use of the Stripe Treasury for Platforms Services may be subject to additional terms specific to User’s Stripe Connect Platform, which User’s Stripe Connect Platform will provide at the time User requests access to the Stripe Treasury for Platforms Services.
Not stated here
The platform-specific terms are not part of this saved text.
Account & Service Control · Permission or license
You authorize RSP to act on your platform's instructions on your account, and must give it your users' details
The User authorizes RSP to accept instructions from its Stripe Connect Platform on Financial Account Transactions, to manage the Financial Account and to take other action on it. The User must give the platform all information about its Treasury for Platforms Authorized Users (individuals it authorizes to use the services), any agent appointed under a power of attorney, and the electronic credentials such as logins for its Financial Account, and must immediately give updated information if it changes.
Supporting quotations
3. Treasury for Platforms Authorized Users.
3.1 Instructions from Stripe Connect Platform.
User authorizes RSP to accept instructions from User’s Stripe Connect Platform with respect to Financial Account Transactions, manage User’s Financial Account and take other action on User’s Financial Account. User must provide User’s Stripe Connect Platform with all information regarding User’s Treasury for Platforms Authorized Users, any agent appointed under an applicable power of attorney, and the electronic credentials (such as logins) for User’s Financial Account, and User must immediately provide User’s Stripe Connect Platform with updated information if that information changes.
"Treasury for Platforms Authorized User" means an individual that a Stripe Treasury for Platforms Accountholder authorizes to use the Stripe Treasury for Platforms Services.
Qualifications & exceptions
RSP acts on the platform's instructions, not only the User's.
Updates must be immediate.
Account & Service Control · Restriction or exception
You must give your platform at least 5 business days' notice before changing your form of ownership or Authorized Users
The User must notify its Stripe Connect Platform at least 5 business days before making any change to (a) its form of ownership, such as changing from a sole proprietor to a limited liability company or corporation, or (b) its Treasury for Platforms Authorized Users.
Supporting quotations
User must notify User’s Stripe Connect Platform at least 5 business days before making any change to (a) User’s form of ownership (such as changing from a sole proprietor to a limited liability company or corporation); or (b) User’s Treasury for Platforms Authorized Users.
Qualifications & exceptions
Notice is due at least 5 business days ahead of the change.
Account & Service Control · Restriction or exception
An agent under a power of attorney needs a form your platform and RSP accept, and they may rely on a copy
If the User appoints an agent under a power of attorney to manage the Financial Account, the power of attorney must be in a form acceptable to its Stripe Connect Platform and RSP. RSP and the platform may rely on a copy of the power of attorney and are not required to confirm its validity.
Supporting quotations
3.2 Agents.
If User chooses to appoint an agent under a power of attorney to manage the Financial Account, the power of attorney must be in a form acceptable to User’s Stripe Connect Platform and RSP. RSP and User’s Stripe Connect Platform may rely on a copy of the power of attorney and are not required to confirm its validity.
Qualifications & exceptions
The platform and RSP need not confirm the power of attorney is valid.
Account & Service Control · Permission or license
RSP may attach conditions such as a surety bond to platform instructions and refuse risky or doubtful ones
If RSP chooses to follow an instruction its Stripe Connect Platform sends for the User, RSP may impose any condition, including requiring a surety bond or an indemnity agreement in a form satisfactory to RSP. RSP may refuse an instruction from the platform if it believes (a) the instruction is fraudulent or the User did not authorize it; (b) there are multiple or conflicting instructions; (c) an Authorized User or agent is exceeding their authority; or (d) complying may expose RSP or its Affiliates to liability.
Supporting quotations
3.3 Instructions.
If RSP chooses to comply with an instruction that User’s Stripe Connect Platform transmits, RSP may impose any condition, including requiring that User provide RSP with a surety bond or put in place an indemnity agreement in a form that is satisfactory to RSP. RSP may refuse to comply with an instruction from User’s Stripe Connect Platform if RSP believes that:
(a) the instruction is fraudulent or User did not authorize it;
(b) there are multiple or conflicting instructions;
(c) User’s Treasury for Platforms Authorized User or agent is exceeding their authority in giving the instruction; or
(d) complying with the instruction may expose RSP or its Affiliates to liability.
Qualifications & exceptions
Refusal depends on RSP's belief.
RSP may attach any condition when it chooses to comply.
Charges & Financial Obligations · Company practice
RSP processes incoming transfers first, then outgoing ones, by Cut-Off Time; provisional credits may be reversed
RSP processes the User's Financial Account Transactions each business day in this order: first, transfers into the account that RSP receives from the User's Stripe Connect Platform before the Cut-Off Time, in the order received, with credited amounts provisional until the funds clear; second, transfers out (other transactions that deduct funds) that RSP receives by the Cut-Off Time, in the order received. Reversals of provisional credits may happen at any time during this process, and RSP may use a different order if the Financial Account Regulatory Requirements require. A Cut-Off Time is the time on a business day by which RSP must receive an instruction for same-day processing.
Supporting quotations
5.4 Processing Order.
RSP will process User’s Financial Account Transactions on each business day in the following order:
(a) first, transfers to User’s Financial Account that RSP receives from User’s Stripe Connect Platform before the Cut-Off Time will be processed in the order in which RSP receives them, but any amounts credited to User’s Financial Account are provisionally credited until those funds clear; and
(b) second, transfers from User’s Financial Account (e.g., other Financial Account Transactions resulting in deducting funds from User’s Financial Account) that RSP receives by the Cut-Off Time will be processed in the order in which RSP receives them.
Reversals of provisional credits may occur at any time during this process. RSP may use a different processing order if the Financial Account Regulatory Requirements require.
“Cut-Off Time” means the time on a business day by which RSP must receive an instruction or Financial Account Transaction request in order to process that instruction or request on the same day.
Qualifications & exceptions
Credits are provisional until funds clear.
A different order may be used if the regulatory requirements require it.
Charges & Financial Obligations · Restriction or exception
There is no overdraft feature; RSP may return a transaction or let it overdraw, and third-party penalties are yours
There is no overdraft feature for the Financial Account. If the Available Balance cannot cover a transaction in processing order, RSP may return or reject it, or may let it go ahead, in which case the account may become overdrawn. RSP does not charge a fee when it returns or rejects a transaction for insufficient funds. Third parties may charge fees or other charges, such as penalty interest, for dishonored or late payments, and the User is solely responsible for them.
Supporting quotations
5.5 No Overdraft Feature.
There is no overdraft feature associated with User’s Financial Account. If User’s Available Balance is not sufficient to pay for each Financial Account Transaction in the order in which it is processed, RSP may return or reject the Financial Account Transaction, or RSP may permit the Financial Account Transaction to proceed, in which case User’s Financial Account may become overdrawn. RSP does not impose a fee when it returns or rejects a Financial Account Transaction for which there are insufficient funds. However, third parties may impose a fee or other charge (such as penalty interest) for dishonored or late payments, and User is solely responsible for those fees and charges.
Qualifications & exceptions
RSP may allow a transaction to overdraw the account.
RSP charges no fee for returning a transaction for insufficient funds.
Charges & Financial Obligations · User right or choice
To stop a scheduled transfer, act in time for your platform to instruct RSP at least 3 business days ahead
To stop a scheduled or preauthorized transfer, the User must instruct its Stripe Connect Platform in time for the platform to instruct RSP at least 3 business days before the day the transaction is scheduled. If the User scheduled or preauthorized it through the Treasury for Platforms Dashboard, it may change or cancel it there at least 3 business days before the scheduled day.
Supporting quotations
5.6 User’s Right to Stop Payment.
If User wishes to stop any scheduled or preauthorized transfer from User’s Financial Account, then User must give User’s Stripe Connect Platform instructions to do so in time for the Stripe Connect Platform to instruct RSP at least 3 business days before the day on which the Financial Account Transaction is scheduled to be made. If User scheduled or preauthorized the transfer via the Stripe Treasury for Platforms Dashboard, then User may change or cancel the transfer via the Stripe Treasury for Platforms Dashboard at least 3 business days before the day on which the Financial Account Transaction is scheduled to be made.
Qualifications & exceptions
The cut-off is 3 business days before the scheduled day.
Charges & Financial Obligations · Permission or license
RSP may refuse a transaction for insufficient funds, unverified information, security or rule violations
To the extent the Regulatory Requirements do not prohibit it, RSP may refuse to complete any Financial Account Transaction, including (a) if the account has insufficient funds; (b) if RSP cannot verify ownership of, or other information about, the account or the person or entity funds are going to or coming from; (c) to protect the security of the account and RSP's systems; or (d) if the transaction would violate the Accountholder Terms or the Regulatory Requirements.
Supporting quotations
5.7 RSP's Right to Refuse.
To the extent the Financial Account Regulatory Requirements do not prohibit the actions listed in this Section, RSP may refuse to complete any Financial Account Transaction, including:
(a) if User’s Financial Account has insufficient funds to cover a Financial Account Transaction;
(b) if RSP is unable to verify ownership of or other information about User’s Financial Account, or the individual or entity to or from whom the funds will be transferred;
(c) to protect the security of User’s Financial Account and RSP’s systems; or
(d) if the Financial Account Transaction would violate these Stripe Treasury for Platforms Accountholder Terms or the Financial Account Regulatory Requirements.
Qualifications & exceptions
The list says “including”, so it is not exhaustive.
Subject to what the Regulatory Requirements permit.
Charges & Financial Obligations · Restriction or exception
Limits on the number and value of transactions apply, and RSP or your platform may change or reduce them without notice
There are limits on the number and value of Financial Account Transactions the User may make, described on the Treasury for Platforms Dashboard or otherwise disclosed by RSP or its Stripe Connect Platform. RSP may allow transactions that exceed the limits, or temporarily reduce the User's limits from time to time without notice unless the Regulatory Requirements require otherwise. RSP or the platform may change the limits at any time.
Supporting quotations
5.8 Financial Account Transaction Limitations.
There are limits on the number and value of Financial Account Transactions that User may make from User’s Financial Account, which are described on the Stripe Treasury for Platforms Dashboard or otherwise disclosed by RSP or User’s Stripe Connect Platform. RSP may allow Financial Account Transactions that exceed applicable limits, or temporarily reduce User’s limits from time to time without notice (unless the Financial Account Regulatory Requirements require otherwise). RSP or User’s Stripe Connect Platform may change the limits at any time.
Qualifications & exceptions
Temporary reductions need no notice unless the Regulatory Requirements require it.
Not stated here
The limits themselves are not stated here.
Charges & Financial Obligations · Restriction or exception
You must review transactions promptly and report errors within 30 days and unauthorized transactions within one day
The User must review its Financial Account history and each transaction as soon as possible. If it believes there is an error or discrepancy, it must tell its Stripe Connect Platform promptly and no later than 30 days after the platform makes the history available, or a longer period the Regulatory Requirements state. If it believes an unauthorized transaction has been made, it must tell the platform immediately and in any case within 1 day of becoming aware, and give a written statement with details if RSP or the platform asks. If it does not notify as required, or the platform does not notify RSP in time, losses from the unauthorized transaction may not be recoverable, or recovery may be slower or harder.
(a) Obligation to Review. User must review User’s Financial Account history and each Financial Account Transaction as soon as possible. If User believes that there is an error or discrepancy in a Financial Account Transaction, User must notify User’s Stripe Connect Platform promptly, and no later than 30 days after User’s Stripe Connect Platform makes the Financial Account history available to User (or, if applicable, a longer period stated in the Financial Account Regulatory Requirements). If User believes an unauthorized Financial Account Transaction has been made on User’s Financial Account, then User must immediately notify User’s Stripe Connect Platform, and in any case within 1 day after User becomes aware. If RSP or User’s Stripe Connect Platform requests, User must submit a written statement with details about the unauthorized Financial Account Transaction. If User fails to notify User’s Stripe Connect Platform as required under this Section, or User’s Stripe Connect Platform does not notify RSP in a timely manner, then losses, damages, or costs User suffers as a result of the unauthorized Financial Account Transaction may not be recoverable, or recovery may be more time consuming or difficult.
Qualifications & exceptions
Error reports are due within 30 days; unauthorized transactions within 1 day of awareness.
Late notice may make losses unrecoverable.
Legal Rights & Agreement Rules · Restriction or exception
You must help RSP and your platform investigate and prosecute claims about unauthorized transactions
The User must help RSP and its Stripe Connect Platform investigate, and prosecute related claims for, unauthorized Financial Account Transactions by completing the statements and reports RSP or the platform reasonably requests.
Supporting quotations
(b) Assistance in Investigations. User must assist RSP and User’s Stripe Connect Platform in the investigation and related prosecution of claims for unauthorized Financial Account Transactions by completing the appropriate statements and reports that RSP or User’s Stripe Connect Platform reasonably requests.
Qualifications & exceptions
Requests must be reasonable.
Charges & Financial Obligations · Permission or license
RSP may withhold a settled transaction's amount while a claim of alteration, forgery or improper payment is resolved
If, after final settlement of a Financial Account Transaction, the User or any third party tells the User's Stripe Connect Platform that the transaction was altered, contained a forged or unauthorized signature or endorsement, or was not properly payable for any reason, RSP may withhold the amount of the transaction from the User's Financial Account until the claim is finally investigated and resolved.
Supporting quotations
5.10 Withholding Financial Account Transactions.
If after final settlement of any Financial Account Transaction, User or any third party asserts a claim to User’s Stripe Connect Platform alleging that the Financial Account Transaction was altered, contained a forged or unauthorized signature or endorsement, or was not properly payable for any reason, then RSP may withhold the amount of the Financial Account Transaction from User’s Financial Account until the claim is finally investigated and resolved.
Qualifications & exceptions
The withholding lasts until the claim is finally investigated and resolved.
Not stated here
No time limit for the investigation is stated.
Charges & Financial Obligations · Restriction or exception
You are responsible for all transactions, authorized or not; Stripe Parties disclaim liability for failures and refusals
The User is responsible for all Financial Account Transactions on its account, whether or not authorized. To the maximum extent Law permits, the Stripe Parties are not liable to the User, its Affiliates or any third party for losses, damages or costs from (a) a failed transaction, including RSP refusing or declining one or a failure from circumstances outside RSP's control; (b) RSP or the User's platform completing a transaction or acting on incorrect or incomplete information; (c) RSP refusing to follow the platform's instructions under Section 3.3; or (d) any correspondent bank's negligence or failure, or funds lost in transit.
Supporting quotations
5.11 Liability Related to Financial Account Transactions.
User is responsible for all Financial Account Transactions on User’s Financial Account, whether or not they are authorized. To the maximum extent permitted by Law, the Stripe Parties will not be liable to User, User’s Affiliates, or any third party for any losses, damages, or costs arising out of or relating to:
(a) a failed Financial Account Transaction on User’s Financial Account, including if RSP decides to refuse to pay or decline any Financial Account Transaction or if a Financial Account Transaction fails due to circumstances outside of RSP’s control;
(b) RSP or User’s Stripe Connect Platform completing a Financial Account Transaction or otherwise acting in reliance upon any incorrect or incomplete information provided or made available to RSP or User’s Stripe Connect Platform;
(c) RSP’s refusal to comply with User’s Stripe Connect Platform’s instructions under Section 3.3 of these Stripe Treasury for Platforms Accountholder Terms; or
(d) any correspondent bank’s negligence or failure, or funds lost in transit.
Qualifications & exceptions
The disclaimer applies to the maximum extent Law permits.
Charges & Financial Obligations · Company practice
Your platform must disclose the fees that apply to you when you request access, and any changes before they take effect
The User's Stripe Connect Platform is responsible for telling the User all fees, if any, that apply to its use of the Treasury for Platforms Services. The platform will disclose them when the User requests access and will disclose any changes before they take effect.
Supporting quotations
6. Fees and Security.
6.1 Fee Disclosure.
User’s Stripe Connect Platform is responsible for disclosing to User all applicable fees (if any) that apply to User’s use of the Stripe Treasury for Platforms Services. User’s Stripe Connect Platform will disclose those fees at the time User requests access to the Stripe Treasury for Platforms Services and will disclose any changes before they take effect.
Qualifications & exceptions
Fees are disclosed by the platform, not set out in these terms.
Not stated here
The fee amounts are not in these terms.
Charges & Financial Obligations · Restriction or exception
You are liable to RSP for losses from disputes on your account, and RSP may deduct or set them off without prior notice
To the maximum extent Law permits, the User is liable to RSP for all losses, damages and costs RSP incurs from any dispute involving the User's Financial Account, including from relying on its Stripe Connect Platform's representations or instructions. The User authorizes RSP to (i) deduct those amounts from funds in the Financial Account or (ii) set them off under Section 6.3, with or without prior notice.
Supporting quotations
6.2 User’s Responsibility for Disputes.
To the maximum extent permitted by Law, User is liable to RSP for all losses, damages, and costs that RSP incurs as a result of any dispute involving User’s Financial Account, including as a result of relying on User’s Stripe Connect Platform’s representations or instructions. User authorizes RSP to (i) deduct these losses, damages, and costs from funds in User’s Financial Account; or (ii) set them off in accordance with Section 6.3 of these Stripe Treasury for Platforms Accountholder Terms with or without prior notice to User.
Qualifications & exceptions
Liability covers RSP's reliance on the platform's representations or instructions.
Deduction or set-off may happen without prior notice.
Charges & Financial Obligations · Permission or license
RSP may deduct, recoup or set off fees you owe even if it overdraws the account, or invoice them payable in 30 days
RSP may deduct, recoup or set off all fees the User owes it, if any, from funds in the Financial Account, even if this causes an overdraft. Alternatively, RSP may invoice the User for some or all of the fees monthly in arrears, and the User must pay within 30 days after the invoice date.
Supporting quotations
6.3 Setoff.
RSP may deduct, recoup or setoff all fees User owes RSP (if any) from funds in User’s Financial Account, even if this would cause an overdraft. Alternatively, RSP may invoice User for some or all of those fees on a monthly basis in arrears, and User must pay the fees within 30 days after the date of the invoice.
Qualifications & exceptions
Setoff may cause an overdraft.
Invoiced fees are payable within 30 days of the invoice date.
Account & Service Control · Company practice
After closure, RSP enables your platform to give you access to your account history for 60 days
After the User's Financial Account is closed, RSP will enable the User's Stripe Connect Platform to provide the User access to its Financial Account history for 60 days.
Supporting quotations
7. Closing User’s Financial Account.
7.1 Closing User’s Financial Account.
After User’s Financial Account is closed, RSP will enable User’s Stripe Connect Platform to provide User access to User’s Financial Account history for 60 days.
Qualifications & exceptions
Access is through the platform and lasts 60 days.
Legal Rights & Agreement Rules · Permission or license
RSP may refer conflicting instructions or disputes to a court, need not judge their merit, and may act without notice
If there are conflicting instructions about the User's Financial Account, or any dispute about it, then without limiting its other rights RSP may refer the conflict or dispute to a court for resolution. If anyone notifies RSP of a dispute, RSP does not need to decide whether it has merit before taking further action. RSP may exercise any of these rights without notice to the User.
Supporting quotations
7.2 Adverse Claims.
If there are conflicting instructions with respect to User’s Financial Account or if there is any dispute regarding User’s Financial Account, then without limiting RSP’s rights under these Stripe Treasury for Platforms Accountholder Terms, RSP may refer the conflict or dispute to a court for resolution. If any person notifies RSP of a dispute, RSP does not need to decide if the dispute has merit before RSP takes further action. RSP may exercise any of these rights without notice to User.
A Connected Account is a Platform User with a Stripe Account onboarded to a Stripe Connect Platform through the Stripe Connect Services, or a Payout Recipient. A Stripe Connect Platform is a platform provider that uses the Stripe Connect Services. The Stripe Connect Services are, for a Connect Platform, the Services that let it create, manage and enable Services for its Connected Accounts and let it or them use the Stripe Payments Services, and for a Connected Account, the Services described in the Connected Account Agreement. A Treasury for Platforms Accountholder is a Connected Account, or a Connect Platform using the services for its own business, that has completed onboarding in the Dashboard.
Supporting quotations
8. Definitions.
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
“Stripe Connect Platform” means a platform provider that uses the Stripe Connect Services.
“Stripe Connect Services" means (a) if User is a Stripe Connect Platform, the Services that allow User to (i) create, manage and enable Services for User’s Connected Accounts, as described in the Stripe Connect Infrastructure Terms; and (ii) enable User or User’s Connected Accounts to use the Stripe Payments Services, as described in the Stripe Connect Terms (if applicable); or (b) if User is a Connected Account, the Services described in the Connected Account Agreement.
“Stripe Treasury for Platforms Accountholder” means a Connected Account, or Stripe Connect Platform using the Stripe Treasury for Platforms Services for User’s own business purpose, who has successfully completed the onboarding requirements in the Stripe Treasury for Platforms Dashboard.
Not stated here
The Connected Account Agreement is a separate document and is not supplied.
Charges & Financial Obligations · Context
Definitions: Custodial Account, Cut-Off Time, Reversal, Account Information, Treasury for Platforms Services
A Custodial Account is a custodial account RSP maintains in its own name at the Treasury Bank for all accountholders using the Treasury Services. A Cut-Off Time is the time on a business day by which RSP must receive an instruction or request to process it the same day. A Reversal is the reversal of the settlement of funds for a Transaction. Treasury for Platforms Account Information is Personal Data or business information a Connect Platform provides for its Connected Accounts so Stripe and its Affiliates can check eligibility, make the services available to Accountholders, and meet their responsibilities to the Treasury Banks and electronic funds transfer networks the services use. The Treasury for Platforms Services let an Accountholder create and maintain a Financial Account where it can store, spend and manage funds and make electronic payments and transfers.
Supporting quotations
“Custodial Account” means a custodial account that RSP maintains, in its name, at the Treasury Bank, for the benefit of all accountholders using the Stripe Treasury Services.
“Cut-Off Time” means the time on a business day by which RSP must receive an instruction or Financial Account Transaction request in order to process that instruction or request on the same day.
“Reversal” means the reversal of the settlement of funds for a Transaction.
“Stripe Treasury for Platforms Account Information” means Personal Data or business information that a Stripe Connect Platform provides on behalf of its Connected Accounts to enable Stripe and its Affiliates to (a) determine the Connected Accounts’ eligibility to access the Stripe Treasury for Platforms Services; (b) make the Stripe Treasury for Platforms Services available to Stripe Treasury for Platforms Accountholders; and (c) fulfill their responsibilities to applicable Treasury Banks and electronic funds transfer networks that Stripe Treasury for Platforms Services use.
“Stripe Treasury for Platforms Services” means the Services that enable a Treasury for Platforms Accountholder to create and maintain a Financial Account where the Treasury for Platforms Accountholder can (a) store, spend, and manage funds; and (b) make electronic payments and funds transfers to and from that account.
Charges & Financial Obligations · Context
Definitions: Account Information, Dashboard, Services, Territory (US and Puerto Rico) and Authorized User
Treasury for Platforms Account Information is Personal Data or business information a Stripe Connect Platform provides for its Connected Accounts so Stripe and its Affiliates can (a) determine their eligibility for the services, (b) make the services available to Accountholders, and (c) meet their responsibilities to applicable Treasury Banks and electronic funds transfer networks. The Dashboard is a user interface Stripe or a Connect Platform provides for an Accountholder to manage its Financial Account. The Treasury for Platforms Services let an Accountholder create and maintain a Financial Account to store, spend and manage funds and make electronic payments and transfers. The Territory is the United States and Puerto Rico, or other jurisdictions Stripe permits as the Documentation describes. An Authorized User is an individual an Accountholder authorizes to use the services.
Supporting quotations
“Stripe Treasury for Platforms Account Information” means Personal Data or business information that a Stripe Connect Platform provides on behalf of its Connected Accounts to enable Stripe and its Affiliates to (a) determine the Connected Accounts’ eligibility to access the Stripe Treasury for Platforms Services; (b) make the Stripe Treasury for Platforms Services available to Stripe Treasury for Platforms Accountholders; and (c) fulfill their responsibilities to applicable Treasury Banks and electronic funds transfer networks that Stripe Treasury for Platforms Services use.
“Stripe Treasury for Platforms Dashboard” means a user interface that Stripe or a Stripe Connect Platform provides that enables a Stripe Treasury for Platforms Accountholder to manage its Financial Account.
“Stripe Treasury for Platforms Services” means the Services that enable a Treasury for Platforms Accountholder to create and maintain a Financial Account where the Treasury for Platforms Accountholder can (a) store, spend, and manage funds; and (b) make electronic payments and funds transfers to and from that account.
“Stripe Treasury for Platforms Territory” means the United States and Puerto Rico, or such other jurisdictions Stripe permits, as further described in the Documentation.
"Treasury for Platforms Authorized User" means an individual that a Stripe Treasury for Platforms Accountholder authorizes to use the Stripe Treasury for Platforms Services.
Qualifications & exceptions
The Territory can include other jurisdictions Stripe permits.
Not stated here
The Documentation that may add jurisdictions is not supplied.
Charges & Financial Obligations · Context
Platform Terms govern offering Treasury for Platforms to your Connected Accounts, not your own use
These Stripe Treasury for Platforms - Platform Terms, last modified September 28, 2026, supplement the General Terms, the Stripe Financial Services Terms and the Stripe Connect Infrastructure Terms, and govern the User's ability to offer the Treasury for Platforms Services to its Connected Accounts. They do not apply to the User's use of the services for its own business; for that, the Accountholder Terms apply to the User as an Accountholder, and references to the Stripe Connect Platform in them also refer to the User. Capitalized terms not defined here take their meaning from those three sets of terms.
Supporting quotations
Last modified: September 28, 2026
These terms (“Stripe Treasury for Platforms - Platform Terms”) supplement the General Terms, the Stripe Financial Services Terms, and the Stripe Connect Infrastructure Terms, and govern User’s ability to offer the Stripe Treasury for Platforms Services to its Connected Accounts. These Stripe Treasury for Platforms - Platform Terms do not apply to User’s use of the Stripe Treasury for Platforms Services for User’s own business purposes. If User wishes to use the Stripe Treasury for Platforms Services for those purposes, then the Stripe Treasury for Platforms Accountholder Terms will apply to User as a Stripe Treasury for Platforms Accountholder, except that references to “Stripe Connect Platform” in those terms are also references to User. Capitalized terms that are not defined in these Stripe Treasury for Platforms - Platform Terms have the same meanings given to them in the General Terms, the Stripe Financial Services Terms and the Stripe Connect Infrastructure Terms.
Qualifications & exceptions
The Platform Terms do not apply to the User's own business use.
Account & Service Control · Restriction or exception
You must not offer Treasury for Platforms to Connected Accounts outside the Territory or let them use it there
The User must not offer, market or otherwise make the Treasury for Platforms Services available to Connected Accounts outside the Treasury for Platforms Territory, and must make sure no Connected Account uses them outside it. The Territory is the United States and Puerto Rico, or other jurisdictions Stripe permits, as the Documentation describes.
Supporting quotations
2. Access to the Stripe Treasury for Platforms Services.
User must not offer, market or otherwise make the Stripe Treasury for Platforms Services available to Connected Accounts located outside of the Stripe Treasury for Platforms Territory. User must ensure that no Connected Account uses the Stripe Treasury for Platforms Services outside of the Stripe Treasury for Platforms Territory.
“Stripe Treasury for Platforms Territory” means the United States and Puerto Rico, or such other jurisdictions Stripe permits, as further described in the Documentation.
“Stripe Treasury for Platforms Services” means the Services that enable a Treasury for Platforms Accountholder to create and maintain a Financial Account where the Treasury for Platforms Accountholder can (a) store, spend, and manage funds; and (b) make electronic payments and funds transfers to and from that account.
Qualifications & exceptions
The Territory can include other jurisdictions Stripe permits.
Account & Service Control · Restriction or exception
You must make sure each Connected Account completes onboarding, and a Stripe Entity and the bank must approve it
The User must make sure each Connected Account that wants to use the Treasury for Platforms Services successfully completes the onboarding requirements in Section 3.3 (Information and Consent). A Stripe Entity and the applicable Treasury for Platforms Bank must both approve each Connected Account during onboarding before it uses the services. The Treasury for Platforms Bank is a bank through which a Stripe Entity holds Accountholder funds.
Supporting quotations
3. Onboarding Connected Accounts.
3.1 General Responsibility.
User must ensure that each Connected Account that wishes to access the Stripe Treasury for Platforms Services successfully completes the onboarding requirements described in Section 3.3 (Information and Consent).
3.2 Approval of Connected Account.
A Stripe Entity, as well as the applicable Treasury for Platforms Bank, must approve each Connected Account as part of the onboarding process before the Connected Account uses the Stripe Treasury for Platforms Services.
“Treasury for Platforms Bank” means a bank through which a Stripe Entity holds Treasury for Platforms Accountholder funds.
Qualifications & exceptions
Both a Stripe Entity and the bank must approve before use.
Data Access & Collection · Restriction or exception
You must submit, or ensure Connected Accounts submit, the information Stripe and the bank request to screen them
The User must submit, or make sure each Connected Account submits, all Treasury for Platforms Account Information that Stripe, its Affiliates and the applicable bank request to verify and screen the Connected Account's eligibility, and to confirm it is not engaged in a Prohibited or Restricted Business. Account Information is Personal Data or business information a Connect Platform provides for its Connected Accounts so Stripe can check eligibility, make the services available and meet its responsibilities to Treasury Banks and funds transfer networks.
Supporting quotations
3.3 Information and Consent.
User must:
(a) submit, or ensure that each Connected Account submits, all Stripe Treasury for Platforms Account Information that Stripe, its Affiliates and the applicable Treasury for Platforms Bank request to verify and screen the Connected Account’s eligibility to access the Stripe Treasury for Platforms Services, and confirm that the Connected Account is not engaging in a Prohibited or Restricted Business;
“Stripe Treasury for Platforms Account Information” means Personal Data or business information that a Stripe Connect Platform provides on behalf of its Connected Accounts to enable Stripe and its Affiliates to (a) determine the Connected Accounts’ eligibility to access the Stripe Treasury for Platforms Services; (b) make the Stripe Treasury for Platforms Services available to Stripe Treasury for Platforms Accountholders; and (c) fulfill their responsibilities to applicable Treasury Banks and electronic funds transfer networks that Stripe Treasury for Platforms Services use.
Qualifications & exceptions
The information requested is whatever Stripe, its Affiliates and the bank request.
Not stated here
The Prohibited or Restricted Business List is a separate document and is not supplied.
Account & Service Control · Restriction or exception
You must ensure Connected Accounts agree to the Accountholder Terms and Connected Account Agreement, and prove it
The User must make sure each Connected Account User that intends to onboard as an Accountholder agrees to the Treasury for Platforms Accountholder Terms and the Connected Account Agreement before accessing the services. On Stripe's request the User must give the proof Stripe requires that those terms are binding on the Connected Account. If Stripe believes the User's acceptance process does not create a binding agreement between Stripe and the Connected Account, the User must change that process as Stripe requires when it asks.
Supporting quotations
(b) ensure that each Connected Account User that intends to onboard as a Stripe Treasury for Platforms Accountholder agrees to the Stripe Treasury for Platforms Accountholder Terms and the Connected Account Agreement before accessing the Stripe Treasury for Platforms Services. At Stripe’s request, User must provide proof as Stripe requires that the Stripe Treasury for Platforms Accountholder Terms and the Connected Account Agreement are binding on the Connected Account. If Stripe believes that User’s existing acceptance process does not create a binding agreement between Stripe and the Connected Account, then, upon Stripe’s request, User must modify that process as Stripe requires;
Qualifications & exceptions
Agreement must come before the Connected Account accesses the services.
The duty to change the acceptance process arises on Stripe's belief and request.
Account & Service Control · Restriction or exception
You must tell Connected Accounts about approval, suspension and terms changes, and stop serving those who decline
The User must (c) tell each Connected Account if Stripe approves its access, and promptly tell a Connected Account that has become an Accountholder if Stripe suspends or ends its access; and (d) tell Accountholders of all changes to the Accountholder Terms and make sure they agree to them. If an Accountholder does not agree to the changed terms, the User must immediately stop making the services available to that Accountholder.
Supporting quotations
User must:
(c) notify each Connected Account if Stripe approves its access to the Stripe Treasury for Platforms Services, and promptly notify a Connected Account that becomes a Stripe Treasury for Platforms Accountholder if Stripe suspends or terminates its access to the Stripe Treasury for Platforms Services; and
(d) notify Stripe Treasury for Platforms Accountholders of all changes to the Stripe Treasury for Platforms Accountholder Terms and ensure that those Stripe Treasury for Platforms Accountholders agree to them. If any Stripe Treasury for Platforms Accountholder does not agree to the modified Stripe Treasury for Platforms Accountholder Terms, then User must immediately stop making the Stripe Treasury for Platforms Services available to that Stripe Treasury for Platforms Accountholder.
Qualifications & exceptions
Suspension and termination notices must be prompt.
Stopping service to a non-agreeing Accountholder must be immediate.
Account & Service Control · Restriction or exception
You must ensure Accountholders and their Authorized Users comply, help enforce the terms and apply changes
The User must make sure Accountholders, and their Treasury for Platforms Authorized Users, comply with the Accountholder Terms. On Stripe's request it must help enforce those terms against Accountholders and Authorized Users. It must also make sure Accountholders put in place and follow any changes to the Treasury for Platforms Services that Stripe tells it about.
Supporting quotations
4. Responsibility for Stripe Treasury for Platforms Accountholders.
4.1 Stripe Treasury for Platforms Accountholder Terms.
User must ensure that Stripe Treasury for Platforms Accountholders, along with their Treasury for Platforms Authorized Users, comply with the Stripe Treasury for Platforms Accountholder Terms. Upon Stripe’s request, User must assist with enforcing the Stripe Treasury for Platforms Accountholder Terms against Stripe Treasury for Platforms Accountholders and Treasury for Platforms Authorized Users. User must ensure that Stripe Treasury for Platforms Accountholders implement and comply with any changes to the Stripe Treasury for Platforms Services, which Stripe will communicate to User.
Qualifications & exceptions
Enforcement help is on Stripe's request.
Charges & Financial Obligations · Restriction or exception
You are responsible, and jointly and severally liable, for all Activity on your Connected Accounts
The User is responsible and liable to Stripe for all Activity on Connected Accounts in connection with the Treasury for Platforms Services, whether or not the User started it, including all Financial Account Transactions, related fines, and any use of the services prohibited by the Platform Terms, the Accountholder Terms or the Connected Account Agreement. The User and the relevant Connected Account are jointly and severally liable to Stripe for amounts the Connected Account owes it, and Stripe may collect them from the User. If Stripe decides the User's responsibility creates an unacceptable risk to Stripe, it may use its remedies in Section 8.2 (Stripe Remedies).
Supporting quotations
4.2 Responsibility for Activity.
User is responsible and liable to Stripe for all Activity on Connected Accounts in connection with the Stripe Treasury for Platforms Services, whether initiated by User or not, including all Financial Account Transactions, associated fines, and any use of the Stripe Treasury for Platforms Services in a manner prohibited under these Stripe Treasury for Platforms - Platform Terms, the Stripe Treasury for Platforms Accountholder Terms, or the Connected Account Agreement. User and the relevant Connected Account are jointly and severally liable to Stripe for amounts the Connected Account owes to Stripe, and Stripe may collect these amounts from User in accordance with this Agreement. If Stripe determines that User’s responsibility for Activity on Connected Accounts creates an unacceptable risk to Stripe, Stripe may exercise its remedies listed in Section 8.2 (Stripe Remedies).
Qualifications & exceptions
Liability applies whether or not the User initiated the Activity.
Joint and several liability means Stripe can collect the whole amount from the User.
Not stated here
Section 8.2 is a later section of these terms.
Account & Service Control · Restriction or exception
You must provide and maintain a Treasury for Platforms Dashboard for Accountholders
The User must provide and maintain a Stripe Treasury for Platforms Dashboard for its Accountholders to use.
Supporting quotations
5. Account Management and Support for Stripe Treasury for Platforms Accountholders.
5.1 Dashboard for Stripe Treasury for Platforms Accountholders.
User must provide and maintain a Stripe Treasury for Platforms Dashboard for use by Stripe Treasury for Platforms Accountholders.
Account & Service Control · Restriction or exception
You must promptly integrate with the Stripe API so Stripe can host onboarding
Promptly after Stripe says Stripe-hosted onboarding is available, the User must integrate with the Stripe API as the Documentation directs, in a way that lets (a) a Stripe Entity host onboarding of Accountholders and (b) the User or Stripe, at the User's option, be responsible for Accountholder account management and access to the services.
Supporting quotations
5.2 Integration with Stripe API.
Promptly after Stripe notifies User that Stripe-hosted onboarding is available, User must integrate with the Stripe API according to the Documentation in a way that allows (a) a Stripe Entity to host onboarding of Stripe Treasury for Platforms Accountholders; and (b) User or Stripe, at User’s option, to be responsible for providing Stripe Treasury for Platforms Accountholder account management and access to the Stripe Treasury for Platforms Services.
Qualifications & exceptions
The integration is due promptly after Stripe's notice.
Account & Service Control · Restriction or exception
If you run account management, you must pass Stripe's information on unchanged and pass accurate data back
If the User elects to be responsible for Accountholder account management and access to the services, it must pass on to Accountholders, without changes or deletions, all information Stripe and its Affiliates make available for that purpose. It must make sure all information it passes from Accountholders to Stripe and its Affiliates, including account balances, transaction history and customer service issues, is accurate and complete. It must also make sure Connected Account Data is passed to Stripe in the manner the Documentation prescribes. Connected Account Data is data about Connected Accounts and Activity, which may include Protected Data and Stripe Data.
Supporting quotations
5.3 Obligation to Pass On Information.
(a) If User elects to be responsible for providing Stripe Treasury for Platforms Accountholder account management and access to the Stripe Treasury for Platforms Services, then User must pass on to the Stripe Treasury for Platforms Accountholders, without changes or deletions, all information that Stripe and its Affiliates make available for User to pass on to them. User must ensure that all information, including account balances, transaction history and customer service issues, that User passes from the Stripe Treasury for Platforms Accountholders to Stripe and its Affiliates is accurate and complete.
(b) User must ensure that Connected Account Data is passed to Stripe in the manner prescribed in the Documentation.
“Connected Account Data” means data about Connected Accounts and Activity, which may include Protected Data and Stripe Data.
Qualifications & exceptions
Applies if the User elects to be responsible for account management and access.
Not stated here
The Documentation's prescribed manner is not supplied.
Charges & Financial Obligations · Restriction or exception
You must clearly tell each Accountholder your fees and whether they are Stripe passthrough fees
The User must clearly tell each Accountholder all fees, if any, that it charges for the Treasury for Platforms Services, and say whether or not those fees are passthrough fees from Stripe.
Supporting quotations
5.4 Communicating Fees.
User must clearly communicate to each Stripe Treasury for Platforms Accountholder all fees (if any) that User charges that are related to the Stripe Treasury for Platforms Services, and specify whether or not those fees are passthrough fees from Stripe.
Charges & Financial Obligations · Restriction or exception
Conversion rates follow the Documentation, and you must give Accountholders the required conversion information
If a requested Financial Account Transaction needs a currency conversion, the exchange rate is determined as the Documentation states. The User must give the Accountholder all required information about the conversion in line with the Documentation and the Financial Account Regulatory Requirements.
Supporting quotations
5.5 Currency Conversion.
If a requested Financial Account Transaction requires a currency conversion, then the exchange rate used for that conversion will be determined as stated in the Documentation. User must communicate to the Stripe Treasury for Platforms Accountholder all requisite/required information about the currency conversion in accordance with the Documentation and the Financial Account Regulatory Requirements.
Not stated here
The Documentation's rate and information rules are not supplied.
Account & Service Control · Restriction or exception
You must provide all support to Accountholders and Authorized Users per the Product Guidelines
The User must provide all support to Accountholders and Treasury for Platforms Authorized Users according to the Stripe Treasury for Platforms Product Guidelines. The Product Guidelines are all product design, marketing, compliance, reporting and other guidelines and requirements a Stripe Entity or the applicable bank establishes from time to time for the services.
Supporting quotations
5.6 Support.
User must provide all support to Stripe Treasury for Platforms Accountholders and Treasury for Platforms Authorized Users according to the Stripe Treasury for Platforms Product Guidelines.
“Stripe Treasury for Platforms Product Guidelines” means all product design, marketing, compliance, reporting and other guidelines and requirements established by a Stripe Entity or the applicable Treasury for Platforms Banks from time to time in connection with the Stripe Treasury for Platforms Services.
Qualifications & exceptions
The guidelines can be changed by Stripe or the bank from time to time.
Not stated here
The Product Guidelines are not supplied.
Legal Rights & Agreement Rules · Restriction or exception
You must offer the service and ensure access in line with regulatory requirements, and never cause a violation
The User must (a) make the services available to Accountholders in line with the Financial Account Regulatory Requirements, and (b) make sure Accountholders and Authorized Users access them in compliance with those requirements. It must not, and must make sure Accountholders and Authorized Users do not, take or fail to take any action that could cause a Stripe Entity or an applicable bank to violate any Financial Account Regulatory Requirement. The Requirements are Law and the rules of the electronic funds transfer networks the services use.
Supporting quotations
6. Compliance.
6.1 Generally.
User must (a) make the Stripe Treasury for Platforms Services available to Stripe Treasury for Platforms Accountholders according to the Financial Account Regulatory Requirements; and (b) ensure that Stripe Treasury for Platforms Accountholders and Treasury for Platforms Authorized Users access the Stripe Treasury for Platforms Services in compliance with the Financial Account Regulatory Requirements. User must not, and must ensure that Stripe Treasury for Platforms Accountholders and Treasury for Platforms Authorized Users do not take or fail to take any action that could cause a Stripe Entity or any applicable Treasury for Platforms Bank to violate any Financial Account Regulatory Requirement.
“Financial Account Regulatory Requirement” means Law and the rules of the electronic funds transfer networks the Stripe Treasury Services use.
Qualifications & exceptions
Covers failures to act as well as actions.
Legal Rights & Agreement Rules · Restriction or exception
You must ensure Accountholders follow the Product Guidelines and run a compliance program
The User must (a) make sure each Accountholder complies with all Product Guidelines, and (b) set up, keep and act under a compliance program that lets and ensures each Accountholder comply with the Financial Account Regulatory Requirements and the Product Guidelines.
Supporting quotations
6.2 Stripe Treasury for Platforms Product Guidelines.
User must (a) ensure that each Stripe Treasury for Platforms Accountholder complies with all Stripe Treasury for Platforms Product Guidelines; and (b) establish, maintain, and act according to a compliance program that will enable and ensure each Stripe Treasury for Platforms Accountholder complies with the Financial Account Regulatory Requirements and the Stripe Treasury for Platforms Product Guidelines.
Not stated here
The terms do not describe the compliance program's required content.
Account & Service Control · Restriction or exception
You need Stripe's prior approval before distributing any marketing materials for the service
The User must not distribute or share any marketing materials about the Treasury for Platforms Services without Stripe's prior approval, and must submit all marketing materials to Stripe through a process Stripe tells it about.
Supporting quotations
6.3 Marketing.
User must not distribute or share any marketing materials relating to the Stripe Treasury for Platforms Services without Stripe’s prior approval. User must submit all marketing materials to Stripe using a process Stripe communicates to User.
Qualifications & exceptions
Approval must come before distribution.
Use & Processing · Restriction or exception
You must get the rights and consents, and give the disclosures, for Stripe and the bank to use Personal Data
The User must get all necessary rights and consents from each actual and prospective Accountholder and Authorized User to (a) provide Personal Data to Stripe and its Affiliates; (b) let them collect, use, retain and disclose it; and (c) let them exercise their rights and perform their obligations under the Platform Terms and under Stripe's Privacy Policy and any Treasury for Platforms Bank's Privacy Policy. When onboarding Accountholders, the User must disclose that it may give Personal Data to Stripe, its Affiliates and the applicable banks, and that they may collect, use, retain and disclose it. A Treasury for Platforms Bank is a bank through which a Stripe Entity holds Accountholder funds.
Supporting quotations
6.4 Stripe Treasury for Platforms Accountholder Consents.
User must obtain all necessary rights and consents from each actual and prospective Stripe Treasury for Platforms Accountholder and Treasury for Platforms Authorized User to (a) provide Personal Data to Stripe and its Affiliates; (b) allow Stripe and its Affiliates to collect, use, retain and disclose that Personal Data; and (c) allow Stripe and its Affiliates to exercise their rights and perform their obligations under these Stripe Treasury for Platforms - Platform Terms and according to Stripe’s Privacy Policy and any Treasury for Platforms Bank’s Privacy Policy (as applicable). User must, when onboarding Stripe Treasury for Platforms Accountholders, disclose to them that User may provide Personal Data to Stripe, its Affiliates, and applicable Treasury for Platforms Banks, and that Stripe, its Affiliates and applicable Treasury for Platforms Banks may collect, use, retain and disclose Personal Data.
"Treasury for Platforms Authorized User" means an individual that a Stripe Treasury for Platforms Accountholder authorizes to use the Stripe Treasury for Platforms Services.
“Treasury for Platforms Bank” means a bank through which a Stripe Entity holds Treasury for Platforms Accountholder funds.
Qualifications & exceptions
Covers prospective as well as actual Accountholders and Authorized Users.
Not stated here
The Privacy Policies are not supplied.
Legal Rights & Agreement Rules · Restriction or exception
You defend and indemnify the Stripe Parties for inaccurate information, Accountholder breaches and negative balances
The User will defend the Stripe Parties against any Claim, and indemnify them for all Stripe Losses, to the extent arising from (a) inaccurate or incomplete information given, including through the Dashboard, to a Stripe Entity or the applicable bank by or for the User or any Accountholder; (b) an Accountholder's breach of the Accountholder Terms; or (c) a negative balance or financial loss or damage caused by the User or an Accountholder.
Supporting quotations
7. Indemnification.
User will defend the Stripe Parties from and against any Claim, and indemnify the Stripe Parties against all Stripe Losses, to the extent arising out of or relating to (a) inaccurate or incomplete information provided (including through the Stripe Treasury for Platforms Dashboard) to a Stripe Entity or the applicable Treasury for Platforms Bank by or on behalf of User or any Stripe Treasury for Platforms Accountholder; (b) a Stripe Treasury for Platforms Accountholder’s breach of the Stripe Treasury for Platforms Accountholder Terms; or (c) a negative balance or financial loss or damage caused by User or a Stripe Treasury for Platforms Accountholder.
Qualifications & exceptions
Covers information given on behalf of the User or any Accountholder.
Includes a duty to defend as well as to indemnify.
Not stated here
Whether any cap applies is not stated in this clause.
Charges & Financial Obligations · Permission or license
You authorize Stripe to debit your bank or Stripe Accounts to cure an Accountholder's negative balance
The User authorizes Stripe to debit each User Bank Account or Stripe Account, at Stripe's discretion, to cure any negative balance of an Accountholder.
Supporting quotations
User authorizes Stripe to debit each User Bank Account or Stripe Account, at Stripe’s discretion, to cure any negative balance of a Stripe Treasury for Platforms Accountholder.
Qualifications & exceptions
Debiting is at Stripe's discretion.
Not stated here
The terms set no notice requirement before a debit.
Legal Rights & Agreement Rules · Permission or license
Stripe may use its remedies if a User Entity has a negative balance, insolvency, breach, fraud or unacceptable risk
Stripe may use the remedies in Section 8.2 if it determines that a User Entity (a) has a negative Financial Account balance; (b) is or is likely to become subject to an Insolvency Event; (c) has experienced or is likely to experience a deterioration in business or financial condition Stripe considers material; (d) has breached or is likely to breach, or is likely to cause Stripe to breach, the Agreement, another Stripe services agreement or applicable Provider Terms; (e) has violated or is likely to violate Financial Account Regulatory Requirements or Financial Provider Terms; (f) has caused or is likely to cause Stripe to violate them; (g) has experienced or is likely to experience a Change of Control; (h) has itself, or through employees, agents, directors or contractors, started or submitted transactions or taken any action that is or is likely to be fraudulent, suspicious or criminal; (i) has changed its business model without Stripe's prior consent, exposing Stripe to increased risk; or (j) has acted or traded in a way that presents an unacceptable risk.
Supporting quotations
8. Stripe Remedies.
8.1 Triggering Event.
Stripe may exercise any one or more of the remedies stated in Section 8.2 (Stripe Remedies) if Stripe determines that a User Entity:
(a) has a negative Financial Account balance;
(b) is or is likely to become the subject of an Insolvency Event;
(c) has experienced or is likely to experience a deterioration of its business or financial condition that Stripe considers to be material;
(d) has breached or is likely to breach, or has caused or is likely to cause Stripe to breach, this Agreement (or any other Stripe services agreement with a Stripe Entity) or the Provider Terms applicable to the User Entity’s use of the Services;
(e) has violated or is likely to violate Financial Account Regulatory Requirements or Financial Provider Terms;
(f) has caused or is likely to cause Stripe to violate Financial Account Regulatory Requirements or Financial Provider Terms;
(g) has experienced or is likely to experience a Change of Control;
(h) has, either itself or by way of its employees, agents, directors or contractors, initiated or submitted Financial Account Transactions or undertaken any other action that is or is likely to be fraudulent, suspicious or involve criminal activity;
(i) has, without Stripe’s prior consent, changed its business model (including services supplied by a User Entity to its customers), exposing Stripe to increased risk; or
(j) has acted in a manner or engaged in business, trading practice or other activity that presents an unacceptable risk.
Qualifications & exceptions
Each trigger depends on Stripe's own determination.
Many triggers apply when the event is merely likely, not yet occurred.
Not stated here
What counts as an unacceptable risk is not defined.
Charges & Financial Obligations · Permission or license
After a triggering event, Stripe may set up a Reserve, debit accounts, suspend submissions or refuse processing
If a Section 8.1 event occurs, Stripe may do one or more of the following: (a) establish, fund and use a Reserve; (b) debit each User Bank Account, Financial Account or Stripe Account to cure any negative balance of an Accountholder; (c) suspend or end the User's ability to submit Financial Account Transactions; and (d) refuse to process Financial Account Transactions.
Supporting quotations
8.2 Stripe Remedies.
If an event described in Section 8.1 (Triggering Event) occurs, then Stripe may do one or more of the following:
(a) establish, fund, and use a Reserve;
(b) debit each User Bank Account, Financial Account, or Stripe Account to cure any negative balance of a Stripe Treasury for Platforms Accountholder;
(c) suspend or terminate User's ability to submit Financial Account Transactions; and
(d) refuse to process Financial Account Transactions.
Qualifications & exceptions
Available once a Section 8.1 triggering event occurs.
Stripe may use one or more of the remedies.
Not stated here
The size of any Reserve is not stated here.
Charges & Financial Obligations · Restriction or exception
You bear all fraud losses and audit costs, and the General Terms' liability limits do not apply
As between the parties, the User is responsible for all (a) losses, damages and costs Stripe and its Affiliates incur from fraudulent Financial Account Transactions, and the limitations on liability in Sections 8.3 and 8.4 of the General Terms (Limitation on Indirect Liability; Liability Cap) do not apply to them; and (b) costs of any Financial Provider-initiated audit or forensic investigation arising from the User's offering of the Treasury for Platforms Services.
Supporting quotations
9. Fraudulent Transactions.
As between the parties, User is responsible for all: (a) losses, damages, and costs Stripe and its Affiliates incur due to fraudulent Financial Account Transactions, and the limitations on liability in Section 8.3 and 8.4 of the General Terms (Limitation on Indirect Liability; Liability Cap) do not apply; and (b) costs associated with any Financial Provider-initiated audit or forensic investigation arising out of or relating to User’s offering of the Stripe Treasury for Platforms Services.
Qualifications & exceptions
The General Terms' liability limits do not apply to fraud losses under this clause.
Not stated here
General Terms Sections 8.3 and 8.4 are not part of this saved text.
Account & Service Control · Company practice
These Platform Terms end automatically if the Stripe Connect Terms end for any reason
These Stripe Treasury for Platforms - Platform Terms terminate automatically if the Stripe Connect Terms terminate for any reason.
Supporting quotations
10. Termination.
These Stripe Treasury for Platforms - Platform Terms automatically terminate if the Stripe Connect Terms terminate for any reason.
Qualifications & exceptions
Termination follows the Connect Terms for any reason.
The Financial Account is the Stripe Account Stripe provides to the User as part of the Stripe Financial Accounts Services. A Financial Account Transaction is an Inbound Transaction or an Outbound Transaction. An Inbound Transaction is any Received Credit, Balance Transfer or other entry that increases the Available Balance, which Stripe may permit in its discretion. An Outbound Transaction is an Outbound Payment, Outbound Transfer or other fiat entry that subtracts from the Available Balance and that Stripe may permit in its sole discretion. A Financial Account Regulatory Requirement is Law and the rules of the electronic funds transfer networks the services use.
Supporting quotations
“Financial Account” means the Stripe Account that Stripe provides to User as part of the Stripe Financial Accounts Services.
“Financial Account Transaction” means an Inbound Transaction or an Outbound Transaction.
“Inbound Transaction” means any Received Credit, Balance Transfer, or any other entry or transaction that increases the Available Balance, that Stripe may permit from time to time, in its discretion.
“Outbound Transaction” means an Outbound Payment, Outbound Transfer, or any other fiat currency entry or transaction that subtracts from the Available Balance that Stripe may permit from time to time in its sole discretion.
“Financial Account Regulatory Requirement” means Law and the rules of the electronic funds transfer networks the Stripe Financial Accounts Services use.
“Financial Account Regulatory Requirement” means Law and the rules of the electronic funds transfer networks the Stripe Treasury Services use.
Qualifications & exceptions
Stripe permits other entries in its discretion or sole discretion.
Charges & Financial Obligations · Context
Definitions: Accountholder, Account Information, Dashboard, Product Guidelines and Treasury for Platforms Bank
A Treasury for Platforms Accountholder is a Connected Account, or a Connect Platform using the services for its own business, that has completed onboarding in the Dashboard. Account Information is Personal Data or business information a Connect Platform provides for its Connected Accounts so Stripe and its Affiliates can check eligibility, make the services available to Accountholders, and meet their responsibilities to the applicable banks and funds transfer networks. The Dashboard is a user interface Stripe or a Connect Platform provides for an Accountholder to manage its Financial Account. The Product Guidelines are all product design, marketing, compliance, reporting and other guidelines and requirements a Stripe Entity or applicable bank establishes from time to time. A Treasury for Platforms Bank is a bank through which a Stripe Entity holds Accountholder funds.
Supporting quotations
“Stripe Treasury for Platforms Accountholder” means a Connected Account, or Stripe Connect Platform using the Stripe Treasury for Platforms Services for its own business purpose, who has successfully completed the onboarding requirements in the Stripe Treasury for Platforms Dashboard.
“Stripe Treasury for Platforms Account Information” means Personal Data or business information that a Stripe Connect Platform provides on behalf of its Connected Accounts to enable Stripe and its Affiliates to (a) determine the Connected Accounts’ eligibility to access the Stripe Treasury for Platforms Services; (b) make the Stripe Treasury for Platforms Services available to Stripe Treasury for Platforms Accountholders; and (c) fulfill their responsibilities to applicable Treasury for Platforms Banks and electronic funds transfer networks that Stripe Treasury for Platforms Services use.
“Stripe Treasury for Platforms Dashboard” means a user interface that Stripe or a Stripe Connect Platform provides that enables a Stripe Treasury for Platforms Accountholder to manage its Financial Account.
“Stripe Treasury for Platforms Product Guidelines” means all product design, marketing, compliance, reporting and other guidelines and requirements established by a Stripe Entity or the applicable Treasury for Platforms Banks from time to time in connection with the Stripe Treasury for Platforms Services.
“Treasury for Platforms Bank” means a bank through which a Stripe Entity holds Treasury for Platforms Accountholder funds.
Qualifications & exceptions
The Product Guidelines can be changed from time to time.
Not stated here
The Product Guidelines are not supplied.
Charges & Financial Obligations · Context
Definitions: Treasury for Platforms Services and Territory, Treasury Services, Authorized User and Bank
The Treasury for Platforms Services let an Accountholder create and maintain a Financial Account to store, spend and manage funds and make electronic payments and transfers. The Territory is the United States and Puerto Rico, or other jurisdictions Stripe permits in the Documentation. The Stripe Treasury Services let the User access a Financial Account, fund it with a Received Credit or Balance Transfer, make Outbound Transactions and engage in other permitted transactions, as the Documentation describes. An Authorized User is an individual an Accountholder authorizes to use the services. A Treasury for Platforms Bank is a bank through which a Stripe Entity holds Accountholder funds. A Received Credit is funds added in a Supported Currency from an external bank account, and a Balance Transfer moves funds from the User's Stripe Account payments balance to its Financial Account.
Supporting quotations
“Stripe Treasury for Platforms Services” means the Services that enable a Treasury for Platforms Accountholder to create and maintain a Financial Account where the Treasury for Platforms Accountholder can (a) store, spend, and manage funds; and (b) make electronic payments and funds transfers to and from that account.
“Stripe Treasury for Platforms Territory” means the United States and Puerto Rico, or such other jurisdiction(s) as Stripe may permit in the Documentation.
“Stripe Treasury Services” means the Services that enable User to (a) access a Financial Account; (b) fund a Financial Account with a Received Credit or with a Balance Transfer; (c) make Outbound Transactions; and (d) engage in other permitted Financial Account Transactions; as further described in the Documentation.
"Treasury for Platforms Authorized User" means an individual that a Stripe Treasury for Platforms Accountholder authorizes to use the Stripe Treasury for Platforms Services.
“Treasury for Platforms Bank” means a bank through which a Stripe Entity holds Treasury for Platforms Accountholder funds.
“Received Credit” means the funds added to a Financial Account in a Supported Currency from an external bank account via the bank transfer, domestic wire, or other supported funding methods.
“Balance Transfer” means a transfer from User’s own Stripe Account payments balance, to User’s Financial Account, in accordance with the Stripe Treasury Terms.
“Stripe Treasury for Platforms Territory” means the United States and Puerto Rico, or such other jurisdictions Stripe permits, as further described in the Documentation.
"Treasury for Platforms Authorized User" means an individual that a Stripe Treasury for Platforms Accountholder authorizes to use the Stripe Treasury for Platforms Services.
Qualifications & exceptions
The Territory can include other jurisdictions Stripe permits.
Not stated here
The Documentation that may add jurisdictions is not supplied.
Legal Rights & Agreement Rules · Context
Definition: Stripe Losses cover finally awarded amounts, penalties, fines and third-party costs arising from the Claim
Stripe Losses means all amounts finally awarded to the third party making a Claim, and all penalties, fines and third-party costs, including legal fees, paid by the Stripe Parties, to the extent arising from the Claim. Unlike some other Stripe Losses definitions in the document, this one counts only amounts finally awarded.
Supporting quotations
“Stripe Losses” means all amounts finally awarded to the third party making a Claim, and all penalties, fines, and third-party costs (including legal fees) paid by the Stripe Parties, to the extent arising from the Claim.
Qualifications & exceptions
Only amounts finally awarded to the claimant count.
Charges & Financial Obligations · Context
UK Treasury for Platforms Accountholder Terms add to three other term sets (last modified July 21, 2026)
These Stripe Treasury for Platforms (United Kingdom) Accountholder Terms, last modified July 21, 2026, supplement the General Terms and, together with the Stripe Financial Services Terms and the Stripe Treasury Terms, govern the use of the Treasury for Platforms Services as an Accountholder if the User is located in the Treasury for Platforms Territory. If the User is a Stripe Connect Platform using the services for its own business purposes, the terms apply to it as an Accountholder and references to the Connect Platform also refer to the User.
Supporting quotations
Stripe Treasury for Platforms—Connected Accounts (United Kingdom)
Last modified: July 21, 2026
These Stripe Treasury for Platforms (United Kingdom) - Accountholder Terms of Service (“Stripe Treasury for Platforms (United Kingdom) Accountholder Terms”) supplement the General Terms, and together with the Stripe Financial Services Terms and the Stripe Treasury Terms, govern the use of the Stripe Treasury for Platforms Services as a Stripe Treasury for Platforms Accountholder if User is located in the Stripe Treasury for Platforms Territory. If User is a Stripe Connect Platform using the Stripe Treasury for Platforms Services for User’s own business purposes, these Stripe Treasury for Platforms (United Kingdom) Accountholder Terms apply to User as a Stripe Treasury for Platforms Accountholder, and references to “Stripe Connect Platform” in these terms are also references to User. Capitalised terms that are not defined in these Stripe Treasury for Platforms (United Kingdom) Accountholder Terms have the same meanings given to them in the General Terms, the Stripe Financial Services Terms and the Stripe Treasury Terms.
Qualifications & exceptions
Applies if the User is located in the Treasury for Platforms Territory.
Not stated here
The UK Territory is defined elsewhere in the document.
Charges & Financial Obligations · Restriction or exception
UK: you must be resident in the Territory, and can add and transfer funds through supported methods
The User must be resident in the Treasury for Platforms Territory to use the services. Its Stripe Connect Platform provides access, if applicable. Subject to the Financial Account Regulatory Requirements and these terms, the User and its Authorised Users can (a) add funds to the Financial Account by supported funding methods and (b) transfer funds from it to any account that can receive fund transfers at any financial institution. An Authorised User is an individual an Accountholder authorises to use the services.
Supporting quotations
1. Stripe Treasury for Platforms Services.
User must be resident in the Stripe Treasury for Platforms Territory to use the Stripe Treasury for Platforms Services. User’s Stripe Connect Platform will provide User access to the Stripe Treasury for Platforms Services (if applicable). Subject to the Financial Account Regulatory Requirements and these Stripe Treasury for Platforms (United Kingdom) Accountholder Terms, User and User’s Treasury for Platforms Authorised Users will be able to (a) add funds to User’s Financial Account via supported funding methods; and (b) transfer funds from User’s Financial Account to any account able to receive fund transfers at any financial institution.
"Treasury for Platforms Authorised User" means an individual that a Stripe Treasury for Platforms Accountholder authorises to use the Stripe Treasury for Platforms Services.
Qualifications & exceptions
Residence in the Territory is required.
Not stated here
The Territory for these UK terms is defined elsewhere in the document.
Account & Service Control · Restriction or exception
UK: your use may be subject to additional terms from your Stripe Connect Platform
The User acknowledges its use of the Treasury for Platforms Services may be subject to additional terms specific to its Stripe Connect Platform, which the platform will provide when the User requests access.
Supporting quotations
2. Use of the Stripe Treasury for Platforms Services.
User acknowledges that User’s use of the Stripe Treasury for Platforms Services may be subject to additional terms specific to User’s Stripe Connect Platform, which User’s Stripe Connect Platform will provide at the time User requests access to the Stripe Treasury for Platforms Services.
Not stated here
The platform-specific terms are not part of this saved text.
Account & Service Control · Restriction or exception
UK: if you open an account for a sole proprietorship, you represent and warrant you are its sole owner
The User represents as of the date it asks to open a Financial Account, and warrants at all times during the Term, that if it is an individual opening the account for a sole proprietorship, it is the sole owner of that business.
Supporting quotations
3. Set up and Operation of the Stripe Treasury for Platforms Account.
3.1 Representation and Warranty.
User represents as of the date User requests to open a Financial Account, and warrants at all times during the Term, that, if User is an individual opening the Financial Account for a business that is a sole proprietorship, User is the sole owner of that business.
Qualifications & exceptions
Applies to an individual opening an account for a sole proprietorship.
The warranty applies at all times during the Term.
Charges & Financial Obligations · Company practice
UK: your account holds one or more Financial Accounts denominated in GBP or other currencies Stripe chooses
The Treasury for Platforms Account contains one or more Financial Accounts. They are denominated in GBP, or other currencies Stripe may make available from time to time in its sole discretion.
Supporting quotations
3.2 Stripe Treasury for Platforms Accounts
The Stripe Treasury for Platforms Account will contain one or more Financial Accounts. Financial Accounts are denominated in GBP, or such other currencies as Stripe may make available from time to time in its sole discretion.
Qualifications & exceptions
Other currencies are available only if Stripe makes them available, in its sole discretion.
Account & Service Control · Permission or license
UK: you authorise Stripe to act on your platform's instructions on your account, and must give it your users' details
The User authorises Stripe to accept instructions from its Stripe Connect Platform on Financial Account Transactions, to manage the Financial Account and to take other actions on it. The User must give the platform all information about its Treasury for Platforms Authorised Users, any agent appointed under a power of attorney, and the electronic credentials such as logins for its Financial Account, and must immediately give updated information if it changes.
Supporting quotations
4. Treasury for Platforms Authorised Users.
4.1 Instructions from Stripe Connect Platform.
User authorises Stripe to accept instructions from User’s Stripe Connect Platform with respect to Financial Account Transactions, manage User’s Financial Account and take other actions on User’s Financial Account. User must provide User’s Stripe Connect Platform with all information regarding User’s Treasury for Platforms Authorised Users, any agent appointed under an applicable power of attorney, and the electronic credentials (such as logins) for User’s Financial Account, and User must immediately provide User’s Stripe Connect Platform with updated information if that information changes.
Qualifications & exceptions
Updates must be immediate.
Account & Service Control · Restriction or exception
UK: you must give your platform at least 5 business days' notice before changing ownership form or Authorised Users
The User must notify its Stripe Connect Platform at least 5 business days before making any change to (a) its form of ownership, such as changing from a sole proprietor to a limited liability company, or (b) its Treasury for Platforms Authorised Users.
Supporting quotations
User must notify User’s Stripe Connect Platform at least 5 business days before making any change to (a) User’s form of ownership (such as changing from a sole proprietor to a limited liability company); or (b) User’s Treasury for Platforms Authorised Users.
Qualifications & exceptions
Notice is due at least 5 business days ahead of the change.
Account & Service Control · Restriction or exception
UK: an agent under a power of attorney needs a form your platform and RSP accept, and they may rely on a copy
If the User appoints an agent under a power of attorney to manage the Financial Account, the power of attorney must be in a form acceptable to its Stripe Connect Platform and RSP. RSP and the platform may rely on a copy and are not required to confirm its validity.
Supporting quotations
4.2 Agents.
If User chooses to appoint an agent under a power of attorney to manage the Financial Account, the power of attorney must be in a form acceptable to User’s Stripe Connect Platform and RSP. RSP and User’s Stripe Connect Platform may rely on a copy of the power of attorney and are not required to confirm its validity.
Qualifications & exceptions
The platform and RSP need not confirm the power of attorney is valid.
Account & Service Control · Permission or license
UK: RSP may impose any condition it deems reasonable on platform instructions and refuse those Stripe believes doubtful
If RSP chooses to follow an instruction its Stripe Connect Platform sends, RSP may impose any condition it deems reasonable before carrying it out. RSP may refuse an instruction from the platform if Stripe believes (a) it is fraudulent or the User did not authorise it; (b) there are multiple or conflicting instructions; (c) an Authorised User or agent is exceeding their authority; or (d) complying may expose RSP or its Affiliates to liability. The UK version does not mention the surety bond or indemnity example in the US version.
Supporting quotations
4.3 Instructions.
If RSP chooses to comply with an instruction that User’s Stripe Connect Platform transmits, RSP may impose any condition that it deems reasonable prior to carrying out the instruction. RSP may refuse to comply with an instruction from User’s Stripe Connect Platform if Stripe believes that:
(a) the instruction is fraudulent or User did not authorise it;
(b) there are multiple or conflicting instructions;
(c) User’s Treasury for Platforms Authorised User or agent is exceeding their authority in giving the instruction; or
(d) complying with the instruction may expose RSP or its Affiliates to liability.
Qualifications & exceptions
Refusal depends on Stripe's belief.
RSP decides which conditions are reasonable.
Account & Service Control · Restriction or exception
UK: you access your account via the Dashboard and your platform's channels, and must follow its documentation
The User may access its Treasury for Platforms Account and the services through the Treasury for Platforms Dashboard, and by any other means its Stripe Connect Platform provides. It may use the Dashboard to view its Account Information and conduct Financial Account Transactions, including adding funds, transferring funds and paying third parties. If it uses other Services connected to the account or Dashboard, additional terms may apply. The User must use the Dashboard only in line with the documentation its platform provides.
Supporting quotations
5.1 Accessing User’s Stripe Treasury for Platforms Account.
User may access its Stripe Treasury for Platforms Account and the Stripe Treasury for Platforms Services through the Treasury for Platforms Dashboard, and by any other means User’s Stripe Connect Platform makes available to User. User may use the Treasury for Platforms Dashboard to view User’s Stripe Treasury for Platforms Account Information and conduct Financial Account Transactions, including adding funds to User’s Financial Account, transferring funds, and making payments from User’s Financial Account to third parties. If User uses other Services made available to User in connection with User’s Stripe Treasury for Platforms Account or the Treasury for Platforms Dashboard, as applicable, additional terms may apply to those Services. User must use the Treasury for Platforms Dashboard only in compliance with the documentation that User’s Stripe Connect Platform makes available to User.
Qualifications & exceptions
Other Services may carry additional terms.
Security & Safeguards · Restriction or exception
UK: you must keep credentials and devices secure and report suspected access to your platform and Stripe at once
The User must keep its account credentials, and the devices it uses to reach its Treasury for Platforms Account, secure and confidential at all times. It must tell both its Stripe Connect Platform through the required channels and Stripe immediately at the Treasury for Platforms support address if there has been any actual or suspected unauthorised access to its credentials. Failing to notify may affect the User's liability for transactions that follow.
Supporting quotations
5.2 Account Security.
User must keep User’s account credentials and the devices on which User accesses User’s Stripe Treasury for Platforms Account secure and confidential at all times. User must notify both User’s Stripe Connect Platform through the required channels and Stripe immediately at Treasury for Platforms-support@stripe.com if there has been any actual or suspected unauthorised access to User’s credentials. Failure to notify of any actual or suspected unauthorised access may impact User’s liability for any Financial Account Transactions that may occur.
Qualifications & exceptions
Both the platform and Stripe must be told.
Suspected access must be reported, not only confirmed access.
Not stated here
The terms do not say how liability is affected.
Account & Service Control · Restriction or exception
UK: you warrant you are a resident Territory business or non-profit, compliant, with no benefit to restricted businesses
The User represents on the date it first uses the services, and warrants at all times during the Term, that (a) it is engaged in a commercial business enterprise (which may be as a sole proprietor) or a non-profit organisation organised and operating in the Treasury for Platforms Territory; (b) it resides in the Territory; (c) it complies with all Financial Account Regulatory Requirements in connection with its use; and (d) it does not use the services to enable any individual or entity, including itself, to benefit from any Prohibited or Restricted Business.
Supporting quotations
5.3 Representations and Warranties.
User represents on the date User first uses the Stripe Treasury for Platforms Services, and warrants at all times during the Term, that:
(a) User is engaged in a commercial business enterprise (which may be as a sole proprietor) or a non-profit organisation organised and operating in the Stripe Treasury for Platforms Territory;
(b) User resides in the Stripe Treasury for Platforms Territory;
(c) User complies with all Financial Account Regulatory Requirements in connection with User’s use of the Stripe Treasury for Platforms Services; and
(d) User does not use the Stripe Treasury for Platforms Services to enable any individual or entity (including User) to benefit from any Prohibited or Restricted Business.
Qualifications & exceptions
The warranty applies at all times during the Term.
Non-profit organisations are allowed in the UK version.
Not stated here
The Prohibited or Restricted Business List is a separate document and is not supplied.
Legal Rights & Agreement Rules · Permission or license
UK: you authorise RSP to comply with Legal Process without checking validity, and to charge fees and costs
The User authorises RSP to comply with each Legal Process relating to the User or its Financial Account that RSP or its platform receives, without needing to decide whether it was validly issued or is enforceable. If a Transaction Hold is in effect, RSP may continue to charge all applicable fees even if the account cannot be closed. RSP may charge a fee for, and recover Stripe's costs of, complying with each Legal Process, and if the Regulatory Requirements permit will deduct them from the Available Treasury for Platforms Balance. A Transaction Hold is a restriction on funds availability Stripe places.
Supporting quotations
5.4 Legal Process.
User authorises RSP to comply with each Legal Process relating to User or User’s Financial Account that RSP or User’s Stripe Connect Platform receives, without needing to determine whether that Legal Process was validly issued or is enforceable. If a Transaction Hold is in effect, RSP may continue to charge all applicable fees, even if User’s Financial Account cannot be closed. RSP may charge User a fee for, and recover Stripe’s costs incurred in, complying with each Legal Process. If the Financial Account Regulatory Requirements permit, RSP will deduct those fees and costs from User’s Available Treasury for Platforms Balance.
“Transaction Hold” means a restriction on the availability of funds in a Financial Account or on User’s ability to effect a Financial Account Transaction that Stripe places as a result of delayed funds availability, Legal Process, or other circumstances as determined by Stripe in its sole discretion.
Qualifications & exceptions
RSP need not check that the Legal Process is valid or enforceable.
Charges & Financial Obligations · Company practice
UK: RSP need not notify you promptly when funds are added; you confirm receipt on the Dashboard
RSP is not obligated to notify the User promptly after funds are added to its Financial Account. The User can confirm through the Treasury for Platforms Dashboard whether RSP has received a transaction that adds funds.
Supporting quotations
6. Transactions on User’s Financial Account.
6.1 Adding Funds onto User’s Financial Account
RSP is not obligated to notify User promptly after funds are added into User’s Financial Account. User can confirm via the Stripe Treasury for Platforms Dashboard whether RSP has received a Financial Account Transaction that adds funds to User’s Financial Account.
Charges & Financial Obligations · Permission or license
UK: starting a transfer authorises your platform and RSP to act; RSP deducts it at once and may refuse some transfers
By starting a transfer through the Treasury for Platforms Dashboard, the User authorises (a) its Stripe Connect Platform to instruct RSP to make the transaction it specifies and (b) RSP to act on those instructions. RSP may deduct the amount of each transfer the platform starts or approves from the Available Treasury for Platforms Balance, even if the transfer is not yet completed. RSP may refuse any transfer (i) by a method RSP does not specifically permit for the account or (ii) that lacks information RSP requires. The Available Treasury for Platforms Balance is the amount of funds available to be transferred or paid out of a Financial Account.
Supporting quotations
6.2 Transfers from User’s Financial Account.
By initiating a transfer from User’s Financial Account via the Treasury for Platforms Dashboard, User authorises (a) User’s Stripe Connect Platform to instruct RSP to make the Financial Account Transaction User specifies; and (b) RSP to act on those instructions. RSP may deduct the amount of each transfer that User’s Stripe Connect Platform initiates or approves from User’s Available Treasury for Platforms Balance, even if the transfer has not yet been completed. RSP may refuse any transfer (i) by any method that RSP does not specifically permit for User’s Financial Account; or (ii) that does not include all information RSP requires.
“Available Treasury for Platforms Balance” means the amount of funds that is available to be transferred or paid out of a Financial Account.
Qualifications & exceptions
Deduction can happen before the transfer completes.
Not stated here
The permitted methods and required information are not listed here.
Charges & Financial Obligations · Permission or license
UK: your platform may answer Confirmation of Payee requests for you, and RSP may rely on its response
For any Confirmation of Payee requests, the Stripe Connect Platform may reply on the User's behalf, and RSP is entitled to rely on the platform's response to the same extent it would rely on the User's own response. Confirmation of Payee is the service to validate a payee's account name before starting a payment.
Supporting quotations
For any Confirmation of Payee requests, the Stripe Connect Platform may reply on User’s behalf, and RSP is entitled to rely on User’s Stripe Connect Platform’s response to the same extent it would rely on User’s response.
“Confirmation of Payee” means the service to validate a payee’s account name before initiating a payment.
Qualifications & exceptions
RSP may rely on the platform's response as it would on the User's.
Charges & Financial Obligations · Restriction or exception
UK: your platform sets conversion rates on cross-border transfers, amounts are estimates, and RSP disclaims FX losses
If a transfer needs a currency conversion, the exchange rate is determined and communicated to the User by its Stripe Connect Platform. Where conversion is part of a transaction, quoted payout amounts and fees are estimates and may change without notice with the exchange rate at conversion. RSP is not responsible for any losses the User suffers from a currency exchange.
If a transfer from User’s Financial Account requires a currency conversion, then the exchange rate used for that conversion will be determined and communicated to User by User’s Stripe Connect Platform. Where currency conversion is part of a transaction, any quoted payout amounts and associated fees are estimates, and may fluctuate without notice based on changes in the exchange rate that applies when the currency conversion takes place. RSP is not responsible for any losses User may suffer as a result of a currency exchange.
Qualifications & exceptions
Quoted amounts and fees are estimates that may change without notice.
Charges & Financial Obligations · User right or choice
UK: to stop a scheduled transfer, act in time for your platform to instruct Stripe 3 business days ahead
To stop a scheduled or preauthorised transfer, the User must instruct its Stripe Connect Platform in time for the platform to instruct Stripe at least 3 business days before the day the transaction is scheduled. If the User scheduled or preauthorised it through the Dashboard, it may change or cancel it there at least 3 business days before the scheduled day.
Supporting quotations
6.4 User’s Right to Stop Payment.
If User wishes to stop any scheduled or preauthorised transfer from User’s Financial Account, then User must give User’s Stripe Connect Platform instructions to do so in time for the Stripe Connect Platform to instruct Stripe accordingly at least 3 business days before the day on which the Financial Account Transaction is scheduled to be made. If User scheduled or preauthorised the transfer via the Stripe Treasury for Platforms Dashboard, then User may change or cancel the transfer via the Stripe Treasury for Platforms Dashboard at least 3 business days before the day on which the Financial Account Transaction is scheduled to be made.
Qualifications & exceptions
The cut-off is 3 business days before the scheduled day.
Charges & Financial Obligations · Permission or license
UK: RSP may refuse a transaction for insufficient funds, collection doubt, unverified details, security, fraud or rules
To the extent the Regulatory Requirements do not prohibit it, RSP may refuse to complete any Financial Account Transaction, including (a) if the account has insufficient funds; (b) if RSP reasonably doubts it can collect amounts owed to Stripe; (c) if RSP cannot verify ownership of, or other information about, the account or the person or entity funds are going to or coming from; (d) to protect the security of the account and Stripe's systems; (e) if Stripe is concerned about potential fraud or other misconduct; or (f) if the transaction would violate the UK Accountholder Terms or the Regulatory Requirements.
Supporting quotations
6.5 Stripe’s Right to Refuse.
To the extent the Financial Account Regulatory Requirements do not prohibit the actions listed in this Section 6.5 (Stripe’s Right to Refuse), RSP may refuse to complete any Financial Account Transaction, including:
(a) if User’s Financial Account has insufficient funds to cover a Financial Account Transaction;
(b) if RSP reasonably doubts that it can collect any amounts owed to Stripe;
(c) if RSP is unable to verify ownership of or other information about User’s Financial Account, or the individual or entity to or from whom the funds will be transferred;
(d) to protect the security of User’s Financial Account and Stripe’s systems;
(e) if Stripe is concerned about potential fraud or other misconduct; or
(f) if the Financial Account Transaction would violate these Stripe Treasury for Platforms (United Kingdom) Accountholder Terms or the Financial Account Regulatory Requirements.
Qualifications & exceptions
The list says “including”, so it is not exhaustive.
Subject to what the Regulatory Requirements permit.
Charges & Financial Obligations · Restriction or exception
UK: RSP or your platform may impose transaction limits and reduce or change them without notice
RSP or the User's Stripe Connect Platform may impose limits on the number and value of Financial Account Transactions the User may make. RSP may allow transactions that exceed the limits, or temporarily reduce the User's limits from time to time without notice unless the Regulatory Requirements require otherwise. RSP or the platform may change the limits at any time. Unlike the US version, the limits are not described in the Dashboard.
Supporting quotations
6.6 Financial Account Transaction Limitations.
Limits on the number and value of Financial Account Transactions that User may make from User’s Financial Account may be imposed by RSP or User’s Stripe Connect Platform. RSP may allow Financial Account Transactions that exceed applicable limits, or temporarily reduce User’s limits from time to time without notice (unless the Financial Account Regulatory Requirements require otherwise). RSP or User’s Stripe Connect Platform may change the limits at any time.
Qualifications & exceptions
Temporary reductions need no notice unless the Regulatory Requirements require it.
Not stated here
The limits themselves are not stated here.
Charges & Financial Obligations · Restriction or exception
UK: you must review transactions and report errors promptly and unauthorised ones immediately
The User must review its Financial Account history and each transaction as soon as possible. If it believes there is an error or discrepancy, it must tell its Stripe Connect Platform promptly. If it believes an unauthorised transaction has been made, it must tell the platform immediately and give a written statement with details if RSP or the platform asks. If it does not notify as required, or the platform does not notify RSP in time, losses from the unauthorised transaction may not be recoverable, or recovery may be slower or harder. Unlike the US version, this clause states no 30-day or one-day deadline.
(a) Obligation to Review. User must review User’s Financial Account history and each Financial Account Transaction as soon as possible. If User believes that there is an error or discrepancy in a Financial Account Transaction, User must notify User’s Stripe Connect Platform promptly. If User believes an unauthorised Financial Account Transaction has been made on User’s Financial Account, then User must immediately notify User’s Stripe Connect Platform. If RSP or User’s Stripe Connect Platform requests, User must submit a written statement with details about the unauthorised Financial Account Transaction. If User fails to notify User’s Stripe Connect Platform as required, or User’s Stripe Connect Platform does not notify RSP in a timely manner, then losses, damages, or costs User suffers as a result of the unauthorised Financial Account Transaction may not be recoverable, or recovery may be more time consuming or difficult.
Qualifications & exceptions
Late notice may make losses unrecoverable.
Not stated here
The 13-month outer limit appears in section 7.3.
Legal Rights & Agreement Rules · Restriction or exception
UK: you must help RSP and your platform investigate and prosecute claims about unauthorised transactions
The User must help RSP and its Stripe Connect Platform investigate, and prosecute related claims for, unauthorised Financial Account Transactions by completing the statements and reports they reasonably request.
Supporting quotations
(b) Assistance in Investigations. User must assist RSP and User’s Stripe Connect Platform in the investigation and related prosecution of claims for unauthorised Financial Account Transactions by completing the appropriate statements and reports that RSP or User’s Stripe Connect Platform reasonably requests.
Qualifications & exceptions
Requests must be reasonable.
Charges & Financial Obligations · Restriction or exception
UK: you are responsible for all transactions, authorised or not; Stripe Parties disclaim liability for listed causes
To the extent Law permits, the User is responsible for all Financial Account Transactions on its account, whether or not authorised. It acknowledges transactions may be sent to the wrong account if it gives RSP inaccurate or incomplete information, including through compromise or fraud. To the maximum extent Law permits, the Stripe Parties are not liable to the User, its Affiliates or any third party for losses, damages or costs from (a) a failed transaction, including RSP refusing or declining one or a failure from circumstances outside Stripe's control; (b) RSP or the platform acting on incorrect or incomplete information; (c) RSP refusing to follow the platform's instructions under Section 4.3; or (d) any correspondent bank's negligence or failure, or funds lost in transit.
Supporting quotations
7.2 Liability Related to Financial Account Transactions.
To the extent permitted by Law, User is responsible for all Financial Account Transactions on User’s Financial Account, whether or not they are authorised. User acknowledges that Financial Account Transactions may be sent to the wrong account if User provides RSP with inaccurate or incomplete information (including due to compromise or fraud). To the maximum extent permitted by Law, the Stripe Parties will not be liable to User, User’s Affiliates or any third party for any losses, damages or costs arising out of or relating to:
(a) a failed Financial Account Transaction on User’s Financial Account, including if RSP decides to refuse to pay or decline any Financial Account Transaction or if a Financial Account Transaction fails due to circumstances outside of Stripe’s control;
(b) RSP or User’s Stripe Connect Platform completing a Financial Account Transaction or otherwise acting in reliance upon any incorrect or incomplete information provided or made available to RSP or User’s Stripe Connect Platform;
(c) RSP’s refusal to comply with User’s Stripe Connect Platform’s instructions under Section 4.3 (Instructions); or
(d) any correspondent bank’s negligence or failure, or funds lost in transit.
Qualifications & exceptions
Responsibility for unauthorised transactions applies to the extent Law permits.
The disclaimer applies to the maximum extent Law permits.
Charges & Financial Obligations · Procedure
UK: report fraud or unauthorised transactions at once via the Dashboard; contact the payee first for defective charges
If the User believes there are fraudulent or unauthorised transactions on its account, it must immediately report them to RSP by filing a dispute through the Treasury for Platforms Dashboard. If it believes the account was subject to an incorrectly executed or defective charge, it must first contact the payee to resolve it, and if that fails must file the dispute through the Dashboard.
Supporting quotations
7.3 Reporting Unauthorised and Incorrectly Executed Transactions.
If User believes there are fraudulent or unauthorised transactions on User’s Financial Account, User must immediately report any such Financial Account Transactions to RSP by filing a dispute through the Treasury for Platforms Dashboard.
If User believes that User’s Financial Account was subject to an incorrectly executed or defective charge, User must first contact the payee to resolve the dispute regarding the relevant Financial Account Transaction. If User is unable to resolve the dispute with the payee, then User must file the dispute through User’s Treasury for Platforms Dashboard.
Qualifications & exceptions
Fraud and unauthorised transactions: report immediately.
Defective charges: payee first, then Dashboard dispute.
Charges & Financial Obligations · Restriction or exception
UK: you must notify incorrect, defective or unauthorised transactions without undue delay and within 13 months
The User must notify RSP of any incorrectly executed, defective or unauthorised Financial Account Transactions without undue delay, and no later than 13 months from the date the transaction appears on its Financial Account.
Supporting quotations
User must notify any incorrectly executed, defective or unauthorised Financial Account Transactions to RSP without undue delay, and no later than 13 months from the date the Financial Account Transaction appears on User’s Financial Account.
Qualifications & exceptions
The 13 months run from the date the transaction appears on the account.
Charges & Financial Obligations · Procedure
UK: RSP evaluates your report and credits the amount back if it determines, in its sole discretion, it was faulty
When the User notifies RSP of an incorrectly executed, defective or unauthorised transaction through the Dashboard, RSP evaluates the information under the Financial Account Regulatory Requirements. If RSP determines, in its sole discretion, that the transaction was incorrectly executed, defective or unauthorised, it credits the amount back to the User's Financial Account.
Supporting quotations
7.4 Determining Incorrectly Executed, Defective or Unauthorised Transactions.
When User notifies RSP of an incorrectly executed, defective or unauthorised Financial Account Transaction through the Treasury for Platforms Dashboard, RSP will evaluate the submitted information in accordance with Financial Account Regulatory Requirements. If RSP determines, in its sole discretion, that the Financial Account Transaction was incorrectly executed, defective or unauthorised, RSP will credit the amount of the applicable Financial Account Transaction back to User’s Financial Account.
Qualifications & exceptions
The outcome turns on RSP's sole-discretion determination.
Charges & Financial Obligations · User right or choice
UK: RSP reimburses unauthorised transactions, but you bear the first £35 if you should have been aware
RSP will reimburse the User for any unauthorised Financial Account Transaction where it determines neither the User nor a Treasury for Platforms Authorised User authorised the underlying transaction, provided the User is liable for the first £35 of any unauthorised transaction where RSP reasonably believes the User should have been aware of the unauthorised use.
Supporting quotations
7.5 Liability for Unauthorised Transactions.
RSP will reimburse User for any unauthorised Financial Account Transaction where RSP determines that neither User nor a Treasury for Platforms Authorised User authorised the underlying Financial Account Transaction, provided that
(a) User will be liable for the first £35 of any unauthorised Financial Account Transaction where RSP reasonably believes User should have been aware of the unauthorised use;
Qualifications & exceptions
Reimbursement depends on RSP's determination that neither the User nor an Authorised User authorised the transaction.
The £35 share applies only where RSP reasonably believes the User should have been aware.
Charges & Financial Obligations · Restriction or exception
UK: no reimbursement if the account was misused, grossly negligently handled, left insecure or not reported at once
RSP is not liable for an unauthorised transaction where (i) the User or an Authorised User used a Financial Account for an Unauthorised Purpose or with intent or gross negligence, or failed to use it in line with the Agreement, including by not taking all reasonable steps to keep credentials and devices secure and confidential, or the Product Guidelines; or (ii) the User failed to notify RSP of the unauthorised use immediately. An Unauthorised Purpose is a fraudulent or illegal purpose, a consumer, personal or household purpose, or any purpose unrelated to the Treasury for Platforms Services.
Supporting quotations
(b) RSP will not be liable for any unauthorised transaction where (i) User or a Treasury for Platforms Authorised User used a Financial Account for an Unauthorised Purpose or with intent or gross negligence, failed to use the Financial Account in accordance with the terms of this Agreement, including to take all reasonable steps to keep account credentials and the devices on which User accesses User’s Stripe Treasury for Platforms Account secure and confidential at all times, or the Stripe Treasury for Platforms Product Guidelines; or (ii) User failed to immediately notify RSP of the unauthorised use.
“Unauthorised Purpose” means (a) a fraudulent or illegal purpose; (b) a consumer, personal, or household purpose; and (c) any purpose unrelated to the Stripe Treasury for Platforms Services.
"Treasury for Platforms Authorised User" means an individual that a Stripe Treasury for Platforms Accountholder authorises to use the Stripe Treasury for Platforms Services.
Qualifications & exceptions
Either ground (i) or (ii) removes RSP's liability.
Consumer, personal or household use counts as an Unauthorised Purpose.
Charges & Financial Obligations · Permission or license
UK: RSP may recoup or set off a reimbursement if the transaction proves duly authorised and correctly executed
If RSP reimburses the User for an unauthorised or incorrectly executed transaction and later determines it was duly authorised and correctly executed, RSP may recoup or set off an equal amount from the User's Financial Account.
Supporting quotations
If RSP reimburses User for an unauthorised or incorrectly executed Financial Account Transaction and subsequently determines that the relevant Financial Account Transaction was duly authorised and correctly executed, RSP may recoup or set off an amount equal to that reimbursed amount from User’s Financial Account.
Qualifications & exceptions
Applies after RSP determines the transaction was authorised and correctly executed.
Charges & Financial Obligations · Restriction or exception
UK: you are responsible for your own tax liability, reporting and remitting, and must keep your platform informed
The User is responsible for (a) working out its tax liability on its Financial Account and (b) reporting, withholding and remitting all taxes due to the appropriate Governmental Authority on time. It must promptly tell its Stripe Connect Platform of all changes to its tax affairs and give all records and information the platform or RSP asks for to meet the Financial Account Regulatory Requirements.
Supporting quotations
8. Tax Reporting.
User is responsible for (a) determining User’s tax liability related to User’s Financial Account; and (b) reporting, withholding and remitting in a timely manner all taxes due to the appropriate Governmental Authority. User must promptly notify User’s Stripe Connect Platform of all changes related to User’s tax affairs, and provide all records and information that it or RSP requests to comply with the Financial Account Regulatory Requirements.
Qualifications & exceptions
Changes must be notified promptly.
Charges & Financial Obligations · Company practice
UK: your platform must disclose the fees that apply to you when you request access, and changes before they take effect
The User's Stripe Connect Platform is responsible for telling the User all fees, if any, that apply to its use of the Treasury for Platforms Services. The platform will disclose them when the User requests access and will disclose any changes before they take effect.
Supporting quotations
9. Fees and Security.
9.1 Fee Disclosure.
User’s Stripe Connect Platform is responsible for disclosing to User all applicable fees (if any) that apply to User’s use of the Stripe Treasury for Platforms Services. User’s Stripe Connect Platform will disclose those fees at the time User requests access to the Stripe Treasury for Platforms Services and will disclose any changes before they take effect.
Qualifications & exceptions
Fees are disclosed by the platform, not set out in these terms.
Not stated here
The fee amounts are not in these terms.
Charges & Financial Obligations · Restriction or exception
UK: you are liable to Stripe for losses from disputes on your account, which Stripe may deduct or set off without notice
To the maximum extent Law permits, the User is liable to Stripe for all losses, damages and costs Stripe incurs from any dispute involving the User's Financial Account, including from relying on its Stripe Connect Platform's representations or instructions. The User authorises Stripe to (i) deduct those amounts from funds in the Financial Account or (ii) set them off under Section 9.3 (Setoff), with or without prior notice.
Supporting quotations
9.2 User’s Responsibility for Disputes.
To the maximum extent permitted by Law, User is liable to Stripe for all losses, damages and costs that Stripe incurs as a result of any dispute involving User’s Financial Account, including as a result of relying on User’s Stripe Connect Platform’s representations or instructions. User authorises Stripe to (i) deduct these losses, damages and costs from funds in User’s Financial Account; or (ii) set them off in accordance with Section 9.3 (Setoff) with or without prior notice to User.
Qualifications & exceptions
Liability covers Stripe's reliance on the platform's representations or instructions.
Deduction or set-off may happen without prior notice.
Charges & Financial Obligations · Permission or license
UK: RSP may deduct, recoup or set off fees you owe, or Stripe may invoice them payable within 30 days
RSP may deduct, recoup or set off all fees the User owes Stripe, if any, from funds in the Financial Account. Alternatively, Stripe may invoice the User for some or all of the fees monthly in arrears, and the User must pay within 30 days after the invoice date. Unlike the US version, this clause does not mention causing an overdraft.
Supporting quotations
9.3 Setoff.
RSP may deduct, recoup or setoff all fees User owes Stripe (if any) from funds in User’s Financial Account. Alternatively, Stripe may invoice User for some or all of those fees on a monthly basis in arrears, and User must pay the fees within 30 days after the date of the invoice.
Qualifications & exceptions
Invoiced fees are payable within 30 days of the invoice date.
Account & Service Control · Company practice
UK: after closure your platform can give you account history access for 60 days unless regulation requires otherwise
Unless the Financial Account Regulatory Requirements require otherwise, after the User's Treasury for Platforms Account is closed, RSP will enable its Stripe Connect Platform to provide the User access to the account history for 60 days.
Supporting quotations
10. Restricting or Closing User’s Financial Account.
10.1 Closing User’s Stripe Treasury for Platforms Account.
Unless otherwise required under Financial Account Regulatory Requirements, after User’s Stripe Treasury for Platforms Account is closed, RSP will enable User’s Stripe Connect Platform to provide User access to User’s Stripe Treasury for Platforms Account history for 60 days.
Qualifications & exceptions
Access is through the platform and lasts 60 days, unless the Regulatory Requirements require otherwise.
Legal Rights & Agreement Rules · Permission or license
UK: Stripe may refer conflicting instructions or disputes to a court and need not judge their merit or give notice
If there are conflicting instructions about the User's Treasury for Platforms Account, or any dispute about it, then without limiting its other rights Stripe may refer the conflict or dispute to a court. If anyone notifies Stripe of a dispute, Stripe does not need to decide whether it has merit before taking further action. Stripe may exercise any of these rights without notice to the User.
Supporting quotations
10.2 Adverse Claims.
If there are conflicting instructions with respect to User’s Stripe Treasury for Platforms Account or if there is any dispute regarding User’s Stripe Treasury for Platforms Account, then without limiting Stripe’s rights under these Stripe Treasury for Platforms Accountholder Terms, Stripe may refer the conflict or dispute to a court for resolution. If any person notifies Stripe of a dispute, Stripe does not need to decide if the dispute has merit before Stripe takes further action. Stripe may exercise any of these rights without notice to User.
Qualifications & exceptions
Stripe may act without notice to the User.
Legal Rights & Agreement Rules · Restriction or exception
UK: where regulation voids liability limits for missed or unauthorised payments, liability is capped at face value
To the extent the Financial Account Regulatory Requirements invalidate or make unenforceable limits or exclusions of liability of RSP and its Affiliates for failing to stop payment on a Financial Account Transaction, or paying an unauthorised one, the Stripe Parties' aggregate liability for those circumstances is limited to the face value of the transaction.
Supporting quotations
11. Limitation of Liability.
To the extent that the Financial Account Regulatory Requirements invalidate or render unenforceable any limitations or exclusions of liability of RSP and its Affiliates under this Agreement with respect to failing to stop payment on a Financial Account Transaction, or paying an unauthorised Financial Account Transaction, then the Stripe Parties’ aggregate liability with respect to those circumstances will be limited to the face value of the Financial Account Transaction.
Qualifications & exceptions
Applies only to the extent the Regulatory Requirements invalidate other limits.
Charges & Financial Obligations · Context
UK definitions: Available Balance, Confirmation of Payee, Connected Account, Platform User and Connect Platform
The Available Treasury for Platforms Balance is the amount of funds available to be transferred or paid out of a Financial Account. Confirmation of Payee is the service to validate a payee's account name before starting a payment. A Connected Account is a Platform User with a Stripe Account onboarded to a Stripe Connect Platform through the Stripe Connect Services, or a Payout Recipient. A Platform User, where the User acts as a Connect Platform, is a user of its platform. A Stripe Connect Platform is a platform provider that uses the Stripe Connect Services.
Supporting quotations
12. Definitions.
“Available Treasury for Platforms Balance” means the amount of funds that is available to be transferred or paid out of a Financial Account.
“Confirmation of Payee” means the service to validate a payee’s account name before initiating a payment.
“Connected Account” means (a) a Platform User that has a Stripe Account onboarded to a Stripe Connect Platform via the Stripe Connect Services; or (b) a Payout Recipient.
“Platform User” means, where User is acting as a Stripe Connect Platform, a user of User’s platform.
“Stripe Connect Platform” means a platform provider that uses the Stripe Connect Services.
Charges & Financial Obligations · Context
UK definitions: Connect Services, Treasury for Platforms Account, Accountholder, Account Information and Dashboard
The Stripe Connect Services are, for a Connect Platform, the Services that let it create, manage and enable Services for its Connected Accounts and let it or them use the Stripe Payments Services, and for a Connected Account, the Services described in the Connected Account Agreement. A Treasury for Platforms Account is an account Stripe creates for an Accountholder as part of the services to manage its Financial Accounts. An Accountholder is a Connected Account, or a Connect Platform using the services for its own business, that has completed onboarding under the Platform Terms. Account Information is Personal Data or business information a Connect Platform provides for its Connected Accounts so Stripe and its Affiliates can check eligibility, make the services available, and meet their responsibilities to the Transfer Networks. The Dashboard is the user interface that lets an Accountholder manage its Treasury for Platforms Account.
Supporting quotations
“Stripe Connect Services" means (a) if User is a Stripe Connect Platform, the Services that allow User to (i) create, manage and enable Services for User’s Connected Accounts, as described in the Stripe Connect Infrastructure Terms; and (ii) enable User or User’s Connected Accounts to use the Stripe Payments Services, as described in the Stripe Connect Terms (if applicable); or (b) if User is a Connected Account, the Services described in the Connected Account Agreement.
“Stripe Treasury for Platforms Account” means an account that Stripe creates for a Stripe Treasury for Platforms Accountholder as part of the Stripe Treasury for Platforms Services to enable the management of Financial Account(s).
“Stripe Treasury for Platforms Accountholder” means a Connected Account, or Stripe Connect Platform using the Stripe Treasury for Platforms Services for User’s own business purpose, who has successfully completed the onboarding requirements described in the Stripe Treasury for Platforms Platform Terms.
“Stripe Treasury for Platforms Account Information” means Personal Data or business information that a Stripe Connect Platform provides on behalf of its Connected Accounts to enable Stripe and its Affiliates to (a) determine the Connected Accounts’ eligibility to access the Stripe Treasury for Platforms Services; (b) make the Stripe Treasury for Platforms Services available to Stripe Treasury for Platforms Accountholders; and (c) fulfill their responsibilities to Treasury for Platforms Transfer Networks.
“Treasury for Platforms Dashboard” means the user interface provided to enable a Stripe Treasury for Platforms Accountholder to manage its Stripe Treasury for Platforms Account.
Not stated here
The Connected Account Agreement is a separate document and is not supplied.
Charges & Financial Obligations · Context
UK definitions: Product Guidelines, Services, Territory, Authorised User, Transfer Networks, Unauthorised Purpose
The Product Guidelines are all product design, marketing, compliance, reporting and other guidelines and requirements a Stripe Entity establishes from time to time for the services. The Treasury for Platforms Services let an Accountholder create and maintain a Treasury for Platforms Account and Financial Account to store, spend and manage funds and make electronic payments and transfers. The Territory is the United Kingdom, Gibraltar, or other jurisdictions Stripe permits as the Documentation describes. An Authorised User is an individual an Accountholder authorises to use the services. Transfer Networks are the electronic funds transfer networks the services use, credit card networks and debit card networks. An Unauthorised Purpose is a fraudulent or illegal purpose, a consumer, personal or household purpose, or any purpose unrelated to the services.
Supporting quotations
“Stripe Treasury for Platforms Product Guidelines” means all product design, marketing, compliance, reporting and other guidelines and requirements established by a Stripe Entity from time to time in connection with the Stripe Treasury for Platforms Services.
“Stripe Treasury for Platforms Services” means the Services that enable a Stripe Treasury for Platforms Accountholder to create and maintain a Stripe Treasury for Platforms Account and Financial Account where the Stripe Treasury for Platforms Accountholder can (a) store, spend, and manage funds; and (b) make electronic payments and funds transfers to and from that account.
“Stripe Treasury for Platforms Territory” means the United Kingdom, Gibraltar, or such other jurisdictions Stripe permits, as further described in the Documentation.
"Treasury for Platforms Authorised User" means an individual that a Stripe Treasury for Platforms Accountholder authorises to use the Stripe Treasury for Platforms Services.
“Treasury for Platforms Transfer Networks” means the electronic funds transfer networks the Stripe Treasury for Platforms Services uses, credit card networks, and debit card networks.
“Unauthorised Purpose” means (a) a fraudulent or illegal purpose; (b) a consumer, personal, or household purpose; and (c) any purpose unrelated to the Stripe Treasury for Platforms Services.
Qualifications & exceptions
The Territory can include other jurisdictions Stripe permits.
The Product Guidelines can be changed from time to time.
Not stated here
The Product Guidelines and Documentation are not supplied.
Charges & Financial Obligations · Context
UK Platform Terms govern offering Treasury for Platforms to Connected Accounts in the Territory (updated July 21, 2026)
These Stripe Treasury for Platforms (United Kingdom) - Platform Terms, last updated July 21, 2026, supplement the General Terms, the Stripe Financial Services Terms and the Stripe Connect Infrastructure Terms, and govern the User's ability to offer the Treasury for Platforms Services to Connected Accounts in the Treasury for Platforms Territory. They do not apply to the User's use of the services for its own business; for that, the Accountholder Terms apply to the User as an Accountholder, and references to the Stripe Connect Platform in them also refer to the User.
Supporting quotations
Stripe Treasury for Platforms—Platform (United Kingdom)
Last updated: July 21, 2026
These Stripe Treasury for Platforms (United Kingdom) - Platform Terms ( “Stripe Treasury for Platforms (United Kingdom) - Platform Terms”) supplement the General Terms, the Stripe Financial Services Terms and the Stripe Connect Infrastructure Terms, and govern User’s ability to offer the Stripe Treasury for Platforms Services to Connected Accounts in the Stripe Treasury for Platforms Territory. These Stripe Treasury for Platforms (United Kingdom) - Platform Terms do not apply to User's use of the Stripe Treasury for Platforms Services for User’s own business purposes. If User uses the Stripe Treasury for Platforms Services for those purposes, then the Stripe Treasury for Platforms Accountholder Terms will apply to User as a Stripe Treasury for Platforms Accountholder, except that references to “Stripe Connect Platform” in those terms are also references to User. Capitalised terms that are not defined in these Stripe Treasury for Platforms (United Kingdom) - Platform Terms have the same meanings given to them in the General Terms, the Stripe Financial Services Terms and the Stripe Connect Infrastructure Terms.
Qualifications & exceptions
The Platform Terms do not apply to the User's own business use.
Account & Service Control · Restriction or exception
UK: you must not offer the service to ineligible Connected Accounts or outside the Territory, or let them use it there
The User must not offer the Treasury for Platforms Services to ineligible Connected Accounts. It must not offer, market or otherwise make the services available to Connected Accounts located outside the Treasury for Platforms Territory, and must make sure no Connected Account uses them outside it.
Supporting quotations
1. Stripe Treasury for Platforms Services.
User must not offer the Stripe Treasury for Platforms Services to ineligible Connected Accounts.
2. Access to the Stripe Treasury for Platforms Services.
User must not offer, market or otherwise make the Stripe Treasury for Platforms Services available to Connected Accounts located outside of the Stripe Treasury for Platforms Territory. User must ensure that no Connected Account uses the Stripe Treasury for Platforms Services outside of the Stripe Treasury for Platforms Territory.
Qualifications & exceptions
Eligibility criteria are not set out in this section.
Not stated here
What makes a Connected Account ineligible is not stated here.
Account & Service Control · Restriction or exception
UK: you must ensure Connected Accounts complete onboarding, and Stripe must approve each before use
The User must make sure each Connected Account that wants to use the services successfully completes the onboarding requirements in Section 3.2 (Information and Consent). Stripe must approve each Connected Account as part of onboarding before it uses the services.
Supporting quotations
3. Onboarding Connected Accounts.
3.1 General Responsibility.
User must ensure that each Connected Account that wishes to access the Stripe Treasury for Platforms Services successfully completes the onboarding requirements described in Section 3.2 (Information and Consent). Stripe must approve each Connected Account as part of the onboarding process before the Connected Account uses the Stripe Treasury for Platforms Services.
Qualifications & exceptions
Stripe's approval must come before use.
Not stated here
The UK version requires approval by Stripe only; the US version also requires the bank's approval.
Data Access & Collection · Restriction or exception
UK: you must submit, or ensure Connected Accounts submit, the information Stripe requests to verify and screen them
The User must submit, or make sure each Connected Account submits, all Treasury for Platforms Account Information that Stripe requests to verify and screen the Connected Account's eligibility, and to confirm it is not engaged in a Prohibited or Restricted Business.
Supporting quotations
3.2 Information and Consent.
User must:
(a) submit, or ensure that each Connected Account submits, all Stripe Treasury for Platforms Account Information that Stripe requests to verify and screen the Connected Account’s eligibility to access the Stripe Treasury for Platforms Services, and confirm that the Connected Account is not engaging in a Prohibited or Restricted Business;
Qualifications & exceptions
The information requested is whatever Stripe requests.
Not stated here
The Prohibited or Restricted Business List is a separate document and is not supplied.
Account & Service Control · Restriction or exception
UK: you must ensure Connected Accounts agree to the Accountholder Terms and Connected Account Agreement, and prove it
The User must make sure each Connected Account User that intends to onboard as an Accountholder agrees to the Accountholder Terms and the Connected Account Agreement before accessing the services. On Stripe's request the User must give the proof Stripe requires that the Accountholder Terms are binding on the Connected Account. If Stripe believes the User's acceptance process does not create a binding agreement between Stripe and the Connected Account, the User must change it as Stripe requires when asked.
Supporting quotations
(b) ensure that each Connected Account User intends to onboard as a Stripe Treasury for Platforms Accountholder agrees to the Stripe Treasury for Platforms Accountholder Terms and the Connected Account Agreement before accessing the Stripe Treasury for Platforms Services. At Stripe’s request, User must provide proof as Stripe requires that the Stripe Treasury for Platforms Accountholder Terms are binding on the Connected Account. If Stripe believes that User's existing acceptance process does not create a binding agreement between Stripe and the Connected Account, then, upon Stripe’s request, User must modify that process as Stripe requires;
Qualifications & exceptions
Agreement must come before the Connected Account accesses the services.
Account & Service Control · Restriction or exception
UK: you must tell Connected Accounts about approval, suspension and terms changes, and stop serving those who decline
The User must (c) tell each Connected Account if Stripe approves its access, and promptly tell a Connected Account that has become an Accountholder if Stripe suspends or ends its access; and (d) tell Accountholders of all changes to the Accountholder Terms and make sure they agree. If an Accountholder does not agree to the changed terms, the User must immediately stop making the services available to it.
Supporting quotations
User must:
(c) notify each Connected Account if Stripe approves its access to the Stripe Treasury for Platforms Services, and promptly notify a Connected Account that becomes a Stripe Treasury for Platforms Accountholder if Stripe suspends or terminates its access to the Stripe Treasury for Platforms Services; and
(d) notify Stripe Treasury for Platforms Accountholders of all changes to the Stripe Treasury for Platforms Accountholder Terms and ensure that those Stripe Treasury for Platforms Accountholders agree to them. If any Stripe Treasury for Platforms Accountholder does not agree to the modified Stripe Treasury for Platforms Accountholder Terms, then User must immediately stop making the Stripe Treasury for Platforms Services available to that Stripe Treasury for Platforms Accountholder.
Qualifications & exceptions
Suspension and termination notices must be prompt.
Stopping service to a non-agreeing Accountholder must be immediate.
Account & Service Control · Restriction or exception
UK: you must ensure Accountholders and their Authorised Users comply, help enforce the terms and apply changes
The User must make sure Accountholders, and their Treasury for Platforms Authorised Users, comply with the Accountholder Terms. On Stripe's request it must help enforce those terms against them. It must also make sure Accountholders put in place and follow any changes to the services that Stripe tells it about.
Supporting quotations
4. Responsibility for Stripe Treasury for Platforms Accountholders.
4.1 Stripe Treasury for Platforms Accountholder Terms.
User must ensure that Stripe Treasury for Platforms Accountholders, along with their Treasury for Platforms Authorised Users, comply with the Stripe Treasury for Platforms Accountholder Terms. Upon Stripe’s request, User must assist with enforcing the Stripe Treasury for Platforms Accountholder Terms against Stripe Treasury for Platforms Accountholders and Treasury for Platforms Authorised Users. User must ensure that Stripe Treasury for Platforms Accountholders implement and comply with any changes to the Stripe Treasury for Platforms Services, which Stripe will communicate to User.
Qualifications & exceptions
Enforcement help is on Stripe's request.
Charges & Financial Obligations · Restriction or exception
UK: you are jointly and severally liable for all Activity on Connected Accounts, including push-payment fraud claims
The User is responsible and liable to Stripe for all Activity on Connected Accounts in connection with the Treasury for Platforms Services, whether or not the User started it, including all Financial Account Transactions, claims for reimbursement relating to authorised push payment fraud, related fines, and any use of the services prohibited by the UK Platform Terms, the Accountholder Terms or the Connected Account Agreement. The User and the relevant Connected Account are jointly and severally liable to Stripe for amounts the Connected Account owes it, and Stripe may collect them from the User. If Stripe decides the User's responsibility creates an unacceptable risk to Stripe, it may use its remedies in Section 11.2 (Stripe Remedies). The US version does not mention push-payment fraud claims.
Supporting quotations
4.2 Responsibility for Activity.
User is responsible and liable to Stripe for all Activity on Connected Accounts in connection with the Stripe Treasury for Platforms Services, whether initiated by User or not, including all Financial Account Transactions, claims for reimbursement relating to authorised push payment fraud, associated fines, and any use of the Stripe Treasury for Platforms Services in a manner prohibited under these Stripe Treasury for Platforms (United Kingdom) - Platform Terms, the Stripe Treasury for Platforms Accountholder Terms, or the Connected Account Agreement. User and the relevant Connected Account are jointly and severally liable to Stripe for amounts the Connected Account owes to Stripe, and Stripe may collect these amounts from User in accordance with this Agreement. If Stripe determines that User’s responsibility for Activity on Connected Accounts creates an unacceptable risk to Stripe, Stripe may exercise its remedies listed in Section 11.2 (Stripe Remedies).
Qualifications & exceptions
Liability applies whether or not the User initiated the Activity.
Joint and several liability means Stripe can collect the whole amount from the User.
Not stated here
Section 11.2 is a later section of these terms.
Account & Service Control · Restriction or exception
UK: you must provide and maintain a Treasury for Platforms Dashboard for Accountholders
The User must provide and maintain a Stripe Treasury for Platforms Dashboard for its Accountholders to use.
Supporting quotations
5. Account Management and Support for Stripe Treasury for Platforms Accountholders.
5.1 Dashboard for Stripe Treasury for Platforms Accountholders.
User must provide and maintain a Stripe Treasury for Platforms Dashboard for use by Stripe Treasury for Platforms Accountholders.
Account & Service Control · Restriction or exception
UK: you must promptly integrate with the Stripe API so Stripe can host onboarding
Promptly after Stripe says Stripe-hosted onboarding is available, the User must integrate with the Stripe API as the Documentation directs, in a way that lets (a) a Stripe Entity host onboarding of Accountholders and (b) the User or Stripe, at the User's option, be responsible for Accountholder account management and access to the services.
Supporting quotations
5.2 Integration with Stripe API.
Promptly after Stripe notifies User that Stripe-hosted onboarding is available, User must integrate with the Stripe API according to the Documentation in a way that allows (a) a Stripe Entity to host onboarding of Stripe Treasury for Platforms Accountholders; and (b) User or Stripe, at User's option, to be responsible for providing Stripe Treasury for Platforms Accountholder account management and access to the Stripe Treasury for Platforms Services.
Qualifications & exceptions
The integration is due promptly after Stripe's notice.
Account & Service Control · Restriction or exception
UK: if you run account management, you must pass Stripe's information on unchanged and pass accurate data back
If the User elects to be responsible for Accountholder account management and access to the services, it must pass on to Accountholders, without changes or deletions, all information Stripe makes available for that purpose. It must make sure all information it passes from Accountholders to Stripe and its Affiliates, including account balances, transaction history and customer service issues, is accurate and complete. It must also make sure Connected Account Data is passed to Stripe in the manner the Documentation prescribes. Connected Account Data is data about Connected Accounts and Activity, which may include Protected Data and Stripe Data.
Supporting quotations
5.3 Obligation to Pass On Information.
(a) If User elects to be responsible for providing Stripe Treasury for Platforms Accountholder account management and access to the Stripe Treasury for Platforms Services, then User must pass on to the Stripe Treasury for Platforms Accountholders, without changes or deletions, all information that Stripe makes available for User to pass on to them. User must ensure that all information, including account balances, transaction history and customer service issues, that User passes from the Stripe Treasury for Platforms Accountholders to Stripe and its Affiliates is accurate and complete.
(b) User must ensure that Connected Account Data is passed to Stripe in the manner prescribed in the Documentation.
“Connected Account Data” means data about Connected Accounts and Activity, which may include Protected Data and Stripe Data.
Qualifications & exceptions
Applies if the User elects to be responsible for account management and access.
Not stated here
The Documentation's prescribed manner is not supplied.
Charges & Financial Obligations · Restriction or exception
UK: you must clearly tell each Accountholder your fees and whether they are Stripe passthrough fees
The User must clearly tell each Accountholder all fees, if any, that it charges for the Treasury for Platforms Services, and say whether or not those fees are passthrough fees from Stripe.
Supporting quotations
5.4 Communicating Fees.
User must clearly communicate to each Stripe Treasury for Platforms Accountholder all fees (if any) that User charges that are related to the Stripe Treasury for Platforms Services, and specify whether or not those fees are passthrough fees from Stripe.
Charges & Financial Obligations · Permission or license
UK: Stripe may review the fees you charge Accountholders and require you to change them at once and reimburse
Stripe may review the fees the User charges its Accountholders for the services to decide whether they comply with Stripe's requirements, applicable Transfer Network requirements and Law. If Stripe decides they do not comply, the User must immediately change the fees and reimburse the Accountholder as Stripe directs. The US version of this clause has no review right.
Supporting quotations
Stripe may review the fees User charges User's Stripe Treasury for Platforms Accountholders in connection with the Stripe Treasury for Platforms Services to determine whether the fees comply with Stripe’s requirements, applicable Treasury for Platforms Transfer Network requirements, and Law. If Stripe determines the fees do not comply, User must immediately modify the fees and reimburse the Stripe Treasury for Platforms Accountholder as Stripe directs.
Qualifications & exceptions
Compliance is measured against Stripe's requirements, Transfer Network requirements and Law.
Not stated here
Stripe's fee requirements are not set out in these terms.
Charges & Financial Obligations · Restriction or exception
UK: conversion rates follow the Documentation, quoted amounts are estimates, and you must give the required information
If a requested Financial Account Transaction needs a currency conversion, the exchange rate is determined as the Documentation states. Quoted payout amounts and fees are estimates and may change with the exchange rate when the conversion happens. The User must clearly give the Accountholder the relevant information about the conversion as the Documentation and the Financial Account Regulatory Requirements require.
If a requested Financial Account Transaction requires a currency conversion, then the exchange rate used for that conversion will be determined as stated in the Documentation. Where currency conversion is part of a Financial Account Transaction, any quoted payout amounts and associated fees are estimates, and may fluctuate based on changes in the exchange rate that applies when the currency conversion takes place. User must clearly communicate to the Stripe Treasury for Platforms Accountholder the relevant information about the currency conversion as required in the Documentation and under the Financial Account Regulatory Requirements.
Qualifications & exceptions
Quoted amounts and fees are estimates.
Not stated here
The Documentation's rate and information rules are not supplied.
Charges & Financial Obligations · Permission or license
UK: Stripe may permit or require you to answer Confirmation of Payee requests for Accountholders and rely on your reply
For any Confirmation of Payee requests, Stripe may permit or require the User to reply on behalf of its Accountholder, and Stripe is entitled to rely on the User's response to the same extent it would rely on the Accountholder's own response. Confirmation of Payee is the service to validate a payee's account name before starting a payment.
Supporting quotations
5.6 Confirmation of Payee.
For any Confirmation of Payee requests, Stripe may permit or require User to reply on behalf of User's Stripe Treasury for Platforms Accountholder, and Stripe is entitled to rely on User's response to the same extent it would rely on the response of the Stripe Treasury for Platforms Accountholder.
“Confirmation of Payee” means the service to validate a payee’s account name before initiating a payment.
Qualifications & exceptions
Stripe may require, not only permit, the User to reply.
Account & Service Control · Restriction or exception
UK: you must provide all support to Accountholders and Authorised Users per the Product Guidelines
The User must provide all support to Accountholders and Treasury for Platforms Authorised Users according to the Stripe Treasury for Platforms Product Guidelines.
Supporting quotations
5.7 Support.
User must provide all support to Stripe Treasury for Platforms Accountholders and Treasury for Platforms Authorised Users according to the Stripe Treasury for Platforms Product Guidelines.
Not stated here
The Product Guidelines are not supplied.
Legal Rights & Agreement Rules · Restriction or exception
UK: you must offer the service within regulatory requirements, give Stripe a test account and ensure business-only use
The User must (a) make the services available to Accountholders in line with the Financial Account Regulatory Requirements; (b) make sure Accountholders and Authorised Users access them in compliance with those requirements; (c) not, and make sure Accountholders and Authorised Users do not, take or fail to take any action that could cause Stripe or its Affiliates to violate any Regulatory Requirement; (d) on request, give Stripe a Treasury for Platforms Account on the User's platform and enable access to features Stripe may use to test and monitor the User's use and compliance; and (e) make sure Accountholders and Authorised Users use the services for business purposes only.
Supporting quotations
6. Compliance.
6.1 Generally.
User must:
(a) make the Stripe Treasury for Platforms Services available to Stripe Treasury for Platforms Accountholders according to the Financial Account Regulatory Requirements;
(b) ensure that Stripe Treasury for Platforms Accountholders and Treasury for Platforms Authorised Users access the Stripe Treasury for Platforms Services in compliance with the Financial Account Regulatory Requirements;
(c) not, and must ensure that Stripe Treasury for Platforms Accountholders and Treasury for Platforms Authorised Users do not, take or fail to take any action that could cause Stripe or any of its Affiliates to violate any Financial Account Regulatory Requirement;
(d) upon request, provide Stripe with a Stripe Treasury for Platforms Account on User's platform, and enable access to features (as needed) that Stripe may use to test and monitor User's use of, and compliance with, these Terms; and
(e) ensure that Stripe Treasury for Platforms Accountholders and Treasury for Platforms Authorised Users use the Stripe Treasury for Platforms Services for business purposes only.
“Financial Account Regulatory Requirement” means Law and the rules of the electronic funds transfer networks the Stripe Treasury Services use.
Qualifications & exceptions
Covers failures to act as well as actions.
The test account and feature access are on Stripe's request.
Account & Service Control · Restriction or exception
UK: you must ensure Accountholders and Authorised Users use the services for business purposes only
The User must make sure Accountholders and Treasury for Platforms Authorised Users use the Treasury for Platforms Services for business purposes only.
Supporting quotations
(e) ensure that Stripe Treasury for Platforms Accountholders and Treasury for Platforms Authorised Users use the Stripe Treasury for Platforms Services for business purposes only.
Legal Rights & Agreement Rules · Restriction or exception
UK: you must ensure Accountholders follow the Product Guidelines and run a compliance program
The User must (a) make sure each Accountholder complies with all Product Guidelines, and (b) set up, keep and act under a compliance program that lets and ensures each Accountholder comply with the Financial Account Regulatory Requirements and the Product Guidelines.
Supporting quotations
6.2 Stripe Treasury for Platforms Product Guidelines.
User must (a) ensure that each Stripe Treasury for Platforms Accountholder complies with all Stripe Treasury for Platforms Product Guidelines; and (b) establish, maintain, and act according to a compliance program that will enable and ensure each Stripe Treasury for Platforms Accountholder complies with the Financial Account Regulatory Requirements and the Stripe Treasury for Platforms Product Guidelines.
Not stated here
The terms do not describe the compliance program's required content.
Account & Service Control · Restriction or exception
UK: you need Stripe's prior approval before sharing marketing materials, but may use unmodified templates
The User must not distribute or share any marketing materials about the Treasury for Platforms Services without Stripe's prior approval, and must submit all marketing materials to Stripe through a process Stripe tells it about. Stripe may provide template marketing materials, which the User may use without further approval as long as it does not modify them.
Supporting quotations
6.3 Marketing.
User must not distribute or share any marketing materials relating to the Stripe Treasury for Platforms Services without Stripe’s prior approval. User must submit all marketing materials to Stripe using a process Stripe communicates to User. Stripe may provide template marketing materials to User, which User may use without further Stripe approval as long as the template marketing materials are not modified.
Qualifications & exceptions
Approval must come before distribution.
Templates need no further approval only if left unmodified.
Use & Processing · Restriction or exception
UK: you must get the rights and consents, and give the disclosures, for Stripe and its Affiliates to use Personal Data
The User must get all necessary rights and consents from each actual and prospective Accountholder to (a) provide Personal Data to Stripe and its Affiliates; (b) let them collect, use, retain and disclose it; and (c) let them exercise their rights and perform their obligations under the UK Platform Terms and under Stripe's Privacy Policy. When onboarding Accountholders, the User must disclose that it may give Personal Data to Stripe and its Affiliates, and that they may collect, use, retain and disclose it under Stripe's Privacy Policy.
Supporting quotations
6.4 Stripe Treasury for Platforms Accountholder Consents.
User must obtain all necessary rights and consents from each actual and prospective Stripe Treasury for Platforms Accountholder to (a) provide Personal Data to Stripe and its Affiliates; (b) allow Stripe and its Affiliates to collect, use, retain and disclose that Personal Data; and (c) allow Stripe and its Affiliates to exercise their rights and perform their obligations under these Stripe Treasury for Platforms (United Kingdom) - Platform Terms and according to Stripe’s Privacy Policy. User must, when onboarding Stripe Treasury for Platforms Accountholders, (a) disclose to them that User may provide Personal Data to Stripe, and its Affiliates, and that Stripe and its Affiliates may collect, use, retain and disclose Personal Data in accordance with Stripe’s Privacy Policy.
Qualifications & exceptions
Covers prospective as well as actual Accountholders.
Not stated here
Stripe's Privacy Policy is not supplied.
Data Access & Collection · Restriction or exception
UK: you must hold the rights and consents to give Stripe User Information about owners, staff and Connected Accounts
The User must get and keep all necessary rights and consents under Law to give the User Information it provides to Stripe about each of (a) its Principal Owners and employees, independent contractors and agents, and (b) its Connected Accounts, Accountholders and Authorised Users.
Supporting quotations
7. Data Use
7.1 Data Collection.
User must obtain and maintain all necessary rights and consents under Law to provide the User Information that User provides to Stripe about each of User's (a) Principal Owners and employees, independent contractors and agents; and (b) Connected Accounts, Stripe Treasury for Platforms Accountholders and Treasury for Platforms Authorised Users.
Security & Safeguards · Restriction or exception
UK: you must secure Personal Data with appropriate measures, including encryption, and monitor for fraud
The User must secure Personal Data in its possession or control, and make sure its Accountholders secure Personal Data they hold. When Personal Data is stored or processed digitally, the User must use appropriate organisational and technical measures, including industry-standard encryption. The User must monitor, and make sure its Accountholders monitor, for suspicious, fraudulent and unauthorised transactions on each Accountholder's Financial Account.
Supporting quotations
7.2 Securing Account Data.
User must secure Personal Data in User's possession or control, and User must ensure that User's Stripe Treasury for Platforms Accountholders secure Personal Data in their possession or control. When stored or processed digitally, User must use appropriate organisational and technical measures to secure Personal Data in User's possession or control, including through industry-standard encryption. User must monitor, and User must ensure that User's Stripe Treasury for Platforms Accountholders monitor, for suspicious, fraudulent and unauthorised Financial Account Transactions on each Stripe Treasury for Platforms Accountholder’s Financial Account.
Qualifications & exceptions
Duties extend to Accountholders' handling of Personal Data.
Not stated here
The terms do not define industry-standard encryption.
Account & Service Control · Restriction or exception
UK: you must give Accountholders a dispute channel, pass disputes to Stripe at once and never block them
The User must provide a channel through which Accountholders can submit disputes to it. It must immediately submit any disputes it receives to Stripe through the Stripe API or Dashboard. It must not interfere with an Accountholder's ability to dispute a Financial Account Transaction.
Supporting quotations
8. Disputes
8.1 Disputes
User must provide a channel through which Stripe Treasury for Platforms Accountholders can submit disputes to User. User must immediately submit any disputes User receives to Stripe through the Stripe API or the Stripe Dashboard. User must not interfere with any Stripe Treasury for Platforms Accountholder’s ability to dispute a Financial Account Transaction.
Qualifications & exceptions
Disputes must be passed on immediately.
Account & Service Control · Restriction or exception
UK: you must report Accountholders' fraud and push-payment scam transactions to Stripe at once or help them file
If an Accountholder believes there are fraudulent or unauthorised transactions on a Financial Account, or that it has been the victim of an authorised push payment scam, the User must immediately report the transactions to Stripe by filing a dispute through the Dashboard, or must help the Accountholder file a dispute with Stripe.
Supporting quotations
8.2 Reporting Unauthorised Transactions.
If a Stripe Treasury for Platforms Accountholder believes that there are fraudulent or unauthorised transactions on a Financial Account, or that they have been the victim of an authorised push payment scam, User must immediately report any relevant Financial Account Transactions to Stripe by filing a dispute through the Stripe Dashboard or User must facilitate the Stripe Treasury for Platforms Accountholder in filing a dispute for any such Financial Account Transactions with Stripe.
Qualifications & exceptions
Reporting must be immediate.
Charges & Financial Obligations · Procedure
UK: for erroneous charges, contact the payee first, then dispute; Accountholders must notify within 13 months
If the User believes a Financial Account was subject to an incorrectly executed or otherwise erroneous charge, it must first contact the payee. If it cannot resolve the matter, it must file the dispute through its Dashboard or help the Accountholder file one through another channel the User provides. Accountholders must notify Stripe of any incorrectly executed, erroneous or unauthorised transactions within 13 months of the date the transaction appears on their Financial Account.
Supporting quotations
8.3 Reporting Erroneous Transactions.
If User believes that a Financial Account was subject to an incorrectly executed or otherwise erroneous charge, the User must first contact the relevant payee regarding the relevant Financial Account Transaction. If the User is unable to resolve the matter with the relevant payee, then User must file the dispute through User's Stripe Dashboard or User must facilitate the Stripe Treasury for Platforms Accountholder in filing a dispute for the Financial Account Transaction through another channel that User provides. Stripe Treasury for Platforms Accountholders must notify any incorrectly executed, erroneous or unauthorised Financial Accounts Transactions to Stripe within 13 months from the date the Financial Account Transaction appears on their Financial Account.
Qualifications & exceptions
Payee contact comes before a dispute for erroneous charges.
The 13 months run from the date the transaction appears on the account.
Charges & Financial Obligations · Procedure
UK: Stripe evaluates reported transactions and credits valid ones; you must abide and not pass costs to Accountholders
When an Accountholder reports an erroneous or unauthorised transaction, Stripe evaluates the information under Law. If Stripe determines, in its sole discretion, that it was erroneous, incorrectly executed or unauthorised, Stripe credits the amount back to the Financial Account. The User must abide by Stripe's determination and may not pass costs or dispute fees it incurs from fraudulent or unauthorised transactions on to an Accountholder.
When a Stripe Treasury for Platforms Accountholder submits or reports an erroneous or unauthorised Financial Account Transaction, Stripe will evaluate the submitted information in accordance with Law. If Stripe determines, in its sole discretion, that the Financial Account Transaction was erroneous, incorrectly executed or unauthorised, Stripe will credit the amount of the applicable Financial Account Transaction back to the applicable Financial Account. User must abide by Stripe’s determination. User may not pass any costs or dispute fees User incurs as a result of any fraudulent or unauthorised Financial Account Transactions on to a Stripe Treasury for Platforms Accountholder.
Qualifications & exceptions
The outcome turns on Stripe's sole-discretion determination.
Legal Rights & Agreement Rules · Restriction or exception
UK: you defend and indemnify the Stripe Parties, including for push-payment fraud reimbursement claims and transactions
The User will defend and indemnify the Stripe Parties against any Claim, and indemnify them for all Stripe Losses, including claims for reimbursement relating to authorised push payment fraud, arising out of or relating to (a) inaccurate or incomplete information given to a Stripe Entity by or for the User or any Accountholder; (b) an Accountholder's breach of the Accountholder Terms; (c) a negative balance or financial loss or damage caused by the User or an Accountholder; or (d) Financial Account Transactions. Compared with the US version, this adds the push-payment fraud reimbursement claims and item (d), covering transactions generally.
Supporting quotations
9. Indemnification.
User will defend and indemnify the Stripe Parties from and against any Claim, and indemnify the Stripe Parties for all Stripe Losses (including claims for reimbursement relating to authorised push payment fraud) arising out of or relating to (a) inaccurate or incomplete information provided to a Stripe Entity by or on behalf of User or any Stripe Treasury for Platforms Accountholder; (b) a Stripe Treasury for Platforms Accountholder’s breach of the Stripe Treasury for Platforms Accountholder Terms; (c) a negative balance or financial loss or damage caused by User or a Stripe Treasury for Platforms Accountholder; or (d) Financial Account Transactions.
Includes a duty to defend as well as to indemnify.
Not stated here
Whether any cap applies is not stated in this clause.
Charges & Financial Obligations · Permission or license
UK: you authorize Stripe to debit your bank or Stripe Accounts to cure an Accountholder's negative balance
The User authorizes Stripe to debit each User Bank Account or Stripe Account, at Stripe's discretion, to cure any negative balance of an Accountholder.
Supporting quotations
User authorizes Stripe to debit each User Bank Account or Stripe Account, at Stripe’s discretion, to cure any negative balance of a Stripe Treasury for Platforms Accountholder.
Qualifications & exceptions
Debiting is at Stripe's discretion.
Not stated here
The terms set no notice requirement before a debit.
Charges & Financial Obligations · Restriction or exception
UK: Stripe is not liable for losses from any Treasury for Platforms Payout Delay, notwithstanding the Agreement
Notwithstanding anything else in the Agreement, Stripe is not liable to the User, Accountholders, Treasury for Platforms Administrators or Authorised Users for any losses, damages or costs arising from any Treasury for Platforms Payout Delay.
Supporting quotations
10. Liability.
10.1 Stripe Liability.
Notwithstanding anything in the Agreement to the contrary, Stripe will not be liable to User, Stripe Treasury for Platforms Accountholder, Stripe Treasury for Platforms Administrators, or Treasury for Platforms Authorised Users for any losses, damages, or costs arising out of or relating to any Treasury for Platforms Payout Delay.
Qualifications & exceptions
Applies notwithstanding any contrary term of the Agreement.
Not stated here
The Payout Delay definition is not among the definitions read for this section.
Legal Rights & Agreement Rules · Restriction or exception
UK: your liability for Accountholders, and for failing to obtain their binding acceptance of the terms, is not limited
Notwithstanding any provision of the Agreement, including any precedence or interpretation clause, there is no limitation or exclusion of the User's liability for Accountholders, or for its failure to get each Accountholder's binding acceptance of the Accountholder Terms as the Agreement requires.
Supporting quotations
10.2 User's Liability for Stripe Treasury for Platforms Accountholders.
Notwithstanding any provision of this Agreement (including any precedence or interpretation clause), there is no limitation or exclusion in relation to User's liability for Stripe Treasury for Platforms Accountholders, or for User's failure to acquire binding acceptance by each Stripe Treasury for Platforms Accountholder of the Stripe Treasury for Platforms Accountholder Terms in accordance with this Agreement.
Qualifications & exceptions
Applies notwithstanding any precedence or interpretation clause.
Account & Service Control · Company practice
UK: these Platform Terms end automatically if the Stripe Connect Terms end for any reason
These UK Platform Terms terminate automatically if the Stripe Connect Terms terminate for any reason.
Supporting quotations
10.3 Termination.
These Stripe Treasury for Platforms (United Kingdom) - Platform Terms automatically terminate if the Stripe Connect Terms terminate for any reason.
Qualifications & exceptions
Termination follows the Connect Terms for any reason.
Legal Rights & Agreement Rules · Permission or license
UK: Stripe may use its remedies if a User Entity has a negative balance, insolvency, breach, fraud or unacceptable risk
Stripe may use the remedies in Section 11.2 if it determines that a User Entity (a) has a negative Financial Account balance; (b) is or is likely to become subject to an Insolvency Event; (c) has experienced or is likely to experience a material deterioration in business or financial condition; (d) has breached or is likely to breach, or is likely to cause Stripe to breach, the Agreement or another Stripe services agreement; (e) has violated or is likely to violate Financial Account Regulatory Requirements; (f) has caused or is likely to cause Stripe to violate them; (g) has experienced or is likely to experience a Change of Control; (h) has itself, or through employees, agents, directors or contractors, started or submitted transactions or taken any action that is or is likely to be fraudulent, suspicious or criminal; (i) has changed its business model without Stripe's prior consent, exposing Stripe to increased risk; or (j) has acted or traded in a way that presents an unacceptable risk.
Supporting quotations
11. Stripe Remedies.
11.1 Triggering Event.
Stripe may exercise any one or more of the remedies stated in Section 11.2 (Stripe Remedies) if Stripe determines that a User Entity:
(a) has a negative Financial Account balance;
(b) is or is likely to become the subject of an Insolvency Event;
(c) has experienced or is likely to experience a deterioration of its business or financial condition that Stripe considers to be material;
(d) has breached or is likely to breach, or has caused or is likely to cause Stripe to breach, this Agreement (or any other Stripe services agreement with a Stripe Entity);
(e) has violated or is likely to violate Financial Account Regulatory Requirements;
(f) has caused or is likely to cause Stripe to violate Financial Account Regulatory Requirements;
(g) has experienced or is likely to experience a Change of Control;
(h) has, either itself or by way of its employees, agents, directors or contractors, initiated or submitted Financial Account Transactions or undertaken any other action that is or is likely to be fraudulent, suspicious or involve criminal activity;
(i) has, without Stripe’s prior consent, changed its business model (including services supplied by a User Entity to its customers), exposing Stripe to increased risk; or
(j) has acted in a manner or engaged in business, trading practice or other activity that presents an unacceptable risk.
Qualifications & exceptions
Each trigger depends on Stripe's own determination.
Many triggers apply when the event is merely likely, not yet occurred.
Not stated here
What counts as an unacceptable risk is not defined.
Charges & Financial Obligations · Permission or license
UK: after a triggering event, Stripe may set up a Reserve, debit accounts, suspend submissions or refuse processing
If a Section 11.1 event occurs, Stripe may do one or more of the following: (a) establish, fund and use a Reserve; (b) debit each User Bank Account, Financial Account or Stripe Account to cure any negative balance of an Accountholder; (c) suspend or end the User's ability to submit Financial Account Transactions; and (d) refuse to process Financial Account Transactions.
Supporting quotations
11.2 Stripe Remedies.
If an event described in Section 11.1 (Triggering Event) occurs, then Stripe may do one or more of the following:
(a) establish, fund, and use a Reserve;
(b) debit each User Bank Account, Financial Account, or Stripe Account to cure any negative balance of a Stripe Treasury for Platforms Accountholder;
(c) suspend or terminate User’s ability to submit Financial Account Transactions; and
(d) refuse to process Financial Account Transactions.
Qualifications & exceptions
Available once a Section 11.1 triggering event occurs.
Stripe may use one or more of the remedies.
Not stated here
The size of any Reserve is not stated here.
Charges & Financial Obligations · Context
UK definitions: Available Balance, Confirmation of Payee, Financial Account and Financial Account Transaction
The Available Treasury for Platforms Balance is the amount of funds available to be transferred or paid out of a Financial Account. Confirmation of Payee is the service to validate a payee's account name before starting a payment. A Financial Account is the Stripe Account Stripe creates for an Accountholder as part of the services. A Financial Account Transaction is a transaction in a Financial Account that adds to or subtracts from the Available Treasury for Platforms Balance.
Supporting quotations
12. Definitions
“Available Treasury for Platforms Balance” means the amount of funds that is available to be transferred or paid out of a Financial Account.
“Confirmation of Payee” means the service to validate a payee’s account name before initiating a payment.
“Financial Account” means the Stripe Account that Stripe creates for a Stripe Treasury for Platforms Accountholder as part of the Stripe Treasury for Platforms Services.
“Financial Account Transaction” means a transaction in a Financial Account that adds to or subtracts from the Available Treasury for Platforms Balance.
Charges & Financial Obligations · Context
UK definitions: Principal Owner, Treasury for Platforms Account, Account Activity and Authorised User
A Principal Owner of a legal entity is an individual who directly or indirectly, through any contract, arrangement, understanding or relationship, owns at least 25% of its equity. A Treasury for Platforms Account is an account Stripe creates for an Accountholder to manage its Financial Accounts. Treasury for Platforms Account Activity, for these UK Platform Terms, is any action on or related to an Accountholder's Financial Account that the User, an Accountholder or an Authorised User starts, submits or performs through Stripe Technology or the services, including any Financial Account Transaction. An Authorised User is an individual an Accountholder authorises to use the services.
Supporting quotations
“Principal Owner” means, with respect to a legal entity, an individual who directly or indirectly, through any contract, arrangement, understanding, relationship, or otherwise, owns at least 25% of the equity interests of the legal entity.
“Stripe Treasury for Platforms Account” means an account that Stripe creates for a Stripe Treasury for Platforms Accountholder as part of the Stripe Treasury for Platforms Services to enable the management of Financial Account(s).
“Stripe Treasury for Platforms Account Activity” for purposes of these Stripe Treasury for Platforms (United Kingdom) - Platform Terms, means any action taken on or related to a Stripe Treasury for Platforms Accountholders’ Financial Account that User, a Stripe Treasury for Platforms Accountholder, or Stripe Treasury for Platforms Authorised User initiates, submits or performs, either through the Stripe Technology or through the Stripe Treasury for Platforms Services, including any Financial Account Transaction.
"Treasury for Platforms Authorised User" means an individual that a Stripe Treasury for Platforms Accountholder authorises to use the Stripe Treasury for Platforms Services.
Qualifications & exceptions
Principal Owner counts indirect ownership as well as direct.
Account & Service Control · Context
Definitions: Treasury for Platforms Accountholder, Administrator and Authorised User
A Treasury for Platforms Accountholder is a Connected Account, or a Connect Platform using the services for its own business purpose, that has completed the onboarding requirements described in the Dashboard. An Administrator is the individual an Accountholder appoints to manage the services on its behalf. An Authorised User is an individual an Accountholder authorises to use the services.
Supporting quotations
“Stripe Treasury for Platforms Accountholder” means a Connected Account, or Stripe Connect Platform using the Stripe Treasury for Platforms Services for User's own business purpose, who has successfully completed the onboarding requirements described in the Stripe Treasury for Platforms Dashboard.
“Stripe Treasury for Platforms Administrator” means the individual that a Stripe Treasury for Platforms Accountholder appoints to manage the Stripe Treasury for Platforms Services on its behalf.
“Treasury for Platforms Authorised User” means an individual that a Stripe Treasury for Platforms Accountholder authorises to use the Stripe Treasury for Platforms Services.
Charges & Financial Obligations · Context
Definitions: Treasury for Platforms Account Information, Dashboard and Product Guidelines
Account Information is Personal Data or business information a Connect Platform provides for its Connected Accounts so Stripe can check their eligibility for the services and make them available to Accountholders. The Dashboard is a user interface Stripe or a Connect Platform provides for an Accountholder to manage its Treasury for Platforms Account and Financial Accounts. The Product Guidelines are all product design, marketing, compliance, reporting and other guidelines and requirements a Stripe Entity establishes from time to time for the services.
Supporting quotations
“Stripe Treasury for Platforms Account Information” means Personal Data or business information that a Stripe Connect Platform provides on behalf of its Connected Accounts to enable Stripe to: (a) determine the Connected Accounts’ eligibility to access the Stripe Treasury for Platforms Services; and (b) make the Stripe Treasury for Platforms Services available to Stripe Treasury for Platforms Accountholders.
“Stripe Treasury for Platforms Dashboard” means a user interface Stripe or a Stripe Connect Platform provides that enables a Stripe Treasury for Platforms Accountholder to manage its Stripe Treasury for Platforms Account and Financial Accounts.
“Stripe Treasury for Platforms Product Guidelines” means all product design, marketing, compliance, reporting and other guidelines and requirements established by a Stripe Entity from time to time in connection with the Stripe Treasury for Platforms Services.
Qualifications & exceptions
The Product Guidelines can be changed from time to time.
Not stated here
The Product Guidelines are not supplied.
Charges & Financial Obligations · Context
Definitions: Treasury for Platforms Services (Preview), Territory (UK, Gibraltar, EEA) and Regulatory Requirements
The Treasury for Platforms Services are Preview Services that let an Accountholder create and maintain a Treasury for Platforms Account in which it can create Financial Accounts to store, spend and manage funds and make electronic payments and transfers. The Territory is (a) the UK and Gibraltar, for Financial Accounts provided by Stripe Payments UK Limited, and (b) the EEA, for Financial Accounts provided by Stripe Technology Europe Limited. Financial Account Regulatory Requirements are Law and the rules of the electronic funds transfer networks the services use.
Supporting quotations
“Stripe Treasury for Platforms Services” means the Preview Services that enable a Stripe Treasury for Platforms Accountholder to create and maintain a Stripe Treasury for Platforms Account where the Stripe Treasury for Platforms Accountholder can create Financial Accounts to (a) store, spend, and manage funds; and (b) make electronic payments and funds transfers to and from its Financial Accounts.
“Stripe Treasury for Platforms Territory” means (a) the UK and Gibraltar, for Financial Accounts provided by Stripe Payments UK Limited; and (b) the EEA, for Financial Accounts provided by Stripe Technology Europe Limited.
“Financial Account Regulatory Requirements” means Law and the rules of the electronic funds transfer networks the Stripe Treasury for Platforms Services uses.
Qualifications & exceptions
The services are Preview Services.
The Territory depends on which Stripe entity provides the Financial Account.
Not stated here
What Preview status changes for the User is set by other parts of the General Terms.
Charges & Financial Obligations · Restriction or exception
Definition: a Payout Delay includes outages, wrong details, Financial Partner failure and Force Majeure
A Treasury for Platforms Payout Delay is a delay to a Financial Account Transaction caused by (a) unavailability of a Financial Partner, Governmental Authority, telecommunications provider or internet service provider; (b) incorrect information, such as a bank account number, given to Stripe; (c) the User's equipment, software or technology; (d) a Financial Partner's delay or failure to settle a transaction to Stripe, including from its default, insolvency or bankruptcy; or (e) a Force Majeure Event. Stripe is not liable for losses from any such delay under Section 10.1.
Supporting quotations
“Treasury for Platforms Payout Delay” means a delay to a Financial Account Transaction caused by (a) the unavailability of a Financial Partner, Governmental Authority, telecommunications provider or internet service provider; (b) incorrect information, such as a bank account number, provided to Stripe; (c) User's equipment, software, or other technology; (d) a delay or failure of a Financial Partner to settle a Financial Account Transaction to Stripe, including as a result of a Financial Partner’s default, insolvency, or bankruptcy; or (e) a Force Majeure Event.
Qualifications & exceptions
Stripe's disclaimer for these delays appears in Section 10.1.
Not stated here
The terms do not say how long a delay may last.
Legal Rights & Agreement Rules · Context
Definition: Stripe Losses cover awarded amounts, penalties, fines and third-party costs including legal fees
Stripe Losses means all amounts awarded to the third party making a Claim, and all penalties, fines and third-party costs, including legal fees, paid by the Stripe Parties.
Supporting quotations
“Stripe Losses” means all amounts awarded to the third party making a Claim, and all penalties, fines, and third-party costs (including legal fees) paid by the Stripe Parties.
Account & Service Control · Restriction or exception
You access your account via the Dashboard and your platform's channels, and must follow your platform's documentation
The User may access its Financial Account and the Treasury for Platforms Services through the Treasury for Platforms Dashboard, and by any other means its Stripe Connect Platform provides. It may use the Dashboard to view its Account Information and conduct Financial Account Transactions, including adding funds, transferring funds and paying third parties. If it uses other Services connected to the account or Dashboard, additional terms may apply. The User must use the Dashboard only in line with the documentation its platform makes available. The Dashboard is a user interface that Stripe or the platform provides, and Account Information is Personal Data or business information a platform provides for its Connected Accounts so Stripe can check eligibility and provide the services.
Supporting quotations
4.1 Accessing User’s Financial Account.
User may access User’s Financial Account and the Stripe Treasury for Platforms Services through the Stripe Treasury for Platforms Dashboard, and by any other means User’s Stripe Connect Platform makes available to User. User may use the Stripe Treasury for Platforms Dashboard to view User’s Stripe Treasury for Platforms Account Information and conduct Financial Account Transactions, including adding funds to User’s Financial Account, transferring funds, and making payments from User’s Financial Account to third parties. If User uses other Services made available to User in connection with User’s Financial Account or the Stripe Treasury for Platforms Dashboard, as applicable, additional terms may apply to those Services. User must use the Stripe Treasury for Platforms Dashboard only in compliance with the documentation that User’s Stripe Connect Platform makes available to User.
“Stripe Treasury for Platforms Dashboard” means a user interface that Stripe or a Stripe Connect Platform provides that enables a Stripe Treasury for Platforms Accountholder to manage its Financial Account.
“Stripe Treasury for Platforms Account Information” means Personal Data or business information that a Stripe Connect Platform provides on behalf of its Connected Accounts to enable Stripe and its Affiliates to (a) determine the Connected Accounts’ eligibility to access the Stripe Treasury for Platforms Services; (b) make the Stripe Treasury for Platforms Services available to Stripe Treasury for Platforms Accountholders; and (c) fulfill their responsibilities to applicable Treasury Banks and electronic funds transfer networks that Stripe Treasury for Platforms Services use.
“Stripe Treasury for Platforms Services” means the Services that enable a Treasury for Platforms Accountholder to create and maintain a Financial Account where the Treasury for Platforms Accountholder can (a) store, spend, and manage funds; and (b) make electronic payments and funds transfers to and from that account.
Qualifications & exceptions
Other Services may carry additional terms.
Use must follow the platform's documentation.
Security & Safeguards · Restriction or exception
You must keep credentials and devices secure, report suspected access at once, and bear losses from delay
The User must keep its account credentials, and the devices it uses to reach its Financial Account, secure and confidential at all times. It must tell RSP immediately at the Treasury support address if there has been any actual or suspected unauthorized access to its credentials. Besides being responsible for transactions on the account, the User is responsible for all losses, damages and costs RSP and its Affiliates suffer because of its delay in notifying RSP.
Supporting quotations
4.2 Account Security.
User must keep User’s account credentials and the devices on which User accesses User’s Financial Account secure and confidential at all times. User must notify RSP immediately at treasury-support@stripe.com if there has been any actual or suspected unauthorized access to User’s credentials. In addition to being responsible for Financial Account Transactions conducted on User’s Financial Account, User is responsible for all losses, damages and costs that RSP and its Affiliates suffer as a result of User’s delay in notifying RSP of the unauthorized access.
Qualifications & exceptions
Suspected access must be reported, not only confirmed access.
Account & Service Control · Restriction or exception
You must be a business in the Territory, avoid foreign wires, follow regulations, report changes, stay sole owner
The User must (a) use the services only for a commercial business enterprise organized in the Treasury for Platforms Territory, meaning the United States and Puerto Rico or other jurisdictions Stripe permits; (b) not send or receive a wire transfer to or from a recipient outside the Transaction Territory; (c) comply with all Financial Account Regulatory Requirements; (d) promptly tell its Stripe Connect Platform of each change to the information it gives RSP and the platform, including country of citizenship, residence, principal place of business, and legal and tax status; and (e) not open a Financial Account for a sole proprietorship unless it is the sole owner, and remain sole owner throughout the Term. The Transaction Territory is any location Stripe makes available from time to time.
Supporting quotations
4.3 User Obligations.
User must:
(a) only use the Stripe Treasury for Platforms Services with respect to a commercial business enterprise organized in the Stripe Treasury for Platforms Territory;
(b) not use the Financial Account to send or receive a wire transfer to or from a recipient located outside the Transaction Territory;
(c) comply with all Financial Account Regulatory Requirements in connection with User’s use of the Stripe Treasury for Platforms Services;
(d) promptly notify User’s Stripe Connect Platform of each change to any information User provides or makes available to RSP and User's Stripe Connect Platform in connection with its Financial Account (including all information pertaining to User’s country of citizenship, residence, principal place of business, and legal and tax status); and
(e) not open a Financial Account for a sole proprietorship unless User is the sole owner of that business, and User must remain the sole owner at all times during the Term.
“Stripe Treasury for Platforms Territory” means the United States and Puerto Rico, or such other jurisdictions Stripe permits, as further described in the Documentation.
“Transaction Territory” means any location that Stripe may make available from time to time for Financial Account Transactions.
Qualifications & exceptions
Sole proprietorship accounts require the User to be the sole owner for the whole Term.
Charges & Financial Obligations · Company practice
You earn no interest unless your platform says otherwise, and Stripe may be compensated for placing your funds at a bank
Unless the User's Stripe Connect Platform advises otherwise, the User will not earn interest on funds in its Financial Account. Stripe may be compensated for placing the User's funds at a Treasury Bank.
Supporting quotations
4.4 Interest.
(a) No Interest Unless Advised. Unless User’s Stripe Connect Platform advises User otherwise, User will not earn interest on funds in User’s Financial Account. Stripe may be compensated for placing User's funds at a Treasury Bank.
Qualifications & exceptions
Interest depends on what the User's platform advises.
Not stated here
The terms do not state how Stripe is compensated or how much.
Charges & Financial Obligations · Procedure
If the account bears interest, RSP allocates it by average daily balance in whole cents, with rounding carried forward
If RSP sets up an interest-bearing Custodial Account and the User's platform tells the User its account will bear interest, RSP allocates accrued interest in proportion to the User's average daily balance over the preceding month against the average daily balance of all funds in that Custodial Account over the same period. Interest is allocated only in whole cents: a fraction below half a cent is rounded down and carried over to the following month, and a fraction of half a cent or more is rounded up and carried forward as negative accrual to the following month. A Custodial Account is a custodial account RSP holds in its own name at the Treasury Bank for all accountholders.
Supporting quotations
(b) Allocation of Interest. If RSP establishes an interest-bearing Custodial Account and User’s Stripe Connect Platform informs User that User’s Financial Account will bear interest, then RSP will allocate accrued interest under that Custodial Account in the proportion that User’s average daily balance during the preceding month bears to the average daily balance of all funds that are held in that Custodial Account over the same time period and calculated on the same basis. RSP will allocate interest to User’s Financial Account only in whole cents. Any fractional amount of the interest amount that would otherwise be credited to User’s Financial Account that is less than half of one cent will be rounded down and that fractional amount will be carried over to the following month. Any fractional amount of the funds equal to half of one cent or more will be rounded up and that fractional amount will be carried forward as negative accrual to the following month.
“Custodial Account” means a custodial account that RSP maintains, in its name, at the Treasury Bank, for the benefit of all accountholders using the Stripe Treasury Services.
Qualifications & exceptions
Applies only if RSP sets up an interest-bearing Custodial Account and the platform says the account bears interest.
Not stated here
The terms do not state the interest rate.
Legal Rights & Agreement Rules · Permission or license
You authorize RSP to comply with Legal Process without checking its validity, and to charge fees and costs for doing so
The User authorizes RSP to comply with each Legal Process relating to the User or its Financial Account that RSP or the User's platform receives, without needing to decide whether it was validly issued or is enforceable. If a Transaction Hold is in effect, RSP continues to charge all applicable fees even though the account cannot be closed. RSP may charge a fee for, and recover its costs of, complying with each Legal Process, and if the Regulatory Requirements permit will deduct them from the Available Balance. Legal Process is a writ of attachment, lien, levy, subpoena, warrant or other legal order, and a Transaction Hold is a restriction on funds availability Stripe places.
Supporting quotations
4.5 Legal Process.
User authorizes RSP to comply with each Legal Process relating to User or User’s Financial Account that RSP or User’s Stripe Connect Platform receives, without needing to determine whether that Legal Process was validly issued or is enforceable. If a Transaction Hold is in effect, RSP will continue to charge all applicable fees, even though User’s Financial Account cannot be closed. RSP may charge User a fee for, and recover RSP’s costs incurred in, complying with each Legal Process. If the Financial Account Regulatory Requirements permit, RSP will deduct those fees and costs from User’s Available Balance.
“Transaction Hold” means a restriction on the availability of funds in a Financial Account or on User’s ability to effect a Financial Account Transaction that Stripe places as a result of delayed funds availability, Legal Process, or other circumstances as determined by Stripe in its sole discretion.
Qualifications & exceptions
RSP need not check that the Legal Process is valid or enforceable.
Fees continue during a Transaction Hold.
Charges & Financial Obligations · Company practice
RSP need not notify you promptly when funds are added; you confirm receipt on the Dashboard
RSP is not obligated to notify the User promptly after funds are added to its Financial Account. The User can confirm through the Treasury for Platforms Dashboard whether RSP has received a Financial Account Transaction that adds funds.
Supporting quotations
5. Transactions on User’s Financial Account.
5.1 Adding Funds to User’s Financial Account.
RSP is not obligated to notify User promptly after funds are added into User’s Financial Account. User can confirm via the Stripe Treasury for Platforms Dashboard whether RSP has received a Financial Account Transaction that adds funds to User’s Financial Account.
Charges & Financial Obligations · Permission or license
By starting a transfer you authorize your platform to instruct RSP, and RSP deducts it before completion
By starting a transfer from its Financial Account through the Treasury for Platforms Dashboard, the User authorizes its Stripe Connect Platform to instruct RSP to make the transaction the User specifies. RSP may deduct the amount of each transfer the platform starts or approves from the User's Available Balance even if the transfer has not yet been completed.
Supporting quotations
5.2 Transfers from User’s Financial Account.
By initiating a transfer from User’s Financial Account via the Stripe Treasury for Platforms Dashboard, User authorizes User’s Stripe Connect Platform to instruct RSP to make the Financial Account Transaction User specifies. RSP may deduct the amount of each transfer that User’s Stripe Connect Platform initiates or approves from User’s Available Balance, even if the transfer has not yet been completed.
Qualifications & exceptions
Deduction can happen before the transfer completes.
Charges & Financial Obligations · Permission or license
RSP sets Cut-Off Times and may change them immediately without notice
RSP sets Cut-Off Times for various Financial Account Transactions and gives them to the User through the Treasury for Platforms Dashboard or otherwise in writing. RSP may change a Cut-Off Time from time to time, effective immediately and without notice. The User may contact RSP at any time to verify the Cut-Off Time. A Cut-Off Time is the time on a business day by which RSP must receive an instruction or request to process it the same day.
Supporting quotations
5.3 Funds Availability.
RSP establishes Cut-Off Times for various Financial Account Transactions and RSP will provide those Cut-Off Times to User through the Stripe Treasury for Platforms Dashboard or otherwise in writing. RSP may change the Cut-Off Time from time to time. Any change to the Cut-Off Time will be effective immediately and without notice to User. User may contact RSP at any time to verify the Cut-Off Time.
“Cut-Off Time” means the time on a business day by which RSP must receive an instruction or Financial Account Transaction request in order to process that instruction or request on the same day.
Qualifications & exceptions
Changes take effect immediately and without notice.