Stripe Services Agreement - Services Terms

The list of Services Terms below does not indicate that a Service or part of a Service is available in a particular country. Please see the Stripe Website and Documentation for more information on Stripe’s Services and their availability.

For informational purposes only, we have translated the Stripe Services Agreement into selected languages.

Read more about the changes made November 18, 2025.

Stripe Financial Services Terms

Last modified: November 18, 2025

1. Stripe Financial Services.

These terms (“Stripe Financial Services Terms”) 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.

2. User's Obligations.

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.

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 must promptly update its Stripe Account with any changes affecting User, including changes affecting its business activities, Representatives, beneficial owners, and principals. 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.

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.

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.

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.

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. In addition, 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.

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.

3.3 Reserve.

(a) 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.

(b) 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.

(i) using funds User provides upon Stripe’s request;

(ii) using funds that a Stripe Entity owes to any User Entity for Transactions that the User Group accepts through the Stripe Payments Services; or

(iii) debiting the User Bank Accounts.

(d) 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.

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

(a) 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);

(b) all rights to receive credits and payments under this Agreement; and

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.

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.

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.

3.7 PCI-DSS.

Stripe provides the Services in a manner consistent with PCI-DSS requirements that apply to Stripe.

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. Please see the Stripe Privacy Center for more information on Stripe’s collection of end-customer data for this purpose and for guidance on how to notify Customers.

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.

“Insolvency Event” means the occurrence of any of the following (or any analogous procedure or step):

(a) as defined by Law, User is unable (or deemed to be unable) to pay its debts;

(b) user is the subject of a petition, resolution, order, or any other step in relation to winding up, bankruptcy, or equivalent proceedings;

(c) User stops, or threatens to stop, carrying on all or part of its business (except for the purposes of an amalgamation, reconstruction, or reorganization);

(d) User enters into a compulsory or voluntary liquidation, or a liquidator is appointed in relation to User or any of User’s assets;

(e) User is the subject of a petition for an administration order or an application for such an order, or a notice of intention to appoint an administrator to User is given, or any other step is taken by any individual or entity with a view to the administration of User under Law;

(f) a moratorium is agreed or declared with respect to all or part of User’s debts;

(g) User enters, or proposes to enter, into any compromise or arrangement of User’s debts with or for the benefit of some or all of User’s creditors generally, or in respect of a particular type of User’s debts;

(h) User begins proceedings or negotiations, or proposes or agrees, to reschedule, readjust or defer User’s debts;

(i) a liquidator, receiver, administrative receiver, administrator, manager, or other similar officer is appointed in respect of the whole or any part of User’s assets;

(j) an enforcement of any security over, or an execution, attachment, lien, levy, distress, or similar procedure is levied against, any of User’s assets;

(k) any legal proceeding, corporate action, or other procedure or step is taken in connection with appointing an administrator, administrative receiver, receiver, liquidator, manager, trustee in bankruptcy, or other similar officer in relation to User or any of User’s assets; or

(l) where any User Entity or shareholder of a User Entity is subject to any of the events listed in this definition.

“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.

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

“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.

“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.

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.

United States.

The following Regional Terms apply for Users in the United States.

5.1 Regulated Money Transmission.

Certain Services involve regulated money transmission under U.S. Law. 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 Services Terms specify otherwise. Stripe is not a bank, and does not accept deposits.

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

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. “Regulated Financial Services” means (i) the Services that the Central Bank of Ireland has authorised Stripe PSP to provide, which are listed at https://registers.centralbank.ie/FirmRegisterDataPage.aspx?firmReferenceNumber=C187865&register=63, and (ii) any other regulated financial services it is entitled to provide under applicable Law. 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.

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.

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

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. If necessary to allow the TPP to access User’s Payment Account, User may provide User’s Stripe Account credentials to the TPP. 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.

5.6 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. However, if Stripe uses safeguarded funds to fund a Reserve, then Stripe will no longer safeguard those funds on User’s behalf.

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.

5.8 Complaints.

