Documentation
Feedback
Guides
API Reference

Guides
CheckoutConfiguration
Get an account's orderForm configuration

The orderForm is the main object processed by VTEX checkout, and one of the most important data structures in the architecture of every VTEX store. It stores a lot of contextual information about the order which is important to the processing of the order: order items, client's personal data, delivery address, freight information, etc.

This guide will describe how to check the following settings applied currently to every orderForm in a specific account:

  • paymentConfiguration: payment configuration information.

    • requiresAuthenticationForPreAuthorizedPaymentOption: determines whether pre-authorized payments require authentication.
    • allowInstallmentsMerge: when in a multi-seller purchase scenario, it allows a flexible installment option that considers maximum installments for each seller, according to their respective configuration options.
    • paymentSystemToCheckFirstInstallment: option to apply a first installment discount to a particular payment system.
  • taxConfiguration: external tax service configuration information.

    • url: endpoint URL.
    • authorizationHeader: authorization header.
    • appId: custom data ID sent to the tax system.
  • minimumQuantityAccumulatedForItems: minimum SKU quantity by cart.

  • decimalDigitsPrecision: number of price digits.

  • minimumValueAccumulated: minimum cart value.

  • apps: apps configuration information.

    • id: app ID.
    • fields: app fields information.
    • major: app major version.
  • allowMultipleDeliveries: allows the selection of items from several delivery channels in the same purchase.

  • allowManualPrice: allows the editing of SKU prices directly in the cart.

  • savePersonalDataAsOptIn: allows users to select whether they want the store to keep their personal and payment data saved.

  • maxNumberOfWhiteLabelSellers: allows the input of a limit of white label sellers involved on the cart.

  • maskFirstPurchaseData: allows, on a first purchase, masking client's data. It could be useful when a shared cart is used and the client doesn't want to share its data.

  • recaptchaValidation: configures reCAPTCHA validation status for the account.

Getting an account's orderForm configuration

To get an account orderForm configuration, you need to use the Get orderForm configuration endpoint. In this request, you must send the accountname through the URL address, as shown by the example below:

https://{accountName}.{environment.com.br}/api/checkout/pvt/configuration/orderForm

After sending the request, the endpoint will return the response body containing the current account orderForm configuration, as shown in the example below:


_61
{
_61
"paymentConfiguration": {
_61
"requiresAuthenticationForPreAuthorizedPaymentOption": false,
_61
"allowInstallmentsMerge": null,
_61
"blockPaymentSession": null,
_61
"paymentSystemToCheckFirstInstallment": null,
_61
"defaultPaymentSystemToApplyOnUserOrderForm": null
_61
},
_61
"taxConfiguration": null,
_61
"minimumQuantityAccumulatedForItems": 1,
_61
"decimalDigitsPrecision": 2,
_61
"minimumValueAccumulated": 0,
_61
"apps": [
_61
{
_61
"fields": [
_61
"cart-extra-context",
_61
"cart-type"
_61
],
_61
"id": "cart-extra-context",
_61
"major": 1
_61
},
_61
{
_61
"fields": [
_61
"orderIdMarketplace",
_61
"paymentIdMarketplace"
_61
],
_61
"id": "marketplace-integration",
_61
"major": 1
_61
},
_61
{
_61
"fields": [
_61
"marketplacePaymentMethod"
_61
],
_61
"id": "cn-centauro-integration",
_61
"major": 1
_61
},
_61
{
_61
"fields": [
_61
"quantity",
_61
"deadlines_1",
_61
"interestRate"
_61
],
_61
"id": "customer-credit",
_61
"major": 1
_61
},
_61
{
_61
"fields": [
_61
"affiliateId"
_61
],
_61
"id": "affiliates",
_61
"major": 1
_61
}
_61
],
_61
"allowMultipleDeliveries": false,
_61
"allowManualPrice": true,
_61
"savePersonalDataAsOptIn": false,
_61
"maxNumberOfWhiteLabelSellers": null,
_61
"maskFirstPurchaseData": null,
_61
"recaptchaValidation": null,
_61
"maskStateOnAddress": null
_61
}

If you need to update any of your account's orderForm settings, access the Update an account's orderForm configuration Dev. Guide.

Error codes

The following errors may appear as a message in the response body.

401 - Unauthorized

  • Message error example (code ORD062): "Unauthorized". The credentials (Application Key and Application Token) used in this request are incorrect or not authorized to access this type of information.

_10
{
_10
"fields": {},
_10
"error": {
_10
"code": "ORD062",
_10
"message": "Unauthorized",
_10
"exception": null
_10
},
_10
"operationId": "8ec4b686-435f-42ab-8cfd-89306f888c3c"
_10
}

404 - Not Found

  • Message error example: "The requested URL was not found on the server": check that the URL data is correct.

_10
<body>
_10
<h1>404 Not Found</h1>
_10
<p>The requested URL was not found on this server.</p>
_10
</body>

Contributors
1
Photo of the contributor
+ 1 contributors
Was this helpful?
Yes
No
Suggest edits (Github)
Contributors
1
Photo of the contributor
+ 1 contributors
On this page