Good questions.
Clear boundaries.

Choose Vault when the customer brings a payment method, Issuing for company-controlled sandbox cards, or Purchase Agent for a bounded buying workflow. The products guide compares these jobs.

Yes. The product scenes are illustrations. The documented sandbox workflows let you inspect requests and results; sandbox purchase confirmation creates no charge and no merchant order.

Start with the relevant sandbox workflow. Talk to us about your integration scope, supported provider, eligibility and commercial terms.

Card details are encrypted on the customer’s device before entering Vault. Device keys and the company-scoped Vault keep the stored record tied to its owner.

No. Storage, device access and purchase approval are separate operations. The approval belongs to a specific request, status and expiry.

The authenticated customer Vault provides connected-company selection, stored test cards and checkout approvals. Device access can be inspected and revoked.

The scenes and workspace examples use sandbox cards and simulated authorizations. Live financial services require a supported provider and an eligible account.

A sandbox card has a label, spending limit and active, inactive or canceled state. Revision-aware updates keep a change attached to the state you reviewed.

No. Authorization, capture and refund are different events. Inspect the returned transaction status rather than inferring payment from an approval or card image.

Coverage follows the configured merchant allowlist and supported observed layouts. Login, a challenge or ambiguous checkout controls require human continuation.

Confirmation is tied to the current observed cart hash. A changed or unknown cart must be reviewed again. Keep the item, merchant and total inside the original boundary.

A durable sandbox result with charge_status none and no merchant order. The result is a record your application can recover; it is not a completed live purchase.

Use the documented HTTP purchase interface from your browser agent, messaging product or application. Keep company context, credentials and operation identifiers explicit.

Read the saved conversation or original operation first. For the same operation, preserve the same idempotency key. Do not create a new purchase to compensate for an uncertain response.

The official documentation covers the current contract and configuration. Use Talk to us for integration requirements and provider availability.