E-commerce & D2C brands
Hosted checkout keeps you near SAQ A — but payment-page scripts and the site that redirects are still yours to secure.
SAQ A / A-EP6.4.3 · 11.6.1Take cards safely. Keep the audit small.
We map where card data flows, shrink your scope with tokenisation and segmentation, close the gaps against PCI DSS v4.0.1 and get you to a signed SAQ or a QSA's Report on Compliance.
4111 1111 1111 1111stored in clearPCI DSS v4.0.1 is the security standard the card brands require from every business that stores, processes or transmits cardholder data — or can affect its security. It is maintained by the PCI Security Standards Council and enforced through your acquiring bank. Its 12 requirements in 6 goals cover networks, stored data, vulnerability management, access, monitoring and policy. Depending on your merchant or service-provider level, you prove compliance each year with a Self-Assessment Questionnaire (SAQ) or a Report on Compliance written by a Qualified Security Assessor, plus quarterly external scans by an Approved Scanning Vendor.
XcellHost does the work in between: scoping, gap assessment, remediation, SAQ completion and evidence, and we coordinate the QSA and ASV partners who sign off — we are not a QSA or ASV ourselves. The biggest saving usually comes first: tokenisation, P2PE and segmentation can take most of your systems out of scope. Under RBI's card-on-file rules most Indian merchants should not be storing card numbers at all, and we can run PCI-ready infrastructure for what's left in our Tier IV data centre.
Every PCI engagement runs in three phases. You get a dated plan in week one and a progress report every fortnight.
We trace every path card data takes — web, terminals, phone, back office — and fix the CDE boundary before anyone fills in a form.
Tokenisation, hosted payment pages, P2PE and segmentation come first. Then we fix what remains — MFA, logging, hardening, scripts — with evidence.
We complete the SAQ with you, or prepare you for the QSA's on-site assessment, and coordinate quarterly ASV scans and the annual pen test.
Every SAQ and every Report on Compliance is a slice of these twelve. Click a requirement to see what it covers, what changed in v4 and the evidence an assessor asks for.
Version 4.0 added 64 new requirements. Thirteen applied at once; the other 51 were best practice until 31 March 2025 and are now assessed like everything else. v4.0.1 clarified wording without adding new ones.
First major rewrite since 2018; adds the customised approach.
All new assessments move to v4.
Clarifications and errata — no new requirements.
v4.0.1 becomes the only active version.
The 51 deferred requirements are now in every assessment.
6.4.3Payment page scriptsInventory, authorise and justify every script on the payment page.
11.6.1Page tamper detectionDetect unauthorised changes to payment pages, at least weekly.
8.4.2MFA into the CDEMulti-factor for all access into the CDE, not just remote admin.
8.3.612-character passwordsLonger minimums, with letters and numbers, where passwords are used.
5.4.1Anti-phishing controlsAutomated mechanisms to detect and protect staff from phishing.
10.4.1.1Automated log reviewUse tooling, not eyeballs, to review audit logs.
12.3.1Targeted risk analysisJustify how often you do flexible-frequency activities.
3.4.2No PAN copy over remote accessTechnical controls stop staff copying PAN when working remotely.
11.3.1.2Authenticated internal scansInternal vulnerability scans must log in to the systems they test.
v4 also adds a customised approach: meet a requirement's objective your own way, with a documented risk analysis the QSA validates. It suits mature teams; most clients start with the defined approach.
Levels follow your yearly card transaction volume. Move the slider to see where you land and what your acquirer will ask for.
Thresholds shown follow the common card-brand model; each brand and your acquirer set the final rules. A business that suffers a breach can be moved to Level 1 regardless of volume.
Scans, tests and reviews recur weekly, quarterly and every six months. Miss one quarter's passing ASV scan and the AoC can't be signed. We run this calendar with you.
The SAQ follows how you take cards, not how big you are. Pick every channel you use — we'll show the questionnaire for each, roughly how many requirements it holds and what makes you eligible.
Guide only. Your acquirer confirms the SAQ you must use; requirement counts are approximate and depend on the SAQ revision and items marked not applicable.
Start from a typical setup, then switch on the scope-reduction moves one by one. Each dot is 1% of your systems: orange stores, processes or transmits card data, blue is connected to it, grey is out of scope.
Illustrative model using typical environments, not an assessment. Real scope is confirmed by data-flow discovery and validated by your QSA or acquirer.
Everything is yours, in Word, Excel, Visio or your GRC platform. Assessors get a clean evidence library instead of a shared drive to dig through.
Req 1.2.4Card data-flow diagramsEvery channel from capture to settlement, including the paths nobody remembered.
Req 1.2.3Network diagramCDE, connected systems and every connection to untrusted networks.
Req 12.5.2Scope document & inventorySystem components in scope, with the reasoning behind every exclusion.
All 12Gap assessment reportEach sub-requirement rated in place, partial or missing against v4.0.1.
PlanRemediation roadmapFixes ordered by risk and effort, with owners, dates and scope wins first.
Req 12.3.1Targeted risk analysesThe written justifications v4 now needs for flexible-frequency controls.
Req 12.1Policy & procedure setSecurity policy and operating procedures for each requirement, for your stack.
Req 12.10Incident response planCard-brand, acquirer and CERT-In notifications built in, with a tabletop test.
Req 12.8–12.9Service-provider registerEvery third party touching card data, its AoC status and a responsibility matrix.
Req 6.4.3 · 11.6.1Payment page script controlScript inventory, authorisation and a weekly tamper-detection routine.
Req 12.6Awareness trainingCard-handling and phishing sessions for staff, with attendance as evidence.
SAQ · RoCSAQ & AoC, or RoC packCompleted SAQ and AoC for your acquirer, or the evidence pack your QSA works from.
Phases overlap so nobody waits. Pick a package to see its typical plan — the real one is fixed after scoping.
Pick by how you validate: a self-assessment, a full gap-and-fix for SAQ D, or Level 1 readiness for a QSA's Report on Compliance. QSA and ASV fees are separate. All prices are indicative and exclude 18% GST.
Prices are indicative placeholders until confirmed on your quotation. QSA, ASV and penetration-test fees, travel outside Mumbai and tooling licences are not included.
Most PCI gaps sit in logging, monitoring, hardening and hosting. We operate all four every day for our own certified environment — ISO 27001, 27017, 27018, 20000-1 and SOC 2 Type I & II.
We push tokenisation, hosted pages and segmentation before remediation, so you fix fewer systems and buy a smaller assessment.
01Log collection, automated review, file-integrity and payment-page monitoring can run on our Mumbai SOC if you don't have one.
02Segmented, hardened and monitored infrastructure in our Tier IV data centre, with a written responsibility matrix for your assessor.
03We're not your QSA or ASV, by design. We coordinate with independent partners and can recommend several to quote.
04Card-on-file tokenisation, payment aggregator expectations, CERT-In reporting and the DPDP Act folded into one control set.
05One project price in rupees with milestone billing — no hourly meter while you dig out evidence.
06Most clients come to us because an acquirer, a payment partner or an overseas customer asked for an AoC. RBI rules then decide how much card data you're allowed to keep.
Hosted checkout keeps you near SAQ A — but payment-page scripts and the site that redirects are still yours to secure.
SAQ A / A-EP6.4.3 · 11.6.1Service providers usually validate at Level 1 with a QSA, and RBI's PA framework expects PCI DSS compliance.
Service provider L1RoCCard-linked onboarding, repayments and stored tokens bring APIs, mobile apps and cloud workloads into scope.
TokenisationCloud CDEHundreds of terminals across stores. Validated P2PE can cut most of them out of scope.
SAQ P2PE / B-IPReq 9.5Taking payments by phone for global clients puts desktops and call recordings in scope unless you mask them.
DTMF maskingPause-and-resumeBooking engines, front desks and fee portals mix online, terminal and phone channels — often one SAQ per channel.
Multi-channelSAQ C-VTSince 1 October 2022, nobody in the payment chain except card issuers and card networks may store full card data for card-on-file payments; tokens replace it.
Req 33.2.13.5.1Payment aggregators are expected to comply with PCI DSS and to ensure the merchants they onboard don't keep card data.
12.812.9AoCNotify CERT-In within 6 hours, keep ICT logs for 180 days and treat cardholder names and contacts as personal data under the DPDP Act.
Req 1012.103.1Not legal advice. PCI DSS supports these obligations but doesn't replace them; confirm specifics with your acquirer, payment partner or legal team.
No. With an SAQ, your own officer signs the Attestation of Compliance. With a Report on Compliance, an independent Qualified Security Assessor (QSA) assesses you and signs. External scans must come from an Approved Scanning Vendor (ASV). XcellHost prepares you, completes the paperwork with you and coordinates QSA and ASV partners — their fees are separate.
An SAQ is a self-assessment: you answer the requirements that apply to your payment channel and sign the AoC. A Report on Compliance (RoC) is an assessment by a QSA, who tests your controls and writes the report. Level 1 merchants and Level 1 service providers normally need a RoC; others usually self-assess, but your acquirer can ask for more.
Yes, but far less. If the gateway hosts the payment page or iframe, you're usually on SAQ A — you still secure the website that sends customers there, manage your service provider and keep the AoC current. If your site loads the gateway's JavaScript or posts card data directly, it's SAQ A-EP and much more of your site is in scope.
Not entirely. Tokens that can't be turned back into card numbers by you take your storage systems out of scope, but the systems that capture or pass card data to the tokenisation provider are still in. Under RBI's card-on-file rules most Indian merchants should hold tokens rather than card numbers anyway, which makes this the cheapest scope reduction available.
Levels are set by each card brand from your yearly transaction count and confirmed by your acquirer. A common model: Level 1 above 6 million transactions a year, Level 2 from 1 to 6 million, Level 3 from 20,000 to 1 million e-commerce transactions, Level 4 below that. Service providers are Level 1 above 3 lakh transactions a year. Try the level slider above, then confirm with your acquirer.
An ASV scan is an external vulnerability scan of your internet-facing systems in scope, run by a PCI-approved scanning vendor. Where your SAQ or RoC requires it, you need a passing scan every quarter and after significant changes. Failures must be fixed and rescanned. Our ASV management add-on schedules the scans, triages findings and files the passing reports.
The 51 future-dated requirements in PCI DSS v4 became mandatory. The ones we see missed most are payment-page script management and tamper detection (6.4.3 and 11.6.1), MFA for all access into the CDE (8.4.2), 12-character passwords (8.3.6), automated log review (10.4.1.1), anti-phishing controls (5.4.1) and targeted risk analyses (12.3.1).
A clean SAQ A or P2PE engagement is often done in about six weeks. An SAQ D gap-and-remediation project typically runs three to four months. Level 1 readiness for a QSA assessment takes around six months, longer if large remediation or scope reduction is needed. The timeline above shows the phases for each.
SAQ D and RoC entities need an annual internal and external penetration test and a test after significant changes; if you rely on segmentation, it must be tested too — every year for merchants and every six months for service providers. Many lighter SAQs don't require one. We scope the test and coordinate an independent tester.
Yes. We can run segmented, hardened and monitored infrastructure for your CDE in our Tier IV data centre in India, with a written responsibility matrix showing which requirements we cover and which stay with you. Your assessor reviews that matrix and our evidence as part of your assessment. Ask for a hosting quote with your consulting scope.
A lot of the governance does — policies, risk assessment, incident response, supplier management and awareness training. PCI DSS is more prescriptive on technical detail such as stored-data rules, scan and test frequencies, MFA and log retention, so expect specific gaps. We map your existing controls first so nothing is done twice.
No. They are indicative and exclude 18% GST. Your fixed fee is confirmed after a short scoping call and appears on your XcellHost quotation. QSA, ASV and penetration-test fees and travel outside Mumbai are quoted separately.
A 30-minute call covers your channels, gateway, card storage and volumes. You get a scope view, the likely SAQ or RoC path and a fixed-fee plan in rupees — QSA and ASV options included.
PCI DSS shares much of its governance with the rest of our consulting services. Combine them and evidence once.