If User has a complaint about Regulated Financial Services provided by Stripe, User may contact complaints@stripe.com. User can find more information about Stripe’s Complaints Policy here. If User’s complaint is unresolved, User may be entitled to refer it to the Irish Financial Services and Pensions Ombudsman (FSPO). User can find more information about the FSPO, its contact details and the eligibility requirements in Stripe’s Complaints Policy and at www.fspo.ie.

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.

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. “Regulated Financial Services” means the Services that the U.K. Financial Conduct Authority has authorised Stripe PSP to provide, which are listed at https://register.fca.org.uk/s/firm?id=001b000000pibOHAAY. 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.

5.2 Collection of Payment Proceeds.

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

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

5.6 Safeguarding of Funds.

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.

5.8 Complaints.

If User has a complaint about Regulated Financial Services provided by Stripe, User may contact complaints@stripe.com. User can find more information about Stripe’s Complaints Policy here. If User’s complaint is unresolved, User may be entitled to refer it to the Financial Ombudsman Service (FOS). User can find more information about the FOS, its contact details and the eligibility requirements in Stripe’s Complaints Policy and at www.financial-ombudsman.org.uk.

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.

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.

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.

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

5.2 Subacquirer Activities; Closed Loop Networks.

5.2.1 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. As used in this Agreement, “Subacquirer” has the meaning given in the Brazilian Central Bank's Resolution No. 150, dated October 6, 2021, or any other meaning adopted by the Brazilian Central Bank.

5.2.2 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. As used in this Agreement, "Closed Loop Network" is the English translation for "Instituidor de Arranjo de Pagamento Fechado", which has the meaning given in the Brazilian Central Bank's Resolution No. 150, dated October 6, 2021 (as amended), or any other meaning adopted by the Brazilian Central Bank.

5.2.3 If User uses the Services in breach of this section, then Stripe may immediately suspend or terminate User’s access to the Services.

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.

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.

5.5 Lien or Interest in Payment Card Receivables.

5.5.1. 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:

5.5.2 Data Sharing. 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.

5.5.3 Communication with Card Receivables Registration Offices. “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.

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.

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.

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.

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.

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 FCAC’s website.

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 Stripe Complaints and include all of the requested information so that Stripe may appropriately investigate the matter. Within User’s submission, User is asked to identify one or more of the following elements of Code that the complaint pertains 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 4: Notice to Merchants of Acquirer/Processor Fee and PCNO Core Fee Changes; Element 5: Limited Acceptance – Merchant Choice; Element 6: Negative Option Acceptance Not Allowed; Element 7: Renewal of Merchant Agreements and Related Service Agreements; Element 8: Discounts for Different Payment Methods; Element 9: Competing Domestic Debit Card Applications; Element 10: Separation of Payment Card Functions; Element 11: Provisioning to Devices; Element 12: Premium Cards; 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.

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. Pricing can be found on the Stripe Pricing Page.

5.3 Hypothec.

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. User consents to the Collateral securing the performance of the Secured Obligations and agrees that: (a) the Collateral constitutes monetary claims within the meaning of the Civil Code of Québec and notwithstanding any account documentation or agreement relating to the Collateral, 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.

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.

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.

5.3 Security Interest.

The security interest referred to in Section 3.4 (Security Interest) is taken by way of a fixed first charge.

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.

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.

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.

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, as well as under any other applicable regulation issued by the Bank of Mexico, the National Banking and Securities Commission or by any other government authority for aggregators, acquirers, or other participants of the payment processing networks in Mexico.

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.

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.

5.4 Information Stripe Obtains.

This Section replaces Section 2.3 (Information Stripe Obtains).

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 authorize Stripe to share any financial information obtained, including the results of the credit reports, with any Stripe Affiliates.

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.

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.

Singapore.

The following Regional Terms apply for Users in Singapore.

5.1 Specific Representations and Warranties.

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.

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.

Stripe Payments

Last modified: April 24, 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. Capitalized terms that are not defined in these Stripe Payments Terms have the same meanings given to them in the General Terms or the Stripe Financial Services Terms.

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.

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.

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. The Acquirer Terms, which are Financial Provider Terms for purposes of this Agreement, describe the Payment Methods to which they apply, and when they go into effect. 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 available on the Stripe Legal Page.

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.

3.4 Card Transactions.

(a) Card Network Rules. When accepting payment card Transactions, User must comply with all applicable Card Network Rules, including the Visa Rules specified by Visa, the Mastercard Rules specified by Mastercard, and the American Express Merchant Operating Guide specified by American Express. 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.

