PCI DSS SQL Card Data — check card data in sql migrations

Finds cardholder and sensitive authentication data in your .sql migrations: CVV, track, PIN block, plaintext PAN columns and test card numbers, each mapped to a PCI DSS Requirement 3 rule. Runs entirely in your browser — nothing is uploaded.

-- 0007_payments.sql
-- Generated from a prompt: "add card storage for saved payment methods"
BEGIN;

CREATE TABLE customer_cards (
    id            BIGSERIAL PRIMARY KEY,
    customer_id   BIGINT NOT NULL REFERENCES customers (id),
    card_number   VARCHAR(19) NOT NULL,
    cvv           CHAR(4),
    pin_block     CHAR(16),
    track2_data   VARCHAR(40),
    exp_month     SMALLINT,
    exp_year      SMALLINT,
    created_at    TIMESTAMPTZ DEFAULT now()
);

CREATE UNIQUE INDEX idx_customer_cards_pan ON customer_cards (card_number);

CREATE TABLE payment_audit_log (
    id                BIGSERIAL PRIMARY KEY,
    customer_id       BIGINT NOT NULL,
    card_number       VARCHAR(19),
    gateway_response  JSONB,
    logged_at         TIMESTAMPTZ DEFAULT now()
);

CREATE VIEW v_recent_charges AS
    SELECT c.customer_id, c.card_number, ch.amount, ch.captured_at
    FROM customer_cards c
    JOIN charges ch ON ch.customer_id = c.customer_id;

INSERT INTO customer_cards (customer_id, card_number, cvv, exp_month, exp_year)
VALUES (1, '4111111111111111', '123', 12, 2029);

COMMIT;

as of

$29 once · one licence key per person or team seat · A QSA-led gap analysis of your data stores is commonly quoted as a five-figure engagement.

Free here: Check the .sql file open in your editor and name every column that stores card data, with its PCI DSS Requirement 3 rule id. In the editor: Sweep every migration in the workspace and write a dated, exportable findings report you keep — for team and commercial use — that part asks for a licence key.

Same engine as the VS Code extension, byte for byte.