Limelight Networks FAQs

Objective

Dive deep into your traffic sources and understand howthey'reaffecting your bottom line. Identify traffic sources positively and negatively impacting Customer Lifetime Value (CLTV). Use this dashboard to evaluate traffic sources using both "early-" and "late- indicators" to help solidify your assessment.

Potential Actions

Eliminate traffic sources because of poor performing measures, including:

Fraud Percentage

In-trial Cancellation Rate

Rebill Rate

Customer Lifetime Value (CLTV)

Chargeback Rate

Refunded Revenue Rate

Emulate traffic sources that generate higher-value customers.

Video Length: 8:16

Glossary of Terms

Video Length: 7:15

Data Elements & Measures

The following data elements and measures are shown on the Traffic Source Quality dashboard. For comprehensive definitions of data elements and measures, please reference the Glossary of Measures.

Data Element / Measure

Definition

Fraud %

The percentage of orders marked as fraud. This includes orders that have manually been marked as fraud and orders caught by risk mitigation providers such as Kount.

In-Trial Cancel %

Percentage of cancellations during the trial period.

Rebill Rate

Percentage of Initial Orders (cycle 0) that convert to a Rebill (Cycle 1) order.

Chargeback %

Percentage of orders that have been marked or flagged as chargeback.

CLTV

Customer Lifetime Value is the profit a business makes from any given customer (often referred to as LTV or CLV). The purpose of the CLTV measure is to assess the financial value of each customer. The formula is Gross Profit Unique Initial Customers, where Gross Profit = Gross Revenue - COGS.

Refunded Rev %

Percentage of revenue refunded.

Orders (Initial)

Total number of approved transactions.

Initial Subscriptions

The first order in a recurring series of orders.

Day 0

Cancellation on the same day as purchase.

Day 1

Cancellation the day after purchase.

Day 2

Cancellation two days after purchase.

Day 3

Cancellation three days after purchase.

Day 4

Cancellation four days after purchase.

Day 5-14

Cancellation 5 to 14 days after purchase.

Day 15-24

Cancellation 15 to 24 days after purchase.

Transactions

Total number of attempts to bill cards. Includes approved, declined, voided, and fully refunded orders.

Additional Resources

You may find the following Help Center articles relevant to Analytics helpful.

Glossary of Measures - Complete Analytics definitions and formulas

How to use Filters - Leverage the full power of Analytics date and data filters

Analytics Vs. Reports - Data Calculation Methodology - Understand the differences between Analytics and Reports

Analytics Overview - Foundational information to help your understanding of Analytics

- industry terms and definitions

Access Development is now fully integrated with Limelight CRM as a Membership Provider.

In order to activate Access Development in your CRM, you will need to navigate to Settings > Providers and select Add New Provider Profile from the Actions drop-down menu. Select Membership as the type, select Access Development from the Provider drop-down list, and fill out the required parameters.

These parameters are briefly described here for your reference:

Alias: This will be for internal purposes only.

Access Token: This will be provided to you by Access Development.

Organization Customer ID: This will be provided to you by Access Development.

Program Customer ID: This will be the campaign Id/ configuration that you configured inside Access Development.

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

After this profile is added, it will be listed in your Providers page along with your other providers. Youll need to click on the green circle to the right of the profile and click on Assign to Campaigns to assign the provider to your campaigns. A new box will pop up for you to select the campaigns that you would like to assign the provider to. This can also be done from within the Campaign settings, via the Third Party Providers section.

NOTE: For the Go Cardless Gateway - you can only create 1 profile. Every profile once directed to the OAuth process at GoCardless gets a token created. When you create a new profile GoCardless deactivates the existing token and creates a new active token for the new profile. GoCardless will only allow 1 active token per account.

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

Creditor ID:This will be provided to you by GoCardless.

Currency:The Alto Global Gateway currently supports EUR, GBP, CAD, AUD, DKK, SEK, NZD currencies.

Test Mode:Select Yes if you would like to put this gateway in Test Mode

https://developer.gocardless.com/api-reference/#appendix-local-bank-details

After clicking on "SAVE' in the gateway profile, you will be redirected to 'authorize' Limelight to create transactions on your behalf.

Below is a screenshot of the form you will be redirected to either create a new GoCardless account or sign into an existing account.

Using the NewOrder method, you will need to include additional parameters, for country specific bank accounts. Some of these methods are sepa_iban, account_number and bank_code. Please refer to Limelight and GoCardless API documentation.

NOTES

-GoCardless supports alternative payment types such as BACS and SEPA.-Each European country has specific parameters for account information. Please refer to the GoCardless documentation for local bank details:

KEY FEATURES

We integrated with a new Gateway Provider calledGoCardless Gateway. Further information on how to configure GoCardless can be found here.

We also integrated with a new Membership Provider called Access Development. For further information on how to configure Access Development, click here.

FEATURES

Order_View API - The shipping total amount is now returned for an order. This will be returned via the shipping_amount response parameter.

Order History Note - We are now adding a history note to the order when a line item product has been refunded indicating that the product was removed from the post to fulfillment.

API The hold_date is passed in the order_view response whenever an upsell is added to an order and the order is put on hold.

API - Ability to add a refund note disposition to the order so that analytics will reflect these refund dispositions. This can be accomplished via the order_refund API method.

Orders Page Allow users to search by 'Hold Type' so that you can locate orders put on hold by the reason, such as customer cancel.

Estimated ProRated Amount -Added the ability on the Order Details page to prorate the monthly amount used when upgrading a customer to an annual service. This will be seen when applying a subscription credit on the order.

FIXED BUGS

API Permission issue -involving New Order API method. If the permission is not available on the users API access they will not be able to process New Orders and will get an error message.

NMI Gateway-ProductID is now being passed to NMI Gateway when manually reprocessing orders. This is sent via the 'MDF4' field.

Reprocess Declined Orders page We were not able to view batch results, this has been fixed

Combine Similar Addresses only posting the main order Sales Tax to fulfillment When using Combine Similar Addresses, we are now posting the sales tax amount from all products in the order to fulfillment.

Overview

This report will provide you with a breakdown of employee activities within your CRM. In order to view this report, go to Reports>Employee Activity.

Potential Actions

Use the Employee Activity report to help with the following activities:

Compare and contrast employees based on the metrics available in the platform to potentially evaluate performance.

Data Elements & Measures

The following data elements and measures are shown on the Employee Activity report. For comprehensive definitions of data elements and measures, please reference the Glossary of Measures.

Data Element / Measure

Definition

Activity

Category of activity conducted by an agent

Count Activity

Number of times the activity was logged

Additional Resources

You may find the following Help Center articles relevant to Analytics helpful.

How to use Filters - Leverage the full power of Reports by leveraging filters

Analytics Vs. Reports - Data Calculation Methodology - Understand the differences between Analytics and Reports

FEATURES

Kount - Enhanced Feature - We added the Omniscore value.This is a transaction safety rating that can be used in rule creation andresults in score that is twice as good at catching fraud and minimizing false positives as any score Kount has ever produced.

Maxpay Gateway - We added the following currencies : NOK, DKK, SEK, NZD, CHF, PLN, CAD, JPY, ZAR, CZK

FIXED BUGS

Tracking Import Fix - the files were not updating correctly due to an encryption issue. This has been resolved.

Country code for Scotland and South Sudan has been corrected in our API documentation.

Reprocess Declined Orders page - When using the sort feature the page will not allow you to navigate to page 2 etc. This page was also having issues when using filters, with a response of no data. This has been corrected.

Avalara - We corrected the issue where we were not sending the order total to Avalara.

The Place Order page was not calculating the order total correctly, this has been fixed.

Advance routing options/ page load issues have been corrected.

KEY FEATURES

Integrated Paysafe Fluidpay Gateway

FEATURES

Adding Billing Cycle (Rebill Depth) to the order details page

We are now storing all MasterCard consent emails.

Deprecated Legacy Reports

Single Purchase Limit can now be used to block shipping address

ShipStation - added the ability to store replacement tracking number

Updated Inovio to display username/ password credentials to users with access to see it.

We are now passing the 'Product Name' instead of the 'Product ID' to Insureship

Added All to the Gateway_View API method - this will allow the API user to get all the gateway ids they are using

Email Notifications - a token has been added for Cancellation Date so that you can add that date to your email notifications

Fixed Bugs

Increased the max limit for the Upsell Field for Webforms to support additional upsell products.

The Tracking Import/Export has been updated to no longer have to convert from scientific notation.

In order to increase your revenue and reduce transaction disruption issues, it is imperative to remain one step ahead of your customers' ever-changing credit card information.

Lime Light CRM's Credit Card Account Updater (AU) is the best option to help, ensuring that your customers' credit card data is always up-to-date and accurate. By doing so, you will be able to help mitigate decline issues relating to a variety of credit card decline reason codes. For example, expiration date changes, as updating credit card account number, and closed accounts.

Merchants who store credit card data information for subscription models will greatly benefit from this value added service, by converting on more rebills and driving more revenue.

To sign up for this service please feel free to contact us at [email protected]. The set-up process will take just a few days and you will be notified as soon as the account is ready to use. Once the Credit Card Account Updater profile is ready, we will then just go through your campaigns and assign the profile to the appropriate campaign(s).

Within Lime Light's Credit Card Account Updater provider profile you will see the following parameters:

Alias: For internal purposes only; it helps you identify your profile among others in your CRM.

BC Password: This will be set up by Lime Light.

BC Username: This will be set up by Lime Light.

Days Before Subscription: This allows you to define how many days prior to recurrence you will be sending your orders to Lime Light's Account Updater.

Merchant ID: This will be set up by Limelight.

Merchant Key ID: This will be set up by Limelight.

Merchant Shared Key: This will be set up by Limelight.

Order Age Limit:Specify the number of days in the past to send non-billable orders that were set to recur. The account updater by default will send orders that were set to recur in the past 30 days, this can be expanded up to 365 days.

Post Back URL: This can be used if you would like to relay these credit card updates to an external server (optional).

Public Key: This is generated by Lime Light during the account set up.

Status Email: This will be set up by Lime Light.

Test Mode: Select if you would like to use the Credit Card Account Updater in Test Mode.

Additional Credit Card Account Updater Information: Below is a list of the supported tokens that you can use in your Post Back URL from Lime Light CRM's Account Updater:

{cc_first_6} The first 6 of the credit card.

{cc_last_4} The last 4 of the credit card.

{cc_exp_month} The credit card's expiration month.

{cc_exp_year} The credit card's expiration year.

{customer_id} The customer Id.

{order_id} - The order Id.

{provider_code} - This is populated with the 3 digit alpha response code from the Account Updater, i.e NUP, CCH, etc. The expected response codes can be found below.

{hard_reject} - This is populated with a value of either '1' or '0'; '1' = hard rejection, '0' = soft rejection from the account updater. Hard rejections ARE NOT automatically placed on hold in the system, so this is only for informational purposes.

The Lime Light CRM's Credit Card Account Updater will verify your customers' credit card numbers a few days before the orders recur and it will update the credit card number or credit card expiration date if there is any update available.

In the case that the credit card is going to expire, we will send it to Account Updater the month before.Example: If the credit card expires 03/16, it gets sent to the Account Updater on 02/16.