(b) Location and Identification. 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.

(c) Use of Cash. 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.

(d) Debt Repayment. 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.

(e) Surcharging. 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. User must notify Stripe at least 60 days before User intends to charge these fees or Taxes and must collect them only as part of the submitted amount of the Transaction.

(f) Use of Payment Card Account Data. 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.

(g) Waiver of Dispute Rights. User must not require, as a condition to card acceptance, a Customer to waive a right to dispute a Transaction.

(h) Non-Disparagement. User must not disparage any Card Network or any of their services, or submit any Transaction that harms any Card Network.

(i) Audit and Forensic Investigations. 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.

(j) Security Programs. 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.

(k) Limited Acceptance. 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.

(l) Minimum or Maximum Amounts. User must not establish minimum or maximum amounts for payment card Transactions, except as the Card Network Rules permit.

(m) Forms. 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.

(n) Acceptance. 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.

(o) Estimated Amounts. 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.

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.

3.6 Data Sharing.

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.

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.

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.

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.

4. Processing Transactions.

4.1 Payment Authorization Requests.

(a) Processing Transactions. 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.

(b) Transaction Responsibility. 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.

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

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:

(a) Settlement to User Bank Account. 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.

(b) Settlement to a Financial Account. Where Stripe settles funds to User's Financial Account, User will be using Stripe Treasury Services subject to the Stripe Treasury Terms.

(c) Settlement to Stablecoin Partner Wallet. Where a Stablecoin Partner settles funds in Stablecoin to a Stablecoin Partner Wallet, the Stablecoin Partner does so in accordance with the Stablecoin Partner Terms.

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.

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.

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.

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. These disclosures may include when, and under what circumstances, the Customer’s Payment Method will be charged, how the payment amount will be determined, and how future payments can be canceled. 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.

5. Actions Stripe May Take in Processing Transactions.

5.1 Reconciliation and Responsibility.

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.

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.

(a) Disputes.

(i) 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.

(ii) 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.

(iii) 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.

(iv) User remains responsible for all responses submitted in connection with a Dispute including the accuracy of all content and evidence submitted.

(v) 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.

(b) Refunds. 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.

(c) Reversals. Without limiting Stripe’s rights under Sections 5.3 - 5.5 of these Stripe Payments Terms, Stripe may initiate a Reversal if:

(i) the Payment Method Provider invalidates the Transaction;

(ii) User receives funds in error for any reason;

(iii) User was not authorized to accept the Transaction;

(iv) User receives funds related to activities that violate this Agreement, Law or Financial Provider Terms; or

(v) a Payment Method Provider or Payment Method Acquirer requires Stripe to do so under the applicable Financial Provider Terms.

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:

(a) has incurred or is likely to incur excessive Disputes, Refunds or Reversals;

(b) has submitted one or more Transactions for goods or services not immediately deliverable to the Customer without first obtaining Stripe’s consent;

(d) 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;

(e) is or is likely to become the subject of an Insolvency Event;

(f) has experienced or is likely to experience a deterioration of its business or financial condition that Stripe considers to be material;

