Skip down to the research record

PCI DSS status: 2 processors to check before a deal

Quota Forecast Editorial Team · Published · 11 min read

A signed deal depends on the PCI DSS status of the processor account its payment link uses, plus your business's own compliance.

This post compares two processors that many B2B teams look at: Stripe and Adyen. Both publish security documentation built around the same industry standard, the Payment Card Industry Data Security Standard, usually called PCI DSS. Neither processor's status removes work from your side. Below is what each claim says, what it does not say, and what to check before the first link goes out.

What PCI DSS covers

Stripe's integration security guide describes the standard this way: "The Payment Card Industry Data Security Standard (PCI DSS) is the global security standard for all entities that store, process, or transmit cardholder or sensitive authentication data." The phrase to notice is "all entities." The standard is not written only for processors. Whether your company is one of those entities depends on how card data moves through your systems.

That is a question to answer before the deal closes, not after. A revenue leader does not need to become a security engineer to ask it. They do need to know that the answer belongs to the business, not to the processor's website.

Why the processor's status is not the whole answer

The same guide says: "As a business accepting payments, you must do so in a PCI-compliant manner, and annually attest to this compliance." That sentence places the obligation on the business that accepts payments. A processor's own assessment covers the processor's side. It does not make your company's attestation for you.

The guide also includes a warning about scale: "If your business handles sensitive credit card data directly when accepting payments, you might be required to meet more than 300 security controls in PCI DSS." Two words in that sentence matter: "handles" and "might." The number of controls depends on how directly your business touches card data. Some businesses touch very little. Others touch a lot. You cannot tell which one you are until someone maps the flow of card data through your tools, your email, and your support process.

So the sentence "our processor is PCI compliant, so we are too" is not a safe thing to say to a customer or to your own legal team. It skips the step that matters most.

What Stripe's status says

The guide states: "Stripe is certified annually by an independent PCI Qualified Security Assessor (QSA) as a PCI Level 1 Service Provider meeting all PCI requirements." Break that into parts. The assessor is independent. The assessor is a QSA. The certification is renewed every year. The claim covers Stripe, in its role as a Level 1 Service Provider.

Read this as a claim about the processor's services, and keep it in its place. A processor can meet every requirement for its own service and still say nothing about how your team handles a card number that a customer sends by email. Read the phrase as a statement about one party, then ask the other party the same question.

The annual cycle is the detail most teams miss. A status that is renewed each year is only current as of the most recent assessment. If your contract runs for a year or more, the document you read today may not be the one that applies when the contract renews. Ask for the current attestation and write its date in your deal file.

What Adyen's status says

Adyen's PCI DSS compliance guide makes a parallel claim: "Adyen is a PCI DSS Level 1 Service Provider, with PCI DSS compliance assessed by an independent Qualified Security Assessor (QSA) annually."

Put the two claims side by side and the structure is the same. The difference is the verb. Stripe's claim says the company is "certified." Adyen's says its compliance is "assessed." For a procurement file, that difference is worth noting, but it is not a reason to prefer one processor on paper. What matters is that you can get the current document for whichever processor you use.

QuestionStripeAdyen
Stated statusLevel 1 Service ProviderLevel 1 Service Provider
Assessor namedIndependent QSAIndependent QSA
Cycle namedAnnuallyAnnually
Verb used"certified""assessed"

Which version of the standard applies

The same page says: "Now, when you assess your compliance, you must use PCI DSS v4.0.1 documents." It also adds: "If you already completed a v4.0 document, you do not need to complete the v4.0.1 document."

Your deal file should state which version your own assessment used and when it was completed. If that is unclear, put the question to whoever signs off on your compliance, before the links go out. Do not guess from the processor's version. The processor's version and yours are separate facts.

Transport security on the payment page

The same guide includes a specific rule for payment pages: "Payment pages must use a recent version (TLS 1.2 or above) because it significantly reduces the risk of man-in-the-middle attacks for both you and your customers." In plain terms, the rule covers the connection between the customer's browser and the page where card details are typed.

Find out where the payment link leads. If it goes to a hosted page run by the processor, the processor's configuration is the one that matters, and you can ask for written confirmation that the page meets this rule. If your own site or app collects card details, that page is yours to check. Ask your engineering team to confirm the TLS version on that page and on any other page a customer sees before paying.

Where card data can slip into your systems

Card data often reaches a business by a route nobody planned. A customer replies to an email with a card number. A sales rep types digits into a CRM note so finance can find them later. A support agent takes a payment over the phone and writes the numbers on a call sheet. Each of these moves card data into a system that the processor's assessment does not describe.

None of this is unusual, and most of it is avoidable. The simplest rule is to decide in advance which tool is the only place card details may be entered, and to tell the sales and support teams that every other route is closed. Write that rule into the deal handoff, so the account owner and the finance contact read the same thing.

The PCI Security Standards Council's merchant pages note: "Entry level option: PCI Awareness training is available online 24/7/365."

When two processors are in play

Some deals involve more than one payment route. A subscription may run through one processor while a one-off invoice runs through another. Your company may already hold an account with one processor and open a second for a new product line. In each case, the status you rely on has to match the flow it covers.