Lime Light CRM's Account Updater is compatible with any gateway integration or payment router configuration, as long as the payment type is Visa or MasterCard.

4. Response Codes:

NED = New Expiration Date

NAN = New Account Number

ACL = Account Closed

CCH = Contact Card Holder

CUR = Card Data Current

DEC = Invalid Expiration Date

NUP = No Match, No Update

Notes: Response codes NED and NAN are the only ones where an update actually occurs. Also, an order that has received an ACL or CCH response code is no longer eligible to be sent again to the Account Updater.

To configure Affirm payment gateway into your Limelight CRM, you will need to navigate to Settings > Providers and select Add New Provider Profile from the Actions drop-down menu. Select Payment as the type, select Affirm from the Provider drop-down list, and fill out the required gateway parameters.

These parameters are briefly described here for your reference:

Alias: For internal purposes only, this will be the name for your profile.

Public Key: This will be provided to you by Affirm.

Private Key: This will be provided to you by Affirm.

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 authorzation and capture process for your orders. Optional.

Currency: This provider supports USD only.

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

When placing orders through Affirm via API, you will need to include the following parameters in your API call:

creditCardType = affirm_pay

alt_pay_return_url

NOTES

Recurring is NOT supported, straight sale orders only

Payment routing is NOT supported

FEATURES

We are now Integrated with Affirm. As an installment loan provider, they loan the full amount due to the customer and then collect installment payments from the customer. Documentation will be available soon.

CheckOut.com has been updated to be in compliance with PSD2 (3D Secure 2) requirements

FIXED BUGS

When creating orders that have special characters in the address via the NewProspect API, it was causing display issues in the order details.

Address updates were not properly sending to ShipStation. This has been fixed.

FEATURE ENHANCEMENTS

ShipStation Enhancement - We are now sending the customers email address to ShipStation in the username field.

Inovio - You can now add a higher dollar pre-auth on initial transactions and then either void the preauth or capture it on the 1st rebill.

Campaign Configurations - we now have the ability to allow users to add a payment router when using an alternative payment provider on the campaign, such as PayPal.

Taxjar - We added the ability to send the transaction back to Taxjar after the order creation

Fixed Bugs

The shipment confirmation email template has been corrected

Order Details fields have been lengthened to accommodate data length

Avalara - The Test Connection button has been fixed

TaxJar - was not calculating tax when the product amount was $0 and there was a shipping amount

PayPal Payments is the new seamless process for PayPal Express. This new version allows you to redirect the customer to PayPal for payment without having to enter in any customer information. This is a one time process that pulls all customer information from PayPal during the redirect process!

To configure PayPal Payments gateway into your Limelight CRM, you will go to Admin > Providers and select "Add New Provider Profile" from the Actions drop down menu. Select 'Payment' as the type, select PayPal Payments from the Provider drop-down list, and fill out the required gateway parameters.

These parameters are briefly described here for your reference:

Client Id: This will be provided by PayPal.

Client Secret: This will be provided by PayPal.

Currency: This gateway currently supports USD, EUR and GBP currencies.

Use Reference Transaction:Will allow you to initiate recurring payments for varying amounts and process one-click upsells on Paypal. To enable different types of billing agreements based on your needs, you'll need to contact your PayPal account manager.

To enable the recurring and one click upsells in PayPal, you'll need to fill out an application with PayPal and also follow a few steps found below and also Here

If you are usingOne Click Upsells for WooCommerceor any other platform, PayPal requires that you enable "reference transactions" on your account.

To Do This:

Log into yourPayPalaccount

Gotothe Email Contact Form

Choose topic: My Account

Choose sub-topic: Changing/Updating Account Information

Copy and paste the message below, inserting yourPayPalemail address and name.

Wait for a reply

PayPal Reference Guide

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

Once your gateway profile is configured, you will need to assign it to your campaign (s).

When placing an order via API for PayPal Payments, you no longer need to use the get_alternative_provider method. Instead, you will just jump right to the NewOrder method. The following parameters are required for the NewOrder call for PayPal Payments:

Method

Username

Password

tranType

creditCardType

ipAddress

alt_pay_return_url

shippingId

campaignId

productId

For further reference on these parameters, please visit the PayPal Guide located within our API documentation.

Lime Light CRM offers you a list of email notifications that you can send out from the CRM using your SMTP server, just be aware that these email notifications should only be enabled on your main products, not on your upsells.

These email notifications are:

Order Confirmation: gets sent out as soon as the order is placed, you can include fields such as order Id, order total, shipping info, and more

Order Refund: gets sent out when a refund is issued on the order, whether it is a partial or a full refund, you can include the amount being refunded

RMA/Return Notification: gets sent out when an RMA number is issued on the order, you can include the RMA number

Void Notification: gets sent out when the order gets voided, you can include the voided amount

Payment Issue Notification: gets sent out after the recurring order gets placed on hold after all decline manager attempts.

Cancellation Notification: gets sent out when recurring has been manually stopped on the order

Shipping Confirmation: gets sent out when the order receives a tracking number on it and gets marked as Shipped, you can include tracking number

Return Notification: gets sent out when an RMA order has been marked or updated as order return

Pending Offline Payment: gets sent out when an offline payment order is processed, and the order is pending receipt of payment

Subscription Notification: this notification can be added to subscription products, it gets sent out "x" number of days before the next scheduled billing; you specify the number of days within the template. You can also specify the payment type for the notification. For further information on VISA's rule for recurring transactions, please visit the file located at the bottom of the page.

Expired Card Notification: When enabled, an email will be sent to a customer when their credit card has expired at the time of their rebill.

Consent Notification: gets sent out for orders that are flagged as 'consent required'. This notifcation can be configured to be sent X number of days before the rebill. within the message template. The notification will be sent to the customer X number of days before their rebill, where they will need to provide their consent for the rebill.

Delayed Charge Notification: notifies the customer when a trial ends and the delayed charge is successful.

Product Instruction Notification:notifies the customer when a product /products are purchased based on the choices you selected in email Triggers - (ALL, Initial or Subscriptions)

All orders - Every order will have a separate email that goes out for each product in that order.

Subscription Orders - Every Subscription order will have a separate email that goes out for each product in that order

Initial Orders - Every Initial order will have a separate email that goes out for each product in that order

Decline Notification: gets sent out when the order has declined. This type can also be configured tosend a different message based on the decline salvage attempt. (i.e; Attempt 1 = Message 1, Attempt 2 = Message 2). Please see below for instructions.

How to Send a Different Email Message for each Decline Manager Attempt

