PCI DSS is not a product with a price tag. It is a standard, and the cost of meeting it is mostly the cost of the scope you create. Two merchants with the same monthly card volume can face very different bills because one lets card numbers pass through its own servers and the other never touches them.
That distinction matters more in Bangladesh than it used to. Online sellers commonly run a website, a Facebook page and a payment aggregator at the same time, and card payments sit beside bKash, Nagad and cash on delivery. Each channel changes what the cardholder data environment looks like, and therefore what you have to assess, harden, log and re-validate every year.
What scope means in practice
Scope is every system, process and person that stores, processes or transmits cardholder data, plus every system that can connect to one and affect its security. A small merchant is often surprised to find the office laptop that opens the gateway dashboard, the shared inbox that receives settlement reports and the agency that maintains the site all inside the boundary.
The cheapest control is almost always scope reduction. If customers enter card details on a hosted payment page, or inside an iframe served by the gateway, the merchant's servers may never see the card number. Tokenisation removes stored numbers from your database. Both approaches can move a merchant toward a shorter self-assessment questionnaire, but eligibility depends on the exact integration and is confirmed with your acquirer or a qualified assessor, not assumed from a marketing page.
Cost lines to budget
- Scoping and gap assessment. A one-off review that maps card data flows, identifies the boundary and lists the controls already in place. This is the line most merchants skip and later pay for twice.
- Remediation engineering. Network segmentation, hardening, key management, log collection, access control and secure development fixes. This is usually the largest line and the one that varies most.
- Validation work. Completing the correct self-assessment questionnaire and assembling evidence takes internal time or a consultant. Where the acquirer requires an assessment by a qualified security assessor, that fee is separate.
- Scanning and testing. Approved scanning vendor scans and penetration testing may apply to your validation route. Frequency is set by the standard and by your acquirer.
- Monitoring and retention. Log storage, alerting and the staff time to review it. This is an annual operating cost, not a project cost.
- Training and policy. Annual awareness training and written policies that match what people actually do.
- Change management. Every new payment method, plugin or integration can change scope. Budget a review before launch, not after.
- Internal effort. The hours your finance, operations and technology staff spend answering questions and producing evidence. It is real cost even when no invoice arrives.
The cost model
Use a two-part model rather than a single number.
Year one equals scoping assessment, plus remediation engineering, plus validation and testing, plus first-year monitoring and training, plus a remediation reserve for findings that only appear once someone looks properly.
Steady state equals annual validation and testing, plus monitoring and log retention, plus training, plus internal evidence time, plus the change reviews triggered by new channels.
The reserve matters. A gap assessment that finds nothing usually means the assessment was too shallow. Set the reserve as a percentage of remediation and agree in advance who can authorise spending it.
A calculator you can fill in
This is a worksheet, not a quote. Enter your own hours and vendor rates.
- Count the systems that touch card data. Website, order management, ERP, call-centre tool, finance spreadsheet, email inbox, backup storage, agency access. Multiply by the average remediation hours per system.
- Count the systems that can reach those systems. Add segmentation work if the answer is greater than zero.
- Choose the validation route with your acquirer. Record the questionnaire type and whether an assessor is required, because that single decision changes the annual line.
- Add scans and tests. Use the frequency your route requires, not an annual guess.
- Estimate log volume. Multiply daily event volume by retention days and by your storage cost per gigabyte.
- Add internal hours. Include finance, operations and technology time at a loaded hourly rate.
- Add the reserve. Apply your agreed percentage to remediation.
Run the worksheet twice: once for the current architecture and once for a reduced-scope design with a hosted payment page and tokenisation. Compare the three-year totals, not just year one. The reduced-scope option often costs more to build and less to run, which is the opposite of how it is usually presented.
Questions to ask a vendor
- Which specific card data flows put us in scope, and which do not?
- What would reduce scope, and what would that change cost to build?
- Which questionnaire applies to our integration, and who confirms eligibility?
- Does the quote include evidence preparation or only the assessment?
- Who owns remediation, and how are change requests priced?
- What happens when we add a new payment channel mid-year?
- Which parts can our own team maintain after handover?
- What will the annual re-validation cost in each of the next two years?
A 90-day plan
- Days 1 to 30: map card data flows, confirm the validation route with the acquirer, and produce a written scope diagram. No spending on tools yet.
- Days 31 to 60: fix the highest-impact gaps, starting with segmentation, access control and logging. Decide on hosted payment capture and tokenisation if they reduce scope.
- Days 61 to 90: assemble the evidence pack, run the first scans or tests, and book the assessment. Put a change-review step into the release process so the next plugin does not quietly widen scope.
Metrics
- Number of systems in scope, tracked quarter by quarter.
- Percentage of card data flows that never touch merchant infrastructure.
- Open remediation items by severity and age.
- Days of log retention actually available for review.
- Time from scope change to scope review.
- Annual validation completed before the deadline, not after.
Where this fits in our work
Our Commerce Systems team designs payment and reconciliation flows so that card data stays with the gateway wherever possible. Scope, deliverables and commercial terms are set out on the pricing page. For the monitoring side of card security, read the payment fraud monitoring guide.
Sources
- PCI Security Standards Council, PCI DSS, accessed 17 November 2026.
- PCI Security Standards Council, Document Library, accessed 17 November 2026.
- PCI SSC, PCI Security Standards Overview, accessed 17 November 2026.
- Bangladesh Bank, official site and circulars, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.