Configuring NMI Paysafe Processing Continuity gateway

To configure the NNMI Paysafe Processing Continuity gateway into your LimeLight platform, you will go to Settings > Providers and click on the Actions drop-down arrow and select "Add New Provider Profile".  Click on "Payment" as the provider type and then select NMI Paysafe Processing Continuity from the Provider drop-down list. You will then need to fill out the required parameters.

 

These parameters are briefly described here for your reference:

NMI.jpg

 

Alias: Name that you will assign to the gateway. This is for internal purposes only; it helps you identify a specific gateway account among several of them in your CRM.

Username: This will be provided to you by Paysafe.

Password: This will be provided to you by Paysafe.

Currency: The NMI Paysafe Processing Continuity Gateway currently supports USD, GBP, EUR, CAD, AED, ARS, AUD, BOB, BRL, CHF, CLP, CNY, COP, DKK, HKD, HUF, IDR, ILS, INR, JPY, KRW, MXN, MYR, NOK, NZD, PEN, PHP, PLN, PYG, SEK, SGD, THB, TRY, TWD and ZAR currencies. You can select one currency per gateway account.

Test Mode: Set to YES if you would like to use this gateway in Test Mode.

Capture On Shipment?: Set to Yes if you want to capture an authorization once an order is marked a shipped in the CRM. Also, an order will remain as pending in the system until the authorization is captured upon shipment. Set to No if you want the standard authorization and capture process for your orders. Optional.

CIT/MIT Parameters: This is necessary to comply to recent Visa and MasterCard regulations. If set to Yes, the following parameters will be added to the transaction request sent to the gateway:
-initiated_by
-initial_transaction_id
-stored_credential_indicator
Please refer to the Visa document located here, and MasterCard document located here, containing additional detailed level information regarding these requirements in support of the mandate for updating merchant systems and processes

Post Descriptor?: Set to Yes to post the descriptor in the sale request. Optional.

Post Phone: Set to Yes to post the customer phone number in the sale request. Optional.

Post processor ID: Set to Yes to post the processor ID in the sale request. This is used for when your gateway account has more than one MID configured. Optional.

Post Product Description?: Set to Yes to post the product description in the sale request. Optional.

Required SSN: Set to Yes if the social security number is required. Optional

Use Pre-Auth Filter?: Set to Yes only if using the Pre-Auth Filter* service through this gateway account functionality described below. Optional.

MDF1 - MDF20: Merchant Defined Fields* are described below. These are optional fields.

CIT/MIT Parameters: This is necessary to comply to recent Visa and MasterCard regulations. If set to Yes, the following parameters will be added to the transaction request sent to the gateway:
-initiated_by
-initial_transaction_id
-stored_credential_indicator
Please refer to the Visa document located here, and MasterCard document located here, containing additional detailed level information regarding these requirements in support of the mandate for updating merchant systems and processes. (edited)
https://www.mastercard.us/content/dam/mccom/global/documents/transaction-processing-rules.pdf

Once your gateway profile has been created, then you will go through your campaigns and assign the gateway to the corresponding campaign(s).

 

*Pre-Auth Filter:

This service applies to initials orders only. It allows you to pre-authorize a higher dollar amount on the customer’s credit card before approving the current order to verify if extra funds are available. This is of great benefit when doing Free Trials as it helps you increase your chances of a successful rebill.

Once you enable this feature, the Void Pre-Auth? Field will appear and automatically be set to.

Void Pre-Auth? set to Yes: if the pre-auth is successful, it gets voided immediately and the current order is approved.

Void Pre-Auth? set to No: if the pre-auth is successful it may remain active for up to 30 days and you can use this pre-auth amount to capture with the next recurring order, some exceptions may apply. However, please keep in mind that this feature is intended to be used only when the next recurring order is a rebill charge and not a shippable product.

In both cases if the pre-auth fails, the current order gets declined and the system will keep log of the decline reason under the declined order details.