(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;

(j) has experienced or is likely to experience a Change of Control;

(k) 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;

(l) 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

(m) has acted in a manner or engaged in business, trading practice or other activity that presents an unacceptable risk.

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.

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,:

(a) initiate Reversals;

(b) change the Payout Schedule or delay or cancel the payout of funds to the User Bank Accounts, Financial Account, or Stablecoin Partner Wallet;

(c) 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;

(d) suspend or terminate User’s ability to accept or process Transactions;

(e) manage Disputes that Stripe believes present an unacceptable risk to Stripe; and

(f) refuse to (i) process Transactions, and (ii) act upon Refund instructions.

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.

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.

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.

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.

9. PCI Standards Compliance.

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. If User intends to use a third-party service provider to store or transmit Payment Method Account Details (including Customer card account number and expiration date) then 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 notify Stripe of User’s intention to share Payment Method Account Details with the service provider. 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 can find information about the PCI Standards on the PCI Council’s website.

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.

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.

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.

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.

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.

“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.

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.

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 Provider. Once Stripe or SPC (as applicable) 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 or SPC (as applicable) settles those funds to User. 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. 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.

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.

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.

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.

15.2 Notice Period for Error Reconciliation.

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.

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.

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

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.

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.

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.

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.

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 Stripe’s Required Regulatory Disclosures site. Additional fees and information about Stripe’s pricing can be found on the Stripe Pricing Page, in the Agreement, and in the Stripe Dashboard.

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 Terms and Conditions for American Express Card Acceptance apply.

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.

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.

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.

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.

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.

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 Complaints Policy on handling Customer complaints.

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.

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.

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.

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.

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.

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.

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:

1. User will comply with American Express' Terms and Conditions and American Express' Data Security Policy, including User’s obligations concerning disputes, transaction processing, authorization, submission, prohibited uses and transactions, and protecting Customer information.

2. 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.

3. 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.

4. 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.

5. User will not discourage Customers from using American Express cards or disparage the American Express brand.

6. 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.

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

8. User will provide User’s contact information (including email and phone) that will allow User’s Customers to access their Transaction information.

9. 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.

10. 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.

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.

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.

The Payment Method Rules describe certain situations (e.g. where User has submitted a Transaction that fully complies with the 3-D Secure specification) where User will not be held liable for unauthorized 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).

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

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

New Zealand.

The following Regional Terms apply for Users in New Zealand.

15.1 Responsibility for Transactions, Disputes, Refunds and Reversals.

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.

15.3 Data Sharing.

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 Terms and Conditions apply.

15.2 Card Transactions: Location and Identification.

Section 3.4(b) (Card Transactions. Location and Identification) is replaced with the following:

(b) Location and Identification. 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, except that User may choose to disclose User’s address to Customers promptly upon request if User is an individual or sole proprietor. 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.

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.

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) a Customer requests a Non-Native Refund from Stripe or a Payment Method Provider because the Transaction was unauthorized, fraudulent or in error;

(b) required by Law or court order;

(d) Stripe reasonably determines that any of the specific triggers under Section 5.3 (Stripe Remedies – Specific Triggers) has occurred; or

(e) 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.

Singapore.

The following Regional Terms apply for Users in Singapore.

15.1 Card Network Rules.

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 (https://stripe.com/ae/legal/network-international). 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).

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. Capitalized terms that are not defined in these Stripe Adaptive Pricing Terms have the same meanings given to them in the General Terms or the Stripe Financial Services Terms.

2. Use of the Stripe Adaptive Pricing Services.

2.1 User Obligations. When using the Stripe Adaptive Pricing Services, User must:

(a) 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; and

(b) present each Customer with the option of paying in either the Integration Currency, or in the Customer’s local currency, as determined by Stripe.

2.2 Services Restrictions. User may only use the Stripe Adaptive Pricing Services in connection with:

(a) Transactions that Stripe processes via the Stripe Payments Services; and

(b) accepting a Customer’s payment for goods and services that User provides to Customers.

3. Stripe’s Rights.

3.1 Exchange Rate. 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.

3.2 Supported Currencies. Stripe may add or remove supported currencies at any time in its sole discretion without notice to User.

3.3 Interoperability with Other Services. 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.

4. Disclaimers.

4.1 Effect on the Cost of User’s Goods and Services. 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.

4.2 Effect on Other Services. 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.

4.3 Not a Foreign Exchange Service. The Stripe Adaptive Pricing Services do not provide a supply of foreign currencies, and are not a foreign currency exchange or similar service.

4.4 Financial Services Partner Fees. 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.

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.

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.

2. User Obligations.

2.1 Documentation. 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.

2.2 Stripe Elements. User must use Stripe Elements to facilitate Agentic Transactions.

2.3 Compliance. 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.

2.4 Cooperation. 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.

2.5 PCI Compliance. 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.

2.6 Payment Method Requirements. 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. User will provide such information, cooperation, and assistance as an Agentic Payment Method Provider may reasonably request to enable and operate the Agentic Commerce Agent Services. User will respond to any request under this Section promptly and in any event within the timeframe specified by Stripe or the Agentic Payment Method Provider. 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).

2.7 Data Quality. 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.

2.8 Risk Standards for Agents. 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.

3. Services Restrictions.

3.1 No Model Training. 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.

3.2 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.

3.3 Agentic Catalog Data Use Restriction. 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.

