Stripe PCI DSS Compliance: 7 Essential Merchant Checks

Stripe PCI DSS compliance is a shared responsibility: Stripe can substantially reduce your workload when card details go directly to its payment systems. It does not make your business automatically compliant. You still need to understand your payment setup, complete the validation required for your account, and maintain the security measures that remain your responsibility.

Woman reviewing a Stripe PCI DSS compliance guide on a laptop with a secure online payment interface.

Start here: work through the seven merchant checks, then copy the integration-and-evidence note to track owners and open questions.

Start by identifying how customers enter their card details: on a Stripe-hosted page, inside Stripe fields embedded in your website, or through code that handles card data directly. That distinction matters more than simply saying, “We use Stripe.”

This guide focuses on online merchants in the US and UK. It does not determine the assessment route for a marketplace, payment service provider, or mixed online-and-in-person business.

Stripe PCI DSS compliance: 7 essential merchant checks

Use this as a first-pass work plan. The order below is an editorial recommendation for a small online merchant, not a substitute for the applicable SAQ or a promise of compliance. Mark an item complete only when you can point to evidence; “our developer handles it” is an owner assignment, not a result.

  1. Map every route to payment. Open your product page, cart, checkout, invoice link and failed-payment support process. Record the integration used on each route. Ask your developer to describe where the card fields originate and whether any custom code receives the full card number. Keep the explanation in the evidence note below.
  2. Match the reporting request to the real setup. Open the PCI documentation area in your Stripe Dashboard. Write down the requested document, responsible person and due date. If the questionnaire does not match the payment map, resolve the discrepancy with the organization accepting your validation before signing.
  3. Separate script eligibility from scan scope. Record whether payment is embedded or redirected. For embedded forms, retain the applicable implementation guidance and protection evidence. Separately record the ASV scope decision and the person responsible for it. A single “Stripe is compliant” email does not answer both questions.
  4. Find accidental collection paths. Walk through a support request with synthetic test data. Inspect the instructions staff follow, order notes and logging configuration. Ask whether chat, analytics or session-replay tools could capture payment inputs. Record what you checked and any collection path that needs correction.
  5. Assign access and key ownership. Identify who can deploy checkout changes, change tags, manage Stripe access and replace credentials. Confirm there is a current owner for each task. Use your secrets manager for credentials; the evidence file should contain a reference to the location, never the secret itself.
  6. Collect evidence that matches the service. Keep the provider documents covering your integration, the responsibility allocation, applicable passing scan reports and remediation records. Label each item with its scope and date. An old document for a different service should remain an open question.
  7. Set the next review trigger. Put the validation deadline and applicable scan dates on the operating calendar. Add a scope-review task to checkout migrations, new payment channels and processor changes. Name a backup owner so a staff absence does not turn a recurring requirement into a missed task.

If you only have 15 minutes: complete the payment map and identify the documentation deadline first. These two outputs tell you whom to involve and which uncertainty to resolve next. Fifteen minutes organizes the work; it does not finish a PCI assessment.

What Stripe handles—and what remains yours

Stripe’s integration security guide describes PCI compliance as a shared responsibility. Stripe undergoes an annual independent assessment as a PCI Level 1 service provider. Your business remains responsible for accepting payments in a compliant way and completing its own required attestation.

With an appropriate integration, Stripe collects sensitive payment details without routing them through your server. That reduces the systems and processes you need to assess. It does not prove that your website, administrative access, or customer-support workflow is secure.

The PCI Security Standards Council’s guidance for merchants that outsource payment processing makes the remaining duties explicit: check the provider’s compliance for the services used, retain appropriate written agreements, monitor its compliance status at least annually, and understand shared responsibilities.

Online merchant reviewing a secure e-commerce checkout form and payment security settings on a laptop.

Identify your integration before choosing an SAQ

A Self-Assessment Questionnaire, or SAQ, records an eligible business’s assessment against applicable PCI DSS requirements. You do not choose the shortest questionnaire because your company is small. Your actual payment flow and the applicable compliance program determine the route.

Stripe’s integration and documentation guidance provides these starting points. Eligibility still needs confirmation for your complete environment.

IntegrationStarting point
Stripe Checkout or ElementsSAQ A, where all eligibility conditions are met.
Legacy Stripe.js v2 formSAQ A-EP; review migration options.
Raw card data sent through your server to Stripe’s APISAQ D for an SAQ-eligible merchant.
Additional telephone, manual, or in-person paymentsAssess those channels separately; an online setup does not cover them automatically.

