To configure Meritus Gateway into your Lime Light CRM, you will go to Payment Systems>Gateway Providers and select Meritus 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:
Merchant Key: This will be provided to you by Meritus.
Username: This will be provided to you by Meritus.
Custom Info 1, 2, and 3: These custom fields allow you to pass certain variables up to the gateway such as a Product Id, Product Sku, Product Name, etc.
Currency: The Meritus Gateway currently supports USD, GBP, EUR, CAD, AUD, MXN, ARS, COP, and CLP currencies.
Use Decline Salvage?: Select "Yes" if you're using the decline salvage service that is offered through Verifi.
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.
Once your gateway profile has been created, then you will go through your campaigns and assign the gateway to the corresponding campaign(s)
Additional Gateway Notes:
The descriptor that is placed under Fees and Descriptor will be sent to Meritus if the following conditions are met:
1. The field is not empty.
2. The field contains an asterisk in the 4th, 8th, or 13th character position.
Meritus has 13 Custom Info Fields that can be inserted into (Custom Info1-3) that allow you to customize the transactions that you will be processing through this gateway. These Custom Info Fields 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 Custom Info Fields, at Lime Light CRM we have created various Tokens that you can use to dynamically insert certain values into these Custom Info 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 Custom Info Fields:
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 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.
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.