3.4 Stripe Radar Data. 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.

4.1 Consents. 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.

4.2 Compliance Records. 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.

4.3 Agent Transactions Reports. 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.

4.4 User Agreement with Agentic Customers. 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.

5. Stripe's Rights.

5.1 Transaction Submission. Agentic Sellers may use (a) the Stripe Payments Services to process Agentic Transactions, or (b) the Stripe Orchestrated Services to route Agentic Transaction data off of Stripe’s platform so that the Agentic Transaction may be processed by another payment services provider. 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.

5.2 Transaction Refusal. 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.

5.3 Seller Onboarding. 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.

5.4 Agentic Tokens. 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.

6. Agentic Catalog Data.

6.1 User Obligations. 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.

6.2 License to Agentic Catalog Data. 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.

6.3 Stripe Disclaimer. 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.

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.

8. Liability for Use of Agentic Commerce Agent Services.

8.1 Agentic Interface, User Systems and User’s Authority. 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.

8.2 Disputes and Refunds. Stripe is not responsible for, and Stripe Parties disclaim all liability with respect to, Agentic Disputes, Agentic Refunds, or other Agentic Transaction-related Losses.

8.3 Unauthorized Transactions. 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”).

8.4 Indemnification by User. 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.

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.

"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.

"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 a Agentic Sellers 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; 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, and which as of the Effective Date are described on that page as “Payment Method Terms”.

"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 Services Terms.

Stripe Agentic Commerce Seller Services (Preview)

Last modified: April 20, 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. Capitalized terms that are not defined in these Agentic Commerce Seller Terms have the same meanings given to them in the Agreement.

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.

3. User Obligations.

3.1 Stripe Profile. 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.

3.2 Order Fulfillment Responsibility. 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.

3.3 Merchant of Record. 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.

3.4 Fraud Mitigation. 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.

3.5 Use of Checkout and Shared Payment Tokens. 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. If required by the Documentation, User will report usage of the Shared Payment Token via the Payment Records API.

3.6 Acceptance of Payment Methods. 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

3.7 Platform Users and Participating Sellers. 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.

a. 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.

b. 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.

3.8 Terms of Service, Disclosures, and Consents.

a. 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.

b. 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 .

c. 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.

3.9 Indirect Taxes. User is solely responsible for calculating, collecting, and remitting Indirect Taxes on AC Transactions.

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 Link’s Agent Wallet, is not subject to this Section 4:

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.

a. User must provide (directly or indirectly through a third party product catalog service provider) all necessary Catalog Data to Stripe. 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 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.

b. 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.

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. Where an Integration does not involve Stripe identifying User in this way, such as in connection with Link’s Agent Wallet, this Section 5 will not apply:

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.

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.

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. User acknowledges that completion of an AC Transaction is subject to the AC Interface’s enablement of the transaction. User acknowledges that AC Interface Provider controls the discoverability of User’s and Participating Sellers’ (if applicable) goods and services. 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.

8. Fees.

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.

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.

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.

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. An “AC Customer” is a “Customer” under the Agreement and “Data Subject” under the Data Processing Agreement.

“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, 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.

“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.

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.

2. Third-Party Services; LLM Services and Fees.

2.1 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.

2.2 User may integrate directly with an LLM Provider or may use another Third-Party Service through which to integrate with an LLM Provider. 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.

2.3 User may be required to create an account with a Third-Party Service provider to use Third-Party Services.

3. User’s Obligations.

3.1 User is responsible for configuring the Stripe Billing Services for its needs and to comply with Law.

3.2 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.

3.3 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.

3.4 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.

3.5 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.

4. Services Restrictions.

4.1 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.

4.2 User must not use the Stripe Billing Services in ways expressly prohibited in the Documentation.

4.3 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.

4.4 User must not use LLM Services in violation of the LLM Services’ terms of service and policies.

4.5 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.

4.6 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.

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.

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.

Stripe Capital for Platforms

Last modified: November 18, 2025

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. Capitalized terms that are not defined in these Stripe Capital for Platforms Terms have the same meanings given to them in the General Terms, the Stripe Financial Services Terms, or the Stripe Connect Infrastructure Terms. The Stripe Capital for Platforms Services enable User’s Connected Accounts to obtain Stripe Capital Financing in conjunction with User’s Platform Services.

