> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/site-configuration/payment-operations/loyalty/loyalty-access-pcats01-major-oil-override.md).

# Loyalty Access - PCATS01 Major Oil Override

The Withdraw Access feature allows a Major Oil Admin (MOA) to release the Major Oil's default exclusive lock on a site's PCATS01 loyalty configuration, granting the site the ability to manage that configuration independently. By default, the Major Oil Admin owns and locks PCATS01 on both the Verifone Commander Configuration Client and Verifone Commander Central, preventing site-level changes. Clicking Withdraw Access removes that lock so the site can configure their own loyalty (PCATS) settings. Also, the Withdraw access can be toggled between MOA and Merchant at any point of time, but after MOA gives access to Merchant (or vice versa), only one of them will have that access.

{% hint style="info" %}
The Withdraw Access button is visible to Major Oil Administrators only. After withdrawing access, the site gains the ability to manage PCATS01 loyalty configuration independently through Verifone Commander Configuration Client and Verifone Commander Central. The Major Oil Admin no longer holds an exclusive lock on that configuration once access is withdrawn.
{% endhint %}

To withdraw PCATS01 access for a site:

{% stepper %}
{% step %}
**Log In**

Log in to Verifone Commander Central as the Major Oil Administrator.
{% endstep %}

{% step %}
**Open Site**

Navigate to Commander Central > Site Management > Sites > (the specific site). Use the site search or hierarchy to locate the site by name or Service ID.
{% endstep %}

{% step %}
**Open Loyalty**

Select Payment Operations > Loyalty from the left column.

<figure><img src="/files/RJtLVOb9n6uImlAZicLn" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Withdraw Access**

Click Withdraw Access. After Withdraw Access is confirmed, the merchant can add PCATS01 via the Verifone Commander Configuration Client.
{% endstep %}
{% endstepper %}

<table><thead><tr><th width="172" valign="top">Field/Button</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top">Withdraw Access</td><td valign="top">Releases the Major Oil's default exclusive lock on PCATS01, granting the site the ability to manage loyalty configuration independently. Use this option when the site needs to configure their own loyalty settings but PCATS01 is locked under the Major Oil Admin. After withdrawing access, the site can modify PCATS01 loyalty settings through Verifone Commander Central or the Verifone Commander Configuration Client.</td></tr></tbody></table>

<br>


---

# 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.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/site-configuration/payment-operations/loyalty/loyalty-access-pcats01-major-oil-override.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.
