Gasboy FleetCor Dual Special Card Handler - Manual (Page 5)

MDE-4310B CFN Series FleetCor Dual Network Special Card Handler V1.0.1 · April 2007 Page 1
Overview Introduction
1 – Introduction
Overview
The FleetCor Dual Network Special Card Handler and some configuration changes allow a
CFN II or CFN III to support the features listed below. This special card handler requires CFN
II/Islander II or CFN III to operate. Gasboy Island Card Readers (ICRs) require Stargate
version 4.2K or higher.
The following are the features of the FleetCor Dual Network Special Card Handler:
• Host-controlled Personal Identification Numbers (PINs)
• Floating PINs (multiple PINs assigned to the same card)
• Host-controlled product authorization
• Host-controlled quantity restrictions
• Host-controlled third party cards (Visa
® , Mastercard ® , T-Chek, Gascard/CFN dual card)
• Host-controlled messages to user
Note: After installing the software, the participant should contact the FleetCor Network help
desk. The help desk should verify that the site(s) is set up for custom PINs and T-Chek
acceptance, the correct site number is used, and the site 99 password is set correctly, if
needed. Also, the help desk should verify if the transactions are being processed
properly and that product control is working.
When a card is swiped, the special handler identifies the card as a T-Chek or Gascard/CFN
dual card that is handled by the host site protocol.
Host-Site Communication Enhancements
• Extended site transaction authorization request response.
• Configuration - New system configuration parameters will be added to enable extended
site authorization requests.
• Vehicle field and issuer fields will be appended to the end of the request message if the
site is configured to use extended authorization.
Extended Host Transaction Authorization
• Authorization code - An optional 2-digit authorization code field may be included in the
host transaction authorization message.
• If a card contains an authorization code, that code will be checked before the transaction is
sent to the host for authorization. The authorization code returned from the host will be
checked later, but it must pass the encoded authorization code check first. If the product
authorization length is set to 0 in SYS_PAR the product will not be authorized before it is
sent to the host.
• Price Level - An optional 2-digit price level field may be included in the host transaction
authorization message.