Map each payment flow to the processor account it uses, and file the processor's current attestation next to it. Do not assume that a status claim for one processor covers the flow handled by the other. Each flow needs its own line in the file. If a flow has no processor attached, treat it as an open item, not as a detail to sort out later.

Related guides: Multi-year deal billing: 6 figures from GitLab and Stripe · 4 Stripe renewal date rules to check before quarter close · Stripe subscription schedule phase limit: up to 10 phases.

Answering a customer's security questions

Enterprise customers often send a security questionnaire before they pay. The answer you give should describe your setup accurately and should not borrow the processor's claim as your own. Name the processor. Use the processor's own wording for its assessment. Then describe the parts of the payment flow that your company owns.

Keep promises narrow. If your agreements allow it, offer to share the processor's current attestation. Do not write that your company is "PCI compliant" unless your own assessment supports that exact statement. A short, accurate answer is worth more than a long reassuring one, because the customer's security team will check it against the documents they request.

A timeline for the deal

The status check is not a single step. It runs across the life of the deal.

At signing, confirm which processor the payment links will use, and record that processor's current attestation with its date. Before the first payment link is sent, finish your own scoping: which flows touch card data, which version of the standard your assessment uses, and where the TLS check was done. When the first payment comes through, confirm that it went through the flow you documented and not a side route.

After that, the calendar takes over. Put the processor's renewal date and your own attestation date into the same calendar. Set a reminder ahead of each date, so the file is current when a customer asks for it.

What to ask your security or finance lead

Your own assessment belongs to someone inside the business, and that person is the one who can answer the questions a processor cannot. Start with ownership. Who signs the annual attestation for your company? Who keeps the copy, and where is it stored? If that person leaves, does the file still make sense to the next person?

Next, ask about evidence. Which documents show what your team did, and when? Which records show that card data was scoped, and that the TLS check was completed on each payment page? A check that was done but never written down is hard to defend when a customer asks for proof. Ask for the records to be kept in one place, with dates and names attached.

What a status change would mean

A processor may lose a status, a new assessment may come back with different findings, or your business may decide to move part of a deal to a different processor.

Ask the processor, before you need to know, how it tells customers about a change in its status. Ask whether notices arrive by email, on a status page, or through your account contact. Then write down who on your side receives those notices and what they do when one arrives. A notice that lands in an unmonitored inbox is the same as no notice at all.

If the change affects the deal, the plan should already exist. Decide in advance who can pause the payment links, who tells the customer, and how an alternative route would be approved. Write those answers down before the first link is sent, not after the first problem.

Before a payment link goes to a customer on a signed deal, get written answers to these questions:

  • Which processor account will the link run under, and which legal entity holds that account?
  • What is the current PCI DSS attestation for that processor, and what is its date?
  • Which parts of PCI DSS remain with our business for this specific payment flow?
  • Which PCI DSS version did our most recent assessment use, and when was it completed?
  • Does any customer card data reach our email, support tools, spreadsheets, or call notes?
  • Which pages does a customer see before paying, and which TLS version do they use?
  • What happens to this deal if the processor changes its status, or if we move to a different processor partway through the contract?
  • Has everyone who takes card details completed awareness training, and where is the record kept?

Each question needs an owner. Assign one. A question with no owner is the one that gets missed.

How to decide which status the deal depends on

For a team that uses Stripe, the processor status to file is Stripe's current annual certification as a Level 1 Service Provider. For a team that uses Adyen, it is Adyen's current annual assessment under the same label. In both cases, the file should also hold your own attestation and the answers to the questions above. If one piece is missing, the deal is only partly supported.

Be careful with the contract wording, too. Name the processor you use. Leave the broader claims to your own assessment. A contract that says your company is certified when only the processor is certified will cause problems at the first audit question, and it may cause problems at renewal.

What the deal file should hold

Keep the file short enough that someone will read it, and complete enough that it answers a customer's questions without a meeting. A workable file usually holds the items in this table. These owners are illustrative; assign them to match your business.

ItemWhat it showsIllustrative owner
Processor accountsWhich account each payment link usesRevenue lead
Processor attestationStatus, assessor, scope, and dateFinance lead
Your attestationYour PCI DSS version and completion dateSecurity lead
TLS checkThe result for each page a customer seesEngineering lead
Open itemsWhat is unresolved, and who closes itDeal owner

Date each entry. A line that says the attestation is current, with no date, will be out of date the next time anyone reads it. Store the file where the sales, finance, and security leads can all open it, and keep one version of it rather than copies in several inboxes. For related record handling, see how to find deal attachments.

Review the file on the same calendar as the renewal dates. A file that is reviewed only when something breaks will always be a step behind the processor's own annual cycle.

Wrapping up

Keep Stripe's guide and Adyen's guide with the file for reference.

For a revenue leader, the useful outcome is not a longer list of certifications. It is a short, dated file that shows which processor the deal depends on, what your business still owns, and who will act when something changes. If that file exists before the first link is sent, the deal stands on evidence rather than a logo.

Sources