Agentic.PayKeep the payment method close to its owner. Bring encrypted card storage, explicit approval and visible device access into your agent experience.
Illustrative sandbox environment · No live transactiondevice_042- Encrypt on device
- Review the request
- Keep access visible
01 / Device encryption
A card enters.
Ciphertext leaves.
Card details are encrypted on the customer’s device before entering Vault. Device keys and a company-scoped Vault keep the stored record tied to its owner.
Illustrative card-sandbox flow · test card 4242cipher_042e8 ◇ 16 ◇ b0 ◇ 5a
VAULTYOUR CARD. YOUR CONTROL.02 / Deliberate approval
Make the request
worth a second look.
Show the merchant and amount before a customer approves or rejects a sandbox payment request. The approval has its own status and expiry; a stored card is not a blanket permission.
Approval is separate from a completed payment.Agentic.Pay03 / Visible access
Know which device
holds the keys.
Inspect enrolled devices and their status. Revoke a device’s access and keep the distinction between an active key, a pending approval and a returned result visible.
Card Vault examples use sandbox mode. Merchant login storage is a separate workflow.Revision 4 → 5Agentic.PayFrom a scene to your workflow
Build with a boundary.
Keep the result.
Start in the sandbox workspace. Use the documentation to connect your application, preserve operation identifiers and inspect each returned status.
- 01Open your company workspace
Keep the company and customer context explicit.
- 02Connect the documented flow
Use the configured credentials and supported operations.
- 03Inspect the returned result
A request, an approval and a payment are separate facts.
A few useful distinctions
Vault, clearly.
Does storing a card authorize every purchase?
No. Card storage, device access and purchase approval are separate operations. An approval is attached to its specific request and status.
Where can a customer manage their card?
The customer Vault is a separate authenticated experience at /vault. It contains the connected-company selector, stored test cards and checkout approvals.
Does this page process a payment?
No. These scenes are illustrations. The card and approval examples describe the sandbox workflow; no card is charged by the page.