Skip to main content
A card purchase takes three steps and one human passkey approval. For the lifecycle, approval flow, ownership model, and per-purchase invariants (one-shot credentials, merchant binding, terminal denials), see Linked cards. This page lists what the agent supplies.

​
Purchase request

  • Amount and currency.
  • A short merchant-facing description.
  • An idempotency key, unique per intent.
  • Optionally, a hint for which card the approval page should default to.
Anchorage Agentic Banking returns a purchase_request_id, a pending_approval status, and an approval_url for the user to open.

​
Polling and expiry

The agent long-polls for the verdict (~25 s per call) using the same idempotency key. PurchaseRequests expire 2 hours after creation; until then the agent can keep polling.

​
Credential retrieval

After the user approves, the agent requests credentials, providing:
  • Merchant name and URL.
  • Merchant country code.
  • For physical goods, the shipping block: shipping_line1, shipping_line2, shipping_city, shipping_region, shipping_postal_code, shipping_country, and an optional products JSON.
Anchorage Agentic Banking returns a card credential — number, expiry, CVC. The agent fills the merchant’s checkout form with the returned credential.