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:
| Product | Category | Resource |
|---|---|---|
| PCI Gateway | Payment-ManageStore | Manage 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.
Path parameters
Rule identification.
Headers
Type of the content being sent.
HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.
Request body
Example request
{
"paymentSystem": {
"id": 1
},
"deadlines": [
{
"paymentOptions": [
{
"days": 30
}
]
}
]
}Response
OK
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
VtexIdclientAutCookiewas added to the APIapi-security-added
- ○
the endpoint scheme security
appKey AND appTokenwas added to the APIapi-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/toobject/request-property-type-changed
- ▲
the
salesChannels/items/request property type/format changed from/toobject/request-property-type-changed
- ▲
the
deadlines/items/response's property type/format changed from/toobject/for status200response-property-type-changed
- ▲
the
salesChannels/items/response's property type/format changed from/toobject/for status200response-property-type-changed
- ▲
- ▲
the response property
installmentOptions/installments/items/interestTaxbecame nullable for the status200response-property-became-nullable
- ○
the request property
installmentOptions/installments/items/interestTaxbecame nullablerequest-property-became-nullable
- ▲
- ▲
the response property
dateIntervalsbecame nullable for the status200response-property-became-nullable
- ○
the request property
dateIntervalsbecame nullablerequest-property-became-nullable
- ▲
- ▲
the response property
countrybecame nullable for the status200response-property-became-nullable
- ○
the request property
countrybecame nullablerequest-property-became-nullable
- ▲
- ▲
the response property
conditionbecame nullable for the status200response-property-became-nullable
- ▲
the response property
connectorbecame nullable for the status200response-property-became-nullable
- ○
the request property
conditionbecame nullablerequest-property-became-nullable
- ○
the request property
connectorbecame nullablerequest-property-became-nullable
- ▲
- ▲
the
paymentSystem/idrequest property type/format changed fromstring/tonumber/request-property-type-changed
- ▲
the
paymentSystem/idresponse's property type/format changed fromstring/tonumber/for status200response-property-type-changed
- ▲
- ▲
the
paymentSystem/idrequest property type/format changed fromnumber/tostring/request-property-type-changed
- ▲
the response property
antifraudbecame nullable for the status200response-property-became-nullable
- ▲
the response property
installmentOptions/installments/items/ruleIdbecame nullable for the status200response-property-became-nullable
- ▲
the
paymentSystem/idresponse's property type/format changed fromnumber/tostring/for status200response-property-type-changed
- ○
the request property
antifraudbecame nullablerequest-property-became-nullable
- ○
the request property
installmentOptions/installments/items/ruleIdbecame nullablerequest-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/toobject/request-body-type-changed
- ▲
the
country/isoCoderequest property type/format changed fromnumber/tostring/request-property-type-changed
- ▲
the
dateIntervals/items/endrequest property type/format changed fromnumber/tostring/request-property-type-changed
- ▲
the response's body type/format changed from
array/toobject/for status200response-body-type-changed
- ▲
the
country/isoCoderesponse's property type/format changed fromnumber/tostring/for status200response-property-type-changed
- ▲
the
dateIntervals/items/endresponse's property type/format changed fromnumber/tostring/for status200response-property-type-changed
- ▲