Chase Paymentech Debit Card Setup

This article is part of the Payment Processing Software Library Categories
Get it...
Credit Card Software Download
Install it...
Installation Upgrade & Migration
Connect to it...
→ Point Of Sale Integration
Set it up...
→ Quick Start Guide → Setup → Processor Setup Licensing
Learn to use it...
→ Manual & User Guide → Knowledge Base → Frequently Asked Questions Compliance Guide Merchant Account Rates User Interface Guides
Fix it...
→ Errors & Troubleshooting → Knowledge Base Corrupted Install Repair
Get Help...
Contact → Processor Support Contacts
More Info ...
Glossary Articles
See also...
911 Software Help

CreditLine Payment Processing Software Processor Setup - Chase Paymentech Debit. This site can also be reached at http://docs.911software.com

→ Looking for better rates?   Get a Free Credit Card Processing Cost Comparison!

Contacts

Please see Processor Support Contact List

Firewall And Connection Information

Select Parameters as Shown

Connection Configuration

IMPORTANT: If using a firewall, please open port 443 for both incoming and outgoing traffic

This information is set in c:\911\data\ccv_link.ini

[Link PAYMENTECHISO]<br\> Host=netconnect.paymentech.net
TestHost=netconnectkavar1.paymentech.net
TestBackupHost=netconnectkavar2.paymentech.net
Port=443
App=/NetConnect/controller
Verb=POST
AuthContentType=PNSISO/HCS
SettleContentType=PNSISO/HCS

Pin Pad Setup

CreditLine Credit Card Software interfaces to this device through a serial port. The serial port is specified in 911\data\CLCAPI.INI file like so:<br\> → Note: every pin pad will autopopulate a section with terminal client name like so [PINPAD.TERMCLIENTNAME]. Remove the three synch lines KeySyncDate, TPK and TAC to reinitialize the pin pad. Individual TerminalID settings for the pin pad must be placed under each relevant section (create if not present).

Initialization will occur on the second attempt (the first attempt will result in error)
→ Important: if using back office to record and edit stored cards make sure set a [PINPAD.xxxx] where xxxx is the BO server name with Enabled=0 to avoid the clcUI code bringing up the pin pad unless one is attached to the server.

Pin Pad Default for all terminals 
[PINPAD]
;TerminalID is taken from the Settlement Setup of the Debit Card by default
TerminalID=
Enabled=1 ; 1=PinPad is enabled
PortDef=COM1:9600 ; COM Port and Baud Rate for attached Pin Pads
;Pin Pad type 
;1 = Verifone (default)
;2 = IDT
;3 = Ingenico 3070
Type=1
UsePinPadSwipe=0; 0 = Do not use Pin Pad for card swipes. Default = 0;

;Terminal specific override (optional)
;TERMCLIENTNAME is the name given to the client by the calling API
[PINPAD.TERMCLIENTNAME]
;TerminalID is taken from the Settlement Setup of the Debit Card by default
;Note that multiple pin pads must have individual Terminal IDs assigned to them by the processor
TerminalID=003
Enabled=1
PortDef=COM2:115200
Type=3
UsePinpadSwipe=1
QuickSetPinEntryData=0
ForceCurrentKey=0
;The following section confirms the correct correct and synch - autopopulated
;REMOVE THIS SECTION TO REINITIALIZE 
KeySyncDate=20120426
TPK=CB60CA9DB4961B03
TAK=2EA255B90B9062D8
KeyIndex=1

Also see Pin Pad for individiual pin pad connection settings.

Merchant Setup

Authorization Setup

Select Debit if present or an un-used card type, such as unused gift card processor or private card and click Edit

Fill out the highlighted areas as shown and click OK

Important Notes

• Card Ranges are not used in debit cards and are ignored
• Class Default means that this setup is the default for all debit card connections (normally, you will only have one)

Settlement Configuration

• Enter CreditLine Settlement Parameters Dialog

• Select the fields as shown below

→ Make sure to check Apply to Auths!

Also See

CreditLine Setup Sheet