Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Payments & Reconciliation 6 min read

PCI DSS scope for small merchants: problems and fixes

Why small-merchant PCI scope grows, the symptoms that reveal it, and the fixes that keep card data out of your systems.

E
EncryptTechBD · 0 comments
Hands using a calculator beside a calendar
Photo: Tevarak / StockSnap

Scope problems rarely appear as a clean error message. They show up as a questionnaire that feels too easy, a plugin that “handles payments”, a shared hosting account nobody can describe, or a scan report that lists systems the business did not know were exposed. Each is a symptom of a boundary that was assumed rather than verified.

This guide is for the small merchant who has already read a cost guide or received a questionnaire and now needs to understand why the scope keeps growing. It follows a simple structure: symptom, likely cause, fix and prevention. It does not replace advice from your acquirer or a qualified assessor.

1. The questionnaire does not match the checkout

Symptom: you complete a self-assessment questionnaire that assumes card data never touches your systems, but customers type card numbers into a form on your domain.

Likely cause: the integration changed from a hosted redirect to an iframe, or from an iframe to a direct post, and nobody updated the scope. The questionnaire type follows the actual data flow, not the original contract.

Fix: draw the payment flow from the customer’s browser to the acquirer. Note every domain, script, server and database that sees the card number, even briefly. Ask the gateway to confirm the integration type in writing.

Prevention: add a payment-flow review to the change process for every new gateway, plugin or checkout redesign. Keep the evidence with the assessment file.

2. A plugin or custom form stores card data

Symptom: the payment provider says it is compliant, but the site’s database, logs or backups contain card numbers or security codes.

Likely cause: a plugin saves the full request for debugging, a custom form posts to the merchant’s server before forwarding, or an abandoned checkout module retains payment fields.

Fix: search the application, database, logs and backup copies for card-number patterns. Stop collection first, purge what should not exist, then correct the integration so the merchant server never receives the data.

Prevention: require a written data-flow diagram from the developer, review what the plugin stores after every update, and ban card data from support tickets and chat.

3. Shared hosting and agency access widen the boundary

Symptom: the merchant believes only the website is in scope, but the hosting account, staging site, file manager and agency laptops can all reach the application.

Likely cause: scope was defined as “the checkout” rather than “every system that can connect to the cardholder data environment and affect its security”.

Fix: list every account, integration and person who can deploy code, read the database or change server configuration. Remove access that is not required, separate staging from production, and record who retains access.

Prevention: review access quarterly and at the end of every agency engagement. Treat hosting and support accounts as part of the payment boundary, not as an IT detail.

4. Segmentation exists on paper but not on the network

Symptom: a diagram shows a clean boundary around payment systems, but the office network, marketing site and payment server share one flat network and one administrator account.

Likely cause: segmentation was designed but never tested. Shared switches, permissive firewall rules or a single domain administrator quietly reconnect the environments.

Fix: test the boundary rather than describing it. Attempt connections from each environment to the card-data systems and record the result. Correct the rules, accounts and routes that allow unintended access.

Prevention: retest after every network, hosting or identity change, and keep the test evidence with the scope documentation.

5. Card data arrives by email, chat or paper

Symptom: customers send card details by email or WhatsApp, and staff copy them into a booking system or a notebook.

Likely cause: the business accepts whatever channel the customer uses, and no one has designed a safe alternative.

Fix: stop accepting card details through insecure channels. Provide a payment link, a hosted page or a phone process that does not record the number. Delete existing messages and paper copies according to a documented procedure.

Prevention: brief customer-facing staff, update order forms and website wording, and monitor shared inboxes for card-number patterns.

6. Logging and retention evidence is missing

Symptom: the merchant cannot show who accessed the payment system, when a configuration changed or how long logs are kept.

Likely cause: logging was left at default, logs are overwritten quickly, or they are stored on the same server as the application.

Fix: define the events that must be logged, the retention period required by your validation route, and who reviews alerts. Store logs where an attacker who compromises the application cannot easily erase them.

Prevention: include logging in the go-live checklist for every new payment component, and test restoration of log data.

7. A new channel was added without a scope review

Symptom: a new payment method, buy-now-pay-later option, marketplace integration or mobile app is live, but the scope document still describes the old website.

Likely cause: product and marketing teams can launch a payment option without involving the person who owns compliance.

Fix: review the new flow, identify every system that touches card data, and update the questionnaire, diagrams and evidence. If the new flow cannot be supported safely, pause it.

Prevention: make a scope review a gate in the launch process. No payment change goes live without a named reviewer and a signed note.

A diagnostic sequence

  1. List every payment channel and the exact integration type for each.
  2. Draw the card-data flow from browser to acquirer, including scripts, servers, databases and backups.
  3. List every person and system that can reach those components.
  4. Compare the real flow with the questionnaire you completed.
  5. Search for stored card data and insecure collection channels.
  6. Test segmentation and review access logs.
  7. Update the scope document, then decide what to fix first.

Fix in the right order

Stop new collection of card data outside approved channels. Then remove stored data you do not need. Then reduce scope through hosted payment pages or tokenisation where your integration supports it. Then segment, harden and log. Validation comes last, because validating an inaccurate scope only documents the wrong boundary.

Prevention controls

  • Keep a payment-system inventory with an owner and a review date.
  • Require a data-flow diagram for every payment change.
  • Review agency and hosting access quarterly.
  • Test segmentation after network or identity changes.
  • Train customer-facing staff on secure payment channels.
  • Review logs and scan findings on a calendar, not after a reminder.

If you need help mapping the boundary and reducing scope before validation, start with Commerce Systems. The pricing page explains how assessments are scoped. For the budget side, read what PCI DSS scope costs a small merchant in Bangladesh.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes