January 29, 2016
UPDATED October 31, 2019

To configure the Maverick 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 Maverick 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:

Username: This will be provided to you by Maverick.

Password: This will be provided to you by Maverick.

Currency: Maverick currently supports AED, ARS, AUD, BOB, BRL, CAD, CHF, CLP, CNY, COP, DKK, EUR, GBP, HKD, IDR, ILS, INR, JPY, KRW, MXN, MYR, NOK, NZD, PEN, PHP, PLN, PYG, RUB, SEC, SGD, THB, TRY, TWD, USD & ZAR currencies.

Lime Light 3D Verify: Set to YES if you are using the 3D Verify service.

Required SSN: Set to Yes if you are going to send the SSN to the Gateway 

Post Phone:  Set to YES if you are going to send the Phone to the Gateway  

MDF1 – MDF20: Merchant Defined Fields are described below.  These are optional Fields.

Alias: For internal purposes only; it helps you identify a specific gateway account among several of them in your CRM.

There are 2 Required Fields on the Merchant Account Details tab.
     *   Descriptor - This will be the MID Descriptor
     *   Customer Service Number - The customer service number assigned to the MID

There is 1 Required Field on the Limits and Fees tab
     *   Global Monthly Cap - This will be the sales amount allowed monthly on this MID 

To maximize the efficiency of LimeLight Reporting Analytics we suggest you take a moment and fill out the rest of the fields. These will all be used in LimeLights profitability reports.

For field definitions on all of the fields on the Merchant Account Details Tab and the Limits & Fees Tab - click here

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







Merchant Defined Fields: 

Maverick 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:


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



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.



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



Inserts the campaign id from where the order is generated.



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



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.



This will return the transaction id for the initial order.



Inserts the product id of the main product sold.



Inserts the product name of the main product sold.



Inserts the product SKU number of the main product sold.



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. 



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.



Inserts the shipping id of the order.



Inserts the shipping method of the order.



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.



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.

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:


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

Did this answer your question?