---
title: "List all payment rules"
method: GET
path: "/api/pvt/rules"
tags: ["Configuration"]
---

# List all payment rules

`GET /api/pvt/rules`

Returns all payment rules applied to the payment providers configured in your store.

## Permissions

Any user or [application key](https://developers.vtex.com/docs/guides/api-authentication-using-application-keys) must have at least one of the appropriate [License Manager resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) 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-Make Payments | **View Payment Data** |

There are no applicable [predefined roles](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy) for this resource list. You must [create a custom role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creating-a-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](https://developers.vtex.com/docs/guides/authentication).

>❗ To prevent integrations from having excessive permissions, consider the [best practices for managing app keys](https://help.vtex.com/en/tutorial/best-practices-application-keys--7b6nD1VMHa49aI5brlOvJm) when assigning License Manager roles to integrations.

## Headers

- `Content-Type` string, required
- `Accept` string, required

## Response `200`

OK

- unknown[] — Array containing payment rules information.
  - unknown

## Changes

- **2024-01-16** `a38afb87a11b` — 4 breaking
  - the response's body type changed from `object` to `array` for status `200`
  - the response property `antifraud` became nullable for the status `200`
  - the response property `installmentOptions/installments/items/ruleId` became nullable for the status `200`
  - the `paymentSystem/id` response's property type changed from `number` to `string` for status `200`
- **2024-01-16** `e6bea95b9c18` — 3 breaking
  - the response's body type changed from `array` to `object` for status `200`
  - the `country/isoCode` response's property type changed from `number` to `string` for status `200`
  - the `dateIntervals/items/end` response's property type changed from `number` to `string` for status `200`

[Change history](https://skmtc.dev/vtex/apis/payments-gateway-api/changes/api/pvt/rules/get.md)

---

[API](https://skmtc.dev/vtex/apis/payments-gateway-api.md) · [All operations](https://skmtc.dev/vtex/apis/payments-gateway-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/vtex/payments-gateway-api/revisions/a38afb87a11b/schema)
