Configuring Lime Light Payment Gateway

To configure Lime Light Payment Gateway into your Lime Light CRM, you will go to Payment Systems>Gateway Providers and select Lime Light in your Gateway Accounts drop down menu. Click on “Add Gateway” and fill out the gateway parameters.

These parameters are briefly described here for your reference:

Username: Will be provided to you by Lime Light Payment Gateway.

Password: Same password that you have set up for your account with Lime Light Payment Gateway.

Currency: Lime Light Payment Gateway currently supports USD, GBP, EUR, AUD, CAD, and BRL currencies. You can select one currency per gateway account.

Use Pre-Auth Filter?: Set to YES only if using the Pre-Auth Filter* service through this gateway account. 

Capture on Shipment?: Set to YES if you want to authorize first and then capture once the order is marked as Shipped within 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. This feature is optional.

3D Verify: Select Yes if you would like to use 3D Verify with this gateway.  If you are not already signed up for this service, you will need to contact clientsuccess@limelightcrm.com. For further information on 3D Verify please visit our Help Center:

Test Mode: Select Yes if you would like to use this gateway in test mode.

Post Address Info?: Select Yes if you would like to post the address info to the gateway.

Post Processor ID?: Set to YES only if you will be doing Load Balance with Sticky Processing* through this gateway account.

Post Product Description?: Set to YES if you desire to post product descriptions to your gateway account.

Post Descriptor?: Select Yes if you want to post the Descriptor to the gateway.

Use Decline Salvage?: Select "Yes" if you're using the decline salvage service that is offered through Verifi.

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

Gateway 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.

 

 

LimeLight_3D_Verify.png

 

 

* Optional Services:

Load Balance with Sticky Processing: This service will be available if you are doing any type of Load Balance within the gateway account. It allows you to process all your recurring orders through the exact same processor that processed the initial transaction for each one of your customers; therefore, you will be using the same processor for the lifetime of your customer subscription.

When you use this service, you must enable one more field within the gateway account. In order to enable this field, you will login to your gateway account, go to Options>API Configuration, select the customized variables returned in your API responses as shown below, from the list on the left side select “Processor ID” to be added as one of the fields returned, and click Save:

processor id.png 

 

Merchant Defined Fields:

Lime Light Payment Gateway 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 based on how you have set up your Merchant Defined Fields within your gateway account.

 

 

Pre-Auth Filter: This service applies to initials orders only. It allows you to pre-auth a higher dollar amount on the consumer’s credit card before approving the current order to verify if extra funds are available. If the pre-auth is successful, it gets voided immediately and the current order is approved. 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.

This is of great benefit when doing Free Trials as it helps you increase your chances of a successful rebill.

To enable this feature, you will set the Pre-Auth Filter to YES under the gateway profile within your CRM, as indicated in the above parameters description. 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.

disabled pre-auth.png 

 

enabled pre-auth.png 

You can assign the same gateway to multiple campaigns and set different pre-auth amounts based on your needs per campaign.

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

 

Additional Lime Light Gateway Notes

If a subscription rebill attempt fails for one of the reasons listed below, the subscription will not proceed through decline salvage. Instead, the subscription order will be placed on an immediate hold.  

250 Pick up card
251 Lost card
252 Stolen card
253 Fraudulent card

Have more questions? Submit a request

0 Comments

Article is closed for comments.