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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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”).
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.
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.
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.