This article covers the process for getting a Chase credit
card reader up and running. The unique factor with these particular credit card
readers compared to OTHER options, is that the Terminals page doesn't really
care about the Serial Number, but instead the static IP that is used by the
credit card reader. The FullCount terminal does not need a static IP, but the
credit card reader requires it in order to work with our system.
Requirements:
A
Chase Credit Card Reader (supported model names?)
A
Supported FullCount Terminal, Tablet or Kiosk
A
static IP address (for the CC reader)
Steps
Step 1: Initial Reader Setup
Chase credit card readers should ship ready to go. Powering
on the reader should boot the Chase Payments application.
Step 2: Setup Network Connection (pages 5 - 9 in PDF)
Please refer to the attached PDF for screenshots if needed - J:\FullCount\Documentation\Support\JPMorgan
Chase\Chase Payment Application Setup Guide 1.0.pdf
With
the device powered on and the Chase Payments application running, tap
the Chase logo 10 times to bring up a menu in the top left of the
screen.
Open
the menu and select Exit.
Locate
the Settings icon and select it.
Input
the password 350000.
Select
Network & internet.
Toggle
Wi-Fi On.
Select
Wi-Fi.
Select
the Wi-Fi you need to connect to.
Enter
your SSID password and select Connect.
Observe
your Connected status. Continue to the next Step to set a Static IP
(required).
Step 3: Setting a Static IP Address (pages 12 - 14 in
PDF)
If you just completed Step 2 - skip to #6 in this section.
With
the device powered on and the Chase Payments application running, tap
the Chase logo 10 times to bring up a menu in the top left of the
screen.
Open
the menu and select Exit.
Locate
the Settings icon and select it.
Input
the password 350000.
Select
Network & internet.
If the
device is connected via Wi-Fi, select Wi-Fi.
Select
the gear icon next to the Wi-Fi network to which the reader is
connected.
Select
the pencil icon in the top right.
Expand
Advanced options and scroll down to IP settings.
Change
IP settings to Static and enter the network info.
Save.
If the
device is connected via ethernet, select Ethernet.
Select
Configure Ethernet.
Select
Static IP under Connection Type
Enter
the network info.
Save.
Exit
Settings and select the Chase Payments application.
You can find more detailed information
at J:\FullCount\Documentation\Support\JPMorgan Chase\Chase Payment
Application Setup Guide 1.0.pdf
Step 4: Connect with a FullCount Device
The Chase credit card terminals need to be linked to the
FullCount device by using the static IP address that gets assigned to the
reader. The Serial Number should still be added for documentation purposes
- but it is technically not required.
After adding the IP address and Serial Number, you should
have a successful connection and can test the payment option. Please ensure
that all other necessary areas have been enabled through Mode Settings (Credit
set to Yes) and the Department in use Allows Other Forms of Payments.
Step 5. Creating and Installing a SSL Certificate
The first time a Chase credit card terminal is set up, we
have to install a FullCount SSL cert on it to secure the WebSocket connection
between it and our POS terminal. This is currently a fairly manual process
involving development and systems.
Contact
development to disable SSL error-handling on the POS terminal associated
with the credit card reader.
Restart
the application for those settings to take effect.
If the
terminal is running self-service, log in to the self-service application.
When the application gets to the customer check-in screen, the credit card
terminal should turn blue, indicating it is generating a new cert request.
Wait until the credit card terminal turns white again.
If the
terminal is running retail mode, log in to the retail mode application.
When the application gets to the operator sign in screen, the credit
card terminal should turn blue, indicating it is generating a new cert
request. Wait until the credit card terminal turns white again.
Contact
development, letting them know the credit card device generated the
certificate request.
Development
will then provide the certificate request to systems, who will generate
and SSL certificate.
Systems
will provide the SSL certificate to development, who will add it, and its
expiration date to the database.
Once
the new certificate is in the database, logout of the application and log
back in (getting to the customer check-in screen or operator sign-in
screen). The credit card device should turn blue again, indicating it is
installing the new certificate. It will then reboot.
The
certificate should now be installed. Contact development to re-enable SSL
error-handling on the POS terminal.
Restart
the application for those settings to take effect.
Start
a credit card payment to make sure the POS can properly communicate to the
credit card device.