Alternative Payments
Support avatar
Written by Support
Updated over a week ago

July 27, 2016
Updated: May 5, 2021

To configure Alternative Payments into your CRM, you will go to Payments>Gateways, under ACTIONS select Add New Provider Profile.Select the type = Payment/Gateway and select Alternative from the drop down.Fill out the gateway parameters which are outlined below and click “Save”.

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 :


The checkboxes provided below need to be configured on your end according to the screen shot below.

Alternative Payments supports the following Payment Types:

  • SEPA

  • iDEAL

  • MisterCash 

  • POLi 

  • Przelewy24 

  • SafetyPay

  • Sofort_uberweisung 

  • Teleingreso 

  • TrustPay

  • Giropay

  • EPS  

  • BrazilPay Bank Transfer 

  • BrazilPay Boleto 

  • Bancário Verkkopankki

  • Ali Pay

  • Argen Card

  • Coinz

  • DirectPayEU

  • MyBank

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

*NOTE*- If you are creating orders with the payment type of BrazilPay Bank Transfer (TEF), you will need to pass the Document ID through the sepa_iban parameter and pass the Bank Code through the sepa_bic parameter.

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

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

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

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

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

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

Did this answer your question?