1.11 EHI Configuration Options

Your EHI mode (setup option, such as Gateway, Cooperative or Full Service Processing). See EHI Operating Modes.

Whether to include declined authorisation transactions in EHI messages (used for information purposes only).

In Cooperative Processing (mode 2): If this is enabled and there is no connection to Host then we operate as we would if there was no external host at all and authorise/decline based on balance and other information we have in our system.

In Cooperative Processing (mode 2): The authorisation can be approved with simultaneous instructing to load certain amount to a card. If this is required and the product is enabled with the ‘Approval with Load’ feature, the authorisation response message of the approved transactions has to contain ‘0A’ response code and amount to load. The Load will be done before the transaction amount is debited from the current balance.

Note: Multi-Fx cards are not supported.

Applicable in Mode 3 (Full Service Processing) only: If enabled, EHI messages only sends messages after the defined time period. If not enabled. EHI attempts to send messages in real-time first, with subsequent attempts after the defined delay.

The transaction types you want EHI to send:

• Authorisation

• Financial (mandatory for modes 1 and 2 - Gateway and Cooperative Processing)

• Load/ Unload

• Balance Adjustment / Expiry

• Authorisation advice

• TAR (transaction authorisation request for a token creation request)

The URL EHI uses to send messages to your external host if you have configured a single EHI endpoint to receive all messages from Thredd. Different endpoints (URLs) can be set up for each product.

The URL EHI uses to send all time-critical (real-time) messages such as Authorisations, Authorisation Reversals and Advices. Different endpoints can be set up for each product.

Discontinued.

The URL EHI uses to send non-time-critical messages such as Chargebacks, Balance Adjustments, Loads/Unloads, Fees and Presentments. Different endpoints can be set up for each product.

Discontinued.

The URL EHI uses to send presentments. Only First Presentments and Second Presentments are sent to this endpoint. Different endpoints can be set up for each product. This optional field can be used to receive presentments in a separate EHI endpoint.
If a Clearing URL is not provided, but an Informational URL is provided, then all presentments are sent to the Informational URL.

Discontinued.

Determines how long EHI waits for a response from the external host before timing out. The default timeout is 200 milliseconds. This can be changed to meet your system requirements. Please contact your account manager or implementations manager to discuss.

Indicates how long EHI waits to resend the message when it does receive any acknowledgement from the external host. The default is 2 minutes.

Indicate how many times EHI needs to resend the message. Default value is 5.

Indicates the number of days your transaction data is stored in the Thredd buffer table. This can be useful in the scenario where your system is down and you need time to fix it. When the system is back up, Thredd can flush all data from the buffer. Default is 3 days. Maximum is 7 days.

Whether to send a cut off message. See Cut Off Messages.

The cut-off period in hours (e.g. if it is set to 4 hours EHI sends a cut-off message every 4 hours). Default is 4 hours.

The URL EHI uses to send Cut Off messages to your external host.

The EHI version you are using.

Select the optional fields you would like sent in Authorisation messages:

• Send CVV2

• Send PIN (If selected, please provide the PIN Key File)

• Send Expiry Date

• Send PAN Sequence Number

The email address to notify you If EHI cannot reach the external host.

The URL EHI uses to send messages to your external host if the primary URL is unavailable (i.e. Disaster Recovery).

The URL EHI uses to send Cut Off messages to your external host if the primary URL is unavailable (i.e. Disaster Recovery).

SSL certification key to use, where SSL is enabled on your external host.

PIN key file to be used where the send PIN field is enabled for inclusion in authorisation request messages. Triple DES Triple DES (3DES or TDES), is a symmetric-key block cipher, which applies the DES cipher algorithm three times to each data block to produce a more secure encryption. keys are used to encrypt PINs in EHI messages. They can be generated either by Thredd or the Program Manager, and must be stored in a separate file. For details, see PIN Block Formats.