Some businesses require a Report on Compliance, or ROC, instead of an SAQ. Confirm your documentation requirements through Stripe’s PCI workflow and any other organization accepting your compliance evidence. If you are comparing professional help, our guide to PCI DSS assessment costs and the SAQ-versus-ROC distinction explains why the required reporting route changes the engagement.

Check embedded payment forms for script-security eligibility

An embedded payment form sits within your webpage. A hosted redirect takes the customer to the provider’s payment page. Both can reduce direct card-data handling, but they do not have identical SAQ A eligibility considerations.

The Council’s clarification of SAQ A script-security eligibility explains that merchants using embedded payment forms must confirm protection against script attacks affecting their e-commerce systems. The clarification describes two routes:

  • Use protective techniques, such as those described in Requirements 6.4.3 and 11.6.1, implemented by your business or a third party.
  • Obtain confirmation from the compliant provider that its embedded solution includes the relevant protections when implemented according to its instructions.

This particular eligibility criterion does not apply to a full redirect or fully outsourced payment-link flow. For an embedded Stripe integration, retain the guidance or confirmation applicable to your implementation. A general statement that Stripe is PCI compliant does not, by itself, document this specific condition.

Do not assume a hosted redirect removes scanning duties

The script-security exception for redirects is not a scanning exception. In its FAQ on ASV scans for SAQ A merchants, PCI SSC confirms that merchant e-commerce webpages using redirects or embedded iframes remain subject to the external vulnerability-scanning requirements included in SAQ A.

An Approved Scanning Vendor, or ASV, is a provider approved for this PCI scanning function. A routine website malware check does not substitute for the approved scan solution. Arrange the applicable quarterly scans, resolve findings, and retain passing results and required rescans.

Confirm the relevant domains, IP addresses, and hosting responsibilities with your ASV and compliance contact. A business that only sends customers payment links, with no merchant e-commerce webpage, needs a scope determination reflecting that different setup.

User completing two-factor authentication on a smartphone beside a laptop displaying a secure payment account login.

Keep card details out of support tools and logs

A checkout review is incomplete if staff collect card details elsewhere. As a practical check, trace a failed-payment request through customer service: does anyone ask for a card photo, paste a number into a ticket, record it during a call, or save it in an order note?

For a business designed around outsourced collection, give staff a secure payment-link procedure and tell customers to enter their own details there. Check whether debugging, session recording, or error-reporting tools capture payment inputs. Use test data for these checks.

There is also a firm storage restriction: PCI SSC prohibits storing sensitive authentication data after authorization, including card verification codes, even if encrypted and even when no full card number is present. Saving a CVV beside a payment token is not an acceptable workaround for future payments.

If you discover real card details in unexpected systems, stop that collection path and obtain qualified help to assess the exposure and handle the records securely. Do not circulate screenshots containing the data while investigating.

Protect your website and Stripe credentials

Stripe’s security guidance calls for payment pages using TLS 1.2 or newer and recommends minimizing third-party JavaScript. HTTPS protects transport; it does not establish that every script running on a page is trustworthy.

As an operational baseline, keep your commerce platform and payment plugin maintained, remove unused extensions, and review who can change checkout pages or publish tags. Use multifactor authentication for administrative accounts and remove access when staff or agencies no longer need it. Map these practices to your applicable requirements rather than treating this paragraph as a complete PCI checklist.

Follow Stripe’s secret API key guidance: keep secret keys in server-side secrets management, never expose them in browser code or repositories, and limit permissions. Publishable keys and secret keys have different purposes; a publishable key appearing in a webpage is not the same problem as a leaked secret key.

Document where keys are used and how to replace them. If a secret key is exposed, follow Stripe’s compromised-key procedure and review activity. Simply deleting the visible copy does not revoke a credential someone may already possess.

Turn the remaining work into a small evidence file

The following is a suggested working file, not an official replacement for your SAQ. Give each item an owner and a review date so renewal does not become a search through old emails.

  • Payment map: Every website and payment channel, the integration used, and where card details enter.
  • Validation record: Your confirmed reporting route, completed documents, submission status, and next deadline.
  • Provider evidence: Current compliance documentation covering the services used, agreements, and a record of shared responsibilities.
  • Technical evidence: Applicable scan results, remediation records, and embedded-form script-protection evidence where relevant.
  • Operating procedures: Access ownership, secure customer-support instructions, key handling, and incident contacts.

