AI Agent Payments: The Security and Compliance Checklist Your CISO Will Ask For

Last updated: 2026-06-07

The security review is the longest gate between your agents and production spend. This checklist covers every domain a CISO examines: data handling, audit completeness, access controls, certifications, regulatory standing, incident response, and vendor due diligence. Answer it before the review starts and you cut weeks off the process.


Key takeaways


Why does this review feel harder than usual?

Two reasons. First, agents take financial actions on their own, they're not processing data, they're moving money. That shifts the risk from data confidentiality to financial integrity, and security teams who've reviewed payroll or ERP access feel it instinctively.

Second, the category is new. Most teams adapt a standard vendor questionnaire and bolt on questions as they go. Walking in with a completed checklist signals you understand the risk surface, and that alone speeds things up. For what makes purpose-built infrastructure different from stitched-together tools, see Best Payment Infrastructure for AI Agents.


Section 1: Data handling and storage

ControlWhat reviewers will ask
Card credential storageAre raw PANs stored in the app layer? If so, where and for how long?
PII handlingWhat customer/employee data is retained? Encrypted at rest (AES-256) and in transit (TLS 1.2+)?
Data residencyWhere does data live geographically? Does it cross jurisdictions (GDPR)?
TokenizationAre credentials tokenized at issuance, before any agent exposure?
Log sensitivityDo audit logs hold raw card data, or only metadata?
Data deletionCan PII be deleted on request within the statutory windows (GDPR: one month; CCPA: 45 days)?

Section 2: Audit trail completeness

This is where most systems fail. A receipt shows money moved. An audit trail shows who authorized it, why, under what delegation, and whether policy was satisfied.

ControlWhat reviewers will ask
Decision logIs every authorization attempt logged, declines and escalations, not just approvals?
Identity attributionCan each transaction tie to a specific agent instance, task, and operator?
Policy versioningCan you reconstruct which policy was in effect at the time of each charge?
Delegation chainIs the full human-to-agent delegation recorded, who granted authority, when, under which consent version?
ImmutabilityCan entries be modified? Who has write access?
RetentionHow long are logs kept? (PSD2 Article 21 sets a five-year minimum for payment institution records.)
RetrievalCan you produce a full log for an agent or date range within hours?

Shatale writes an immutable, append-only log for every authorization decision, approved, declined, or escalated, keyed to agent ID, task ID, policy version, and timestamp.


Section 3: Access controls

ControlWhat reviewers will ask
Least-privilegeDo agents get scoped credentials limited to their envelope, or broad access?
RotationHow often are credentials rotated? Automated?
Admin accessWhat can staff touch in agent credentials and controls? Role-separated and logged?
Revocation speedHow fast can a credential be killed? (Target: under 60 seconds.)
Admin MFADo humans managing policy require MFA?
Separation of dutiesCan whoever sets policy also approve exceptions? (Should be separated.)
Agent-to-agentIn multi-agent systems, does each sub-agent get its own scoped credential, or inherit a parent's?

Section 4: Certifications

CertificationWhy it mattersWhat to request
SOC 2 Type IIOngoing operational controls; the minimum barLatest report + bridge letter
PCI DSSRequired if the vendor issues or manages payment credentialsSAQ or QSA report with scope
ISO 27001Common requirement for EU enterprise buyersCertificate + scope statement
GDPR / DPARequired for any EU personal dataSigned DPA; confirm SCCs if data leaves the EEA

Section 5: Regulatory standing

This one causes late-stage deal failures, when a buyer discovers mid-review that a vendor has no standing for payment services.

QuestionWhat to look for
Licensed or not?A licensed PI/EMI/bank, or unregulated software on a licensed partner? Licensed (or pending) is meaningfully different.
Which regulator?A named national authority and jurisdiction; reference number if available.
License scopePayment initiation, e-money, account info? Should match what you're buying.
Pending applicationsHas the vendor applied if not yet licensed?
SafeguardingHow are customer funds protected if the vendor fails? Look for segregated accounts with a named bank partner.

Section 6: Incident response

ControlWhat reviewers will ask
IR planDocumented plan covering payment-system compromise specifically?
Breach notificationContractual timeline to notify you? (GDPR: 72 hours to regulators.)
Payment-specific responseIf a credential is compromised, can spend freeze immediately? What's the procedure?
TabletopHas a tabletop covering agent compromise run in the last 12 months?
Pen testDate of last third-party test? Report available under NDA?

Section 7: Vendor due-diligence questions

Ask these live in the review:

  1. If an agent initiates an out-of-policy transaction that settles, who's liable?
  2. How do you handle a policy change needed mid-session?
  3. What's your sub-processor list, and how are their controls reviewed?
  4. Have you had an unauthorized agent-transaction incident? What happened?
  5. Where do you stand under PSD2 today, and what's your PSD3/PSR readiness plan?

The fast path through review

Fill out every section before you submit. Attach certifications and your DPA. If a vendor can't answer Section 2 or 3, keep looking. Most delays come down to missing documentation.


Frequently asked questions

What certifications should an agent payment vendor have? At minimum SOC 2 Type II and PCI DSS scoped to their cardholder data environment. ISO 27001 for EU buyers. A GDPR DPA for EU data. Request the actual reports, not just confirmation they exist.

Does the vendor need to be a licensed Payment Institution? Not everywhere, but it matters for risk allocation. Unregulated software initiating payments creates ambiguity about who's responsible when something breaks. Enterprise teams increasingly treat licensed (or pending) standing as a baseline.

How long should transaction logs be retained? Five years minimum under PSD2 Article 21; some member states require longer. They must cover every authorization decision, not just settled transactions, be immutable, and be retrievable within hours.

What is least-privilege access for an agent? Each agent gets only what its task needs, a specific merchant category, a cap, a time window. Broad credentials are an anti-pattern whether the holder is human or synthetic.

What should the vendor's IR plan cover? Detecting and freezing compromised credentials, identifying affected transactions, breach-notification timelines (72 hours to regulators under GDPR), and evidence it's been tested for agent-compromise scenarios specifically.


Shatale issues scoped agent cards, enforces policy at the authorization moment, and keeps an immutable audit trail, the infrastructure that makes a security review completable. Free for publishers right now. Apply for early access.