Key Concepts
- 1PCI-DSS governs how cardholder data is handled, and the single most important architectural move is keeping card data out of the agent/LLM path entirely
- 2Scope is the enemy: any system that touches, stores, or transmits card data falls in PCI scope; minimizing scope minimizes audit burden, cost, and breach risk
- 3Tokenization and hosted payment fields let the agent orchestrate a purchase while the actual PAN (card number) never enters your systems or the model context
- 4Never log card data — and LLM prompts/completions are logs. An agent that ever sees raw card numbers risks writing them into transcripts, telemetry, and training data
- 5SAQ level and validation requirements scale with how you handle cards; a well-architected tokenized flow can qualify for the lightest self-assessment tier
- 6Third-party processors and gateways carry much of the compliance load, but the merchant remains responsible for the integration boundary and data flow
- 7Prompt injection is a PCI risk vector too: an attacker who can manipulate the agent must never be able to coax it into echoing or exfiltrating payment data
Why It Matters for PMs
Compliance cost and liability: PCI scope drives audit expense and breach exposure. Architecting the agent out of the card path is one of the highest-leverage decisions a PM makes.
LLM logging is a landmine: Because model I/O is captured, an agent that sees card data can silently leak it into transcripts and training sets — a compliance and privacy disaster.
Trust and legality: Mishandling card data risks fines, processor termination, and reputational damage. Getting the data flow right is foundational, not optional.
Test Your Understanding
Question 1 (Multiple Choice)
What is the single most important PCI architectural decision for an agent?
Question 2 (Multiple Choice)
Why is letting the LLM see raw card numbers especially dangerous?
Question 3 (Multiple Choice)
How does minimizing PCI scope help the merchant?
Question 4 (Short Answer)
How would you architect an agent checkout so the LLM never touches cardholder data?
Think about your answer before revealing the explanation.
Question 5 (Short Answer)
Why is prompt injection a PCI concern, and how would you mitigate it?
Think about your answer before revealing the explanation.