> ## Documentation Index
> Fetch the complete documentation index at: https://agentmall.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Security

> How AgentMall handles credentials. Card numbers and passwords are encrypted before they reach us.

![Plaintext credentials enter the Evervault vault and emerge as ciphertext](https://mintcdn.com/agentmall/ZuoglRqW4CDsIaRs/images/security.svg?fit=max\&auto=format\&n=ZuoglRqW4CDsIaRs\&q=85\&s=09de7bc1379e0780ab39ca247dae3b4f)

AgentMall never sees your card number or merchant password in plaintext. Credentials are encrypted before they reach us.

## The vault

All sensitive credentials — card numbers, CVCs, and merchant passwords — are encrypted by [Evervault](https://evervault.com) into `ev:` ciphertext before they leave the browser. AgentMall stores only ciphertext. We cannot decrypt it. Evervault holds the cryptography.

```
ev:RFVC:abc123...   ← this is what AgentMall stores
4111 1111 1111 1111 ← this never touches our servers
```

## PCI scope

AgentMall is out of PCI cardholder data scope. We do not accept, process, store, or transmit plaintext card numbers. The `ev:` ciphertext is not cardholder data under PCI — it is an encrypted token that only Evervault can resolve.

## Who pays

The shopper pays with their own card. The merchant is the merchant of record and charges the shopper directly. There are two ways to give AgentMall the card:

* **Our vault (Evervault):** the shopper enters the card once on our hosted page, and you get a token back.
* **Your vault:** you send a token from your own vault provider.

Either way, the card number never touches your systems or the model.

## How credentials are collected

**Cards**: use the console's `/collect` page. It loads an Evervault iframe that encrypts the card number on the user's device. The encrypted `ev:` value is stored on the session. Plaintext never enters AgentMall's JavaScript or backend.

**Merchant logins**: the `sign_in` tool accepts `email` and `password` as `ev:` ciphertext. For the platform account, credentials are pre-configured as ciphertext. For shopper accounts, collect them through the console `/collect` page.

## How credentials reach the merchant

Plaintext goes from Evervault to the merchant, never through AgentMall's servers:

| Path | How it works |
| - | - |
| **Browser Tokens** | Evervault decrypts the credential inside the browser session and types it into the merchant's login form. AgentMall's code sees only the token, not the value. |
| **Evervault Functions** | For card save (Walmart's Voltage flow), an Evervault Function decrypts and forwards to the merchant's payment API. The plaintext exists only inside Evervault's enclave. |

## What AgentMall stores

| Stored | Not stored |
| - | - |
| `ev:` ciphertext (card, password) | Plaintext PAN |
| Last 4 digits of card | Full card number |
| Card brand (Visa, Mastercard, etc.) | CVC |
| Expiry month and year | Plaintext password |

The console shows masked values only. There is no decrypt button. Screenshots taken during checkout mask password and payment fields.

## API keys

API keys authenticate your organization. Treat them as secrets:

* Do not commit keys to source control
* Do not paste them into shared chats or docs
* Do not embed them in client-side code
* Prefer the `Authorization: Bearer` header over the `?key=` query parameter, so the key stays out of server logs and browser history

Mint and revoke keys in the [console](https://console.getagentmall.com/keys). A revoked key returns `invalid_key` immediately.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.