How we keep card numbers out of agent memory

Language model agents are very good at remembering things, and very bad at keeping secrets. Anything that passes through a prompt can end up in a log, a trace, a vector store or a summary written for the next run. A card number is exactly the kind of thing you do not want to find there.

Tokens, not numbers

When your agent asks for a card, it receives a token scoped to one merchant and one amount. The real card details only exist inside our card environment, and they are passed to the merchant by our payment API at the moment of purchase.

What this means for you

• A leaked prompt or trace exposes a token that is already spent or expired
• Your own systems stay out of scope for card data audits
• Revoking an agent revokes every token it holds in one call

The full picture, including how keys are stored and rotated, is on our Security page.