MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 73 OF 138

EXHIBIT G

FLEET CARD SERVICE REQUIREMENTS

This exhibit details Fleet Card service requirements and Contractor responses to how these requirements will be met as submitted with their bid.

1. RESERVED – Identifies card products available in Exhibit A.

2. ADMINISTRATION OF ACCOUNTS

2.1 System must allow for Program Administrator to setup new accounts online – including ordering and registering cards, establishing User ID and password.

2.2 System must allow for Program Administrator to add, edit, or remove single or multiple Product Codes (PC) or Merchant Category Codes (MCC) from multiple card accounts at once.

2.3 System must allow for Program Administrator to initiate one-time overrides per transaction.

2.4 System must allow for Program Administrator to establish roles, access, and authority levels for all user types (i.e. managers, approvers, cardholders) within the Purchasing Entity.

2.5 System must allow for Program Administrator to unlock system access, reset User ID and reset password for any User within the Purchasing Entity.

2.6 System must allow for Program Administrator to see changes made to a card profile and who made those changes.

2.7 System must allow for system to allow Program Administrator to view cancelled, deactivated and suspended cards within the Entity.

2.8 System must allow for Program Administrator to order and issue replacement cards (singular or multiple simultaneously) online.

2.9 System must allow for Program Administrators and Cardholders to access statements online.

2.10 System must allow for Program Administrators and Cardholders to mark accounts for paper or paperless statement delivery.

2.11 System must notify Program Administrators and Cardholders of statement availability.

2.12 System must allow for Program Administrator and Cardholders to check status of cards and view account information including but not limited to:

• balances

• limits

• charges

• declined transactions

• spend history

• default accounting codes

• demographics

2.13 System must allow for the Program Administrator to choose the billing cycle close date for the Purchasing Entity. The billing cycle date will be established at account implementation and will be set for the Purchasing Entities’ agreement period.

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 74 OF 138

2.14 System must have the ability to roll-up billing to managing account level or bill at department level as determined by the Purchasing Entity.

2.15 System must display all transactions in US Dollars.

2.16 System must be able to restrict fuel type at the card and/or vehicle level by not allowing the wrong fuel type to be purchased and by being able to report exceptions for wrong fuel type.

2.17 System must be able to apply hard limits on quantity (gallons) of fuel dispensed.

2.18 System must be able to restrict maintenance purchases.

2.19 System must allow for Program Administrator to reset Driver PIN online and in real time.

2.20 System must have the ability for Program Administrator to set/change PIN for each driver and/or vehicle.

2.21 System must be able to provide federal fuel tax exemption prior to invoicing.

2.22 Reserved, see Exhibit D Establishing an Account.

2.23 System must allow for Program Administrator to edit User ID, role and authority level online.

WEXOnline® allows the Program Administrator, or other individuals with appropriate permission levels, to add/edit new online users, manage existing users, and manage online enrollment requests. The module also allows for a prospective user to self-enroll online and have their request route to a Program Administrator to be approved and have the appropriate level of access assigned to them by the Administrator. A prospective user is not granted any level of access until after their request has been approved by a Program Administrator and their level of access is assigned.

The administrator retains ultimate control over access and assignment of roles, authority level and privileges allowed online. The module contains prepopulated templates for roles with varying levels of permissions available online to control the access an individual may have for their given job duty. The module also allows for users to create custom roles for levels of access specific to an individual or job duty. This creates appropriate account and system access, based on user responsibilities; ultimate control over who has access to the module, what level of access, and to what accounts; and the ability to track user logins.

Additionally, WEXOnline® allows users to reset their passwords on their own should they need to do so. This allows for a greater level of control at the user level and helps minimize the need to reach out for assistance with a reset.

2.24 System must have a minimum of seven (7) program hierarchies.

WEX’s system allows for robust account structures and reporting functionality. WEXOnline® supports nine (9) levels of hierarchy, providing a high level of detail and flexibility. The levels of hierarchy are customizable to the set-up of an individual entity participating in the contract to meet their specific needs.

For example, the State of Washington could be set up as a level 1 (L1) account with multiple L2 accounts hanging off of the overall contractual relationship. The accounts under the L2 would then have the ability to structure the departmental breakdown unique to that agency or entity.

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 75 OF 138

- Identifying accounts:

• Accounts can be identified in multiple ways in WEXOnline®. WEX offers custom reporting, account search functionality, and visual hierarchy layouts that are collapsible for finding and identifying accounts. Reporting can also offer account details about the account with the hierarchy regarding addresses (shipping, billing, primary and physical) total drivers and/or vehicles, total cards, default authorization profile, and primary shipping method and carrier.

- Reporting rebate earnings:

• WEX does offer rebate reporting that provides a full breakdown of rebate for a given time period. WEX will work with states at implementation to get the appropriate rebate reporting set-up to cover their needs.

- Reporting transaction data:

