The vault
All sensitive credentials — card numbers, CVCs, and merchant passwords — are encrypted by Evervault intoev: ciphertext before they leave the browser. AgentMall stores only ciphertext. We cannot decrypt it. Evervault holds the cryptography.
PCI scope
AgentMall is out of PCI cardholder data scope. We do not accept, process, store, or transmit plaintext card numbers. Theev: 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.
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:What AgentMall stores
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: Bearerheader over the?key=query parameter, so the key stays out of server logs and browser history
invalid_key immediately.