> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/customer-documentation/petro-and-c-store/commander-central/commander-central-user-guide/account-types-and-features.md). # Account Types and Features Currently, Verifone Commander Central is designed to support a diverse set of users, each with specific responsibilities and access levels. Below is an introduction to the four primary account types: * Merchant - They are the C-Site owners or operators for managing the daily operations of a gas station. * Major Oil - They sell fuel products under well-known names. Branded gas stations are C-Sites that operate under the branding of these major oil companies. * VASC - They are the Verifone Authorized Service Contractors that have received a certification through Verifone’s training course. They are responsible for setting up, configuring, and ensuring proper operation of Verifone’s POS equipment. * Partner - They develop complimentary products or solutions that are designed to connect with, extend, or enhance the Verifone POS equipment. These partnerships are built on shared standards, APIs, or certifications to guarantee reliability and performance. The following table organizes accessible features by mapping them to the above four account types for visibility and comparison.

Feature	Merchant	Major Oil	VASC	Partner
Site Provision	Yes	Yes	No	No
Hierarchy	Yes	Yes	Yes	Yes
Site Onboarding	Yes	No	Yes*	No
Onboarded Device Swap	Yes	No	Yes*	No
Site Assets Data	Yes	Yes	No	No
Transaction Data	Yes	No	No	No
Transaction Data through API (T-Log)	No	No	No	Yes*
Fuel Price Change API	No	No	No	Yes*
Loyalty and Mobile Configuration	Yes	Yes	No	No
POS and Forecourt Configuration	Yes	No	Yes**	No
Payment Configuration	Yes	Yes	Yes*	No
VIPER (EPS) Table Management	Yes	Yes	No	No
Major Oil Policy	No	Yes	No	No
Verifone Commander Generated OTP	Yes	No	No	No
Commander Reports	Yes	No	No	No
Commander Fleet	Yes	No	No	No
Access Control	No	No	Yes*	No
Devices	No	No	Yes*	No
Promos and Discounts	No	No	Yes*	No
Reporting	No	No	Yes*	No
Store Operations	No	No	Yes*	No
System Settings	No	No	Yes*	No

\*Requires merchant administrator authorization. \*\*VASC access to Payment Configuration is granted per configuration area, not as a single on/off setting. Most areas grant View and Edit together by default; Fuel Prices is the exception and defaults to View only, with Edit requiring a separate, explicit action by the site administrator. See [VASC Site Management](https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/external-access-approval/vasc-site-management) for the full list of configuration areas and their default permission levels. --- # 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://commanderhelp.verifone.com/customer-documentation/petro-and-c-store/commander-central/commander-central-user-guide/account-types-and-features.md?ask=&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.