• All WEX transaction data is available within WEXOnline® to view and is reportable through the system. Additionally, WEX offers custom files and file interfaces to provide transactional data to customers. Below are several templated examples of how transactional data as well as authorization data can be accessed in WEXOnline®.

■ Custom Report/ Authorization Activity – This template helps users build a custom report with a direct view of authorization activity, including declines transactions.

■ Custom Report/ Transaction Management – This template permits users to generate a transactional-level report, whereby a user may analyze usage at certain merchants, or within certain timeframes, or exceeding specified dollar amounts and more.

2.25 System must allow for a Statewide Program Administrator account with access to view and pull reports for all transactions made by Purchasing Entities within the Participating State under this Master Agreement.

WEXOnline® allows for a Statewide Program Administrator with access to view and pull reports for all transactions made by Purchasing Entities within the Participating State under this Master Agreement. This would be accomplished by providing the administrator with an access role rooted at the top of the hierarchy. This can be accomplished through either the templated roles available within the module or creating a custom role should it be required.

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 76 OF 138

2.26 System must allow for Program Administrator to simultaneously activate, deactivate, suspend, and terminate cards online.

WEXOnline® allows the Program Administrator to update cardholder and vehicle information online, including simultaneously activating, deactivating suspending or terminating cards. This is accomplished by providing the administrator with edit access to vehicle/cards and driver information. The administrator can select multiple cards and then choose to activate, deactivate, suspend or terminate these cards simultaneously. Additionally, through the account support provided by WEX, an agency can also send large amounts of data to the WEX Premium Fleet Services Account Manager to handle for them on their behalf. For example, if a State’s motor pool had a large amount of new vehicles incoming or old vehicles being sold, the agency’s fleet manager could send a spreadsheet of the information to WEX to activate, deactivate, suspend or terminate cards on the State’s behalf. This often helps save time, energy and resources in a given agency.

2.27 System must allow for Program Administrator to update all cardholder information online, unless barred by Federal Regulation.

WEXOnline® allows the Program Administrator to update all cardholder and vehicle information online. This is accomplished by providing the administrator with edit access to cardholder/driver information. Additionally, through the account support provided by WEX, an agency can also send large amounts of data to the WEX Premium Fleets Services (PFS) Account Manager to handle for them on their behalf. For example, if a State agency had a large amount of seasonal workers coming on again to work, the agency’s fleet manager could send a spreadsheet of the information to WEX to activate, deactivate, suspend or terminate drivers/card holders on the State’s behalf.

This often can help save time, energy and resources in a given agency. WEX Fuel cards are not individual liability cards, so WEX is not aware of any Federal Regulations preventing the editing of cardholder information online.

2.28 Throughout the life of the Master Agreement and associated Participating Addendums, Purchasing Entities may have reason(s) to cancel a card (or a group of cards).

Cards or groups of cards can easily be canceled within the WEXOnline® module. Cards can be found under the Fleet Manager tab, administrator can search to find the card or group of cards an authorized user may want to cancel. Once a card has been reported lost, stolen, canceled, suspended or otherwise inactive, it is immediately invalidated in the WEX system. As stated above, this can be accomplished in WEXOnline® or by contacting the fleets Premium Fleet Services Account Manager or by calling WEX’s 24/7 customer service. After cancellation, all electronic authorizations associated with the card are declined at the time a purchase is attempted.

Additionally, once WEX receives proper notification, the fleet is relieved from liability for any subsequent charges.

2.29 When a card (or group of cards) is closed, a credit may be due to the card based on an overpayment, transaction credit, or something similar.

WEX’s receivables department reviews all credits on termed accounts and cards 90 days after termination. If the credit qualifies for a refund, WEX will process that transaction and send a check for closed accounts or post a credit to an account, if it is a cancelled card within an active account.

The timeline for a credit to post to an account can vary. This is due to the nature of the credit.

For example, in some cases a WEX representative may be able to confirm immediately that a credit is owed. In other cases WEX may need to do additional research or contact a merchant to

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 77 OF 138

verify additional information. WEX always works to resolve any owed credits as quickly as possible. Once the credit is confirmed to be owed to the customer, it is posted to the account and it will be reflected as a credit on the next invoice in the billing cycle. Should the customer require payment for the credit, WEX will process the credit for payment which typically takes 3-5 business days.

2.30 Foreign Transaction Fee

For US-based WEX card programs, the WEX system recognizes an assigned originating site ID and/or country code, provided to WEX by the merchant, for the corresponding country of origin of a transaction.

For example, if an agency transacted in Canada, WEX would receive the transactional data that would include a site ID, country code or similar identifying code, provided to WEX by the merchant, for the site. The WEX system would then compare that transaction’s location against the merchant location’s country of origin, in this case being Canada.

The check in the WEX system is also tied to the currency. For US-based WEX card programs, the currency is based in US Dollars. If a transaction comes through in Canadian Dollars, the WEX system would flag that transaction and assess the associated Foreign Transaction Fee.

