LimeLight CRM Setup

Learn how to connect LimeLight and BlueSnap for a unified CRM and payment processing solution.

LimeLight CRM provides a powerful e-commerce platform for marketing automation, billing optimization, and actionable analytics. Connect LimeLight and BlueSnap to enable global payment processing.

Supported features

Auth/Capture and Separate Auth and Capture
Built-in Fraud Prevention and Risk Management
Chargeback Management
Credit and Debit Card Processing
LatAm Local Processing
Multiple Currencies and Multiple Languages
Partner Sandbox Testing
Payment Analytics and Reporting
Payment Optimization
Vaulted Shoppers

Requirements

LimeLight and BlueSnap accounts

You must have accounts at both LimeLight and BlueSnap to proceed.
 If you need a LimeLight account, go to the LimeLight website to sign up.
 If you need a BlueSnap account, go to the BlueSnap website to get started.

Supported currencies

BlueSnap supports the currencies listed here. We recommend configuring your store to only accept currencies supported by BlueSnap.

Supported countries

BlueSnap supports the countries listed here. If a shopper is located in one of these supported countries, they will be able to purchase with the BlueSnap payment module.

PCI compliance

A PCI compliance level of SAQ-A is required.

Before you begin

Contact an Implementation Specialist to get your account ready. BlueSnap provides you with the gateway credentials you use in Step 2.

Step 1: Configure your BlueSnap account settings

Complete these steps in your BlueSnap Console for production or sandbox.

  1. Get your BlueSnap API credentials and define the authorized IP addresses for your server. Both of these actions are performed on the same page; for instructions click here.

  2. Set up your statement descriptor. The statement descriptor is the description that appears on the shopper's credit card statement or bank statement for each transaction and helps the shopper identify the transaction.

    • Go to Settings > General Settings.
    • In the Branding Settings section, enter a Default Statement (Soft) Descriptor and Support Phone Number (both appear on the shopper's statement).
    • Click Submit.
  3. To get paid, you need to configure your payout settings. Refer to Payout for more information.

Step 2: Configure your LimeLight account settings

Complete these steps in your LimeLight CRM account. You need your gateway credentials from BlueSnap to proceed.

  1. Go to Payment Systems > Gateway Providers.

  2. From the Gateway Accounts drop-down menu, select Network Merchants Inc.

  3. Click Add Gateway.

  4. Configure the following settings:

    • Username — Enter your gateway username that BlueSnap provided.
    • Password — Enter your gateway password that BlueSnap provided.
    • Gateway Alias — Enter a name to help you identify the payment gateway record (i.e. BlueSnap Production).
  5. Click Save.

Best practices & tips

Considering shopper impact of currency conversions

While transactions are placed in your store’s base currency, you might have your store configured to display product prices in multiple currencies. To account for any differences between the currency conversion rates used to display prices on your website and the rates used by the shopper’s issuing bank, we recommend including a note on your checkout page that informs shoppers of potential price variations. For example: “The price listed is approximate and may vary slightly”.

Reporting

Use BlueSnap's reporting capabilities to gain a comprehensive understanding of your business through the detailed transaction and payout reports, through payment conversions reports, and much more. Reports can be viewed right in your BlueSnap Console or pulled via the Reporting API to be parsed or pushed to your third-party reporting tools.

Updated 2 months ago

LimeLight CRM Setup


Learn how to connect LimeLight and BlueSnap for a unified CRM and payment processing solution.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.