Frequently asked questions
The questions we get asked first.
If yours isn't here, ask us directly — we answer within one business day, whether or not you're a client.
Ask us a questionThe basics
What is PCI DSS?
The Payment Card Industry Data Security Standard. It's a set of security requirements for any business that stores, processes, or transmits cardholder data. It's written by the PCI Security Standards Council, which is owned by the card brands. It applies to you because your processor's contract requires it, not because a government regulator enforces it.
Do I have to be compliant?
Contractually, yes — your merchant agreement with your processor requires it. There's no PCI police, but processors can charge non-compliance fees, and acquirers can pass card brand fines to merchants. In practice, the requirement lands on you when your bank asks for a Self-Assessment Questionnaire.
What's the difference between PCI DSS and a SAQ?
PCI DSS is the standard — the requirements. A Self-Assessment Questionnaire is the form you use to report how you meet them. The SAQ is the paperwork; PCI DSS is the thing the paperwork is about.
What is a merchant level?
A category based mainly on your annual card transaction volume, from Level 4 (smallest) to Level 1 (largest, usually over 6 million transactions). Your level determines what evidence your processor expects. Most of our clients are Level 3 or 4.
The questionnaire
Which SAQ do I need?
It depends on how you take payments, not how big you are. Roughly:
- SAQ A — your checkout is fully hosted and card data never touches your systems.
- SAQ A-EP — your website takes the card details but the payment page itself is hosted by a provider.
- SAQ B / B-IP — card-present terminals, dial-up or IP-connected.
- SAQ C / C-VT — payment application or virtual terminal.
- SAQ D — everything else, including most service providers and anyone storing card data.
- SAQ P2PE — point-to-point encrypted terminals.
The Scope Check exists because this list is genuinely ambiguous for most businesses, and the wrong choice costs real money. Read the plain-English walkthrough →
How long does a SAQ take?
The questionnaire itself, for a simple merchant, is a few hours of your time spread over a couple of weeks. The part that takes longer is gathering the written policies and evidence it asks about — often because they've never existed.
Can I just do it myself?
Yes, and many businesses should. The forms are public and free. What a consultant buys you is the correct scope, the policy templates, the review, and the confidence that what you're filing will survive your bank's scrutiny. If your setup is simple, do it yourself — we'll tell you that on the Scope Check call.
Will my bank accept a consultant-prepared SAQ?
The SAQ is signed by you, not by us. We prepare it and review the evidence; you review and sign. That's normal practice and processors accept it. What we can't do is sign it for you or vouch for it as an assessor.
Do I need a QSA?
Most small and mid-size merchants don't. A QSA-led assessment — ending in an Attestation of Compliance or a Report on Compliance — is generally required for Level 1 merchants and certain service providers. If that's you, we'll tell you, prepare you for the assessment, and hand you over. We're not a QSA company and we don't perform PCI DSS assessments.
Money and time
How much does this cost?
Why do you charge less than a security firm?
Because we do one thing. We're not carrying a pentest team, a SOC, or a sales organisation. Narrow scope, small overheads, fixed fees.
What if I need to cancel?
Fixed-fee engagements: full refund before kickoff, pro-rata after. Retainers: 30 days' notice, cancel any time after the first three months.
How fast can you start?
Usually within a week. If your bank has given you a deadline, say so on the Scope Check call and we'll tell you honestly whether we can meet it.
Working with us
Do you need access to our systems?
Almost never. Most engagements run on documents, screenshots and conversations. If something genuinely requires a look at a configuration, we'll ask, explain why, and use a read-only account.
Do you store cardholder data?
No. Never. CardComply does not collect, process, or store cardholder data in any form. If you send us something that looks like a card number, we delete it and tell you to stop sending it.
Do you work outside the US?
We work with US-based businesses only, in all 50 states, remotely. Video or phone, whichever you prefer.
Do you work with MSPs and agencies?
Still not sure which questionnaire you need?
The free Scope Check answers that in 20 minutes, in writing, whether or not you work with us.
