Source
Catalogue & checkout — found from sitemap — VTEX
Checked for VTEX on 10 Nov 2026
- Page
- https://developers.vtex.com/docs/guides/headless-cart-and-checkout
- Checked
- 10 Nov 2026, 06:45 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:b3491736022862faa399e2bcba34c66a47f6c5c589e1721b18d5f7592a4b1230
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Checkout API headless Report an error
“This guide explains how to implement a shopping cart and manage the checkout process in a headless ecommerce store, using the Checkout API to handle all interactions through API requests, without a traditional user interface.”
-
Orderform structure Report an error
“In the Checkout API, the VTEX shopping cart information is organized using the orderForm, an object containing all information relevant to the purchase, including products, shipping, and payment information.”
-
API payload changes Report an error
“New fields can be added in the Checkout API payload without previous warning.”
-
Cart endpoints Report an error
“When you use the Get current or create a new cart endpoint, you get an orderFormId in the response.”
-
Cart attachments Report an error
“Shopping cart attachments are orderForm objects containing order information related to: Customer profile Shipping address and delivery option Marketing data Payment data Merchant context data”
-
Order placing methods Report an error
“Place new order: Manage shopping cart information in your frontend and then use one API request to send all order information to VTEX.”
-
Recommended method Report an error
“This method is generally recommended.”
-
Pii masking Report an error
“VTEX Personal Identifiable Information (PII) data is masked by default.”
-
Order ownership cookie Report an error
“When a new cart is created, a new cookie named CheckoutOrderFormOwnership is sent empty alongside the existing checkout.vtex.com cookie, which contains the cart's orderFormId.”
-
Feature enablement Report an error
“Please contact VTEX support to enable this feature in your store. This feature is not available to stores using FastStore.”
-
Order completion window Report an error
“Your integration must use this information to complete the purchase process within 5 minutes. This involves sending payment information and then requesting order processing. Failing to perform these steps within 5 minutes will cause the order to be automatically canceled and tagged as incomplete.”
-
Saved credit cards Report an error
“To check if the customer has any saved cards, use the Get client profile by email endpoint. This endpoint returns the available cards. The card information is displayed in the availableAccounts array”
-
Save card optin Report an error
“You can enable a checkbox that allows the customer to choose if they want to save the credit card information or not.”
-
Process order endpoint Report an error
“you must request order processing by using the Process order endpoint after the order's payment is approved. If the payment has not been approved yet, it will return a status code 500 error.”
-
Order verification Report an error
“You can also use the Get order and List orders endpoints for this purpose. Another way to check the order updates is by integrating Feed v3 and Hook with your store.”
-
Address autofill Report an error
“GET Get address by postal code”
-
Pickup points Report an error
“GET List pickup points by location”
-
Recaptcha limitation Report an error
“reCAPTCHA integration doesn't work with Headless checkout. It only works with stores using Checkout v6.”
-
Payment connector warning Report an error
“Keep in mind that this process uses payment connectors configured in your VTEX environment.”
Scores citing this record
- The B2B Seller Catalogue & checkout
- The B2B Seller Extensibility & developer surface
- The B2B Seller Order operations & back office
- The B2B Seller European sovereignty
- The Data Protection Officer Catalogue & checkout
- The Data Protection Officer Extensibility & developer surface
- The Data Protection Officer Order operations & back office
- The Data Protection Officer Data ownership & exit
- The Data Protection Officer European sovereignty
- The Developer Catalogue & checkout
- The Developer Extensibility & developer surface
- The Developer Order operations & back office
- The Merchant Catalogue & checkout
- The Merchant Extensibility & developer surface
- The Merchant Order operations & back office
- The Merchant European sovereignty
- The Operations Lead Catalogue & checkout
- The Operations Lead Extensibility & developer surface
- The Operations Lead Order operations & back office
- The Operations Lead Data ownership & exit
- The Operations Lead European sovereignty
- The Skeptic Catalogue & checkout
- The Skeptic Extensibility & developer surface
- The Skeptic Order operations & back office