← All posts
SOC 2 vs PCI DSSPCI DSS for SaaSSOC 2 for startups

SOC 2 vs PCI DSS for SaaS: Does Hosted Checkout Change the Answer?

Map your payment flow to check PCI DSS duties, then ask customers whether they also need a SOC 2 report. Hosted checkout can narrow scope, but it does not settle either question.

A SaaS payment flow and a customer's report request lead to separate PCI DSS and SOC 2 decisions.
A SaaS payment flow and a customer's report request lead to separate PCI DSS and SOC 2 decisions.

If your SaaS company accepts card payments through a hosted checkout, you still need to check PCI DSS. Outsourcing payment processing can narrow the requirements you handle, but the PCI Security Standards Council says it does not remove a merchant’s responsibility. SOC 2 answers a different request: a buyer may want a CPA firm’s report on controls for the service it uses. Map the payment flow and ask for the buyer’s exact report requirement before promising either result.

SOC 2 vs PCI DSS: what decides each scope?

PCI DSS concerns payment account data and systems that can affect its security. The PCI Council’s merchant guidance includes entities that store, process, or transmit cardholder data or can affect its security. Payment brands and acquirers run compliance programs and set validation and reporting requirements; the Council maintains the standard. Your payment role, technical flow, and the entity accepting your validation determine what work to confirm.

SOC 2 is a CPA examination of controls for a described service against selected Trust Services Criteria. The report’s service boundary, criteria, type, and date or period determine what it covers. Ask the buyer what it will accept. A SOC 2 report does not replace PCI DSS validation, and PCI DSS validation does not give a buyer a SOC 2 report.

One company may have both jobs. For example, a SaaS vendor might collect its own subscription fees with a hosted payment page and also sell a data service to a buyer that requests a SOC 2 Type 2 report. The first question concerns its merchant payment flow. The second concerns the service in the buyer’s report request. If the SaaS product also lets its customers take card payments, that is a third flow to map because the vendor may have a separate service-provider role.

Does a hosted payment page take your SaaS company out of PCI DSS scope?

Do not decide from a processor logo or integration name. The PCI Council says merchants that outsource all processing still need to oversee the provider, understand shared duties, and generally validate compliance. Confirm the method with your acquirer or payment brand.

Write down what the customer’s browser loads when a card is entered:

  1. Does the browser leave your site for a page served by the processor, or does your site host any payment page elements?
  2. Does an embedded form come entirely from a PCI DSS compliant provider?
  3. Can your scripts, redirects, support tools, logs, or backend receive card details or change where the browser sends them?
  4. Which provider owns each payment step, and what do your agreements say about shared responsibilities?

These answers affect scope. The PCI Council explains SAQ A payment-page eligibility: all elements of the payment page must come from compliant service providers, and all other SAQ criteria must also be met. A processor’s iframe does not make every merchant implementation eligible. The Council also clarifies the script criterion for merchant pages with embedded payment forms; that particular SAQ A criterion does not apply to a merchant redirecting customers to the processor’s page. Other applicable requirements and eligibility criteria still need review.

If your app builds a card-entry form, receives full card numbers, or handles payment data in logs or support tools, stop treating the hosted-checkout example as your architecture. Record the actual flow and get qualified PCI scope advice before selecting a validation path.

Are you a merchant, a service provider, or both?

A founder can miss this distinction when a product helps its customers collect payments. Your company buying a processor for its own subscriptions is one relationship. Your product providing checkout, redirects, hosting, or other payment-related services to merchants is another. Map each separately.

The PCI Council says a service provider can be in scope if it can affect a customer’s cardholder data environment, even without directly storing, processing, or transmitting payment account data. Its examples include a service that facilitates payment data transmission through a URL redirect. The Council also says merchant SAQs do not set service-provider assessment scope. So do not reuse your company’s merchant SAQ as proof that the SaaS product meets a customer’s PCI DSS service-provider requirement.

Ask the customer and the entity accepting PCI validation which services and systems they expect covered. A qualified PCI assessor can test and document the assessment scope; the compliance-accepting entity sets the reporting route. Keep payment architecture, contracts, and shared responsibility records current because they are the basis for that discussion.

What should you do when a buyer also asks for SOC 2?

Get the customer’s report request in writing: report type, covered service, criteria, date or period, and deadline. Then define the SOC 2 service boundary with the CPA firm. The payment environment may be inside, outside, or related to that boundary; do not assume that passing one assessment sets the scope of the other.

Some facts can be collected once and reviewed for both efforts: a current architecture diagram, access list, change record, incident procedure, provider agreement, and approved evidence reference. Reuse the source fact, but label which requirement and period each reviewer needs. Neither an old diagram nor a link to a live dashboard proves that a control worked at the right time. The PCI assessor and SOC 2 CPA firm decide whether the evidence they receive supports their respective work.

For the SOC 2 side, FileGRC is a Git-native GRC workspace. JSON holds structured records, Markdown holds long-form work, and Git supplies the change history. You can review scope, controls, risks, and evidence references as files. Starter records are proposals, not compliance claims. FileGRC does not determine PCI DSS scope, run payment or other source systems, perform a PCI assessment, or conduct the SOC 2 examination.

If you are still deciding whether a report is worth starting, use the SOC 2 startup decision guide. Keep the PCI payment-flow decision on its own track so a buyer’s report request does not hide a separate payment obligation.

Open source · MIT

Run your SOC 2 program as files in Git.

Keep policies, controls, work, and evidence indexes in a repository your team and agents can inspect. Add optional FileGRC Autopilot email and Slack reminders to keep work moving.

Frequently asked questions

Does a SaaS company need SOC 2, PCI DSS, or both?

Check the payment role and data flow for PCI DSS, then ask buyers whether they need a SOC 2 report for your service. A company that accepts cards and sells to buyers requesting SOC 2 may need both. Confirm PCI validation with the acquirer or payment brand and SOC 2 scope with the buyer and CPA firm.

Does hosted checkout remove PCI DSS obligations?

No. The PCI Security Standards Council says merchants that outsource all payment processing still have responsibilities, including oversight of the provider, and generally validate compliance. A hosted flow may narrow applicable requirements if it meets the relevant eligibility criteria. Confirm the implementation and validation method with the acquirer or payment brand.

Can a SOC 2 report replace a PCI DSS assessment?

No. A SOC 2 report covers the described service and selected Trust Services Criteria in a CPA examination. PCI DSS has its own payment account data requirements and validation methods. Some control evidence may support both efforts, but each result has its own scope and reviewer.

Is SAQ A always right when a SaaS company uses a payment processor?

No. SAQ eligibility depends on the company's merchant role and the actual payment implementation. The PCI Security Standards Council says all criteria for the chosen SAQ must be met. Merchant SAQs do not apply to a SaaS provider assessed in a service-provider role.

What if customers take payments through our SaaS product?

Map that flow separately from how your company collects its own subscription fees. A SaaS service that can affect a customer's cardholder data environment may have PCI DSS service-provider duties even if a processor captures card details. Confirm the role, systems, contracts, and validation route with the customer, compliance-accepting entity, and qualified PCI assessor.

Can FileGRC manage a PCI DSS assessment?

FileGRC is a Git-native GRC workspace for SOC 2 work. It can keep SOC 2 scope, controls, and evidence references reviewable, but its starter records are proposals, not compliance claims. It does not determine PCI DSS scope, run payment systems, conduct a PCI assessment, or replace the CPA firm for SOC 2.