USAePay PCI

Contents of this Topic: ShowHide

Overview

• This topic describes the fields pertinent to a USAePay payment account.

• You must be logged into the program with an administrator User ID to create or edit payment accounts.

• USAePay can be used for Internet, Manual, or Point-of-Sale orders.

• For internet orders, check the settings of the main and/or cart-based system parameter WebTransactionType to make sure it agrees with your workflow. The choices are Pre-Authorize, Sale or Token. If payments are captured via SEOM, it should be set to Pre-Authorize. If payment is captured at the web store, it should be set to Sale. To pre-authorize or charge new transactions on import, WebTransactionType must be set to TOKEN.

USA ePay Access Credentials

APIAcessKey

• enter the Transaction Key obtained from USA ePay for Payment API access

ClientCertificateName

• enter the name of the SSL Secure Sockets Layer: a cryptographic protocol that provides communication security over the Internet. SSL encrypts the segments of network connections above the Transport Layer, using symmetric cryptography for privacy and a keyed message authentication code for message reliability. Predecessor of TLS, or Transport Layer Security. Certificate used for API communications

DeveloperMode

• this parameter is for use during development testing

• set to NO to run "Live Transactions"

• default setting is NO

HashKey

• if you have the USA ePay API set up to validate transaction authenticity through the use of a hash created using a Source PIN, enter the PIN for the given USA ePay account

ProcessorSendEmail

• set to YES to have USA ePay send customers an email confirmation
• default setting is YES

TestMode

• if set to YES, transactions sent to USA ePay are treated as "test" data
• if set to NO, transactions sent to USA ePay are treated as "live" data

UseClientCertificate

• set to TRUE to use a client SSL Certificate for communications with the USA ePay API
• default setting is NO   

USA ePay XML Access Credentials

APIAcessKey

• enter the Transaction Key obtained from USA ePay XML a mark-up language similar to HTML, except that it is used to structure data, not display it. XML is used to order data in such a way that it can be passed between applications with relative ease. for Payment API access

ClientCertificateName

• enter the name of the SSL Certificate used for API communications

DeveloperMode

• this parameter is for use during development testing

• set to NO to run "Live Transactions"

• default setting is NO

HashKey

• if you have the USA ePay XML API set up to validate transaction authenticity through the use of a hash created using a Source PIN, enter the PIN for the given USA ePay XML account

ProcessorSendEmail

• set to YES to have USA ePay XML send customers an email confirmation
• default setting is YES

TestMode

• if set to YES, transactions sent to USA ePay XML are treated as "test" data
• if set to NO, transactions sent to USA ePay XML are treated as "live" data

UseClientCertificate

• set to TRUE to use a client SSL Certificate for communications with the USA ePay API
• default setting is NO   

Created: 11/15/12

Revised:

Published: 04/14/2016