Foreign Transaction Fees are denoted in WEX reporting to reflect the appropriate amount invoiced to a customer, versus what may show on a customer’s point of sale receipt from a merchant.

2.31 System must be able to route transactions through approval/workflow path as established by the Program Administrator.

WEXOnline® provides the ability to route transactions through an approval workflow path. The user roles required for this functionality and the process flow is outlined below.

An eligible approver is a User within a hierarchy who

• has the Approve Transactions permission

• has opted in to receive approval emails

• is an active online user

• a Fleet Manager/Program Administrator. A Fleet Manager will have all of the Manage

Transactions features and functionality including the Approve Transactions permission

• or, have a Custom Role that includes the Approve Transactions permission only.

For those responsible for reviewing transactions:

These users will have Manage Transactions without the Approve Transactions permission. They:

• can filter transactions

• can view transactions

• can change transaction status as follows:

- None → Follow Up

- None → Reviewed

- Follow Up → None

- Follow Up→ Reviewed

- Reviewed → None

- Reviewed → Follow Up

- will have all other existing manage transaction functionality (including upload receipt, MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 78 OF 138 reallocate, notes, view history)

- If there is an eligible approver at and/or above the reviewing user in the hierarchy, the user can see the "Email Approval Request" button and send an email to those Approvers.

For those responsible for approving transactions:

These users will have a Custom Role with the Approve Transactions permission that allows them to:

• filter transactions

• view transactions

• change transaction status as follows:

- reviewed → approved

- reviewed → follow up

- approved → reviewed

• receive and read approval emails sent from a User at and/or below their level in the hierarchy as long as long as the user has opted in to receive Approval Emails

Or, they can be assigned a Fleet Manager/Program Administrator role so they:

• can do everything available in the Manage Transactions

• Fleet Manager/Program Administrators also have the ability to change permissioning or access to allow for substitution scenarios when the approver role maybe out on vacation or leave allowing another user who is either new or would have a lesser role normal to step in an approve transactions in the Fleet Manager/Program Administrators absence.

2.32 System must allow for Program Administrator to add, edit, or remove security features (temporarily or permanently) in real time at the card account level including, but not limited to:

• dollar per transaction limit

• maximum daily/weekly/monthly spend

• transactions per day/week/month limit

• pay at pump only

• tank capacity limit

• type of fuel, by individual vehicle

• authorized State or Province

• Product Code (PC) blocks

The WEX system and the Fleet Manager module of WEXOnline® allows the fleet manager to add, edit, suspend, reactivate, and terminate cards and drivers, to add and manage card controls, and to view and download invoice details, card by card or simultaneously among a grouping of cards.

The Program Administrator has all the capabilities requested above, the ability to do so in real-time and simultaneously to multiple cards. Pay-at-pump ONLY functionality is systematically supported by WEX but cannot be done online. This is supported by the WEX Customer Service team on request or during account set-up at the time of implementation. Product code blocks are achieved by our product-type controls in the authorization profile card is assigned. These can be changed, created and applied in real-time and simultaneously to multiple cards.

Users can also:

• Assign card to driver, vehicle or location

• Transfer cards from one account to another

• Group cards into authorization profiles to enforce purchasing policies

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 79 OF 138

• Create organizational units or departments to better organize cards, vehicles and drivers for reporting and management purposes (initially added during implementation phase)

• Edit account information

WEXOnline® is structured to provide the ultimate flexibility to meet unique account program needs. The Administration module of WEXOnline® allows the fleet manager to create custom roles that can be assigned to online users to limit or broaden access into the system. The fleet manager can create custom roles which provide users with access to different sections – like the driver section. This setup allows them to focus on their defined tasks without giving broader permissions that could be abused.

Authorization profiles are the purchasing control parameters, or limits, that fleet managers assign to cards. This allows for easy management of the program to ensure purchasing policies are enforced each time a card is used.

WEX offers the flexibility for the fleet manager to name the authorization profiles via numeric or alphabetic naming scheme. For example, one group of profiles could be named “sedan,” and the profile could be applied to that group of vehicles. Or, the profile could be called “delivery driver,” and be set up for that type of employee. The fleet manager can assign as few or as many profiles as necessary

Fleet managers can add new profiles, view existing profiles, view cards assigned to each profile, clone, edit or modify the values, change the status of the profile, set account defaults, and reassign cards to other profiles.

Authorization control profiles allow the fleet manager to edit a profile and have that change impact all cards associated with that profile. There is no limit to the number of cards that can be assigned to a certain profile and this functionality eliminates the need to manually edit each driver or vehicle record when a policy changes.

Benefits include centralized account management; efficient administration of cards, driver, vehicles and authorization controls; and quick link navigation to all management features and functions.

2.33 System must allow for Program Administrator to assign card (with an identifying PIN or VIN number) to a driver, vehicle, department, etc. as determined by the Program Administrator.

