# Full Service Attendant

{% hint style="info" %}
&#x20;Full Service Attendant is Read-Only.
{% endhint %}

Full Service Attendant is a network setting that marks a transaction as being handled by an employee rather than the customer, affecting fees, prompts, and how the processor classifies the sale.

## Full Service Acquirer Settings

These settings define how the terminal communicates with the payment processor for full-service transactions. They ensure the transaction is routed, formatted, and classified correctly so the processor knows it was handled by an attendant rather than the customer.

<figure><img src="/files/SZybH3FGksCJ275bPoDM" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="171" valign="top">Field/Button</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top">FEP Enabled</td><td valign="top">This indicates whether full-service transactions should be sent through a front-end processor instead of directly to the host.</td></tr><tr><td valign="top">Key Index</td><td valign="top">The key index tells the terminal which encryption key to use when securing full-service transaction data.</td></tr><tr><td valign="top">Discard</td><td valign="top">Remove any changes made to this form.</td></tr><tr><td valign="top">Apply Changes</td><td valign="top">Save all changes made to this form.</td></tr></tbody></table>

## Full Service Attendant FEP Cards

These specify which card brands (like Visa, Mastercard, American Express, etc.) should be processed through the front-end processor when the transaction is handled by an attendant.

<figure><img src="/files/fGZOIBXybwyHR2WWWi75" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="181" valign="top">Field/Button</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top">Search Cards</td><td valign="top">To locate a card in the list, begin typing the card name in the search field. Select the card configuration to view or edit.</td></tr><tr><td valign="top">Card Table Index</td><td valign="top">The internal reference number the system uses to identify the card’s configuration entry</td></tr><tr><td valign="top">Card Abbreviation</td><td valign="top">A short code representing the card brand (e.g., VS for Visa).</td></tr><tr><td valign="top">Card Name</td><td valign="top">The full name of the card brand or network.</td></tr><tr><td valign="top">Lower ISO</td><td valign="top">The lowest BIN/ISO range that identifies cards belonging to this brand</td></tr><tr><td valign="top">Upper ISO</td><td valign="top">The highest BIN/ISO range for that card brand’s number range.</td></tr><tr><td valign="top">Pan Length</td><td valign="top">The allowed length(s) of the card number for that brand.</td></tr><tr><td valign="top">Card Enabled</td><td valign="top">Indicates whether the terminal is allowed to accept and process this card type.</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/site-configuration/payment-operations/full-service-attendant.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
