CardComply

SAQ B-IP vs SAQ C

B-IP or C? What changes when you have more than one location taking cards.

Standalone card terminals that connect to the internet on their own → SAQ B-IP. A payment application running on a computer at each site, connected to the internet → SAQ C.

The number of locations does not change which questionnaire applies. It changes the size of the job and, with us, the retainer: single-location B-IP or C merchants are quoted $1,000/mo; more than one location is $1,500/mo, because every site is its own set of terminals, its own network, and its own evidence.

Two older variants worth ruling out first: SAQ B is for dial-up terminals, which almost nobody has now — if someone calls your terminals "B", check whether they are actually IP-connected, because that is B-IP. And SAQ C-VT is for keyed entry through a browser, not for terminals.

How to tell which one you are

Walk into a site and look at what the card is put into.

  • A device that only takes cards, plugged into the network or the router, talking to the processor by itself → B-IP.

    The device is the payment channel. Nothing else on site is in scope.

  • A computer running point-of-sale or payment software, with the card read by that software → C.

    The computer is now a payment application system connected to the internet, and it brings its own requirements: configuration, patching, access control.

The question that settles it: is there a computer involved in taking the card, or only a terminal? If the answer differs between locations — say, terminals at three sites and a POS till at the fourth — you have both, and both get covered.

What each one asks for

What SAQ B-IP asks for

Network segmentation, device configuration, patching, and a written policy for the terminal estate.

Where people trip: terminals sitting on the same network as everything else with no documented separation. This is the most common finding at this level, and it is the one that turns "we have terminals" into "we have terminals on the staff Wi-Fi and the back-office PC." Segmentation does not have to be expensive, but it has to be documented — a network diagram and a short written description of what is separated and why.

Effort: a few hours plus a conversation with whoever manages your network, per site. Project work: SAQ Done Right $1,500–$3,500, starting fee up front. Retainer $1,000/mo single location, $1,500/mo multiple.

What SAQ C asks for

The payment application's configuration, patching, access control, and written policy around it.

Where people trip: assuming the software vendor's own compliance covers you. It does not. The vendor may be compliant as a vendor; you still have to evidence your side — that the application is patched, that only the right people can log in, that the machine is configured as the vendor requires, and that you can show it.

Effort: half a day of your time, plus vendor documentation. Project work: SAQ Done Right $1,500–$3,500, starting fee up front. Retainer $1,000/mo single location, $1,500/mo multiple.

What multiple locations actually change

The requirements do not change. The work multiplies, and it multiplies in places people forget:

  • Evidence per site.

    Each location's terminals or payment machines need their own records — patching, configuration, who has access.

  • One policy, applied everywhere.

    A written policy that exists at head office and is unknown at the fourth branch is the gap that shows up in a review.

  • New sites start compliant.

    A site opened in a hurry with a terminal on the office network is how a compliant estate stops being one.

  • Decommissioning.

    Terminals get replaced and old ones get stored. A terminal in a cupboard with a live configuration is still a terminal.

  • Scans, where they apply.

    If your SAQ type is one where quarterly ASV scanning applies, each external IP address in scope gets scanned. A vendor does that scanning; you do not.

Annual renewal is the part that gets missed

Whichever of the two you file, it is annual — and the renewal date does not announce itself. Neither does the quarterly scan, the annual policy review, or the evidence refresh. With several sites, these dates drift apart fast, and the first sign is usually another letter from the processor.

Our Compliance Managed Monthly service exists for exactly this: we generate the deadline set when we set your SAQ type, track the renewals, keep the evidence current, and send you a monthly status. Clients can upload evidence to their portal against each request and see what is still outstanding. See what the retainer includes →

Start here.

The free PCI Scope Check asks how you take cards at each location and how many locations take card payments, then gives you your likely SAQ type, your merchant level, and the retainer tier that matches — name and price together, so there is nothing to reconcile. Twenty minutes, no charge.

CardComply provides consulting, readiness, and compliance-management services. CardComply is not a QSA company and does not perform PCI DSS assessments or issue Reports on Compliance or certifications. CardComply never collects or stores cardholder data.