A WEX card can be assigned to a vehicle/asset, driver, or organizational unit (or cost center) in the fleet, enabling the card to capture and track all purchase activity. This flexibility allows a Fleet Manager/Program Administrator to assign a card (with an identifying PIN (Driver/Vehicle ID) or VIN number) to a driver, vehicle, department or any other entity, asset or individual needing a card as determined by the Program administrator. When the card is swiped at the point-of-sale device, the driver is prompted to enter a Driver ID (DID), or PIN as referenced in the requirement, and the odometer reading of the vehicle in order to receive authorization for the ensuing transaction.

Each DID can be assigned to one, many, or all cards on the WEX account and can be generated by WEX at random, or assigned by the fleet customer. This 4- or 6-digit DID can be assigned to a driver, vehicle/asset, or organizational unit on the WEX account (based on the type of card preferred to use). For example, if Purchasing Entity decides to assign the card to the driver, the driver would typically enter a DID associated with the vehicle. If Purchasing Entity prefers to assign the card to a vehicle, typically the DID is associated with the driver.

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 80 OF 138

The DID, combined with the card and account validation rules, is queried against the WEX database for verification and transaction authorization. If valid, the transaction is authorized. The WEX card cannot be electronically activated without entering a valid DID, making the card useless to someone who has found or stolen it and does not know the DID. The authorization process acts as a security measure, and provides a layer of protection against fraudulent activity.

2.34 System must allow for Program Administrator to create an approval path of setting specific card limits higher than Entity established limits.

2.35 System must allow for Program Administrator and/or Cardholder to mark transactions sent to accounting for payment.

2.36 System must be able to send notifications of pending approval(s) based on established approval path.

2.37 System must allow for Program Administrator to lock transaction accounting code data from editing.

2.38 If capable, system must allow for Program Administrator to create templates for card/account set up (i.e. same billing address, TIN, workflow, etc.).

The WEX system allows for templates with different functions within the site as well as the ability to utilize “clone” functionality, which acts in the same manner as a template. Cloning functionality exists for card and authorization profile information to leverage like information (address, cost center, TIN, org/department, user defined fields, etc.) associated between card or driver types.

• Templated default limits for authorization profile & set-up

• Clone function

The WEX team lead by an assigned Strategic Relationship Manager and Premium Fleet Services Account Manager will work to set-up and establish these with customer during the initial implementation. For needs that arose after implementation the Premium Fleet Services Account Manager will be able to assist in setting up these functions.

2.39 If capable, system must allow for Users, with multiple roles within a program, (i.e., Cardholder & Program Administrator) to opt to have one login to be able to access all aspects of their accounts (dual role). If yes, provide details on how that functionality works/is implemented.

The flexibility of the WEXOnline® module allows for each user’s User ID to have one assigned role.

However, this requirement can be met by creating a Custom Role with all necessary levels of permissions to support scenarios where a user maybe both a cardholder and Program Administrator or have other roles and responsibilities with a given agency. Another example is when the user is a cardholder who also carries financial responsibilities and also need to access the system for pulling invoices and reporting, and making payments. The module allows for this user’s access to be customized to the specifications specific to their job function.

3. DATA COLLECTION AND MANAGEMENT

3.1 System must capture and display transaction data at the following minimum levels:

• Cardholder

• Approving official

• Entity office or unit

• Account/billing (available at different levels)

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 81 OF 138

• Entity Program Administrator or alternates (available at different levels)

• Participating State (all state entity transactional data, statewide administrative level and compliance review group)

3.2 System must have the ability to view transaction authorization/declines in real time.

3.3 System must post transactions within twenty-four (24) to forty-eight (48) hours of receipt from merchant.

3.4 System must have the ability to capture and display Level 1, Level 2, and Level 3 transaction data as made available from the merchant.

3.5 System must allow for Users to add notes, comments, and additional descriptions to a transaction in a separate field. This field must:

• Allow for alpha, numeric, and special characters.

• Be searchable

• Be reportable

• Be accessible to all hierarchies within the system

3.6 System must be able to capture and display merchant Tax Identification Number (TIN) or similar unique identifier.

3.7 System must allow for user to input a minimum of 150 character of Entity defined accounting code structure/segments at the transaction level.

3.8 System must allow for the Purchasing Entity to set requirements for accounting code segments (i.e. mandatory, non-mandatory, etc.)

3.9 System must allow for Purchasing Entity to define, edit, maintain, and upload valid value tables for each accounting code segment.

3.10 System must actively validate accounting segment data against valid value table data as determined by the Purchasing Entity.

3.11 System must allow for Program Administrator to assign, edit, and delete "default" accounting codes for all program hierarchies within the Purchasing Entity.

3.12 System must allow for User to save and edit frequently used accounting codes.

3.13 System must allow for a minimum of 99 accounting code splits per transaction.

3.14 System must allow for User to manually enter tax detail at the transaction level.

3.15 System must allow Program Administrator to download the entire Fleet Card number for use in other systems.

