Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


Use the values in the tables below to configure the Paymentech payment provider/authorizer with the described settings.


(The procedures for accessing and configuring these settings are described in Add an Authorizer.)

Parameter

Value

Comments

AUTHORIZER NAME

Paymentech

Can be any meaningful value.

AUTHORIZER CODE

Paymentech

This value should exactly match the provider/ authorizer Bean implementation.
(Service Implementation Bean is a term used in Java Platform, Enterprise Edition,
for a Java object implementing a Web service.)

Do not change if you are not sure.

SITE URL
Test: 

Production:


http://www.paymentech.net/download/

http://www.paymentech.net/download/

The field must be populated, but the value is not currently used.
Any value is valid.
Suggest using specified values for consistency/clarity.

LOGIN URL
Test:

Production:


https://wsvar.paymentech.net/PaymentechGateway

https://ws.paymentech.net/PaymentechGateway


URL/SOAP Endpoint for payment processing.

CUSTOM URL 1


Not used

START DATE

10/20/08 

Effective date

END DATE

 

Ending date, as applicable. Can be empty.

STATUS

Active 

Should be "Active" for the current provider.
(Status of "New" is not recommended)

(The procedures for accessing and configuring these settings are described in Add Authorization Info.)

Parameter

Value

Comments

AUTHORIZER NAME

Paymentech

Match the value in the Authorizer Name field in the Authorizer parameters.

AUTHORIZATION INFO CODE

Paymentech

Any meaningful value

USER NAME

Unique for each merchant

Paymentech Orbital Connection Username

PASSWORD

********

Paymentech Orbital Connection Password

EXTERNAL MERCHANT ID

Unique for each merchant,
value provided by Paymentech

Assigned by Paymentech MerchantId

TERMINALID

Unique for each merchant,
value provided by Paymentech

Assigned by Paymentech TerminalId

PAYMENTECH BIN

Unique for each merchant,
value provided by Paymentech

Assigned by Paymentech BIN (Bank Identification Number)

Example:
  "Tampa (000002)"

PAYMENT TOKENIZATION
ENABLED

Yes/No

Tokenization is supported.
Can be enabled (Yes) or disabled (No), as applicable

DOES AUTHORIZER SUPPORT
MULTIPLE CAPTURE AGAINST
SINGLE AUTHORIZATION?

Yes

Supports multiple captures against a single authorization.
Must be "Yes"

START DATE

11/17/15 

Effective date

END DATE

 

Ending date, as applicable. Can be empty.

CURRENCIES

By default, all available
currencies are supported

Select from list of available currencies, as applicable. If empty, all currencies are considered to be supported.

 ITEM TYPES 
Select from a list of available catalog item types. (Optional)

With this parameter, authorizers can be set up to process payments using one or more specific catalog item types. Multiple authorization info configurations can be set up for one or more authorizers using different codes, each associated with a unique item type or item types. Order items can then be processed through the authorizer/authorizer code that is based on the item's corresponding type.

Item types are defined in EDGE System Admin>Catalog>Item Types.

 PAYMENT TYPES

Credit Card

 Credit Card processing is supported. Checking must be selected.

DISABLE FRAUD DETECTION
FOR ORDER SOURCES


Not Used

STATUS

Active

Should be "Active" for the current provider.
(Status of "New" is not recommended)

(The procedures for accessing and configuring these settings are described in Configure Authorization Info Parameters.)

Parameter

Default Value

Comments

DoNotProcessTransaction

No

Optional parameter.

For payment transactions that are for reporting purposes only. When "Yes," third parties that manage their own payments can send full transaction details upon order import so that EDGE can track the payments in an Order Details page or Payment Transactions report without actually processing any payments.

Valid values:

  • Yes - a payment transaction WILL NOT be processed
  • No (default value) - a payment transaction WILL be processed





  • No labels