Industries · Payments

The PCI Council enforces nothing. Your acquirer, the brands, and your sponsor bank do.

Requirement 6.2.3 wants code reviewed by someone other than its author. When an agent writes payment code, the Report on Compliance and the registry listing depend on the record naming who reviewed it.

Pre-production only: how agents change your systems, not how those systems run.

  • CISO
  • PCI Program Owner
  • QSA liaison
  • VP of Engineering

Approval queue

Illustrative · demo data

Approval queue with demo data: a command pending second-line review, a rerun approved by a named reviewer, and a public model call blocked by policy.

Each review names the reviewer. Individual developer keys also name the requester, so independence can be checked.

Industry trend

Source: Stack Overflow Developer Survey 2026, self-reported; data under ODbL 1.0. AutoDevOps is not affiliated with Stack Overflow.

01Where agents meet your obligations

Three sessions your examiner will ask about.

  1. 01

    An agent changes tokenization code inside the CDE.

    The edit waits for a reviewer who did not request it. Both names are recorded.

    PAY.PCI-CODE-REVIEW
  2. 02

    An agent runs a production deploy with no recorded reason.

    A finding stays open until the session records why the change was made.

    PAY.PCI-CHANGE-RECORD
  3. 03

    A card number in a log excerpt reaches agent context.

    A critical finding opens. Account data may reach no model provider.

    PAY.NO-PAN-IN-CONTEXT

02The authorization at stake

Your sponsor bank’s consent order is your offboarding notice.

Brands, acquirers, and sponsor banks can each withdraw your right to process.

At stake
Card-brand registration, your acquirer agreement, state money transmitter licenses, and for most fintechs the sponsor bank’s charter.

  1. 01

    Assessment and Report on Compliance

    An agent-written change with no independent reviewer fails Requirement 6.2.3 on your Report on Compliance.

  2. 02

    Brand and acquirer enforcement

    Assessments and deadlines flow from the brands through your acquirer to you.

  3. 03

    Registry removal

    Stay listed only with current validation. Visa can remove you.

  4. 04

    Sponsor bank consent order

    The Fed’s 2024 Evolve order barred new fintech partners without written approval. Your program is one of those programs.

  5. 05

    License and certification

    A New York money transmitter certifies Part 500 every April.

Sources: PCI DSS v4.0.1 Req. 6.2.3, 6.2.3.1 · PCI SSC FAQ on enforcement · Visa Global Registry of Service Providers · Federal Reserve, Evolve order (June 2024) · 23 NYCRR 500.1(e), 500.17(b) · Directive (EU) 2015/2366 (PSD2), Art. 13

Delisting as a first step is rare. Assessments and sponsor-bank reviews are routine, and each starts with one unreviewed change. The record is evidence for your QSA and your sponsor bank, not a finding of compliance.

03Obligations checked

Every clause, checked on every session.

Review and forbidden-action rules hold the agent before it acts. Provider, data, and intent rules record after.

  1. BANK.NPI-PROVIDERS

    Customer financial data reaches covered providers only

    Regulation · Gramm-Leach-Bliley Act · GLBA §501(b); 12 CFR 30 App. B §III.D (banks); 16 CFR 314.4(f) (non-bank financial institutions)

    DORA.TPRM-02NYDFS.TPSP-03

  2. PAY.PCI-CODE-REVIEW

    Payment code is reviewed by someone other than the author

    Framework · PCI DSS v4.0.1 Req. 6.2.3; 6.2.3.1 for manual reviews

    PCI.REV-01FFIEC.SOD-01

  3. PAY.PCI-CHANGE-RECORD

    Production changes record their reason

    Framework · PCI DSS v4.0.1 Req. 6.5.1

    PCI.CHG-02DORA.CHG-04

  4. PAY.NO-PAN-IN-CONTEXT

    Card numbers never reach a model

    Framework · PCI DSS v4.0.1 Req. 3 (protect stored account data), 12.8 (third-party service providers)

    PCI.TPSP-03ISO27001.DAT-02

Plus 5 baseline obligations every pack checks
  1. BASE.SECRET-CONTEXT

    Credentials stay out of agent context

    Framework · ISO/IEC 27001:2022 · Annex A 5.17 (authentication information)

    ISO27001.DAT-02EUAI.ART15-04

  2. BASE.DPA-PROVIDERS

    Model calls stay on the DPA subprocessor list

    Contract · Customer data processing agreement · DPA subprocessor schedule

    DORA.TPRM-02NAIC.TP-03NYDFS.TPSP-03

  3. BASE.PROD-CHANGE-REVIEW

    Infrastructure changes get an independent approver

    Framework · SOC 2 Trust Services Criteria · CC8.1 (change management)

    SOC2.CC8-03FFIEC.SOD-01DORA.CHG-04

  4. BASE.AGENT-SYSTEM-REVIEW

    Agent prompts, tools, and guardrails get an independent reviewer

    Internal policy · AI system change policy · Customer AI system change policy; EU AI Act Art. 14 (human oversight)

    EUAI.ART14-03ISO42001.RSK-01NIST.MANAGE-04

  5. BASE.NO-FORCE-PUSH

    Agents never rewrite shared history

    Internal policy · Secure development standard · Protected branch policy

    FFIEC.LOG-03MAS.LOG-04

Templates ship without dollar figures; the register shows a labeled illustrative band until you add yours. Pre-run checks use review mode, a customer-cloud CLI capability.

05For your risk and insurance reviewers

Evidence an AI liability underwriter can rate.

Verified controls
Gate coverage, independent review rate, and self-approvals.
Change velocity
Weekly changes to prompts, tools, or guardrails, and the share with a stated reason or approval.
Autonomy
Unattended sessions and the allow, hold, and block mix.
Obligation posture
Findings by status, priced per obligation.

Production behavior is out of scope and marked that way. The packet is evidence for a reviewer. It is not insurance, a certificate of coverage, or a premium quote.

Sources and citations · 5 rules referenced
  • PCI DSS v4.0.1

    Req. 6.2.3 review before release; 6.2.3.1 manual review by someone other than the author

  • PCI DSS v4.0.1

    Req. 6.5.1: production change procedures

  • PCI DSS v4.0.1

    Req. 3 account data; Req. 12.8 third-party service providers

  • FTC Safeguards Rule

    16 CFR 314.4(f): oversee service providers

  • 23 NYCRR Part 500

    §500.1(e) covered entity; §500.8 application security; §500.17(b) annual certification

Your QSA confirms cardholder data environment scope and tests each requirement, and your acquirer agreement sets the assessments. Agent records are inputs to that assessment. For your counsel and compliance team, not legal advice.

Other industries: Banking, Insurance, Healthcare.

Bring one payments obligation

We run it against your agents’ recorded sessions and hand you the findings, priced exposure, and evidence packet.