3.16 Participating States and Purchasing Entities have a need to access past transaction detail data in real time for a minimum of thirty-six (36) months throughout the life of the Master Agreement and Participating Addendum.

WEX’s system maintains past transactional data for a period of seven years (84 months). In the WEXOnline® module, files are retained for a period of 24 months. WEX’s Premium Fleet Services Account manager can fulfill requests from NASPO participating entities for transaction details going back to 84 months.

In addition, WEX Fleet ClearView™ data analytics module has no cap on accessible data, so users of WEX Fleet ClearView™ Essentials and Snap modules, offered as part of WEX’s core product

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 82 OF 138

offering at no extra cost, are able to access past transaction data for a minimum of 36 months throughout the life of the Master Agreement, as required.

3.17 Templates/defaults

At the time of account set-up and during implementation, WEX can establish user-defined fields with a State or Agency. User-defined fields can be used for any information or data the State or Agency may wish to capture. For example, as it relates to accounting information, a user defined field can be created for a particular GL Codes or set of GL codes and made a mandatory field as part of the card set-up template a user will have to complete in order to place a card order. This ensures the data will be assigned to it can be reported against. These fields can also be added, removed or edited after the account set-up as well given the user has the appropriate permissions to do so.

3.18 System must allow for user to upload and attach supporting documentation to the transaction in the following formats (at a minimum): pdf, jpg, png.

WEXOnline® Receipt Upload feature supports the uploading of supporting documentation to a transaction in the following file formats: .png, .jpg, .gif, and .pdf. Additionally, WEX has the ability to add support for more file types for upload should an agency require it. WEX will work with agencies should there be a file format they may need.

3.19 Contractor will be required to work directly with Participating State to develop effective strategies to address product code errors with merchants.

WEX routinely works with merchants, the processing networks, and point-of-sale providers to ensure product code accuracy and address issues. Once WEX becomes aware that there is an issue with a merchant(s), we work with all parties involved to identify the root cause and remediate it. For customers whose tax exemptions may be negatively impacted by a product code error, if WEX is able to definitively validate the product that was actually purchased, WEX will perform a transaction correction to ensure that either the exemption or reported taxes are accurate.

WEX also employs other tools, like WEX Fleet ClearView™, to assist both our Merchant Services Team, this team is responsible for working with merchants, networks and point of sales providers to remediate issues like product coding errors, and our customers to actively catch errors in merchant data, like bad product codes.

WEX Fleet ClearView™ is a dynamic a suite of powerful, cloud-based analytics solutions that automatically organizes, interprets, and intuitively displays fleet-related information. Critical data is presented in an intentional layout of simple and informative visualizations, helping fleet managers monitor operations, uncover card misuse and potential driver theft, understand trends, benchmark performance, investigate anomalies, and recognize cost-saving opportunities.

WEX offers the ClearView™ Essentials and ClearView™ Snap modules as part of our core product offering with extra no charge. Included in the ClearView™ Essentials module is a live product code cleansing algorithm fleets can utilize to proactively catch and see corrected product types.

Product Code Cleansing: The data scientists on the ClearView™ Team solved a long-standing, industry-wide issue by designing and developing a proprietary machine learning algorithm, which automatically detects and corrects inaccurate product codes transmitted by fuel merchants. The algorithm can make the following determinations with a 0.3% error rate:

• Categorize transactions by Product Group: fuel and non-fuel

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 83 OF 138

• Categorize fuel transactions by Product Type: gasoline and diesel

• Categorize gasoline transactions by Product Grade: regular, mid-grade, premium

Corrected values are used in ClearView™ analysis, calculations, and exceptions reporting.

Purchasing Entity can trust their product-related data displayed in ClearView™ and use it to make informed and confident decisions. This corrected information is aggregated in the Reports Module and displayed in ClearView™ transaction tables. ClearView™ displays both the type, grade and product level information provided by the merchant and the corrected values enabled by the algorithm. This information can be downloaded into Excel.

For information about how WEX handles disputed transactions, see 16.1.

3.20 Controls and Non-Vehicle Spending

The WEX Fleet card was developed to provide control and transparency. The card allows for fuel spending, non-vehicle spending at accepting locations within WEX’s closed-loop network, and non-fuel vehicle spending -- along with the ability to discern between those various types of purchases -- to allow ONLY purchases that comply with an agency’s policy or those that have been approved by a reviewer with permission to grant that level of approval.

One of the most significant advantages the WEX proprietary closed-loop card offers over an open-loop solution is our custom-built network that operates on product codes and not Merchant Category Codes (sometimes referred to as MCC codes). The WEX Fleet card can only be used at fuel and maintenance locations that accept the WEX card. This is the first line of defense against unauthorized or fraudulent spending, either of which could more easily occur with an open-loop credit card that can be used at any type of retailer.

WEX can ensure that all vendors accepting our cards comply with the same requirements and that data capture is tailored specifically to meet fleet customer needs.

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 84 OF 138

