Skip to content
EA

If it needs evidence from several people and someone to sign it off, hand it to EA.

Browse the full library

PCI DSS · For payments and compliance leads

Each year, the same attestation. Never the same evidence.

EA takes your PCI DSS year: the scope, the questionnaire and the Attestation of Compliance. It fills them from your own records, asks each owner for the rest, and brings the attestation to your Finance Director to sign.

Try EA free. No card needed.

Organisations that run work on EA

The work

Card payments reach well beyond the till.

  • Scope comes first

    Before a single requirement is answered, someone has to work out which systems touch card data, and confirm it again each year.

  • Your providers count too

    The payment page, the hosting and the contact centre’s call recording each sit with a provider, and your attestation leans on theirs being current.

  • Evidence expires between years

    Scans fall due every three months, access reviews every six and training every year. By the time the questionnaire opens, some are already out of date.

Keep the scope known, each provider current and each record in date, and the attestation goes to your acquirer with nothing left to find.

What EA does

One year’s assessment, through to the signature.

Shown on a merchant’s self-assessment. If an assessor visits instead, the same stages gather what they will test.

01 / 05

  1. EA

    Reads your network diagrams, card data flows and system inventory, and drafts the scope: each data flow by payment channel, each system in or connected to the card data environment, each third-party connection, and why each segmented system sits out of scope.

    Your team

    The Head of IT confirms the scope, each year and after any significant change, and your acquirer confirms the route: a self-assessment questionnaire (SAQ), or an assessment by a Qualified Security Assessor (QSA).

  2. EA

    Answers each requirement in the SAQ from your policies, configurations and records, with the source beside each answer. Autofill 

    Your team

    The owner of each requirement corrects the detail before anything is approved.

  3. EA

    Sends one request per owner for what the documents don’t show, such as the contact centre’s call recording settings or the list of scripts running on your payment page, and follows up. EA Agent 

    Your team

    The Payments Operations Manager and the E-commerce Manager answer for their parts, and the Head of IT sees what is still open.

  4. EA

    Keeps the list of providers that handle card data for you, with each one’s attestation, its date and the requirements it manages, checks each at least once a year, flags the one that has expired, and asks the Procurement Lead to get the current one, following up until it’s filed. Knowledge Library 

    Your team

    The Procurement Lead requests the current attestation from the provider, and Legal holds the written acknowledgements.

  5. EA

    Fills the Attestation of Compliance from the approved questionnaire, and reopens an answer edited after approval. Approvals 

    Your team

    The Finance Director approves and signs the attestation in EA, and your team sends it to your acquirer.

Illustrative data: stage by stage

Pick a requirement, and watch EA answer it from your own records.

Book a demo

Year two

Next year opens with this year’s answers.

  • Scope, confirmed again

    The yearly scope check starts from this year’s approved scope, and EA takes a significant change in between, such as a new payment page provider, to the Head of IT as it happens.

  • Providers, watched

    Each provider’s attestation carries its date, and EA drafts the request for the new one as the old one lapses, for the Procurement Lead to send.

  • Records, kept in date

    As each scan, access review and training record comes due, EA asks its owner for the new one, so next year’s questionnaire opens with its records current.

Illustrative data

Then a customer asks for your attestation.

If you handle card data for others, your customers will ask for your Attestation of Compliance and which requirements are yours, theirs or shared, as Requirement 12.9.2 requires. EA drafts that responsibility matrix from your approved scope, and you share the attestation by a link you can revoke.

Read about customers’ security reviews in EA 
Illustrative data

EA’s own security

Your assessment, without a single card number.

Your scope, diagrams and questionnaire map exactly where card data travels, so only the people you choose see them. Card numbers don’t need to go into EA. We ran our own ISO 27001 certification on EA: read how it ran on the ISO 27001 page.

  • Hosted your way

    EA’s cloud in a region you choose, hybrid options or on-premises. Data never used to train the models EA runs on.

  • Access

    Single sign-on, which you can enforce, and an access list for each workspace.

  • Support access

    EA staff see your data only in a time-limited window you open.

  • Testing

    An independent firm runs a penetration test on EA every year.

  • Security contact

    EA’s security team is at security@eaglobal.ai.

In the demo, see who can open your scope, and how you take that access back.

Book a demo

Why EA for PCI DSS

Compared with how it’s done today.

Compared withWhat it does wellWhat EA adds
Doing it by handYour team knows its own systems, and there’s no new tool to learn.This year’s approved scope and provider list become next year’s starting point, and only what has changed goes back to its owner.
A QSA or PCI consultantKnows the standard, scopes well and, as a QSA, assesses you.EA gathers the evidence they test and keeps it filed by requirement, ready when they arrive.
Compliance softwareTracks requirements and pulls evidence from connected systems.Fills in the self-assessment questionnaire and the Attestation of Compliance documents, not a tracker beside them, and takes each open requirement to the person who can close it.

FAQ

Questions from payments and compliance leads.

SAQ D for Service Providers is the only self-assessment questionnaire for service providers. The payment brands and your acquirer decide whether you can self-assess or need a QSA’s Report on Compliance.

Your acquirer, if you take card payments as a merchant, or your customers and the payment brands, if you handle card data for others. Where a Report on Compliance is required, a QSA assesses you and signs their part; your Finance Director signs the attestation, and EA prepares the work behind it.

EA answers from your policies, configurations and records, with the source beside each answer. Where there is nothing to show, say no record that the card terminals in your shops were checked for tampering this year, it marks the requirement “Needs evidence” and leaves it open for its owner.

Keep it out, as your scope does. The assessment describes where card numbers travel, such as the calls your contact centre’s provider records, without holding any of them. Your workspace’s access list decides who sees it, and an assessor sees only what you share, by a link you can revoke.

Your QSA still assesses you and signs their part of the attestation. EA takes their evidence list to each owner and keeps what comes back with its requirement.

Yes. Hand EA last year’s SAQ and attestation, your policies and your providers’ attestations as they are; our Customer Success team helps with exports from other platforms. Plans differ by the number of autofills, the workspaces you need and the size of your knowledge library; see the pricing page.

Your next PCI DSS attestation, without scoping it all again.

From the scope to your Finance Director’s signature.