If the terms end other than for your breach, you have 30 days to ask Stripe to send card details to a new processor
If these Payments Terms terminate for reasons other than the User's breach, the User may, within 30 days after the termination date, ask Stripe in writing to provide all relevant Payment Method Account Details to an alternative PCI-DSS Level 1-certified payment processor the User identifies. Stripe will provide the details the User is entitled to receive to that processor to the extent commercially reasonable. Stripe may delay or refuse the request if it believes the named processor lacks sufficient systems or controls to protect the details, that their integrity may be compromised, or that Law or Financial Provider Terms do not allow the transfer.
Supporting quotations
7.2 Provision of Payment Method Account Details.
If these Stripe Payments Terms terminate for reasons other than User’s breach, then within 30 days after the termination date, User may request in writing that Stripe provide all relevant Payment Method Account Details to an alternative PCI-DSS Level 1-certified payment processor that User identifies to Stripe. Stripe will provide the Payment Method Account Details that User is entitled to receive to the named payment processor to the extent commercially reasonable.
Stripe may delay or refuse any request if Stripe believes the payment processor User has identified does not have systems or controls in place that are sufficient to protect Payment Method Account Details, that the integrity of Payment Method Account Details may be compromised, or that Law or Financial Provider Terms do not allow Stripe to provide the Payment Method Account Details.
Qualifications & exceptions
Not available where termination was for the User's breach.
The request must be in writing within 30 days after termination and name a PCI-DSS Level 1-certified processor.
Stripe's duty is limited to details the User is entitled to receive and to what is commercially reasonable.
Not stated here
Which details the User is 'entitled to receive' is not spelled out here.
Retention & Deletion · Procedure
Keep auditable records of consents, disclosures and each agent’s Authority, update your agreements, report to sellers
The User must retain auditable records of all Agentic Customer consents obtained and disclosures provided under Section 4.1, make any updates to its User Agreement (including its Privacy Policy) these terms require, and retain auditable records of its Authority, the express scope of permission an Agentic Customer gives an AI agent including spending limits, merchant restrictions and time bounds, at the time of each Agentic Transaction. On Stripe's written request, the User must promptly provide documentation and evidence of compliance. Where the Documentation or the User's agreements with Agentic Sellers or Customers require, the User must give each Agentic Seller usage reports, performance data and other relevant information about that seller's Agentic Transactions.
Supporting quotations
User must: (a) retain auditable records of all Agentic Customer consents obtained, and disclosures provided under Section 4.1 of these Agentic Commerce Agent Terms; (b) make all necessary updates to its User Agreement (including its Privacy Policy) that may be required for the purposes of these Agentic Commerce Agent Terms, and (c) retain auditable records of User’s Authority at the time of each Agentic Transaction.
At Stripe's written request, User must promptly provide Stripe with documentation and evidence to verify User's compliance with this Section 4.2.
User must provide to the Agentic Seller usage reports, performance data, and other relevant information about that Agentic Seller's Agentic Transactions where required by the Documentation or User’s agreements with Agentic Sellers or Agentic Customers.
“Authority” means the express scope of authority an Agentic Customer grants to any AI agent operating within the Agentic Interface to initiate Agentic Transactions on Agentic Customer's behalf including any applicable spending limits, merchant restrictions, or time-bound parameters.
Qualifications & exceptions
Authority records must be captured at the time of each Agentic Transaction.
Seller reporting applies only where the Documentation or the User's agreements require it.
Not stated here
No retention period for the records is stated.
Retention & Deletion · Procedure
You handle data subject requests about data moved to your Destination, including deleting it there when Law requires
The User is responsible for responding to Data Subject Requests, as defined in the DPA, relating to SDP Data transferred to a Destination, including deleting the applicable SDP Data from the Destination where Law requires.
Supporting quotations
2.3 Data Subject Requests.
User is responsible for responding to Data Subject Requests (as defined in the DPA) relating to SDP Data transferred to a Destination, including by deleting applicable SDP Data from the Destination where required by Law.
Qualifications & exceptions
Responsibility covers deletion at the Destination where Law requires.
Not stated here
The DPA (Data Processing Agreement) defining Data Subject Requests is not supplied.
Retention & Deletion · User right or choice
Connections Data duties outlive the Agreement; you may request the data, verify only, or get identifiers when leaving
The User's obligations under Section 3 continue after the Term and survive termination. The User may request to receive Connections Data as part of the Services, but if it uses only the verification portion it receives none. When the User stops using the Stripe Payments Services, it may ask Stripe for the account identifiers of each Connections End User's financial account used to process transactions via the Approved Payment Network (the ACH Network under the US Regional Terms, or ACSS under the Canadian ones) as part of its use of Stripe Payments.
Supporting quotations
3. Connections Data.
User’s obligations under this Section 3 will continue after the Term, and this Section 3 will survive termination of this Agreement.
3.1 Receiving Connections Data.
User may request to receive Connections Data as part of the Stripe Financial Connections Services. However, if User chooses to use only the verification services portion of the Financial Connections Services, User will not receive Connections Data. When User stops using Stripe Payments Services, User may request that Stripe provide to User the account identifiers of each Connections End User’s financial account used to process transactions made via the Approved Payment Network as part of User’s use of Stripe Payments Services.
“Approved Payment Network” means the ACH Network.
“Approved Payment Network” means the ACSS.
Qualifications & exceptions
Section 3 survives termination.
Verification-only use yields no Connections Data.
Not stated here
Which Approved Payment Network definition applies depends on the User's Regional Terms.
Retention & Deletion · Company commitment
Stripe stores Submitted Data 7 years on your instruction, deletes personal data on request, may delete at termination
The User instructs Stripe to store a copy of Submitted Data on its behalf for 7 years after verification, or, within Stripe's standard maximum retention period, for a different period the User sets per the Stripe Identity Services Documentation. The User is responsible for determining how long Law requires it to keep Submitted Data, for storing it (itself or through Stripe) for that period, and for fulfilling all data subject requests it receives about Submitted Data or Stripe Data. If the User or a data subject asks Stripe to delete an individual's Personal Data for the Identity Services, Stripe will delete the Personal Data it possesses. On termination of these terms Stripe may delete the copies of Submitted Data and Stripe Data it stored on the User's behalf.
Supporting quotations
7. Retention and Deletion of Data.
7.1 Data Stripe Stores on User’s Behalf.
The following terms govern Stripe’s storage of Submitted Data on User’s behalf:
(a) User instructs Stripe to store on User’s behalf a copy of Submitted Data for a period of 7 years following verification, or subject to Stripe's standard maximum retention period for Users, a different period as User may instruct according to the Stripe Identity Services Documentation. User is responsible for (i) determining how long Law requires User to store copies of Submitted Data; (ii) storing (either through User or through Stripe) the Submitted Data for the time period Law requires; and (iii) fulfilling all data subject requests that User receives with respect to the Submitted Data or Stripe Data. If User or a data subject requests that Stripe delete an individual's Personal Data with respect to the Stripe Identity Services, Stripe will delete any such Personal Data Stripe possesses.
(b) Upon termination of these Stripe Identity Terms, Stripe may delete copies of Submitted Data and Stripe Data that Stripe has stored on User’s behalf.
Qualifications & exceptions
The 7-year default can be changed by the User within Stripe's standard maximum retention period.
Deletion at termination is at Stripe's option ('may').
Not stated here
Stripe's standard maximum retention period is not stated in these terms.
Retention & Deletion · Company practice
Apart from storage on your behalf, Stripe may keep its own copy of Submitted Data and results as long as Law permits
Notwithstanding the Section 7.1 rules on data Stripe stores on the User's behalf, Stripe may retain a copy of Submitted Data and Stripe Data for its own purposes for as long as Law permits. This retention is not bounded by the User's 7-year instruction or by deletion requests under Section 7.1.
Supporting quotations
7.2 Data Stripe Stores for its Own Purposes.
Notwithstanding Section 7.1 of these Stripe Identity Terms, Stripe may retain a copy of Submitted Data and Stripe Data as long as Law permits.
Qualifications & exceptions
Retention for Stripe's own purposes is limited only by what Law permits.
Retention & Deletion · Restriction or exception
Fraud tools data is Stripe Data: you must delete it on termination or on request, unless Law requires you to keep it
Advanced Fraud Tools Data, and any subset of it, is Stripe Data under the Agreement. The User must promptly delete or destroy all of it in its possession or control (a) when these terms end or (b) at any time Stripe asks. The User may keep copies only to the extent Law requires, and then may use them only to comply with Law.
Supporting quotations
3.3 Advanced Fraud Tools Data.
Advanced Fraud Tools Data, and any subset thereof, is Stripe Data for the purposes of this Agreement. User will promptly delete or destroy all Advanced Fraud Tools Data in User’s possession or control received in connection with the Advanced Fraud Tools Services (a) upon termination of these Advanced Fraud Tools Terms; or (b) at any time upon Stripe’s request. However, in each case User may retain copies of the Advanced Fraud Tools Data to the extent Law requires, so long as User uses the Advanced Fraud Tools Data only to comply with Law.
“Advanced Fraud Tools Data” means Authorization Risk Scores, Card Testing Risk Levels, Merchant Dispute Rates, Fraud Disputability Assessments, Compromised Card Alerts, and all other data User receives through the Advanced Fraud Tools Services.
Qualifications & exceptions
The retention exception applies only to the extent Law requires it.
Retained copies may be used only to comply with Law.
Retention & Deletion · Company commitment
SMP honors valid Customer deletion requests in Stripe systems, tells you, and may let you review concerns
In line with applicable DP Law, SMP will honor valid deletion requests from Customers who bought through the Service. On a valid request, SMP manages deletion of the Customer's Personal Data within Stripe systems for SMP, including Customer Personal Data the User shared with Stripe and stored there. SMP will notify the User of the request and the actions taken, and will endeavor to give the User the chance to review the request with SMP if SMP has specific concerns or legal obligations in mind.
Supporting quotations
6.2 Customer Data Deletion.
In compliance with applicable DP Law, SMP will honor valid deletion requests from Customers who made a purchase through Stripe Managed Payments Service. Upon receiving a valid deletion request, SMP will manage the deletion of the Customer’s Personal Data within Stripe systems for SMP, including any Customer Personal Data User shared with Stripe and stored on Stripe systems. SMP will notify User of the deletion request and actions taken. SMP will endeavor to provide User the opportunity to review the request with SMP if SMP believes there are specific concerns or legal obligations.
Qualifications & exceptions
Applies to valid deletion requests under DP Law.
The chance to review the request is an endeavor, not a promise.
Not stated here
The terms do not state how quickly deletion happens.
Retention & Deletion · Restriction or exception
You handle deletion requests you receive directly and data you collect, and must cooperate and follow DP Law
SMP is not responsible for deletion requests the User receives directly from Customers, or for deleting Personal Data the User collects from Customers; the User must manage those requests. The User agrees to cooperate and to make sure any additional data it controls is handled in line with DP Law.
Supporting quotations
SMP is not responsible for managing any deletion requests that User receives directly from Customers or for the deletion of Personal Data that User collects from Customers. User is responsible for managing those deletion requests. User agrees to cooperate and ensure that any additional data User controls is handled in compliance with DP Law.
Qualifications & exceptions
Covers requests sent to the User directly and data the User itself collects.
Retention & Deletion · Restriction or exception
Radar Data is Stripe Data: delete it on termination or request, though you may keep copies Law requires
Radar Data is Stripe Data under the Agreement. The User must promptly delete or destroy all Radar Data in its possession or control received through the Radar Services (a) when the Radar Terms end and (b) at any time Stripe asks. The User may keep copies if Law requires.
Supporting quotations
7. Stripe Radar Data.
Stripe Radar Data is Stripe Data for the purposes of this Agreement. User must promptly delete or destroy all Stripe Radar Data in User’s possession or control that User received in connection with the Stripe Radar Services (a) upon termination of these Stripe Radar Terms; and (b) at any time upon Stripe’s request. User may retain copies of Stripe Radar Data, if required by Law.
Qualifications & exceptions
The retention exception applies if Law requires it.
Not stated here
Unlike the parallel fraud tools clause, this one does not limit use of retained copies.
Retention & Deletion · Restriction or exception
Stripe Tax Data is Stripe Data, and you must keep copies for the period Law requires
Stripe Tax Data is Stripe Data for the purposes of the Agreement. The User is responsible for retaining copies of Stripe Tax Data for the time period Law requires.
Supporting quotations
4.2 Stripe Tax Data.
Stripe Tax Data is Stripe Data for purposes of this Agreement. User is responsible for retaining copies of Stripe Tax Data for the time period required by Law.