WEX Fleet Cards and open-loop credit cards both offer fleet managers the ability to track and set controls on fuel spend. However, the WEX closed-loop solution provides more in-depth transaction data, greater flexibility and security, and tighter controls than open-loop credit cards.

Greater Access to Level III Data: All WEX-accepting merchants are required to be capable of transmitting Level III data, and that level of data is transmitted on 99.8% of transactions. When a driver swipes the card, the point-of-sale device prompts him or her to enter the Authorization Prompt ID and odometer reading. Level III line-item detail allows fleet managers to better track expenditures and facilitates cost analyses, vehicle life-cycle analyses, and overall fleet management.

For example, entering the correct odometer reading helps provide valuable vehicle information such as cost per mile, miles per gallon, vehicle operating costs, and intelligence for preventive maintenance schedules and vehicle replacements. It can also help streamline administrative operations, reducing the time and resources devoted to accounting.

Additionally, the WEX proprietary closed-loop network removes the need for fleets to have to perform site lockouts for merchants that do not transmit Level III Data on open-loop networks.

Site lockouts can significantly reduce the number of accepting locations of an open-loop network card. This can be highly problematic for drivers utilizing open-loop solutions as they may pull up to a station that will decline their card due to merchant not being able to transmit Level III Data on an open loop solutions. This is not an issue for WEX’s proprietary closed-loop network.

The WEX closed-loop proprietary network has an added advantage for government fleets eligible fuel tax exemptions. The IRS requires Level III Data to be included in that transaction data in order for a Credit Card Issuer to invoice a fleet net of the eligible taxes. These are typically Federal Excise Taxes for unleaded and diesel fuel and can have a significant impact to the bottom line for a fleet if they are not exempted up front by the fuel card provider. Transactions on an open-loop network where Level III Data is not present are not eligible for tax exemptions by the fuel card issuer.

Greater Security: The cardholder is required to enter an Authorization Prompt ID for each transaction. This helps prevent the card’s use in case of loss or theft. Authorization Prompt IDs make fleet cards more secure and help limit internal and external fraud.

The Authorization Prompt ID can be linked to a specific purchase profile in WEXOnline®, providing further security by limiting expenditures to certain types of purchases, at specific dollar levels, and during specific timeframes.

Contrast this to a typical credit card, which usually requires no additional verification.

WEX customer have the ability to choose between Fuel Only cards and Custom Control cards.

Fuel Only cards permit the purchase of fuel -- such as gasoline, diesel, or alternative fuels -- based on the coding in the card’s magnetic strip. Non-fuel purchases are not permitted when non-fuel items are identified at the time of authorization. It does not prevent items such as car washes paid for at the pump as merchant devices do not send this authorization request to us.

Custom Control cards permit all allowed types of purchases, based on the coding in the magnetic strip, at WEX accepting locations. This includes fuel, maintenance, and other items, such as general merchandise. Fleet managers have the option to apply Product Type Controls, allowing certain product categories to be allowed or blocked. For example, “General Merchandise” could

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 85 OF 138

be deselected, allowing only Fuel and Parts/Service-related purchases. Custom Control Cards and Product Type Controls provide control over what drivers buy, not just where they buy it.

WEX accounts may be comprised of all Fuel Only cards, all Custom Control cards, or a mix of the two. This enables fleet managers to issue the appropriate card type based on a variety of purchasing needs.

Purchasing Controls: WEX developed its own closed-loop acceptance network among merchants and can control transactions at the merchant-type level. The WEX card is accepted at approximately 135,000 fuel and maintenance locations across the US.

Most generic credit cards can control the type of merchant. However, WEX goes a level deeper and is able to control the product type being purchased.

Product Type Controls: Product Type Controls are groupings of like products separated by type such as services, fuels, oil and fluids, food, etc. These controls enable or disable access to specific product categories, within WEX’s closed-loop network of fuel and service merchants. WEX uses Level III data to allow customized card controls that allow use only at certain times and/or on specific product types.

Fleet managers can then set spending limits at the transaction level:

dollar limits, fuel quantity limits, and timeframe of purchase.

Product Type Controls enable the fleet manager to limit transactions within WEX’s pre-determined network of fuel and service vendors. For example, the fleet can allow drivers to purchase fluids, like washer fluid or oil, and disallow general merchandise, like snacks and soft drinks. A typical credit card would be open to all gas stations, and any merchandise that is available in this retail channel. For example, a driver could purchase electronics or snack food.

This opens up the business to unauthorized expenses and program abuse.

Purchase Controls: WEX Purchase Controls allow fleet managers to control the amount and frequency of purchases at the card level. Defining limits helps a fleet manager detect and prevent unauthorized transactions, potentially saving Purchasing Entity money by limiting unauthorized purchases. Fleet managers can use these tools to establish daily, weekly, twice monthly, or monthly limits for fuel and service expenditures. If a transaction is outside of the set limit, it is logged and recorded at the point of sale or, in the case of hard controls, declined at the point of sale.

