Use the values in the tables below to configure the Mercury 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

Mercury

Can be any meaningful value.

AUTHORIZER CODE

Mercury

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:


https://w1.mercurycert.net/PaymentsAPI/

https://w1.mercurypay.com/PaymentsAPI/

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://w1.mercurycert.net/PaymentsAPI/

https://w1.mercurypay.com/PaymentsAPI/


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

Mercury

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

AUTHORIZATION INFO CODE

Mercury

Any meaningful value

USER NAME

Unique for each merchant

Mercury MerchantId

PASSWORD

********

Mercury Password

EXTERNAL MERCHANT ID


Not Used

TERMINALID

Unique for each merchant,
value provided by Mercury

Assigned by Mercury TerminalId

PAYMENTECH BIN

 

Not Used

PAYMENT TOKENIZATION
ENABLED

No

Tokenization is not supported.
Must be "No"

DOES AUTHORIZER SUPPORT
MULTIPLE CAPTURE AGAINST
SINGLE AUTHORIZATION?

No

Does not support multiple captures against a single authorization.
Must be "No"

START DATE

11/17/15 

Effective date

END DATE

 

Ending date, as applicable. Can be empty.

CURRENCIES

USD

USD is the only supported currency.

 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 Gift Card Gift Card processing is supported. 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


For the Mercury gift card payment processor only, when this is set to “Yes,” then a the payment transaction type will be logged as “Authorization,” when, in actuality, Mercury only supports “Sale” transactions.