> 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></tbody></table>

Currently PAR service only supports 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.