Provision VGS vault credentials
Resolves the CreditCard payment account for the cart, pins the routing
decision on the cart, and returns the VGS Collect vault credentials used to
tokenize card data client-side. No request body. This begins the card
payment flow: after tokenizing the card (and completing 3D Secure via
verify when the returned requires_3ds is true) the server produces a
Fluid payment reference that the Cart checkout complete_cart step
(POST /api/checkout/v2026-04/carts/{cart_token}/complete, Checkout endpoints
reference) consumes as its payment_uuid query parameter. Cart-token
authenticated. Returns 404 when the cart or payment account is not found
and 410 when the cart has already been processed or holds an authorized enrollment.
Headers
Optional non-authorizing checkout journey UUID. Use with X-Checkout-Attempt-Id. Capture is disabled by default; malformed or incomplete pairs are ignored without changing checkout behavior. Cart scope comes from the authenticated cart token, never these headers.
Optional customer-submission UUID paired with X-Checkout-Journey-Id. Retain it for transport retries and originating continuations; use a new UUID for a new customer submission. It does not replace payment or order idempotency keys. Invalid pairs are ignored rather than rejecting payment.
Path Parameters
Opaque cart token returned by the create-cart response. It scopes the request to a single cart and is the credential for these endpoints — cart-token authentication carried in the path, with no bearer token or API key.
Response
Vault credentials
Success body for VGS vault provisioning.
VGS Collect vault credentials used to tokenize card data client-side.
true when 3D Secure is required for this card; mirrors vault.requires_3ds. When true, call verify before authorizing.
Id of the CreditCard payment account resolved and pinned to the cart for this tokenization. Routing normally stays fixed to this account for the rest of the flow, but a stale pin is invalidated and re-resolved when the account set that produced it changes (for example after a gateway configuration change), so a later call can return a different account.
Standard response metadata included on every response.