Configuration

Update payment rule by ID

Updates information about a specific payment rule applied to the payment providers configured in your store.

Permissions

Any user or API key must have at least one of the appropriate License Manager resources to be able to successfully run this request. Otherwise they will receive a status code 403 error. These are the applicable resources for this endpoint:

ProductCategoryResource
PCI GatewayPayment-ManageStoreManage Store

There are no applicable predefined roles for this resource list. You must create a custom role and add at least one of the resources above in order to use this endpoint. To learn more about machine authentication at VTEX, see Authentication overview.

❗ To prevent integrations from having excessive permissions, consider the best practices for managing API keys when assigning License Manager roles to integrations.

put/api/pvt/rules/{ruleId}

Path parameters

ruleIdstring required
Example:fe6c470b-f80b-4bb1-a75c-378617f8767a

Rule identification.

Headers

Content-Typestring required
Example:application/json

Type of the content being sent.

Acceptstring required
Example:application/json

HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.

Request body

idstring required

Rule identification.

namestring required

Rule name.

isSelfAuthorizedboolean nullable required

Indicates whether the payment is automatically authorized.

requiresAuthenticationboolean nullable required

Indicates whether it is necessary to log in to make the payment.

enabledboolean required

Indicates whether the rule is enabled in the store.

installmentsServiceboolean required

Indicates whether any specific type of installment service is used.

isDefaultboolean nullable required

Indicates whether this rule should be considered the default for a given payment condition.

beginDatestring nullable required

Rule start date in ISO 8601 format (YYYY-MM-DDThh:mm:ss.fff), if applicable.

endDatestring nullable required

Rule end date in ISO 8601 format (YYYY-MM-DDThh:mm:ss.fff), if applicable.

multiMerchantListstring[] nullable required

Indicates the names of the accounts to which the rule is being applied exclusively.

externalInterestboolean

Indicates whether interest can be calculated externally.

minimumValuenumber nullable

Minimum payment transaction amount for the rule to be applied.

excludedBinsRangesnumber nullable

Range of card bins excluded from application of this rule.

Example request

{
  "paymentSystem": {
    "id": 1
  },
  "deadlines": [
    {
      "paymentOptions": [
        {
          "days": 30
        }
      ]
    }
  ]
}

Response

OK

idstring required

Rule identification.

namestring required

Rule name.

isSelfAuthorizedboolean nullable required

Indicates whether the payment is automatically authorized.

requiresAuthenticationboolean nullable required

Indicates whether it is necessary to log in to make the payment.

enabledboolean required

Indicates whether the rule is enabled in the store.

installmentsServiceboolean required

Indicates whether any specific type of installment service is used.

isDefaultboolean nullable required

Indicates whether this rule should be considered the default for a given payment condition.

beginDatestring nullable required

Rule start date in ISO 8601 format (YYYY-MM-DDThh:mm:ss.fff), if applicable.

endDatestring nullable required

Rule end date in ISO 8601 format (YYYY-MM-DDThh:mm:ss.fff), if applicable.

multiMerchantListstring[] nullable required

Indicates the names of the accounts to which the rule is being applied exclusively.

externalInterestboolean

Indicates whether interest can be calculated externally.

minimumValuenumber nullable

Minimum payment transaction amount for the rule to be applied.

excludedBinsRangesnumber nullable

Range of card bins excluded from application of this rule.

Example response

{
  "paymentSystem": {
    "id": 1
  },
  "deadlines": [
    {
      "paymentOptions": [
        {
          "days": 30
        }
      ]
    }
  ]
}

Changes

Changed in 10 of the 52 revisions of this API.2110

    • the endpoint scheme security VtexIdclientAutCookie was added to the API

      api-security-added

    • the endpoint scheme security appKey AND appToken was added to the API

      api-security-added

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • request body became optional

      request-body-became-optional

    • the deadlines/items/ request property type/format changed from / to object/

      request-property-type-changed

    • the salesChannels/items/ request property type/format changed from / to object/

      request-property-type-changed

    • the deadlines/items/ response's property type/format changed from / to object/ for status 200

      response-property-type-changed

    • the salesChannels/items/ response's property type/format changed from / to object/ for status 200

      response-property-type-changed

  • 660227ebd7e811See the full diff
    • the response property installmentOptions/installments/items/interestTax became nullable for the status 200

      response-property-became-nullable

    • the request property installmentOptions/installments/items/interestTax became nullable

      request-property-became-nullable

  • 6ca16ae78f1b11See the full diff
    • the response property dateIntervals became nullable for the status 200

      response-property-became-nullable

    • the request property dateIntervals became nullable

      request-property-became-nullable

  • 7d66c05ad76f11See the full diff
    • the response property country became nullable for the status 200

      response-property-became-nullable

    • the request property country became nullable

      request-property-became-nullable

  • f750e068231622See the full diff
    • the response property condition became nullable for the status 200

      response-property-became-nullable

    • the response property connector became nullable for the status 200

      response-property-became-nullable

    • the request property condition became nullable

      request-property-became-nullable

    • the request property connector became nullable

      request-property-became-nullable

    • the paymentSystem/id request property type/format changed from string/ to number/

      request-property-type-changed

    • the paymentSystem/id response's property type/format changed from string/ to number/ for status 200

      response-property-type-changed

  • a38afb87a11b42See the full diff
    • the paymentSystem/id request property type/format changed from number/ to string/

      request-property-type-changed

    • the response property antifraud became nullable for the status 200

      response-property-became-nullable

    • the response property installmentOptions/installments/items/ruleId became nullable for the status 200

      response-property-became-nullable

    • the paymentSystem/id response's property type/format changed from number/ to string/ for status 200

      response-property-type-changed

    • the request property antifraud became nullable

      request-property-became-nullable

    • the request property installmentOptions/installments/items/ruleId became nullable

      request-property-became-nullable

    This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • the request's body type/format changed from array/ to object/

      request-body-type-changed

    • the country/isoCode request property type/format changed from number/ to string/

      request-property-type-changed

    • the dateIntervals/items/end request property type/format changed from number/ to string/

      request-property-type-changed

    • the response's body type/format changed from array/ to object/ for status 200

      response-body-type-changed

    • the country/isoCode response's property type/format changed from number/ to string/ for status 200

      response-property-type-changed

    • the dateIntervals/items/end response's property type/format changed from number/ to string/ for status 200

      response-property-type-changed