To enable the Pre-Auth feature: you will set the pre-auth filter to Yes in the gateway profile within your CRM, as indicated in the above parameters description. Also, in the gateway profile you will specify whether you want to void this pre-auth or not. Next, you will assign the gateway to the campaign where you would like to use the filter, and you will set the amount that you want to pre-auth at the campaign level. This will be disabled by default with a $0.00 amount in it, and it gets enabled as soon as you enter a valid dollar amount to pre-auth.

 

 

 

*Merchant Defined fields:

Network Merchants Inc. contains several Merchant Defined Fields (MDF1-MDF20) that allow you to customize the transactions that you will be processing through this gateway. These MDFs will append certain information to these transactions based on the order details. Please be aware that these fields are optional.

To ease the process of using the MDFs, at Lime Light CRM we have created various Tokens that you can use to dynamically insert certain values into these Merchant Defined Fields depending on what values you want to send over to the gateway.

These are the tokens** you can use and a brief description of the values that each one will insert in your MDF:

{ACQUISITIONDATE}

Passes to the gateway the date of the original parent order on rebills in MM/DD/YYYY format.

 

{AFFILIATEID}

Inserts the affiliate id from the order. It will obtain this value from the AFFID, AFID or AID field, whichever is populated; if none of them have data, it will not include it on the post.

 

{CAMPAIGNDESCRIP}

Inserts the campaign description of the campaign from where the order is generated.

 

{CAMPAIGNID}

Inserts the campaign id from where the order is generated.

 

{CATEGORYNAME}

Inserts the category name that the main product sold belongs to.

 

{COUPONDISCOUNTAMOUNT}

This is populated with the coupon discount on the order, i.e. `1.00`.

 

{CUSTOMERID}

Provides the customer id of the order being billed.  Please be aware that this is only valid on rebills; on new initial orders, the customer id will be 0 because a new customer will not have a customer id until after he has a successful order in your system.

 

{INITIALTRANSID}

 

This will return the transaction id for the initial order.

 

{PRODUCTID}

Inserts the product id of the main product sold.

 

{PRODUCTNAME}

Inserts the product name of the main product sold.

 

{PRODUCTSKU}

Inserts the product SKU number of the main product sold.

 

{REBILLDEPTH}

This will insert the current rebill depth of the order. For example, if the order is the first rebill for a customer, this would be 1, if it was the second rebill, it would be 2, and so on. For initial new orders, this will be 0.

 

{REPROCESSINGATTEMPTS}

This is populated with the current reprocessing attempt for the order, which will be populated with `0` if the order is not being reprocessed.

 

{RETRYCOUNT}

Inserts what retry count the order is at. For example, if a rebill has declined two times, then this would be 3, meaning it is the third attempt to get an approval.

 

{SHIPPINGID}

Inserts the shipping id of the order.

 

{SHIPPINGMETHOD}

Inserts the shipping method of the order.

 

{SUBAFFILIATEID}

Inserts the sub affiliate id. It will post all the sub id's based on the affiliate id of that order. For example, for AFFID, it will post the value of C1, C2 and C3 as a concatenated string separated by commas: C1value,C2value,C3value  For AFID and AID it will just be the value of SID or OPT respectively.

 

{THM_SESSION_ID}         

Passes a session Id to the gateway.  In order to set the value received from Threat Matrix after they give you a session ID on the webforms,  use a javascript to set the value of a hidden Lime Light field that is in the HTML form on your credit card payment page.

 

Example:

document.getElementById("thm_session_id").value = threatMatrixID;

To use with our API, submit the value that Threat Matrix responds back in an example like this where the threat matrix session id is 12345:

 

&thm_session_id=12345

  • The {THM_SESSION_ID} token can only be used in the MDF17 field.

 

 

**These tokens can be placed in any of the 20 Merchant Defined Fields.  For an explanation of what each MDF is actually used for, please look at your gateway API documentation, as this will vary per gateway.