For budgeting, separate assessment assistance from scanning, engineering fixes, and ongoing maintenance. Our breakdown of PCI DSS compliance costs for e-commerce stores helps organize those categories before requesting quotes.

Copy a short integration-and-evidence note

Review date / responsible owner:
Stripe product and exact checkout integration / version:
Card-field origin and data path / implementation reference:
Other payment channels or custom code:
Documents requested in the account's PCI workflow:
Validation path confirmed by / date / reference:
Embedded-form eligibility guidance, if relevant:
Applicable scan scope / owner / evidence:
Remaining account, app, support and logging actions:
Unconfirmed point / owner / next review trigger:

This is a private working note, not an attestation. Record references to evidence, not card details, account secrets or API keys. A Stripe product name alone does not document the complete integration or every payment channel.

Revisit the setup when the business changes

Consider a hypothetical store that redirects customers to Stripe but later adds telephone orders. Its original online payment map no longer describes the whole business. The same issue arises when a developer replaces hosted fields with a custom form or introduces a second processor.

Make payment changes a trigger for reviewing scope and validation. Ask the person responsible for the change to document what data is collected, which systems receive it, and whether the existing assessment route still fits.

Your next step is to put the actual payment flow beside the PCI requirements shown for your Stripe account. Resolve any mismatch before signing an attestation. Stripe can remove much of the card-handling burden; your job is to keep the remaining responsibilities visible, assigned, and supported by evidence.

Questions to send your developer or payment agency

Use the following request to turn a vague assurance into a reviewable answer. Replace the bracketed text with your checkout URLs and integration details. Send it through your normal project channel without including cardholder data or credentials.

Please review [checkout URLs] and document the Stripe integration and plugin/version used on each payment route. Which party serves the card fields? Does any of our browser code, server code, logs, support tools or session recording receive full card numbers or verification codes?

For embedded forms, please provide the implementation reference and evidence addressing the applicable script-security eligibility condition. Separately, who will confirm ASV scan scope, arrange any required scans and resolve findings?

Please identify the owner of each remaining action, its evidence location, and any uncertainty that needs confirmation from Stripe, our acquirer or a QSA. Do not include secret keys or real card data in the response.

How to evaluate the reply: a useful answer names the integration, describes the data path and points to evidence. If the reply only says “we use tokenization,” ask where tokenization occurs and whether anything handles the card details before that step. Keep unanswered questions visible until the responsible person resolves them.

Stripe PCI DSS compliance FAQ

Does using a Stripe plugin make my store automatically compliant?

No. Stripe’s PCI compliance FAQ says the documentation obligation still applies when you use a third-party plugin. Record the plugin, its version and the actual payment flow. A plugin name alone does not establish what your customizations do.

Where can I get Stripe’s attestation and responsibility matrix?

Stripe directs account users to the Dashboard compliance documents area. Its Attestation of Compliance (AoC) concerns Stripe’s assessed service; it is not your business’s own attestation. Keep the responsibility matrix with the integration record so your team can see which tasks remain assigned to you.

Does Stripe perform my ASV scans?

Stripe says it does not provide ASV scanning. Where scans apply, engage an approved vendor and keep the results. Stripe says those results do not need to be submitted to it unless requested; retaining evidence and satisfying the applicable requirement remain separate from uploading a file.

Does a hosted redirect remove every website obligation?

No. The narrow script-eligibility distinction and the ASV scanning requirement answer different questions. Review the two sections above separately, and record your scope decision rather than marking all website work “not applicable.”

What should I do if the Dashboard requests SAQ D?

Ask your developer to compare the requested route with the real data flow. Raw card handling is a likely reason, according to Stripe. Do not simply choose SAQ A instead. Investigate the integration, discuss any discrepancy with the compliance contact, and reassess after a migration.

Editorial review: November 16, 2026. Checked the linked Stripe integration security and PCI documentation guidance, plus PCI SSC guidance on script eligibility and ASV scan applicability. This article explains published guidance; no merchant account, live integration or payment was accessed or tested.

Stay Updated with Kioptrix

Get practical guides, useful resources, and new articles delivered to your inbox.

No spam. Unsubscribe anytime. Read our Privacy Policy.