Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Localtab Group


Localtab
idShift4_Authorizer
titleAuthorizer

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

Parameter

Value

Comments

AUTHORIZER NAME

Shift4

Can be any meaningful value.

AUTHORIZER CODE

Shift4

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.shift4.com/

http://www.shift4.com/

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

Anchor
login_url
login_url
LOGIN URL
Test: 

Production:


Unique for each merchant

Unique for each merchant

URL for payment processing.
Must be obtained from Shift4. (The URL should be the same for all merchants within a single EDGE instance.)


Info
Refer to the ConnectionURL Authorization Info parameter for related information.


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)



Localtab
idShift4_Authorization_Info
titleAuthorization Info

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

Parameter

Value

Comments

AUTHORIZER NAME

Shift4

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

AUTHORIZATION INFO CODE

Shift4

Any meaningful value

USER NAME

 


Not used

PASSWORD

 


Not used

EXTERNAL MERCHANT ID

 


Not used

TERMINALID

 


Not used

PAYMENTECH BIN

 


Not used

PAYMENT TOKENIZATION
ENABLED

Yes

Tokenization is supported.
Must be "Yes"

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

Gift Card

 Both Credit Card and Gift Cart processing are supported. Either or both Credit Card and/or Gift Card must be selected.

Warning
titleImportant:
When configuring for gift card support, if you want Shift4 to allow refunds to the same gift card used for the original payment, the merchant's Shift4 account must be set up to specify that a PIN is NOT required for a refund back to the original gift card. Contact Shift4 customer support for information or assistance.


DISABLE FRAUD DETECTION
FOR ORDER SOURCES

 


Not Used

STATUS

Active

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



Localtab
idShift4_Authorization_Info_Parameters
titleAuthorization Info Parameters

The following Authorization Info parameters need to be configured for Shift4 (unless specified as an "Optional parameter"):   

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

Parameter

Default Value

Comments

ReceiptTextColumns

80

Defines how many columns in a receipt.

AccessToken

Obtain directly from Shift4 or generate as described in comments >

Optional parameter.
Value can be obtained in either of two ways:

  • Request and obtain value directly from Shift4. or
  • Generate the AccessToken by sending an FRC CE query with AuthToken and ClientGUID.

ClientGUID

Obtain directly from Shift4

  • Required along with AuthToken in an FRC CE query to exchange for (generate) an Access Token.
  • This field must be hard coded.
  • The API Team will require the Client GUID to be changed for each certification.
  • ClientGUID is also known as Application GUID (GUID = Globally Unique ID)

AuthToken

Obtain directly from Shift4

  • Required along with ClientGUID in an FRC CE query to exchange for (generate) an Access Token.
  • The Auth Token issued for testing may be used more than once, but production Auth Tokens can only be used once.
  • Production Auth Tokens must be used within a time window configured by the merchant.

ValidAVS

false

Value can be true (enabled) or false (disabled).

  • When enabled, the results of an AVS (Address Verification System) verification will be accepted. (Simplified verification based on merchant configuration of accepted responses of "Y" if valid, "N" if not valid.)
  • When disabled, the results of the AVA verification will be ignored.

CVV2Valid

false

Value can be true (enabled) or false (disabled).

  • When enabled, the results of a CVV2 (Card Verification Value) verification will be accepted. (Simplified verification based on merchant configuration of accepted responses of "Y" if transaction matched, "N"' if transaction did not match.)
  • When disabled, the results of the CVV2 verification will be ignored.

ConnectTimeout

65000

Connect timeout in milliseconds (ms).

ReadTimeout

65000

Read timeout in milliseconds (ms).

GetInvoiceInformationDelay

3000

Optional parameter.
Delay for Get Invoice Information request. System parameter.

Anchor
ConnectionURL
ConnectionURL
ConnectionURL

 


Optional parameter.
When a value is provided, it overrides the Authorizer.LoginURL value.

 DoNotProcessTransactionNo 

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





...