Card Data Desk for PCI DSS - which SAQ is yours, and where card data leaks in your code

Answer six questions and paste your checkout code, config or logs: the browser reads your PCI DSS v4.0.1 SAQ and merchant level and scans for card numbers, CVVs, track data, http:// and unmanaged payment scripts (masked before sending); then a scope reading or a review with exact edits. Derived from @wshobson/pci-compliance (Seth Hobson, MIT).

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.