Purchase Control Tools * Level

Per transaction dollar limit Card

Per period dollar limits (daily, weekly, twice monthly, monthly) Card

Per period # of transactions (daily, weekly, twice monthly, monthly)

Card

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 86 OF 138

Total Fuel per period (daily, weekly, twice monthly, monthly) Card

Total Non-Fuel per period (daily, weekly, twice monthly, monthly) Card

Total Gallons per period (daily, weekly, twice monthly, monthly) Card

Time of day (subject to server location’s time zone) Card

Day of week (subject to server location’s time zone) Card

*Enforcement of some limits depends upon adoption of specification and merchant participation.

3.21 Account Maintenance Services

The WEX system works off product codes that discern between what is being purchased. This includes maintenance services. If the WEX Product Type controls allow for maintenance services to be purchased in the card’s assigned profile, then the corresponding product/service being purchased will be reported as any other transaction would. The controls in place are stated in

3.20 and maintenance services can be opted out of entirely as well should those types of purchase be not allowed. All of these controls can be accessed through the WEXOnline® module.

Additionally, WEX also offers a tool we call WEXPay™ to provide drivers a mechanism that enables out-of-network purchases at an additional 398,000 merchants in the MasterCard® network.

Typically used for independent or geographically remote fuel and service sites, WEXPay™ utilizes a virtual card interface to provide the control of a fleet card with the convenience of a credit card.

This out-of-network tool reduces the number of out-of-network sites where drivers would have to use an alternative form of payment.

Using WEXPay™ in conjunction with a Custom Control fleet card lets Purchasing Entity set the rules for their drivers. Custom Control cards allow Purchasing Entity to set merchant, transaction, and even product type limits. WEX applies those limits to both WEX Fleet Card and WEXPay™ MasterCard transactions. Expanded coverage combined with integrated reporting and invoicing will further streamline Purchasing Entity’s fleet purchasing and operations.

How It Works

As a MasterCard issuing bank, WEX uses Single-Use Account Number technology to authorize a one-time payment to a merchant. The account number provided to the merchant by phone is fast and secure — good only for that one purchase.

When the merchant calls for authorization, WEX applies Purchasing Entity’s purchase controls and collect the same level of purchase detail, including Prompt ID and odometer. WEX integrates the purchase details into Purchasing Entity’s WEX Fleet Card invoice and reports. One card, one invoice, one report with the same controls and service our customers expect from WEX.

As an additional option for fleets that operate a call center type operation for maintenance approvals, WEX offers Purchase Log to facilitate payments to merchants that accept MasterCard®.

Lastly, WEX does offer an ancillary product that is separate from our fuel card offering that and completely optional for use that we call Purchase Log. Purchase Log is a web-based interface that allows fleet-designated staff to securely log in to WEX’s MasterCard® settlement website and enter pertinent Level III data associated with a transaction (or invoice). This can include up to six entry fields for the fleet-specific data such as billing codes. Once the transaction information and

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 87 OF 138

payment amount is entered, a virtual card/single use ghost account with expiration dates and CVC2 values is presented. The fleet provides this to the merchant for payment. The Purchase Log product typically works well for fleets that operate a call center or central garage locations where an authorized fleet or service manager is working directly with service merchant locations who is servicing an asset of theirs. Purchase Log helps facilitate safe, secure, quick and easy payment.

Additionally, it allows for maximum data capture to feed fleet management systems and removes the need for having to invoice on account, issue checks or other forms of payment.

Using the MasterCard® payment network, Purchasing Entity’s see all requests and approve all transactions before they take place. Purchasing Entities can give their managers different levels of approval, while maintaining control over larger purchases.

Purchase Log uses Single Use Virtual Accounts to make secure payments to vendors. It is a safe and secure method of paying vendors that lowers the possibility of misuse or fraud, and significantly reduces paperwork.

Purchase Log transactions appear on their own invoice and report since the program is separate from WEX Fleet Card account. Reports can often be formatted to be imported into most customer accounting programs.

*Purchase Log purchases are subject to the MasterCard transaction processing rules and terms of use, including tax exemption rules and would be a separate account set-up.

3.22 Level 3 Data

When a driver swipes the card, the point-of-sale device prompts him or her to enter the Authorization Prompt ID (required) and odometer reading. Level III data line-item detail allows fleet managers to better track expenditures and facilitates cost analyses, vehicle life-cycle analyses, and overall fleet management. The Authorization Prompt ID is flexible to allow for the input of driver ID information for cards assigned to vehicles or department or the input of asset/vehicle ID information for cards assigned to a person or department, yet this Prompt ID is required for authorization.

For example, entering the correct odometer reading helps provide valuable vehicle information such as cost per mile, miles per gallon, vehicle operating costs, and intelligence for preventive maintenance schedules and vehicle replacements. It can also help streamline administrative operations, reducing the time and resources devoted to accounting.

