> For the complete documentation index, see [llms.txt](https://docs.verygoodsecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verygoodsecurity.com/cmp/developer-resources/guides/testing/payment-account-reference-par.md).

# Payment Account Reference (PAR)

### **PAR Testing Guide**

This guide explains how to test Payment Account Reference (PAR) in a controlled environment. You can simulate various responses using the respective Network PANs for the PAR endpoint and the expected responses for each.

**Very Important Information:** Please use only the provided test cards for this process. Under no circumstances should you input real PANs or live card data.

### Onboarding 

1. **Account Setup & Prerequisites:** Before merchants can use the the PAR service, their account must be configured.
   1. **Enable PAR on Your Account:** PAR must be explicitly enabled for your VGS account. Please contact <support@vgs.io> or merchant-designated VGS implementation representative to have this feature activated.
   2. **Configure Service Account:** Once PAR is enabled, merchants should configure their Service Account with the necessary permissions, including the `account-reference-numbers:read`  scope (in addition to `cards:read` and `cards:write`).
2. Create Card IDs using the PANs below

### **General Setup**

* **Content-Type Header:** `application/vnd.api+json`
* **HTTP Method:** `POST`&#x20;
* **Authentication:** <https://auth.verygoodsecurity.com/auth/realms/vgs/protocol/openid-connect/token>

**Base URL:**&#x20;

```
https://sandbox.vgsapi.com
```

**Initialize API Endpoint:**

```
POST /cards/{cardID}/payment-account-references
```

### PAR API - Test Card Scenarios

<table><thead><tr><th width="188.84320068359375">PAN</th><th width="120.47369384765625">Network</th><th width="153.2923583984375">PAR Response</th><th width="376.11968994140625">PAR</th></tr></thead><tbody><tr><td>5102589999999913</td><td>Mastercard</td><td>Successful PAR</td><td>500165B0HVP7GJMBJQETCP10SZBEA</td></tr><tr><td>5105105105105100</td><td>Mastercard</td><td>PAR Not Found</td><td>N/A</td></tr><tr><td>6539495236090154</td><td>Discover</td><td>Successful PAR</td><td>6001D13RLVD4PLTG4C5FNDXYB3J8T</td></tr><tr><td>6011000000010005</td><td>Discover</td><td>PAR Not Found</td><td>N/A</td></tr><tr><td>4545632267964322</td><td>Visa</td><td>Successful PAR</td><td>4001Z1B2C3H4E5F6G7T8J9K0L1G2N3P4</td></tr><tr><td>4957030420210462</td><td>Visa</td><td>Successful PAR</td><td>4001GJB84L0VVD9IZ7K68F0QVQPEQ</td></tr><tr><td>4147 2061 0764 1002</td><td>Visa</td><td>PAR Not Found</td><td>N/A</td></tr></tbody></table>

Currently PAR service only supports Visa, Mastercard and Discover cards.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verygoodsecurity.com/cmp/developer-resources/guides/testing/payment-account-reference-par.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.