New Search
Award SummaryPage 22 of 33 <br />- Units <br /> <br />- Cost per Unit <br /> <br />- Gross Purchase Amount <br /> <br />- Exception Code 1 <br /> <br />- Exception Code 2 <br /> <br />- Exception Code 3 <br /> <br />- Purchase Method <br /> <br />- Service Type <br /> <br />- Federal Tax <br /> <br />- Primary State Fuel Tax <br /> <br />- Secondary State Fuel Tax <br /> <br />- State Sales Tax <br /> <br />- Local Tax <br /> <br />- Misc. Tax <br /> <br />- Vehicle User Codes 1- 5 <br /> <br />- Card User Codes 1 - 5 <br /> <br />- Driver User Codes 1 - 5 <br /> <br />- Location Number <br /> <br />- Fuel/Non-Fuel Indicator <br /> <br />- PO Number <br /> <br />- Net Purchase Amount <br /> <br /> <br /> <br /> <br />5.8 Editable User Identification Field <br /> <br /> <br />Contractor shall provide the Participants with the following editable user fields. <br /> <br />- Seven Levels of Hierarchy <br /> <br />- Create Agency, Department, Sub-Department, etc. card designations for highly <br /> <br />granular report refinement <br /> <br />- The seven levels of hierarchy is attached to each transaction for reporting <br /> <br />purposes <br /> <br />- Enhanced Data Capture Tied to Card <br /> <br />- 5 Vehicle-Specific User Code Fields (can be used to capture vehicle class, GVW, <br /> <br />On/Off Road designation, garage location, etc.) <br /> <br />- 5 Card-Specific User Code Fields (can be used to capture accounting strings, GL <br /> <br />codes, temporarily assigned project codes, etc.) <br /> <br />- 5 Driver-Specific User Code Fields (can be used to capture vehicle class, GVW, <br /> <br />On/Off Road designation, garage location, etc.) <br /> <br />- All the User Code Fields are attached to each transaction for reporting purposes <br /> <br /> <br />5.9 Smart Card Technology <br /> <br /> <br />Contractor will monitor the industry for this technology, and when available in the United <br /> <br />States, it shall offer this technology as a option to the Participants. The Contractor <br /> <br />would still continue to support traditional/magnetic-stripe-based security features such as <br /> <br />Card Verification Value (CVV), but it would also contain new features and data that are <br /> <br />specific to the chip application: <br /> <br /> <br />- Offline authorization controls would add security when an online authorization is <br /> <br />unavailable. Customers could determine the number and dollar amount of offline <br /> <br />authorizations allowed on their cards. <br /> <br />- Offline data authentication between the card and the terminal would protect <br /> <br />against fraudulently created accounts. Unlike magnetic stripes, which can be more easily <br /> <br />counterfeited, chips are virtually impossible to copy. <br /> <br />- The cardholder's PIN would be stored directly on the chip, allowing <br /> <br />authentication of the cardholder at the point of sale without having to go online. All <br /> <br />chip transactions will require a PIN for authorization, greatly reducing opportunities for <br /> <br />fraud. <br /> <br />- Definable individual credit limits <br /> <br /> <br />5.10 Unique Card Security Features <br /> <br /> <br />Contractor shall track a three month average on each card, of the dollars spent for fuel, <br /> <br />the gallons, and the dollars spent for non-fuel purchases. If the current month of <br /> <br />purchases for a single card exceeds a certain percent of the three, the account is then <br /> <br />reviewed by Contractor's fraud department and the Participant is contacted to determine if <br /> <br />the card is being abused. The future of this process is to notify you of this exception <br /> <br />through internet exception reporting. <br /> <br /> <br />5.11 RESERVED <br /> <br /> <br />5.12 PIN Number Capabilities <br />https://orpin.oregon.gov/open.dll/showDocSummary?sessionID=1921160&disID=985529&docTy...6/10/2008 <br /> <br />