# Proprietary Fleet {% hint style="info" %} Proprietary Fleet is Read-Only. {% endhint %} Proprietary fleet cards are private, closed-loop fuel cards issued by a specific oil company or fuel brand for use only at their own stations. They’re different from universal fleet cards because they don’t run on the major card networks. Instead, they use the brand’s own processing system and often come with brand-specific pricing, discounts, and reporting tools tailored for commercial fleets ## Proprietary Fleet Acquirer Settings Acquirer settings for proprietary fleet cards define how the terminal communicates with the fuel brand’s private processing network, ensuring those closed-loop fleet cards are routed, authorized, and settled according to that brand’s specific requirements.

Field/Button	Description
Network
FEP Enabled	Indicates whether proprietary fleet transactions should be routed through the front-end processor instead of directly to the host.
Dealer ID	The unique identifier assigned to the station by the proprietary fleet network for routing and settlement.
Communication Options
Serial Port	Specifies which physical serial port the terminal uses when communicating over a serial connection.
Baud Rate	Sets the speed of data transmission for serial communication.
Bits	Defines the number of data bits used in each unit of serial transmission.
Parity	Determines the error-checking method used during serial communication.
Stop Bit	Indicates how the end of each serial data packet is marked to ensure proper timing and synchronization.
Discard	Remove any changes made to this form.
Apply Changes	Save all changes made to this form.

## Proprietary Fleet FEP Parameters Proprietary Fleet FEP parameters encompass organization specific data points—such as vehicle ID, driver’s license, driver ID, and odometer readings—that uniquely identify assets and operators while enabling secure tracking, analytics, and operational control across the fleet

Field/Button	Description
Department	Identitifies the type of purchase for fleet reporting.
Misc1	Optional custom field required by certain fleet programs.
Job ID	Work-order or job number used to track fuel by project.
Driver License	Indicates whether the driver’s license number should be collected.
Vehicle ID	Captures the fleet’s assigned vehicle or unit number.
Driver ID	Identifies the driver for authorization and reporting.
Misc2	Second optional field for additional fleet-specific data.
Odometer	Prompts for the vehicle’s odometer reading if required.
Last 4 digits of Acct Number	Controls printing of the account’s last four digits on receipts.
Discard	Remove any changes made to this form.
Apply Changes	Save all changes made to this form.

## Proprietary Fleet FEP Cards In a proprietary fleet configuration, FEP Cards define which fleet card types must be routed through the Front-End Processor (FEP) instead of going directly to the host.

Field/Button	Description
Search Cards	To locate a card in the list, begin typing the card name in the search field. Select the card configuration to view or edit.
Card Table Index	The internal reference number the system uses to identify the card’s configuration entry
Card Abbreviation	A short code representing the card brand (e.g., VS for Visa).
Card Name	The full name of the card brand or network.
Lower ISO	The lowest BIN/ISO range that identifies cards belonging to this brand
Upper ISO	The highest BIN/ISO range for that card brand’s number range.
Pan Length	The allowed length(s) of the card number for that brand.
Card Enabled	Indicates whether the terminal is allowed to accept and process this card type.
Accept Manual/Scanned Entry	It allows the terminal to take a card number entered by hand or captured by a scanner instead of reading it from the card itself.
Card Limits
DCR Auth Amount	It sets the maximum monetary amount the dispenser controller is allowed to authorize for a single card.
Discard	Remove any changes made to this form.
Apply Changes	Save all changes made to this form.

--- # 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/proprietary-fleet.md?ask= ``` 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.