Skip to content. | Skip to navigation

Sections
Credit Card Processing Simplified
Payment Processing Simplified
Personal tools
Home Processors Chase Paymentech CN!Express CX7000 Tech Profile for Chase Paymentech

CN!Express CX7000 Tech Profile for Chase Paymentech

 

The following is a sample Chase Paymentech Technical Profile completed for CN!Express® CX-7000 series™  Version 4.0. This is only an example showing the maximum CN!Express functionality. You may not be implementing all available functionality. You should only check off the functionality you intend to use.

Since CN!Express is already fully certified with Chase Paymentech, the Chase Paymentech certification team will take you through an abbreviated certification process. Primarily, Chase Paymentech is checking to see your communications are working properly and that you are sending the types of data and transactions they are expecting. Additionally, this mini-certification ensures all the Chase Paymentech server settings are configured properly.

We've included some comments throughout the sample.

 Chase Paymentech Technical Profile Questionnaire for Orbital Gateway

(Please complete one Profile Questionnaire for each software version

 
Technical Profile Questionnaire

For Orbital Gateway

 
Merchant Name:

Technical Contact:       e-mail address:

Contact Phone:       Fax # :

 1. What is the physical location of your computer system and associated connectivity?

Data center address

2. What are the Computer Make, Model, and Operating System of the platform you will be sending/receiving transactions to/from Chase Paymentech Solutions Orbital Gateway?

Computer Make

Computer Model

Operating System

 
3. Who is your ISP provider?

 4. Is your ISP access a dial up connection or a dedicated connection?

Dial Up

Dedicated (i.e. T1)

 5. Do you have a firewall this data will pass through?

Yes

No

 
6. What is the IP addresses of your host system(s)? (dynamically allocated IP addresses are not supported)

  Test       Production

  Test       Production

 You may use the following link to determine your IP address -

https://www.Paymentech.net/myip/index.jsp

NOTE: There is a 72-hour turnaround time for all additions of IP addresses.

 7. Please identify the integration option that you will use to send transactions to the Orbital Gateway.

 

XML – written by in-house programmers

 

Chase Paymentech Solutions supplied SDK (please identify which one and the version number)

Java – please specify SDK version number

- compiled for Windows NT, Win 2000, Solaris 2.8, Solaris 8, SunOS 5.8, Linux Red Hat 7.1 (using JVM-Java Virtual Machine)

 

Perl – please specify SDK version number

- compiled for NT SP6, Win2000 SP2, Linux Red Hat 7.x (using GCC 2.95), Solaris 8 (GCC 2.95)

 

C++ – please specify SDK version number

- compiled for Linux (using GCC 3.0.3 and greater), NT 4.0 SP6, Win2000 SP2, Win95 SR2, Win98 SE, WinXP Professional and Home (all Windows versions using MSVC 6.0a)

 

COM – please specify SDK version number

  • compiled for NT4.0 SP6, Win2000 SP2, Web Server 4.0 or later (for ASP applications), MS Visual Basic 6.0 (for VB applications), MS Visual C++ 6.0a SP5 (for COM/C++ application integration)

 

.NET – please specify SDK version number      

 

Baseline Requirement for SDK’s: You must have Command Line access on the system you intend to install any Orbital SDK on. If you do not, you may need additional support that Chase Paymentech Solutions does not provide.

 

Note: if the supplied SDK’s are installed on a platform other than the ones identified, please understand that non-compatibility and/or unknown errors could occur. While Chase Paymentech Solutions will make every effort to assist with the debugging of these issues, we may not be able to provide a solution.

 

Chase Paymentech Solutions supplied Web Services (SOAP) API

 

Third Party Software (please specify)

- Software Vendor Name

Auric Systems International

- Software Version

CN!Express CX-70XX

Version 4.0

 

8. What protocol will be used for on line processing?

 

X       HTTPS

Not Applicable (not sending online authorizations)

 

9. What Protocol will be used for batch processing?

 

S – FTP: User setup at the Chain (Company) level at the MID(Division) level

 X      Not Applicable (not sending batch files)

 

  1. What Chase Paymentech Solutions functionality do you intend to test?

 

X       Credit Card

X       Electronic Check Processing (ECP)

European Direct Debit

Gift Card

Pinless Debit

 

X       Full AVS

X       Zip only AVS

X       No AVS

 

X       Visa CVV2

X       MasterCard CVC2

X       Amex CID

X       Discover CID

UKDM CVC2 (switch)

 

International Currency (please specify)

 

Switch/Solo Cards

X       Amex TAA

X        Procurement/Purchasing Cards       X   Level 2              Level 3

 

X        Verified by Visa

X        MasterCard SecureCode

UKDM SecureCode

 

Merchant Descriptor (requires Risk approval and Division setup)

Bill Me Later (BML)

 

 X     Merchant Selectable Response (MSR) for AVS:

At the Company level X at the Division/MID level X

- which AVS responses should display the transaction as declined?

 

 

X      Merchant Selectable Response (MSR) for Card Security Value:

At the Company level X at the Division/MID level X

  • which CSV responses should display the transaction as declined?

 

Customer Profiles: at the Company level at the Division/MID level

 

Manage Billing (Profiles must be set up at the MID level)

Recurring

Deferred

Installment

 

Auth Recycle

 

X     Retry Logic

 

11. What types of transactions will you perform?



X      Authorize

X      Capture (Mark for)

X      Authorize/Capture (1 step process)

X      Void/Reversal

X      Force (can be used for voice auths)

X      Refund

 

12. How will you specify End of Day for settlement?

XML message

 X      Virtual Terminal

 X      Auto-Settle

Other - please specify merchant or submitter PID if applicable

 

 

13. What division(s)/Merchant ID(s) will you be testing (6 digit number)?

 

14. Who will be the application testing contact?

 

Contact Name:

 

Phone #:      

 

Fax#:

 

E-mail:      

 

15. When will you be ready to begin application testing?

 

ADDITIONAL INFORMATION:

 

 

Document Actions