If you want to send a different notification to the customer based on their decline manager attempt, you can use the segment tokens [###RETRY_ATTEMPT_1_START###] and [###RETRY_ATTEMPT_1_END###] wrapped around the message body. This will send the message body within the segment tokens.

To define the message that will be sent for the default notification, you can use the segment tokens [###RETRY_ATTEMPT_DEFAULT_START###] and [###RETRY_ATTEMPT_DEFAULT_END###] wrapped around the message body. This will send the message body within the segment tokens.

All can be used in the same message body to send a different message to customers based on their decline manager attempt:

[###RETRY_ATTEMPT_1_START###] Attempt 1 Message [###RETRY_ATTEMPT_1_END###]

[###RETRY_ATTEMPT_2_START###] Attempt 2 Message [###RETRY_ATTEMPT_2_END###]

[###RETRY_ATTEMPT_3_START###] Attempt 3 Message [###RETRY_ATTEMPT_3_END###]

[###RETRY_ATTEMPT_4_START###] Attempt 4 Message [###RETRY_ATTEMPT_4_END###]

[###RETRY_ATTEMPT_5_START###] Attempt 5 Message [###RETRY_ATTEMPT_5_END###]

It will be the same for attempts 6-10, you'll just need to replace the digits.

All these emails will be automatically sent out by Lime Light CRM when they get assigned to a product, and any of the above referred actions is applied to an order that contains that product.

NOTE: The 'Member Creation' and 'Member Forgot Password' trigger events are the only events that do not need to be assigned to the product. All other notifications must be assigned to the product in order to be triggered.

Creating your Message Template:

The first step to create an email notification will be to create your message. You will go to Admin > Email Notifications > Message Template and click on Create Template. You will see the following pop up:

Lime Light CRM already has a standard template for each type of email notification, so when you select the type of message that you are creating from the drop down menu, the system will actually take you to the default template from the CRM. Then, you will have the opportunity to personalize it based on your preferences, or you can always use the default template that has been provided to you by the system.

Please notice that there will be two versions, an HTML version and a Plain Text version, when you personalize your message just make sure you add the same content to both versions. The HTML version counts with a great tool bar to help you create a unique message:

To view the different tokens that you can use on your message, to personalize it based on the order details of each customer, just click on View Tokens:

How to Send a Different Email Message for Initial Orders vs. Rebills

If you want to send a different notification to the customer based on an initial purchase, you can use the segment tokens[###INITIAL_ORDER_START###] and [###INITIAL_ORDER_END###] wrapped around the message body. This will send the message body within the segment tokens.

To define the notification that will be sent for the subscription rebills, you can use the segment tokens[###REBILL_ORDER_START###] and [###REBILL_ORDER_END###] wrapped around the message body. This will send the message body within the segment tokens.

Both can be used in the same message body to send a different message to customers based on if they are opting into a new subscription or rebilling on a current subscription.

How to Use the Retry Discount Segment Tokens

If you desire to send an order confirmation notification to your customer which includes the retry discount percentage and amount they received, then you will need to use segment tokens e.g. [###DEFAULT_START###] and [###DEFAULT_END###] to segment your default and retry discount messages.

The example listed below shows you how to properly setup your order confirmation template using the segment tokens. In using the segment tokens, the system will send the default message to those whose customers who are successful on their first attempt, and will send the retry discount message to those customers who are receiving a retry discount based on your settings in the subscription management area of the CRM.

[###DEFAULT_START###]

Thank you for purchasing this product!

Here are your details!

[###DEFAULT_END###]

[###RETRY_DISCOUNT_START###]

Here are the billing details for your retry attempt. We have taken {retrydiscountpct} off of your order for a total discount of {retrydiscountamt}.

Sincerely,

[###RETRY_DISCOUNT_END###]

Tpl Tokens

The template represents a single row for a product detail listing. Meaning it will be used and repeated for all products. In order for the template to stay preserved within the wysiwyg (the message editor (*what you see is what you get*)) it will be wrapped in HTML Comment Tags e.g. <!-- template -->. In addition to this, the template needs to be wrapped in the template-row tags e.g. {tpl_product_row} template {tpl_product_row}. Notice the tag at the beginning, before the actual template and at the end, after the template. so the end result is as follows <!-- {tpl_product_row} template {tpl_product_row} --> A full working example is below: <!--{tpl_product_row}<tr> <td class="label" style="width:100%"> ({tpl_product_id}) {tpl_product_name}</td> <td style="border: 0px solid red; text-align: center; width: 50px;"> {tpl_product_base_cost}</td> <td style="border: 0px solid red; text-align: center; width: 50px;"> {tpl_product_quantity}</td> <td style="border: 0px solid red; text-align: center; width: 50px;"> {tpl_product_total_cost}</td></tr>{tpl_product_row}-->

Giro Tokens

If you are using the Pacnet Gateway and have assigned Giro as a payment type on your campaign, then the following tokens can be used with your email message templates. The tokens can be used with any email message template, but it is intended to be used with the Pending Offline Payment email notification.

{giroaccountname}

Giro account name

{giroaccountnumber}

Giro account number

{girobankname}

Giro bank name

{girobankaddress}

Giro bank address

{girosortcode}

Giro sort code

{giroiban}

Giro IBAN

{giroswift}

Giro Swift code

Other Tokens

{orderdatetimecustom} - This token can be used to customized your message templates with a date format that is different than the standard US date format. If you are using this token, you will need to send a request to [email protected], and include the desired date format you would like to use.

While you are working on your message and the same is not ready to be used, you should have the Publish field set to No. Once your message is ready to be used, then you will set this field to Yes.

When you are done with your message template, just click Save at the bottom of the page.

{gateway_specific_html} - This email event token is used with the Cobre Bem gateway to generate a link to the consumer to download and print their Boleto.

Setting Up your SMTP Mail Server:

This will be your second step to create an email notification. You will go to Email Notifications > SMTP Mail Servers and click on Add SMTP.

The SMTP abbreviation stands for Simple Mail Transfer Protocol, which is a protocol for sending email messages from one server to another. It defines a message format and a procedure to route messages through the Internet from a source to a destination via email.

You must first set up an account with a mail server, and this mail server will provide you with the SMTP credentials that are needed.

You will be able to use multiple mail servers, or the same mail server for different trigger events.

You will fill out the form with your SMTP Mail Server details, and authenticate the same, so please make sure your mail server is set up to perform SMTP authentication.

If the SMTP profile is not ready to be used, you will set the Publish field to No, once it is all set up and ready to be used then you will change the setting on this field and set it to Yes.

When you are finished setting up your SMTP profile just click Save at the bottom of the form.

NOTE: Some SMTP mail servers do not support SMTP authentication; however, most of them will still send out the emails without any problem. We just recommend you to test them first to confirm if they work even without the SMTP authentication or not. The mail servers that are not compatible with Limelight are GoDaddy,RackSpace, and Office365.

Creating your Trigger Events:

This is the last step of creating your email notifications; here is where you are going to attach your SMTP profile, to your message template and the event type; being the event types: Order Confirmation, Order Refund, RMA/Return Notification, Void Notification, Payment Issue Notification, Cancellation Notification, and Shipping Confirmation.

You will go to Admin >Email Notifications > Trigger Events and click on Create Event. Select the SMTP profile by the name you assigned to it, select an event type, assign a name to this event that will help you differentiate it from other similar events, add a brief description, and select a message templates by the name that you have assigned to the template.

While you are working on your trigger event and the same is not ready to be used, you should have the Publish field set to No. Once your trigger event is ready to be used, then you will set this field to Yes.

When you are done with your trigger event, just click Save at the bottom of the page.

The system will list your trigger events as shown in the next illustration showing relevant details such as the products that have been associated to each particular trigger event, the user account who created the trigger event, the last update date and the user account who applied the update. Also there will be features available to you as edit, delete or copy the trigger event.

Assigning the Email Notification to your Product:

Now that you have completed all the steps to create your email notifications, you can assign it to your products. You will just need to click on the ellipsis to the right of your trigger event to assign to a product, or multiple products as shown below.

Deleting Message Templates, SMTP Profiles and Trigger Events:

You will not be able to delete any Message Template if it is assigned to a Trigger Event, the same way you will not be able to delete any SMTP Profile if it is assigned to a Trigger Event, and a Trigger Event cannot be deleted if it is assigned to a product.

In order to delete a Message Template and/or SMTP Profile you must go to the Trigger Event that it is assigned to, remove it from there, and assign other Message Template and/or SMTP Profile to the Trigger Event, or delete the Trigger Event completely.

In order to delete a Trigger Event you will just need to click "delete" under the trigger event.

FEATURE ENHANCEMENTS

Email Templates - Add a product level welcome/instruction notification. This feature enables the client to set up a notification that is created at the product level after the order is successfully placed. So if you have 2 products in an order and they both need different emails you can set them up using this new feature

Segments - You can now export your contact list from Segments directly to Google Sheets.

Fixed Bugs

Recurring date update issue - The recurring dates were reflecting incorrectly in the history notes when they were changed from the order details page - this has been fixed.

Tracking import does not function properly - it is corrected now

Subscription Management display issue via All Active Subscriptions

FEATURE ENHANCEMENTS

Sales Restrictions - By State - If you are selling in the United States you may now block sales in one or more states. These settings are configured by product. This feature is a must have if you are selling a product such as CBD that is not legal in all 50 states.

Products - Allow users to create new categories while they are creating/editing a product. This is a time saver when adding a product if you realize you need to create a new category you can click the create new category link and build the new category without losing your place in the add product process.

Add AUD currency to Maxpay integration - you can now select AUD as the currency type for Maxpay Gateway.

Add the ability to update an order from paused to cancelled (and trigger the appropriate emails + post backs for cancellation) This will allow you to cancel a subscription that is currently on hold.

BUG FIXES

The order history note was not properly reflecting the order activity when attempting to update the next recurring product (Updated note on delayed charge cycle)

Total installments display issue - values were being added when the value should have been 0

FEATURE ENHANCEMENTS

MaroPost is now compatible with cloud based accounts

Paypal Payments now has the ability to submit upsells and rebills. Paypal needs to be contacted directly to have this configured on the account.

Place Order page - when a payment type other then Mastercard is selected and Consent Required is selected, a message will pop asking Are you sure you want to require consent ?

Ability to assign Sales Tax profiles to multiple campaigns

Added ability to control custom field permissions by API user

SSO users - Added the ability for Admins to view/edit campaign permissions per group

Postbacks - added tokens to support custom fields

We are now integrated with eMercury Autoresponder

We are now storing the original gateway id and the reprocess attempt number to enable us to get more granular processing reports in analytics

The API for order_view now also has the hold_type so that the hold reason is known (Customer, merchant, and System)

Email Templates - ability to configure a separate end of trial template for delay charge

BUG FIXES

IpPay - Fixed - unable to update customers billing address.

Segments - Fixed - Error - Unable to Run

Payon/ Open Payment Platform - Special character issue causing declines - fixed

Payment Router - Monthly Recurring Forecast display issue - fixed

Forecasted Revenue showing as $0 on the Payment Routing monthly scheduled forecast has been fixed.

Advanced search in Subscription Management bar character limit has been increased.

Cancellation notification emails were being sent when an order is placed on Hold by decline manager. This has been fixed.

NMI Void issue resolved

Order Update allows the user to set billing and shipping states to non US states if US is selected.

IP lookups are now showing the correct geolocation

FEATURE ENHANCEMENTS

Decline notification Added the ability to send a different message template based on the decline salvage attempt. (i.e; Attempt 1 = Message 1, Attempt 2 = Message 2)

API We added the ability to pass a custom shipping charge with the order. This will override the Shipping amount configured to the shipping profile.The Shipping Charge will always be preserved unless the shipping method is changed. A change to the shipping method will remove the custom charge and will take the amount configured to the new shipping method.

Account Updater - Enhanced account updater to allow orders to be resent to check for card updates. After the batch has been received following an unsuccessful update, the card is eligible to be resent check for updates.

BUG FIXES

NewOrderCardOnFile Updated this method to work with Square when the CC number and CVV are not present

Updated the Insureship integration to reflect a new endpoint

Braintree Issue address updates were not working they are now fixed

Prospect Page refresh issue changes made to the prospect were only updating the list view when the page was refreshed

Subscription Forecast Manager showing 0.00 as the forecasted amount - fixed

Next subscription product price not accounting for preserve price this has been corrected and the preserve price is now displayed

FlexPay 'hold type' was reverting to generic system hold. Now it is using the correct hold type for decline salvage

Hold type missing when stopping subscription through refund hold type is now updated when refund or partial refund is processed and subscription is stopped

Payment Router emails failing to send Email Notifications for Payment Routing thresholds were going out intermittently. This issue has been resolved now emails will go out every day that the threshold has been met or exceeded

TaxJar Quantity miscalculation has been adjusted

FEATURE ENHANCEMENTS

Email Notification SMTP setup - We are now automatically authenticating the SMTP profile when Save is clicked, rather than having the user select Authenticate SMTP.

API - We have added the ability to find test orders using is_test_cc to the order_find method.

Gateway Profiles - We have removed the fee requirements within the limits and fees tab. The only required field is the Global Monthly Cap.

Added PostBack action Tracking Updated to the trigger type order action which will be fired when there is an update to the tracking number field.

Place Order Page - The default campaign selected in the campaign will now be pre-selected when placing an order on the Place Order Page.

BUG FIXES

Discounts - Flat discounts on the billing model at the offer level were not being preserved after the initial order.

Reprocess Declined Orders Page Time Out has been corrected

Monthly MID CAP Notifications are now being sent to all appropriate parties

3PL 2.0 Fulfillment - We are now fetching for tracking numbers on the same day that the orders are posted to fulfilment.

Kount - The decline reason for test credit cards is now accurately reflected in the order history notes.

Infocu5 - Reformatted the fields for leadCCnumber and leadProductList so they can be received successfully by Infocu5.

ShipStation - When ShipStation sends a Too Many Requests response we are now correctly displaying the response in the CRM via the order history notes.

Avalara - Corrected the issue where orders from other countries were being sent to Avalara - no tax was being held.

Analytics/Reports main page is now able to return results when multiple keywords are entered in the search field.

Navigation Bar was working incorrectly for some users, this issue has been corrected

Shipping confirmation emails were not firing when the notification was not saved at the product level.

NewOrderCardOnFile orders are now being flagged as test if created with a test card.

FEATURE ENHANCEMENTS

Square Gateway Integration - Changes completed to allow LimeLight CRM users to seamlessly integrate Square for straight sales as well as recurring sales. For instructions on setting up Square, click HERE.

Account UpdaterFor any new accounts using Account Updater we would go back 30 days to update information we are changing this to 60 days.

We also now check for the rebill date of upsell subscriptions, so that 7 days before rebilling any line item the information will be sent to Account Updater. (Reminder there is only a fee when the account information is updated.)

FlexPay Tokenized gateways are now supported with FlexPay.

Decline Manager We updated the 'Global Default Settings' for new users to use to get them started. These settings are preferred when first getting started with Decline Manager:

Attempts before Hold = 3 Attempts

Gateway = None

Schedule = Custom Cycle > 6 days

Not Before = 12 PM

Salvage Percentage = 0

Discount = NO (unselected)

Import / Export Data - Added the reason an order was placed on hold to the Order Export data

Hold_types (User, Merchant, Hard Decline, Decline Salvage, Chargeback)

Prepaid Indicator - Added an indicator to the order record for Prepaid subscriptions so that a customer service rep can easily tell if a prepaid order is set to auto renew at the end of its term.

Campaign update - Expanded the width of the multi-select fields on the Campaign configuration to improve the user experience when selecting profiles

BIN Analytics Dashboards - Added Gateway filters to the BIN Analytics dashboards.

Order Analysis Dashboard - Added Sub-Affiliate Id filter to the Order Analysis dashboard.

BUG FIXES

Kount Kount error messages have been adjusted to show correctly within the Order History Notes.

Overview

The Sales by Product report is a product level report that provides a raw quantity count of products sold, as well as the raw total revenue amount for each product that you have in the platform.

Video Length: 3:24

Potential Actions

Use the Sales by Products report to:

Understand product demand.

Better manage inventory.

Data Elements & Measures

The following data elements and measures are shown on the Sales by Products report. For comprehensive definitions of data elements and measures, please reference the Glossary of Measures.

Data Element / Measure

Definition

Initial #

Count of products associated with Cycle 0 Orders. | Cycle 0 = initial order

Initial $

Product revenue generated from cycle 0 orders. | Cycle 0 = initial order

Subscription #

Product revenue generated from cycle 1+ orders. | Cycle 1 = rebill order. Cycle 2+ = recurring orders

Subscription $

Product revenue generated from cycle 1+ orders. | Cycle 0 = initial, Cycle 1 = rebill, Cycle 2+ = recurring

Total #

Sum of initial and Subscription order count. Note: Voids and Refunds are removed from the this total.

Total $

Sum of initial and subscription order revenue

Pending #

Orders that have not reached the billing date or are attempting through decline manager

Pending $

Pending revenue on incomplete orders in a state where funds have not yet transferred. Pending orders are not sent to fulfillment

Hold/Cancel #

Count of products purchased within the date range placed on hold/canceled. Note: The actual hold/cancellation date of the order may be outside of the selected date range. Orders canceled via a system process is a "hold" and via an actual person is called a "cancel."

Prior Hold/Cancel #

Orders that were created prior to the date range but were stopped. e.g., If an order was created a month ago and you cancel that order today and you pull the Sales by Campaign report for today's date, that one cancellation will show on the Prior Holds and Cancels column.

Hold/Cancel $

Product revenue lost from the order being placed on the hold or canceled.

Void/Refund #

Orders that have been voided, fully refunded, and partially refunded.

Void/Refund $

Revenue from orders that have been voided, fully refunded, and partially refunded.

FAQ's

-Why is this report not showing all the products I have in my CRM?

This report provides you with data based on relevance. If some of your products had zero orders during the date range that you have selected to see, then our system will not include these products in the report; it will only include those products with available data on them.

-Is the shipping revenue included in the Sales Report by Product?

No, since shipping is not a product, its revenue is not included in the Sales Report by Product, but it is included in the Sales Report by Campaign and the Sales Report by Date.

-Do the new products, recurring, and total revenue columns include orders that have been refunded or voided?

Yes. The new products, recurring, and total revenue columns will include the counts/amounts that have been refunded or voided since the report is designed to only provide a raw quantity count of products, and the raw total revenue amount for each product. The Sales Report by Date and Sales Report by Campaign are order level reports; therefore, you will need to view these reports in order to see the total revenue generated excluding refunds/voids.

-Does the hold column include orders that were generated prior to the selected date range, but that were placed on hold during the selected date range?

Yes, the hold column includes orders that were generated and placed on hold during the selected date range, as well as orders that may have been generated some time prior to the selected date range, but were placed on hold during the date range you selected.

Additional Resources

You may find the following Help Center articles relevant to Analytics helpful.

How to use Filters - Leverage the full power of Reports by leveraging filters

Analytics Vs. Reports - Data Calculation Methodology - Understand the differences between Analytics and Reports

Lime Lights Decline Manager brings highly customizable criteria whether that be days, date, day of the week, or any combination. You can now truly maximize revenue.

To configure your Decline Manager in your CRM, you will need to go to Payment > Decline Manager.

NOTE: If you do not have any decline manager profile assigned to a campaign, the Global Default settings will be applied. If you do not want to use decline manager, you will just need to set Immediate Hold for your attempts on the global default profile.

The Global Default profile will already be configured for any new users with the recommended settings:

Attempts before Hold = 3 Attempts

Gateway = None

Schedule = Custom Cycle > 6 days

Not Before = 12 PM

Salvage Percentage = 0

Discount = NO (unselected)

Under the 'Features' column to the right, you will have the following options:

Edit: Select this if you would like to edit your profile and attempts.

Jump to Position: You will only use this if you have the same campaign selected for more than one (1) profile. This will allow you to choose which profile will take precedence.

Enable/Disable: Select this to Enable or Disable your profile.

Delete: Click this to delete your profile.

Create a new Decline Manager profile:

To create a new Decline Manager profile, you will need to select the drop-down arrow next to Actions and select Add. A box will then pop up where you will have the following options:

Once clicking on add, the following box will appear where you will have the following options:

Name: This will be the name for the profile.

Attempts Before Hold: Here you can choose how many attempts you would like to use. The options range from No Retries to 10 attempts before hold.

Gateway: Selecting a gateway here is optional. This will override and reroute ALL salvage attempts to tuse the gateway selected.

Preserve Gateway: By selecting this, you will override any Payment Routing or Cascade preservation you may have configured and the gateway selected above will be preserved for all future rebills.

Schedule: The options to schedule these attempts are Daily, Weekly, Monthly, Custom Cycle, Custom Date and Custom Day.

Custom Cycle: Customize how many days between each attempt.

Custom Date: Select a specific date or dates for the attempt. To specify more than one date enter as a comma separated list, type last for the last day of the month. i.e 1, 15, last would attempt on the fist (1st), fifteenth (15th), and the last day of each month.

Custom Day: Attempt a specific day each month. i.e the First Sunday of every month.

Within the Schedule, you can specify that the attempt should be queued before a certain hour of the day. i.e Not before 8AM Eastern. If the Not before field is left blank, then the attempt will be queued at midnight Eastern time.

Salvage Percentage:This is only applicable for the Global default profile. This will control the daily percentage of rebills that you want to attempt salvage. For example, if you have 100 rebills decline and you wish to not attempt to salvage every transaction, you can use 70% in which case only the first 70 declines would attempt to salvage.

Discount: Select this box if you would like to discount the decline manager attempts. You also have the option to apply the discount to shipping.

Minimum: Here is where you will enter in the minimum order total amount needed for the discount to take effect.

When finished, click Next. The following box will pop up where you can assign your profile to campaigns and customize each attempt:

You have the option to click on the pencil to edit each attempt. Here you can customize each attempt with a different schedule for each attempt if you like. The specific attempt schedule will take precedence over the profile default schedule on the left half of the popup. Within this section you can also set the discount percentage that you would like to use for each attempt.

The Rules that are available to choose from are Campaign, Product, Decline Reason, Card Type, Gateway and Payment Method. If you have more than one (1) rule configured, then the transaction would need to match all rules in order to attempt.

The decline reason (s) to choose from are pulled from your Hard Decline Rules. These can be found and configured in Payment > Hard Decline Rules.

Also, this is where you will select your campaigns. You will just need to click on the plus sign next to Add Rule and select campaign as the rule. Now you can select which campaigns you would like to assign the profile to.

The campaigns that are selected are going to be applied to the profile, meaning only orders from those campaigns will be sent to the profile.

To configure the Square Gateway into your LimeLight CRM, you will need to follow a few steps that are described below.

Step 1: Go to Settings > Providers, click on the 'Actions' drop-down arrow and select "Add New Provider Profile". Click on "Payment" as the provider type and then select Square from the Provider drop-down list. You will then need to fill out the required parameters.

https://developer.squareup.com/docs/payment-form/payment-form-walkthrough?origin_team=T044SPD88

These parameters are briefly described here for your reference:

Alias: This will be the name of your profile and will help you identify it among other gateway profiles.

Location ID: You will manually need to obtain this from your Square interface. Please see details below.

Capture On Shipment: This is an optional feature. Set to YES if you will be completing the monetary transaction at the time the order is shipped. Set to NO if you want the standard authorization and capture process for your orders.

Currency: Currently this integration supports: AUD, CAD, GBP, USD, and JPY.

Test Mode : ONLY SELECT if you have a SandBox Account with Square. If set to YES, you must use Limelight's Sandbox Application ID.

The Application ID used in the javascript file used to create the nonce in the checkout page should be Limelight's Sandbox Application ID: sandbox-sq0idp-daKjieXHzkmQt4JV2pS3Cg

Once you have configured the profile, you will then need to select 'SAVE.'

Step 2: Once the profile is saved, you will automatically be redirected to Square where you will need to login:

After entering in your login information and 'Sign In', a new 'Permissions' box will pop up where you will need to click 'Allow' to provide Limelight access.

Step 3: Once you 'Allow' access, you will be redirected back to Limelight, to the Providers page where your profile is configured, and you will need to enter in the Location ID. To obtain the 'Location ID', you'll need to navigate to your Square interface, and navigate to Account & Settings > Business > Locations. The Location ID will shown within the URL as shown below:

Enter the 'Location ID' into your profile in Limelight and then SAVE. Your profile is now complete, and you can move on to step 4.

Step 4: You will need to insert a Javascript onto your checkout page that you will need to obtain from Square:

Within this Javascript, you will need insert Limelight's Application Keyinto the 'SqPaymentForm' snipped.

Limelight Production Application ID: sq0idp-daKjieXHzkmQt4JV2pS3Cg

Once your checkout page has been updated with the Javascript, you can move on to the last step.

Step 5: Add the gateway to your campaigns. To do so, you will need to navigate to Products > Campaigns, and select 'Square' from the 'Credit Card Gateway' drop down within the Gateway Configuration section.

API NOTES

In the NewOrder API request, you will exclude the credit card parameters, but you must submit the parameter "square_token" with the nonce value that you'll get in return from Square in your checkout page.

ADDITIONAL SQUARE NOTES

Payment Routing is supported when using all Square gateways only.

Forcing of orders is not supported with this gateway.

Cascading is only supported when cascading to and from Square gateways only.

Integrations

We are now integrated with Square Payment Gateway! Here is the url for Square if you would like more information about what they offer https://squareup.com/us/en

Fixes/Bugs/Updates:

When updating Prospect information via the API if anything but a numeric value is sent an error message of Invalid Prospect ID Supplied will be returned.

Stripe Connect will now properly add the rebill to the existing customer record.

Declined orders where the Initial and the Rebill amounts are the same will no longer require consent.

If an Attribute is deleted, it is now visible in the list when it is re-added.

Feature Releases:

MasterCard Compliance - In an ongoing effort to help you remain in compliance with the MasterCard regulations, Customer Service Email and Customer Service Mail From fields have been added to the gateway provider profile in the Merchant Account Details tab. If populated these fields will override the SMTP profile configurations for outgoing notifications to customers.

LimeLight Terms and conditions link has been added to the standard platform login and my.limelight portal login pages.

Enhancements:

Orders

The Shipping Confirmation Email Trigger now allows you to select if you want the Shipping notification to be sent on initial orders, subscription orders, or all orders.

Order history notes have been updated for the order_update API to now return the Userid of the API user that performed the order update.

Payments

3D Verify has been added to the PayCertify gateway.

AUD,NGN and PEN currencies have been added the Stripe Connect gateway.

Insights

Return Count and Return Rate have been added as new measures to the Traffic Source Quality dashboard.

Campaign ID has been added as a new filter to the Account Updater dashboard.

Fixes/Bugs:

Updated the NewOrderCardOnFile API call to properly apply shipping for an order created with a shippable main product and an unshippable upsell product.

Extended BIN blocking to prevent blocked BINs from being sent to Transaction Select & Kount.

Resolved issue with duplicate MemberMouse profiles being created.

Resolved issue on Custom Recurring Offers with a trial causing the wrong Next Recurring date to be applied to an order.

Resolved issue causing prospects with a UK IP Address to be created with the wrong country.

Resolved issue causing the wrong amount to be sent for KRW on the NMI gateway.

Resolved issue causing a 3D Secure redirect to return a white screen.

Resolved issue with the 3D redirect engine causing the order history note not to be recorded when the final capture fails.

To configure the Limelight 2.0 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 Limelight 2.0 from the Provider drop-down list. You will then need to fill out the required parameters. parameters.

The corresponding URL for Limelight 2.0 is the following: https://saltpayments.transactiongateway.com/merchants/login.php. If you have any questions in regards to this gateway, please contact us at [email protected].

These parameters are briefly described here for your reference:

Username:Will be provided to you by Limelight 2.0 Gateway.

Password:Same password that you have set up for your account with Limelight 2.0 Gateway.

Currency:Limelight 2.0 Gateway currently supports USD, GBP, EUR, CAD, AUD, NZD, SGD, HKD, NOK, DKK, CHF,JPY, ZAR, MXN, SEK, INR, PHP, MYR, IDR, AED, and ARS 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. Optional.

*NOTE*-If you select YES to use the Pre-Auth Filter, the Void Pre-Auth Filter will populate.

Void Pre-Auth:Set to YES if you want to void a successful Pre-Auth immediately; set to NO if you want to hold a successful Pre-Auth and capture it at the rebill charge. Optional

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.

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

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

Post Processor ID:Set to YES only if you will be doing Payment Routing with Sticky Processing* through this gateway account. Optional.

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

Post Descriptor?: Set to YES if your processor requires you 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.

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

* Optional Services:

Payment Routing with Sticky Processing:This service will be available if you are doing any type of Payment Routing 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:

Merchant Defined Fields:

Limelight 2.0 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 current reprocessing attempt for the order, which will be populated with `0` if the order is not being reprocessed.

{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}

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

Pre-Auth Filter:This service applies to initials orders only. It allows you to pre-auth a higher dollar amount on the consumers 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.

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

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

Additional Limelight 2.0 Notes

Gateway Notes

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

250 Pick up card251 Lost card252 Stolen card253 Fraudulent card

Note: If you would like to validate the customer's card via API, you will need to use a new request parameter in the`authorize_payment` method called `validate_only_flag`, which will allow you to validate the card without holding funds from your customer, etc.

To configure Network Merchants Inc Gateway into your Lime Light CRM, you will go to Settings>Providers and select "Add New Provider" from the 'Actions' drop-down menu. Select "Payment/Gateway" as the Type, and "Network Merchants Inc" as the provider. A new window will then pop up for you to create your gateway profile.

These parameters are briefly described here for your reference:

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: Will be provided to you by Network Merchants Inc.

Password: Same password that you have set up for your account with Network Merchants Inc.

Currency: Network Merchants Inc currently supports USD, GBP, EUR, CAD,CNY, AUD, NZD, SGD, HKD, NOK, DKK, CHF,JPY, ZAR, MXN, SEK, INR, PHP, MYR, IDR, AED, and ARS 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. Optional.

Void Pre-Auth: Set to YES if you want to void a successful Pre-Auth immediately; set to NO if you want to hold a successful Pre-Auth and capture it at the rebill charge. Optional

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 authorzation and capture process for your orders. Optional.

Post Processor ID: Set to YES only if you will be doing Payment Routing with Sticky Processing* through this gateway account. Optional.

Post Descriptor?: Set to YES to post the descriptor from your profile to the gateway. Optional.

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

Lime Light 3D Verify: Set to YES if you are using Lime light's 3D Verify service.

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

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

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.

* Optional Services:

Payment Routing with Sticky Processing: This service will be available if you are doing any type of Payment Routing 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:

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.

Pre-Auth Filter: This service applies to initials orders only. It allows you to pre-auth a higher dollar amount on the consumers 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.

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

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

Additional Network Merchants Inc Gateway Notes

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

250 Pick up card251 Lost card252 Stolen card253 Fraudulent card

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:

here

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_indicatorPlease refer to the Visa document located here, and MasterCard document located, 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_indicatorPlease 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 customers 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.

Upload, manage and automatically assign License Key values. This new feature allows merchants to easily and conveniently assign digital product keys.

NOTES:

A product record can have an unlimited number of License Key values

A License Key may contain number, letters and characters

A License Key has a maximum of 255 characters

A License Key value must be unique

You cannot assign a License Key to more than one product record

Currently, if you place a test order for a License Key product, the test order will assign a License Key to the order that cannot be released back into the available key list.

You must enable the option 'License Key Restricted' on at least one product record to be able to import product keys

CONFIGURATION STEPS

1.Mark the Product record to accept license key values

a. Click on Products menu link

b. Locate the product record that you want to associate the product keys to

c. Click the name of the product to edit the record

d. Select the License Key Restricted check box

e. A new panel, called License Keys will display

Email Notifications

2.Assign Product Key values to the product records

Manually add a key value to the product key

From the product record, expand the License Keys panel

Click the Add button

3. Define a license key value

4.Click Save button

5.Import a set of Product Key values

Click on Insights -> Import/Export Data

Select Queue Import

Type = Product Licenses

File = select your import file

3.Configure the Order Confirmation email template with the Product Key tokenWhen a customer purchases a product enabled with a license key, you can use our system generated emails to deliver the product key values to your customers. The product keys can be formatted three different formats:

A CSV of all the product license keys assigned to the order

A CSV of the license keys for the product

A list of the license keys for the product.

Click Settings -> Email Templates

Locate the Order Confirmation template you would like to include the Product Key

Click View Tokens to locate the license key token you want to use for the email

Make sure that your Email Notification template is assigned to your Product

NOTE: refer to help article for details on designing templates

4.Assign a Product Key to an order

Place an Order that includes at least one product with an assigned License Key

View the Order Details page. There is a new section called License Keys

If configured, an order confirmation email will be triggered and the License Key values will be included in the email to the customer

NOTE: if the order declines, the License Key values are released back to the pool to be assigned out

5.View the assigned product keys at the customer record

To make it easier for your customer service agents to look up a license key value, we have made this information easy to find with a customer search.

Click Customers ->Search by email address

Locate the customer record and click the recordID to view all the orders placed by this customer.

A key icon will appear next to any order in which a product was assigned a LIcense Key value

Click the key icon to view the License Key values

NOTE: click below for an import file template:

Feature Release:

Segments - Contacts Custom Fields and Member are now options for Segments to help you understand your customers by dividing your customer and prospect base. For more information on segments please check out our Help Center

Enhancements:

Email Notifications

A new Expired Card Notification Email Trigger and Email Template have been created. When enabled, an email will be sent to a customer when their credit card has expired at the time of their rebill. For more information on creating email notifications check out our Help Center

Orders

Orders can now be placed without address information for non-shippable products via API and the Place Order page in the platform. Note: order_update has been updated to allow you to remove generic address information that may have been added on the past. Please refer to our API documentation : Navigate to API > Orders > subscription_order_update

Insights

Tracking & Return imports are now located under the Import/Export Data menu.

An IsTest Order? filter has been added to the SMTP report.

Fixes/Bugs/Updates:

CVV is now being passed to Checkout.com through the gateway integration.

Updated Offer Configurations to prevent adding a trial when a trial is not configured on the Offer.

Updated MID Group matching to ignore leading and trailing spaces.

Fixed issue with gateway delete preventing the profile from being deleted.

Fixed FluidPay integration causing void responses to be misinterpreted.

Fixed Subscription Discount helper text display on the Place Order page.

The New Order tab is used to place new orders over the phone for new or existing customers.

You just have to go to New Order and click on Place Order to access the Place Order form.

Any order placed through the New Order will be treated just as if the customer would have ordered through an online campaign, including any services from third party providers that have been assigned to the campaign. For example: if you have assigned an auto-responder to your campaign, when you submit the order on the Place Order form, our system will pass the data to them, same as it does with the orders placed online.

Steps to place a New Order:

1. Select the campaign.

2. Select the product (products will be display after you select the campaign). Next to each product you will see a feature to look at the product information. Also, depending on whether or not the campaign has it enabled, you will also see a feature to customize the product price directly from the order page. The quantity free text box allows you to enter a purchase quantity for the product up to the limit allowed for that product. Please click the product information icon located next to the product selection button to view the maximum purchase quantity allowed for the product. Under your product description, you can always add a short script about the product. This will help your agents to provide more information to your customers not only about the main product, but also about the upsell products, when taking orders over the phone.

3. Select the shipping method.

4. Select or de-select the upsells as necessary. If you select all, then the system will select all upsells, and their price amounts will be included in the order. If you select None, the system will de-select all upsells, and their price amounts will not be included in the order. The quantity free text box allows you to enter a purchase quantity for the upsells up to limit allowed for each upsell product. Please click the product information icon located next to the product selection check boxes to view the maximum purchase quantity allowed for each upsell product.

5. Fill out the customer information such as the first and last name, shipping address, phone, email, and billing address, if different than shipping.

NOTE: ONLY the customers 'Country' is required for the address.

6. The affiliate/sub-affiliate fields allows you to add new or view current affiliate data on orders placed on the place order page. Please be sure to use the appropriate pairing of the affiliate data fields, e.g. AFID is used with SID, so that there are no discrepancies in the reporting within your system.

7.Review the order summary for an overview of what is included in a customers order. The order summary will include a sales tax if the product(s) in the order are taxable. Also, the sales tax will be generated if the customers zip code and country corresponds to a sales tax profile that it setup in the CRM.

8. Fill out Payment Information and submit the order. If the customer is paying by credit card, fill out the credit card number, expiration date and security code. If the customer is paying by check, fill out the bank routing number and bank account number. If the customer is paying by an offline payment e.g. money order, just select offline payment.

An offline payment order will be assigned a pending status after an order is processed, and the orders will remain as pending until the payment has been marked as received under the order details.

Tracking Numbers

After you have successfully fulfilled your orders and you have the list of tracking numbers, the Lime Light CRM will allow you to import these tracking numbers back onto their associated orders.You just need to follow the example attached to this document, which is a simple CSV template.

You will go to Insights > Import / Export Data and navigate to the 'Import Queue'. From the 'Actions' drop-down menu you will select 'queue import'. A box will then pop up for you to select the type of import. You'll need to select 'tracking' and then select the file. The system will run the cron at the top of the hour importing the tracking numbers onto their associated orders; it will automatically change the status of the order from Approved to Shipped and send the completed orders to the sub-folder called "Shipped".

Once this process has finished, the system will also send out the Shipping Confirmation email to your customers if you have enabled this feature on your products.

Return Orders

After you have a list of return orders and their return reasons, the Lime Light CRM will allow you to import these return orders back onto their associated orders. You just need to follow the example attached to this document, which is a simple CSV template.

The accepted values for Return Reason are:

Refused / RTS

Undeliverable

Customer Returned

Other

You will go to Insights > Import / Export Data and navigate to the 'Import Queue'. From the 'Actions' drop-down menu you will select 'queue import'. A box will then pop up for you to select the type of import. You'll need to select 'return' and then select the file. The system will run the cron at the top of the hour importing the return orders and reasons onto their associated orders; the history of each order will also be updated indicating that the order has been returned.

Once this process has finished, the system will also send out the Return Notification email to your customers if you have enabled this feature on your products.

*The system will still accept your return orders import file even if an RMA number was not previously generated for the orders you are importing. Also, your return orders import file will still be accepted if there is no returns profile associated with the orders you are importing.

Market Segmenting is a way for you to understand your customers purchasing behavior by dividing yourcustomer and prospect base into into groups, or segments, based on different characteristics. This will help identify less satisfied segments of customers, and also ensure customer retention by nurturing the relationship.The segments created are composed of customers that share traits such as similar interests, needs, or locations.

ActiveCampaign

How to create your segments:

To create a new segment, you will need navigate to the Actions drop-down menu and select "New Segment". This will bring you to the Segment List Builder where you will need to create a name for your segment list, and then start creating your list by selecting your conditions. You also have the option to add "groups" within your segment lists as shown in the illustration below.

Conditions:

You have the ability to add up to a total of nine (9) conditions, and five (5) groups within each segment list. The groups will allow you to show options for your lists such as I want to see customers that purchased product A OR customers that purchased product B. Below is a list of the available conditions to choose from for your lists.

Successful Order

An approved order in LimeLight

Decline Transaction

A declined transaction in Limelight

Show Interest (Partial)

A prospect in Limelight that has not created an order

Date Created

Contact creation date in Limeligjt

Email

Customer email address

Phone Number

Customer phone number

First Name

Customer first name

Last Name

Customer last name

Billing Country

Customer billing country.ISO Alpha 3 (USA, CAN, AUS etc.)

Billing State

Customer billing state

Billing City

Customer billing city

Billing Zip/Postal Code

Customer billing zip/postal code

Shipping Country

Customer shipping country.ISO Alpha 3 (USA, CAN, AUS etc.)

Shipping State

Customer shipping state

Shipping City

Customer shipping city

Shipping Zip/Postal Code

Customer shipping zip/postal code

Tags

A tag created in Limelight

Campaign

A specific campaign

Product

A specific product

Vertical

A specific vertical

Category

A specific category

Transaction Date

Order creation date

Order Count

The total number of orders from a single customer

Total Spending

Total amount spent by that customer

Subscription Depth

Customers subscription billing cycle

Single Order Total

The order total of a single order

Chargebacks

Number of orders marked as chargeback in Limelight

Cancels

Number of orders cancelled in Limelight

Refunds

Number of orders marked as refund in Limelight

Member

Customers membership enrollment status

Contacts (Custom Fields)

Contact type custom fields

Auto Processing Settings:

In order to use the Auto Processing Settings, you will need to first configure your Auto Responder Profile within Settings > Providers. After you configure your Auto Responder profile, you can then move on to add the provider to your segments.

Within your Segmented List Builder is where you will configure the Auto Processing Settings. Once you select the Auto Responder Profile, the lists and segments that you have configured within your auto responder terminal (MailChimp, ActiveCampaign) will populate. The list and segment information is synced directly from your provider into Limelight once you select the Auto Responder Profile.

To create your lists, you will need to do so within your MailChimp or ActiveCampaign terminal. For further instruction on how to configure, please visit our MailChimp anddocumentation.

The segments that you create within your Segmented builder will then be sent to your Auto Responder.

Use Cases and Examples:

Lets say you want to see a list of customers in the state of Florida that cancelled their order within their trial period. Your list would look like this:

Lets say you want to see a list of prospects in campaign 107 that opted into your site but didn't purchase. Your list would look like this:

As a business owner, I want to view a list of customers that purchased product 477 this month in the country of Canada. Your segment list would look like:

Additional Notes:

*To refresh your segment list, you will need to just click on "run segment" as shown in the illustration below.

Enhancements:

Insights

Cycle and Acquisition Date have been added to the Active Subscription Forecast look within the Subscriptions dashboard.

Fixes/Bugs:

Fixed issue causing the Rebill Pre Auth to not be sent to the Inovio gateway.

Fixed display only issue within the Decline Manager Card Type rule that caused Prepaid to display instead of the card type that was selected.

Updated the modal for User Defined Priority within the Payment Router to allow for scrolling so the full list of gateways can be viewed.

Removed duplicate functionality in the SMTP profile to view the password.

Lime Light CRM allows you to import Customer profiles in a CSV formatted text file. The Customers import also allows you to simultaneously create the customers membership record and trigger the Member Creation email. Customers can be uploaded under the Import Queue located within Insights > Import/Export Data.

Import Customers includes the customers first name, last name, email, phone, create member, event id, and replace customer. If a required item is not properly formatted or blank, the import process will skip that record and it will not be processed.

Note: If replace_customer is not specified and the same email address already exists with another name, the import record will be skipped and old customer record will remain as it is.

Field Name

Format

Values

Comments

first_name

String 50 characters

The customer's first name

Required

last_name

String 50 characters

The customer's last name

Required

email

String 50 characters

The customer's email address

Required

phone

Numeric

The customer's phone number- No hyphens

Required

create_member

Numeric 1 or 0

When set to 1 (yes) a member record will be created for the customer

Optional

event_id

Numeric

The Email Trigger ID in the LimeLight platform to send the Member Notification if create_member = 1

Optional

set_temp_password

Numeric 1 or 0

When set to 1, we will use the temporary password as the customer's permanent password. When set to 0, the customer will be required to set their own password. Will be used only if creating member.

Optional

replace_customer

Numeric 1 or 0

When set to 1, if the same email address already exists with another name, this new record will override the existing record for the customer. When set to 0, the old customer record will remain as it is, a new record will not be created.

Optional

The CSV template to import Customers can be found below:

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

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 LimeLight Platform.

Client ID: This will be provided to you by GreenBox

Client Secret: This will be provided to you by GreenBox.

Location ID: This will be provided to you by GreenBox.

Currency: The GreenBox Gateway currently supports USD only.

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

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

Feature Release:

MasterCard Compliance-As part of the new MasterCard regulations, LimeLight has implemented three changes affecting trial subscription transactions processed via the NMI Paysafe Processing Continuity gateway. Please review the Help Center article for full details of the changes.

Consent Rules Enforcement

consent_required override prevention via API

Consent notification requirement

Enhancements:

Providers

New payment gateway integration- GreenBox offers fast to-market time and reliably handles high volumes of transactions. Refer to this Help Center article for configuration details.

Fixes/Bugs:

Fixed issue preventing User Defined Decline Reasons from being deleted.

Fixed issue causing newly migrated orders to be declined on the Bill 1st gateway.

To configure the Paypal Express 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 Paypal Express 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 Paypal Express Gateway.

Password: This will be provided to you by Paypal Express Gateway.

Signature: This will be provided to you by Paypal Express Gateway.

Currency: The Paypal Express Gateway currently supports USD, EUR, GBP, CAD, AUD, ZAR, JPY, DKK, NOK, SEK, BRL, CLP, MXN, KRW, NZD, SGD, HKD, CHF, and TWD currencies.

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

Adding Paypal Express to a Lime Light Campaign

1. Under the list of payment types for your campaign, select Paypal Express under Other.

https://www.google.com/?token=EC-7LY82491FL121212&PayerID=ABC9dEFDVHCC&g_rd=ssl

2. Under the Gateway Configuration for your campaign, select your Paypal Express Gateway profile at the Alternative Payment Provider field.

Other Paypal Express Gateway Notes

The Paypal Express Gateway must be used in conjunction with a single credit card gateway on your campaign, but load balancing with credit card gateways is not supported when using PayPal Express on a campaign .

There is an inability to void transactions made through the Paypal Express Gateway.

There is an inability to perform partial refunds through the Paypal Express Gateway. All refunds must be in full.

The Paypal Express Gateway does not support decline reprocessing.

The Paypal Express Gateway does not support recurring transactions.

The Paypal Express Gateway does not support after order upsells via webforms integration.

The Paypal Express Gateway is the payment module where the customer gets redirected to their Paypal account to complete payment.

Integrating Paypal Express Using the API

The get_alternative_provider API method within our Membership API must be used to retrieve redirection information for Paypal Express. Please visit our API documentation for further details.

Thealt_pay_token and alt_pay_payer_id must be retrieved when using the NewOrder or NewOrderWithProspect API methods within our Transaction API. Please visit our API documentation for further details.

Please find here a description of the payment process that takes place when using PayPal Express with the Lime Light API:

-Upon the customer selecting PayPal Express as the payment method you will post a get_alternative_provider call to the Membership API

Please visit our API documentation to find the parameters used for this call, notice that this call requires you to provide us with a "return_url", this URL is the one that will be used after the customer completes the transaction on PayPal.

-In response to the get_alternative_provider call you will receive a "redirect_url" with a token Id in it; and you will use this URL to redirect the customer to PayPal so they can process the payment

- When the customer has completed their payment on PayPal you'll receive the final outcome to the "return_url" that you provided with the get_alternative_provider call

- In this return_url you will get the token Id and payer Id that you'll need to populate in the "alt_pay_token" and "alt_pay_payer_id" fields with the NewOrder or NewOrderWithProspect calls to the Transaction API to complete the order in your CRM

- The field names will appear in the return_url as in the following example:

token= alt_pay_token

PayerID= alt_pay_payer_id

Offer Configurations allow you to streamline the platform Place Order page and NewOrder API calls by creating predetermined product and billing model profiles to choose from.

Offer Configurations

Once you have created and saved your Standard Offer, the Offer Configurations tab will appear on the Offer Edit page.

here

Creating your Offer Configurations

To create a new Offer configuration select the Actions dropdown > Add

Name: The name of the Offer Configuration that will be displayed on the Place Order page dropdown.

What is the Main Product?: Select the main product of the order

If you want more than one main product in the offer configuration, you will need to utilize the Pre-built Bundle Product. For more information on creating a pre-built bundle product please reference the Create Bundles Help Center article.

Custom-built Bundles cannot be used in offer configurations.

Override product price (optional): This can be used to override the Price (MSRP) of the main product.

Default quantity?: This can be used to configure the product quantity, leaving the field blank will default the quantity to 1.

Will this have a trial?: Select Yes to add a trial, the trial will follow the configuration set up in the main offer.

If Yes, select the trial product.

What is the billing frequency?: Select the Billing Model to be used with this offer configuration

Is this an upsell offer?: Select Yes to create the offer configuration as an upsell. For more information on upsells within LimeLight reference the Submitting Upsells in LimeLight Help Center Article

What step is this in the offer flow?: Add the step number of the upsell offer configuration.

Campaign Configuration

Campaign configuration has not changed, you will still select the main offer on the campaign.

Place an Order

To place an order in the platform with the offer configuration profile navigate to New Order > Select the Campaign > Select the Offer > Select the Configuration

The Trial (if configured), Billing Model, Product, Quantity and Step Number (if configured will be automatically populated and cannot be changed.

To Add another offer configuration, click the Add link

Custom orders can only be created if the user has the Build Custom Order permission selected. See explanation below.

Offer Configurations Permissions

A new Build Custom Order permission has been added to the Offers section in Employee Permissions. This will allow the user to place custom orders on the Place Order page and not have to select an offer configuration profile.

In addition, a new Offer Configurations section has been added to the Employee Permissions. Within the section you can enable or disable capabilities to Add, Edit and Delete Offer Configurations.

By default, only Administrator, Manager and Technical Departments will have Offer Configurations permissions enabled.

API

For API documentation on the Offers Array changes, please refer to the API documentation . Navigate to API > Orders

LimeLight platform updates for MasterCard regulations compliance:

In order to remain compliant with the new MasterCard regulations (AN2202) as a TPP LimeLight will be implementing two changes on Wednesday 6/5/2019 that will affect all subscription transactions processed on the NMI Paysafe Processing Continuity gateway.

1 - Consent RulesEnforcement

Functionality update:The LimeLight "NMI Paysafe Processing Continuity" Gateway profile will enforce consent rules on all MasterCard trial orders (where initial amount doesnt equal the recurring/rebill amount).

If a standard subscription (meaning the amount of the initial is the same as the recurring/rebill) is detected, then consent requirements will be bypassed.

2 - consent_required override via API

Functionality update: Passing consent_required=0 in the API call will no longer override consent required.

All MasterCard initial subscription orders processed through the LimeLight "NMI Paysafe Processing Continuity" Gateway profile withtrial orders will require consent. If consent_required=0 is passed in the API call it will be ignored and the subscription will not rebill until consent is received.

3 - Consent Notification

Functionality update: The Consent email notification must be sent before an order can receive consent (flag as consent_received.)

Currently the LimeLight platform is set up to automatically require consent for any MasterCard initial order processed through an NMI Paysafe Processing Continuity gateway profile. These transactions will not rebill until consent is received from the cardholder. The transaction cannot be flagged as consent_received until the Consent notification has been sent.

Configure the Consent Notification Email Template.

Navigate to Settings > Email Notifications > Email Templates > Actions > Add Email

Templates > Select Consent Notification from the dropdown > Select Template > Customize your Consent Notification > Save. Be sure to add:

Alert Days (use 1 day to ensure you comply with after the trial period has ended)

Master Card as the Payment Type

API documentation

In the Template body you must include the following:

Your specific cancellation instructions which includes a direct link to an online cancellation procedure on the website where the cardholder made the initial purchase (See Cancellation Policy below).

Your merchant name as it appears on cardholders statement.

The {nextsubscriptiondate} token - The date in which the credit card charge will happen.

The {nextsubscriptionamount} token - The amount that the credit card will be charged.

Cancellation Policy: The merchant must provide a direct link to an online cancellation procedure on the website where the cardholder made the initial purchase.

Configure the Consent Notification Email Template (Instructions listed in Rebill Consent above).

This online cancellation link must be provided by the merchant. LimeLight does not provided a hosted cancellation link. We only provide a hosted consent link if merchant chooses to use it.

A standard {consent_url} and {consent_token} are included in the default template body (e.g. <a href="{consent_url}{consent_token}">Click here to opt-in to subscription</a>). Clicking the LimeLight hosted consent link will provide a generic message Thank You, [customer name]. Your order has been updated. Your next billing will occur on mm/dd/yyyy. However, if you prefer to use your own branded page/link you can add it to the template. Please refer to our API documentation : Navigate to Orders > Order Compliance Consent.

Configure the Consent Notification Email Trigger.

Navigate to Settings > Email Notifications > Actions > Add > select Consent Notification > configure the Name, Description, SMTP Profile > select the Consent Notification created above > add your list of BCC Emails that should also get the Notification (A record of the notification sent to your customer must be retained for one year - See #4 Storage of transaction receipt below) > Publish > Save

Storage of transaction receipt: Acquirers will be required to monitor transactions to identify when the same cardholder account number is used across multiple MIDs. When this is identified the acquirer may require proof of each transaction.

Navigate to Settings > Email Triggers > Click the Order Confirmation name configured to your trial product > Add your list of BCC Emails that should also get the Notification > Save.

Configure the Consent Notification Email trigger (See above).

Navigate to Settings > Email Triggers > Click the Consent Notification name configured to your trial product > Add your list of BCC Emails that should also get the Notification > Save.

Add the Notification to the trial product.

Navigate to Products > Products > click on the trial product name > select Custom Notifications in the Parameters section > click the down arrow on Custom Email Notification to open the section > Actions > Add > select Consent Notification as the Type > select the Trigger configured above > Save the product

*To Add the notification to multiple products; Click the ellipsis on the on the Consent Notification email trigger > Select Add to Products > Select the products to apply the notification to > Save.

Example of default Consent Notification and hosted consent page:

3 ways an order is updated as consent_received

The cardholder clicks the LimeLight hosted consent link in the Consent Notification email as described in the steps above.

Order Compliance Consent API POST when the cardholder clicks a consent link from your branded page. Please refer to our : Navigate to Orders > Order Compliance Consent.

A customer service rep clicks the Consent Received on the Order Details page in the LimeLight platform when the cardholder give verbal consent.

Note: A customer service rep cannot update Consent Received on the order details page until after the consent notification has been sent.

Feature Release:

Offer Configurations - Save your team time and ensure you're placing the correct order every time. Offer Configurations allow you to streamline the platform Place Order page and NewOrder API calls by creating predetermined product and billing model profiles to choose from. For more information about Offer Configurations check out the Help Center. For API documentation on the Offers Array changes, please refer to the API documentation here. Navigate to API > Orders. To start using Offer Configurations, reach out to your Client Success representative.

Enhancements:

Offers

A new Last Cycle Rule Complete Subscription has been added for Custom Recurring offers. This will allow the subscription to be stopped, but not placed on hold so the naturally completed subscriptions can be separated from subscriptions placed on hold in reporting.

Fixes/Bugs:

Fixed orderSalesTaxPercent issue with Taxjar.

Fixed issue with adding and removing Decline Rules

Fixed issue with adding smart tag automation

Added solution ID to Authorize.net

Watch the Webinar by LimeLight

MasterCard Compliance Webinar Recording 4/9/2019

LimeLight setup to stay compliant with the MasterCard regulations:

In order to remain compliant with the new MasterCard regulations in effect on 04/12/2019 (AN2202) you will need to make some changes to your API calls and add some extra configurations to your LimeLight platform listed in the steps below.

Currently the LimeLight platform is set up to automatically require consent for any MasterCard initial order processed through an NMI Paysafe Processing Continuity gateway profile. These transactions will not rebill until consent is received from the cardholder.

Free Trial 5968 merchants not using the NMI PaySafe gateway

If you are a free trial 5968 merchant using another gateway/processor, you will have to pass the consent_required=1 parameter in the NewOrder API call for MasterCard transactions.

For more information please refer to our API documentation : Navigate to API > Orders

Merchants using the NMI PaySafe gateway with subscriptions that are not free trial transaction

If you are on NMI Paysafe and experimenting with straight subscriptions, you will need to reach out to PaySafe to discuss your processing options.

Disclosure of offer page information. Transactions must include the Website URL where the cardholder requested the product.

NewOrder API requests must be updated to include the website parameter.

For more information Please refer to our API documentation : Navigate to API > Orders > NewOrder

Note: To assist during the migration process, you can add your website URL field in the NMI PaySafe Gateway profile. If a NewOrder call is received without the website parameter we will use the URL from the gateway profile. *This is not intended to take the place of the website parameter in the NewOrder API call

Trial Start Date and Duration: The trial period must begin on the date that the product is received by the customer.

Configure the trial duration with delivery time in mind. For example: if you are selling a 14 day trial and average delivery time is 4 days, then configure the trial duration as 18 days.

For Next-Gen: Navigate to Products > Offers > Click on the Offer name > In the Trial section: Click on the Custom Duration radio button in the Trial Duration sub-section > enter in the new trial duration to account for delivery time > Save. (Example A)

If using Delayed Billing; Select 'When to Charge' > Delayed Billing > Configure the Days to Delay duration to account for delivery time > Save (Example B)

Example A API documentation

Example B

For Legacy: Navigate to Products > Click on the trial Product name > Click the down arrow on Subscription to open the subscription section > Update Subscription Type field to Bill By Cycle > Update the Days To Next Billing days to the new trial duration to account for delivery time > Save.

Rebill Consent: After the trial period for a product has ended, but before any rebill is initiated the merchant must provide subscription information and cancellation information to the consumer. The merchant MUST also get explicit consent BEFORE issuing the rebill.

Configure the Consent Notification Email Template.

Navigate to Settings > Email Templates > Actions > Add Email Templates > Select Consent Notification from the dropdown > Select Template > Customize your Consent Notification > Save. Be sure to add:

Alert Days (use 1 day to ensure you comply with after the trial period has ended)

Master Card as the Payment Type

In the Template body you must include the following:

You must add your specific cancellation instructions which includes a direct link to an online cancellation procedure on the website where the cardholder made the initial purchase (See Cancellation Policy below).

You must add your merchant name as it appears on cardholders statement.

{nextsubscriptiondate} token - The date in which the credit card charge will happen.

{nextsubscriptionamount} token - The amount that the credit card will be charged.

A standard {consent_url} and {consent_token} are included in the default template body (e.g. <a href="{consent_url}{consent_token}">Click here to opt-in to subscription</a>). Clicking the LimeLight hosted consent link will provide a generic message Thank You, [customer name]. Your order has been updated. Your next billing will occur on mm/dd/yyyy. However, if you prefer to use your own branded page/link you can add it to the template.Please refer to our API documentation : Navigate to Orders > Order Compliance Consent.

Configure the Consent Notification Email Trigger.

Navigate to Settings > Email Triggers > Actions > Add > Select Consent Notification > Configure the Name, Description, SMTP Profile > Select the Consent Notification created above > Add your list of BCC Emails that should also get the Notification (A record of the notification sent to your customer must be retained for one year - See #4 Storage of transaction receipt below) > Publish > Save

Add the Notification to the trial product.

Navigate to Products > Products > Click on the trial product name > Select Custom Notifications in the Parameters section > Click the down arrow on Custom Email Notification to open the section > Actions > Add > Select Consent Notification as the Type > Select the Trigger configured above > Save the product

*To Add the notification to multiple products; Click the ellipsis on the on the Consent Notification email trigger > Select Add to Products > Select the products to apply the notification to > Save

Example of default Consent Notification and hosted consent page:

3 ways an order is updated as consent_received

The cardholder clicks the LimeLight hosted consent link in the Consent Notification email as described in the steps above.

Order Compliance Consent API POST when the cardholder clicks a consent link from your branded page. Please refer to our : Navigate to Orders > Order Compliance Consent.

A customer service rep clicks the Consent Received on the Order Details page in the LimeLight platform when the cardholder give verbal consent.

Note: A customer service rep cannot update Consent Received on the order details page until after the consent notification has been sent.

Cancellation Policy: The merchant must provide a direct link to an online cancellation procedure on the website where the cardholder made the initial purchase.

Configure the Consent Notification Email Template (Instructions listed in Rebill Consent above).

This online cancellation link must be provided by the merchant. LimeLight does not provided a hosted cancellation link. We only provide a hosted consent link if merchant chooses to use it.

Storage of transaction receipt: Acquirers will be required to monitor transactions to identify when the same cardholder account number is used across multiple MIDs. When this is identified the acquirer may require proof of each transaction.

Configure the Order Confirmation Email trigger.

Navigate to Settings > Email Triggers > Click the Order Confirmation name configured to your trial product > Add your list of BCC Emails that should also get the Notification > Save

Configure the Consent Notification Email trigger (See above).

Navigate to Settings > Email Triggers > Click the Consent Notification name configured to your trial product > Add your list of BCC Emails that should also get the Notification > Save.

Send receipt for all transaction attempts: Each time a merchant attempts a transaction, a receipt must be sent to the cardholder via email or other electronic means. The merchant must also provide instructions to cancel the subscription. For unsuccessful transactions, the decline reason must be provided.

Configure the Decline Notification Email Template.

Navigate to Settings > Email Templates > Actions > Add Email Templates > Select Decline Notification from the dropdown > Select Template > Customize your decline template > Save. Be sure to add:

In the Template body you must include the following:

{declinereason} token - The decline reason provided by the gateway

{nextsubscriptiondate} token - The date in which the credit card charge will happen.

Configure the Decline Notification Email Trigger.

Navigate to Settings > Email Triggers > Actions > Add > Select Decline Notification > Configure the Name, Description, SMTP Profile > Select the Decline Notification created above > Add your list of BCC Emails that should also get the Notification > Publish > Save

Add the Notification to the trial product.

Navigate to Products > Products > Click on the trial product name > Select Custom Notifications in the Parameters section > Click the down arrow on Custom Email Notification to open the section > Actions > Add > Select Decline Notification as the Type > Select the Trigger configured above > Save the product

Confirm that the Order Confirmation, Cancellation Notification, Return Notification and Void Notifications are all configured to your trial and rebill products.

Recurring Transactions: All recurring transactions at the same acquirer must be processed under the same MID that was used for the initial payment transaction.

Configure your Campaign.

Navigate to Products > Campaigns > Click on the campaign name > Select the NMI Paysafe Processing Continuity gateway profile that all initials and rebills should process through. Only one gateway profile should be configured to each campaign, however, a gateway profile can be configured to more than one campaign.

Paysafe / MasterCard Audit Fields

Paysafe/MC Audit Field

LimeLight Field / Data Element

merchant_identifier

NMI Username from NMI Paysafe Profile

merchant_name

Descriptor from NMI Paysafe Profile

merchant_website_url

Website URL passed in to NewOrder or from NMI Paysafe Profile

customer_service_phone_number

Customer Service Number from NMI Paysafe Profile

subscription_plan_id

Unique ID assigned to trial/rebill/subscription order chain

trial_amount

Order total for trial order

subscription_amount

Order total for rebill order

token_value

NMI Token generated for the NMI Paysafe transaction

product_description

Main trial product description

start_of_trial_date

Date of original trial order

end_of_trial_date

End of trial date

start_of_subscription_date

Date of rebill order (depth = 1) associated to original trial order

subscription_frequency

Frequency of subscription billing after rebill date (e.g. 30 days)

proposed_primary_rebill_date

Date of rebill order (depth = 1) associated to original trial order

proposed_secondary_rebill_date

Date of rebill order + 1

nmi_transaction_id_trial

NMI transaction ID of the original trial order

nmi_transaction_id_rebill

NMI transaction ID of the rebill order associated to original trial order

transaction_status_trial

Status (approved or declined) of trial order

transaction_status_rebill

Status (approved or declined) of rebill order

order_id_trial

Order ID of trial order

order_id_rebill

Order ID of rebill order

Date of email notification

Date of email notification

notification_type

Order confirmation, Cancellation, Decline notification, Consent notification

notification_method

email

order_id

Order ID of trial or rebill order the notification was associated with

nmi_transaction_id

NMI transaction ID of the trial or rebill transaction

transaction_status

Status (approved or declined) of trial or rebill order associated with notification

customer_name

Customer name on order that notification was associated with

customer_email

Customer email on order that notification was associated with

customer_phone

customer_phone

action_datetime

Date of consent or cancellation action

action_type

consent_received or cancel_subscription

action_method

via API, call center (Lime Light UI), or email link click

action_source

IP address that action_method came in from

MemberMouse is a WordPress membership plugin. Simply download the plugin and upload it to your WordPress installation and you instantly get a flexible and feature-rich platform to grow almost any type of business.

In order to activate the integration of MemberMouse in your CRM, you will go to Clients and Fulfillment>Membership. Click on the Actions drop down selection to add a new MemberMouseprofile.

Lime Light CRM Domain: This is the URL of your Lime Light CRM install so that we know which account to apply the profile to.

Post Back URL: This is the MemberMouse post back URL. You'll find this URL on the Payment Methods screen in the Lime Light configuration form under Post Back URL within the MemberMouse portal.

Alias: This is the name of the profile that will show up in the Lime Light CRM so you can identify which site it's related to.

This provider will be assigned at the campaign level, so you will need a separate member site profile in your CRM for each member site that you activate. Once the profile has been created, you will go through your campaigns and assign it to those campaigns that you want to assign the member site to, and your profile can be assigned to a Lime Light CRM campaign once you select Third Party Providers under the Options menu.

MemberMouse Support

Please navigate to the page for a detailed description on how to configure this on the MemberMouse side.

LimeLight is now integrated with TaxJar which offers country and state configuration.

Configuring TaxJar

To configure the TaxJar profile into your LimeLight platform, you will go to Settings > Providers and click on the Actions drop-down arrow > select "Add New Provider Profile" > click on "Tax" as the provider type then select TaxJar 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:

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

Access Code: This will be provided to you by TaxJar.

Countries Filter: Select the countries for your tax request.

States Filter: Select the states for your tax request.

Tax Shipping: Specify if you will be charging tax on shipping.

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

LimeLight is now integrated with ShipBob which offers Combine Similar Addresses and Delay Hours features.

Configuring ShipBob

To configure the ShipBob fulfillment profile into your LimeLight platform, you will go to Settings > Providers and click on the Actions drop-down arrow > select "Add New Provider Profile" > click on "Fulfillment" as the provider type then select ShipBob 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:

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

Access Code: This will be provided to you by ShopBob.

Combine Similar Address: This field allows you to set whether or not you want orders with identical shipping addresses to be combined in one order and sent to the fulfillment provider.

Delay Hours: Specify if you would like to delay our system from pushing the orders to your fulfillment center for an X amount of hours. This would allow you to review the orders before they get sent out to the fulfillment provider.

Receive Tracking #: This field allows you to set whether you want orders with identical shipping addresses to be combined in one order and sent to the fulfillment provider.

Enhancements:

Providers

New Tax provider integration-TaxJar supports both country and state configurations. Refer to this Help Center article for configuration details.

New fulfillment integrationShipbob supports same, next, and 2-day shipping for ecommerce companies of all sizes taking the hassle out of storing, picking, packing, and shipping your products. Refer to this Help Center article for configuration details.

Acquired gateway is now compatible with LimeLights Account updater.

Dynamic descriptors have been added to the IPPay gateway integration to help lower chargeback rates due to the customer not recognizing the descriptor.

Insights

Void Failures are now included in the Refund Failures report.

Fixes/Bugs:

Fixed issue with custom bundle products causing errors in the Kount service when the PROD_ITEM was not passed in the request.

Fixed issue with the certain segment exports displaying the wrong phone number.

Fixed issue with the CVV not being passed to NMI gateway on initial purchases after tokenize_payment was used.

Feature Release:

MasterCard Compliance - To help you remain compliant with the MasterCard regulations, weve added a Post-Alert Days (After Rebill Date) configuration option to the Consent Notification email template. This will automatically resend the consent notification after the rebill date has passed if consent has not been received.

Enhancements:

Orders

Subscription credits can now be removed from a customers subscription. In the case that a subscription credit was added by mistake or is no longer valid, the credit balance can be completely removed from the customers subscription.

API

The Member API calls have been updated to allow a member to be created for a prospect record. Note: If you utilize this API method, you may need to make code changes. API Documentation : Navigate to API > Members.

The order_update API call now allows a token to be passed in place of the credit card number. If you utilize this API method, you may need to make code changes. Refer to API Documentation : Navigate to API > Orders.

Providers

Auto-Responder functionality has been updated to now allow customers to be subscribed to more than one Auto-Responder list based on the campaign configurations.

Insights

A new Is Pinless Debit? filter has been added to the Chargeback Representment dashboard.

Fixes/Bugs:

Removed the duplicated page header from the Customer details page.

Creating API Accounts

API Accounts allow you to create custom API users within your CRM. In order to create an API user, just go to Settings > API Accounts. Once there, just click on Add API User in order to create a new user account.

*NOTE*- Please keep in mind that if you see the message "This order was placed by unlinked API user", it just means that the user has not been updated to include the newly added user data fields. The API account access/functionality hasn't changed, we just can't pull full reports on that user's API calls.Adding this additional information will allow for more meaningful analysis of API activity.

For API accounts that you have already created, you can search for them by Id or a list of Ids by entering the search criteria in the search field. The system will automatically populate the results for you once the search criteria is entered.

The API Accounts page will be available to users who are assigned to the administrator and technical departments within your system. An API password will automatically be generated by the system once a username is created for your API user. The API username and password that is generated can then be used in conjunction with our Transaction and Membership API. There is no limit on the number of API users that can be created in your system.

API Account Permissions

When you edit the permissions for an API user, the API Account Permissions page will allow you to enable or disable API methods for an API user.Examples of the permissions that can be set within our Transaction and Membership API are listed below.

Campaign Permissions

On the API Account permissions page, you have the ability to restrict or allow certain campaigns for your API Users; just select edit next to campaign permissions in order to set these permissions.

Third Party API Accounts

These will appear in your API Accounts page only. If you are using certain third party providers that require API access from you to post back into your system; for instance, Order Confirmation Providers among others. If you are not using any of these providers, the Third Party API Accounts will not be listed in your system.

These accounts will automatically be created by the system once the third party provider is enabled. These cannot be edited on your end; however, anytime you reset your master API account, the Third Party API Accounts will automatically be reset as well, and you will just need to update your third party provider with the new credentials.

To access your Third Party API Accounts, you will need to go to the 'Actions' drop-down menu and select 'Third Party API Credentials' as shown below. Once clicking on 'Third Party API Credentials', a box will pop up with all of your Third Party Credentials.

The General API documentation has moved! Please click Here to view our General API documentation.

Limelight Restful API offers some new functionality with fully restful routes. This documentation can be found Here

LimeLight General API

LimeLight Restful API

We've created simple, easy-to-follow implementation instructions so you can integrate Gratify into your checkout page: Gratify API Documentation

We've created simple, easy-to-follow implementation instructions so you can integrate PayPal Payments into your checkout page: PayPal Payments Instructions