Requiring the cardholder to enter an Authorization Prompt ID, typically referred to as a Driver/Asset ID or PIN, for each transaction helps prevent the card’s use in case of loss or theft.

Authorization Prompt IDs make fleet cards more secure and help limit internal and external fraud.

The Authorization Prompt ID can be linked to a specific purchase profile in WEXOnline®, providing further security by limiting expenditures to certain types of purchases, at specific dollar levels, and during specific timeframes.

Contrast this to a typical credit card, which usually requires no additional verification.

Additionally, if a merchant is not set-up to pass Level III Data on an open-loop network most times this additional prompting is non-existent.

WEX also offers flexible prompting at merchants who have adopted and coded to our most recent point of sale specification. This flexible or 3rd prompting allows fleets the option to ask for an additional field of data that is prompted at the pump. For example, this could be for a job number, MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 88 OF 138 cost center, department code or any other piece of data a fleet may want to capture. This is an optional feature that can be opted in or out of.

3.23 If capable, System will provide accurate Merchant latitude and longitude. WEX complies with this requirement.

3.24 Participating States and Purchasing Entities have the need to capture their state’s specific merchant diversity information (i.e. small business, minority owned, etc.) including Federal Diversity information.

WEX has all of the source data behind our merchant diversity information and standard reporting.

Should a Participating State or Purchasing Entity have a need to capture information specific to their state, WEX can provide this information on a state-by-state basis by building and delivering a custom report based on the individual state's specifications.

3.25 Ability for Contractor to initiate/create one-time overrides after hours with follow-up notification to Program Administrator.

The WEX Customer Service Department is open 24 hours a day, 365 days a year (366 days in leap years), the WEX Customer Service Department are WEX Employees hired by WEX, US based, fleet-trained in-house through a WEX training program, located in several call centers across multiple states and time zones and are always available to handle the needs of the fleet by calling the toll-free number 800-492-0669.

WEX has a No Driver Stranded (NDS) policy and will work with States and Agencies to tailor that policy at the time of account set-up to ensure it complies with that given fleets needs and own policies. This policy will be put into the WEX account notes available to our customer service representatives for account so that representative can follow the stated policy to assist a driver in need, help safeguard against possible misuse and appropriately notify a fleet when an occurrence may happen. NDS policy can include scenarios such as:

• Emergency and/or Extenuating Situations

• Out of Network

• Specific Agencies: State Police/Patrol, DOT, etc.

• Exceeding Authorization Controls

• Lost/Stolen Card

• Terminated Card

• Card Suspended for Fraud

• Card Suspended

• Driver is unsure of Vehicle ID but it is active

• Driver is unsure of Vehicle ID and it is not active

• Vehicle ID is terminated

In addition to the WEX NDS policy, WEX also offers a virtual card option to facilitate out of network payments called WEXPay™. WEXPay™ can also be used to facilitate a No Driver Stranded program.

WEXPay™ is a tool that enables out-of-network purchases at an additional 398,000 merchants in the MasterCard® network by utilizing a virtual card interface. Typically used for independent or geographically remote fuel and service sites, WEXPay™ provides the control of a fleet card with the convenience of a credit card. This out-of-network tool reduces the number of out-of-network sites where drivers would have to use an alternative form of payment.

MASTER AGREEMENT NO. 00819 – FLEET CARD SERVICES PAGE 89 OF 138

Using WEXPay™ in conjunction with a Custom Control fleet card lets Purchasing Entity set the rules for drivers. Custom Control cards allows the ability to set merchant, transaction, and even product type limits. WEX applies those limits to both WEX Fleet Card and WEXPay™ MasterCard transactions. Expanded coverage combined with integrated reporting and invoicing will further streamline Purchasing Entity’s fleet purchasing and operations.

The merchant would call the number on the back of the WEX Fleet Card, and the merchant will be routed MasterCard for a virtual payment. Use of WEXPay™ is subject to MasterCard terms & conditions and enrollment at the time of account set-up.

3.26 Roadside Assistance.

WEX Emergency Roadside is an existing WEX service delivered through partnership with National Automobile Club (NAC), one of the premier service motor clubs in the United States. Their mission since they were founded in 1924 has been to render Emergency Road Service promptly, courteously, safely and efficiently. WEX Emergency Roadside is available to all WEX Fleet Card users, and it’s free until it is used. Users must “opt in” using settings in their online profile. Service is available for any class of vehicle, including Class 7 and 8 vehicles.

Services include winching, fluid delivery, lockout services, towing, tire change, jumpstart and more. Benefits include no out-of-pocket expense for drivers, 24/7/365 service with toll-free call or by placing a digital service request, preferred rates and ease of pay through the WEX Fleet Card, coverage across the United States, Canada and Puerto Rico, with service right from the driver's seat using available mobile app access. Drivers can also call WEX customer service connected to NAC or call NAC directly.