To configure Alternative Payments into your Lime Light CRM, you will go to Payment Systems> Gateway Providers and select Alternative Payments from your Gateway Accounts drop down menu. Click on “Add Gateway” and fill out the gateway parameters.
These parameters are briefly described here for your reference:
API Secret Key: This will be obtained from your Alternative Payment's profile.
Currency: The Alternative Payments Gateway currently supports USD, EUR, GBP, AUD, NOK, SEK, BRL and PLN currencies.
Test Mode: Select YES if you want to use Alternative Payments in test mode.
Gateway Alias: For internal purposes only; it helps you identify your gateway account among several others 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).
You will be responsible for configuring your own webhook URL with the gateway by creating a "business case" within your Alternative Payments terminal. Your webhook URL can be derived from the following template URL: Please contact Alternative Payments for additional details.
Your Webhook URL should look similar to this :
Alternative Payments supports the following Payment Types:
BrazilPay Bank Transfer
BrazilPay Boleto Bancário
|Payment Option||Supports Rebilling||Supported Country (ISO Code)|
|SEPA||YES||AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IS, IE, IT, LV, LI, LT, LU, MT, NL, NO, PL, PT, RO, SK, SI, ES, SE, CH, GB|
|TrustPay||NO||BA, CZ, EE, GB, HR, HU, LT, LV, SK, TR|
|BrazilPay Bank Transfer (TEF)||YES||BR|
|BrazilPay Boleto Bancário||NO||BR|
The campaigns must be configured under the appropriate countries for the payment type to work properly, i.e. MisterCash only works with BE - Belgium
Additional Alternative Payments Notes
-Campaigns must be configured under the appropriate countries for the payment type to work properly, i.e. MisterCash only works with BE – Belgium.
To create SEPA transactions using Alternative Payments gateway, it is now mandatory to validate the phone number. To do this, you can leverage the method "get_alternative_provider". One of the parameters of this method is "function". In order to do the validation you need to pass that parameter with the value "phone_verification" and in another parameter called "phone" you need to pass the phone number with a valid format (refer to http://www.alternativepayments.com/developers/API/#phone-verification for a better explanation on what you need to do in the checkout page).
After you fire the get_alternative_provider call, the customer will receive a SMS message with a PIN that he/she will have to insert in the respective field in the checkout page. At the same time, you will receive in the response of that method a "token" for that phone number, in which you need to pass that token in the new_order call through a new parameter called "phone_token". With this, you also need to pass the PIN that the customer is going to insert in the checkout page through a parameter call "pin_number".