Security & control

Trust begins
with a boundary.

Customer permission, company scope and an inspectable result. Make each one an explicit part of your agent’s payment workflow.

01 / Device

The card stays close to its owner.

Card details are encrypted on the customer’s device before entering Vault. Device keys and the company-scoped record preserve the connection to the owner.

02 / Permission

Storage is not blanket approval.

A customer reviews a specific merchant and amount. Approval has a status and expiry; confirmation is separately bound to the current observed cart.

03 / Access

Access has a visible state.

Inspect enrolled devices and revoke device access. Keep a pending approval, an active key and a returned result distinct.

04 / Outcome

An approval is not a charge.

Read the returned transaction and purchase status. Sandbox confirmation produces a durable no-charge result and no merchant order.

Understand the flow.

Review the product guides and current contract for your integration. Provider eligibility and live financial requirements are separate from sandbox examples.