For a shop that takes cards

The terminal is fine. The notebook with a regular's card number in it is the breach.

Not a hypothetical company’s story — yours. Here’s how the security paperwork finds a shop that takes cards, and what to do about it before it’s urgent.

The story

01

Your stack

The processor's terminalOnline checkoutThe notebook / spreadsheet
02

How it actually goes wrong

The terminal is fine. The notebook is the breach. Card brands treat stored card numbers as radioactive: one incident and you're facing forensic audits, fines passed down by the processor, and the possibility of losing the ability to take cards at all — which for most shops is the business.

03

Who's already asking

Your processor — the annual SAQQuarterly scansThe monthly non-validation fee

Your processor already requires an annual SAQ and, for some setups, quarterly scans — the portal emails you keep deleting, plus the monthly non-validation fee you keep paying.

04

What Vouchra does about it

Vouchra scopes cards out of your systems, writes the handling rules, walks you through the SAQ the processor actually wants, and keeps the whole thing current — in plain English.

Next move

See it on a business like yours.

The walkthrough uses your world — your tools, your paperwork — not a demo company’s.

A human replies — no drip campaign, no list.

See your own paperwork answered.

Bring a real questionnaire — an insurer's renewal, a client's spreadsheet, the processor's SAQ — and watch it answered from real policies, with citations.