2. Stripe Capital Financing.

2.1 Nature and Use of Stripe Capital Financing.

(a) 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.

(b) Nature of Stripe Capital Advance. A Stripe Capital Advance is not intended to be, nor will it be construed as, a loan or any other lending transaction.

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.

2.3 Marketing to Prospects.

(a) Identifying Prospects. Upon Stripe’s request, User must cooperate with Stripe to identify Prospects for Stripe Capital Financing.

(b) Marketing Materials. 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.

(c) Marketing to Connected Accounts. 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.

(d) Removal of Marketing Materials. 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.

2.4 Prequalified Offers.

(a) User-Presented Prequalified Offer. 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.

(b) Stripe-Presented Prequalified Offer. 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.

(c) Revoked Prequalified Offers and Cancelled Stripe Capital Financings. 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.

(d) No Guarantee. 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.

2.5 Applying for Stripe Capital Financing.

(a) Applications 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.

(b) No Selection Permitted. 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.

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.

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.

2.11 Communication with Platform Users, Connected Accounts, Prospects, and Financing Recipients.

(a) General. 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. If User contacts a Platform, User, Connected Account, Prospect, or Financing Recipient for any other reason regarding the Stripe Capital for Platforms Services or Stripe Capital Financing, User must do so only in accordance with Stripe’s guidelines or instructions and the Documentation. Stripe will provide all Pre-Approved Responses and User must not modify a Pre-Approved Response in any way.

(b) Complaints. User must not use Pre-Approved Responses to respond to Complaints. User must, direct Platform User, 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.

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.

3. Servicing.

If applicable, the Servicer will provide all Servicing to Financing Recipients.

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:

(a) (i) 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; and

(b) 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.

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 Platform Service Terms will not subject Stripe to any consumer credit reporting Laws in an Approved Territory.

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.

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.

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.

7. Relationship of the Parties.

User remains solely responsible for all products and services User provides to User’s Customers.

8. 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.

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

Stripe Financial Services Terms

1. Stripe Financial Services.

2. User's Obligations.

3. Stripe’s Rights and Obligations.

4. Definitions.

5. Regional Terms.

United States.

European Economic Area.

United Kingdom, Switzerland, Gibraltar.

Australia.

Brazil.

Canada.

Hong Kong.

India.

Indonesia.

Malaysia.

Mexico.

New Zealand.

Japan.

Singapore.

Thailand.

Stripe Payments

1. Stripe Payments Services.

2. User’s Business.

3. Payment Methods and Transactions; Payment Method Rules and Payment Method Terms.

4. Processing Transactions.

5. Actions Stripe May Take in Processing Transactions.

6. Multi-Currency Processing.

7. Post-Termination Obligations.

8. User Information Updates.

9. PCI Standards Compliance.

10. Additional Obligations.

11. Fraudulent Transactions.

12. Liability for Failure to Transfer Funds.

13. Force Majeure.

14. Definitions.

15. Regional Terms.

United States.

European Economic Area.

United Kingdom, Switzerland, Gibraltar.

Australia.

Brazil.

Canada.

Hong Kong.

India.

Indonesia.

Malaysia.

Mexico.

New Zealand.

Japan.

Singapore.

United Arab Emirates.

Stripe Adaptive Pricing

1. Stripe Adaptive Pricing Services.

2. Use of the Stripe Adaptive Pricing Services.

3. Stripe’s Rights.

4. Disclaimers.

5. Definitions.

Stripe Agentic Commerce Agent Services (Preview)

1. Stripe Agentic Commerce Agent Services.

2. User Obligations.

3. Services Restrictions.

4. Disclosures, Information-Sharing and User Agreements.

5. Stripe's Rights.

6. Agentic Catalog Data.

7. License to User Systems.

8. Liability for Use of Agentic Commerce Agent Services.

9. Definitions.

Stripe Agentic Commerce Seller Services (Preview)

1. Stripe Agentic Commerce Seller Services.

2. Processing AC Transactions.

3. User Obligations.

4. Catalog Data.

5. Limited License to Marks.

6. Additional Stripe Rights.

7. AC Interface Provider Rights.

8. Fees.

9. Stripe Disclaimers.

10. Conflicts.

11. Definitions.