1.13.3 Adding payment providers


The Payments.config file, located in the main onlineshop directory, contains definition templates of all supported platforms. To enable one or more providers edit the file, enter the provider’s specific details and uncomment the relevant lines of the provider’s section. After saving the changes the IIS (web server) has to be restarted.

The example Payments.config file: Payments.config (todo)

All the supported payment gateways definitions are in the providers section. Each tag within it contains current configuration of the particular provider. The set of attributes will differ among providers and will be described later.

Some of the parameters are common for each provider and they include:

Default credit card provider

Each of the provider has its own type which is given during the implementation and describes the way how it integrates with the onlineshop. One of the type is CreditCardProvider, for example VS.PaymentProvider.CreditCardProviders.ElavonCardProvider

This type means that the provider supports credit cards payments and works in the “through an API” mode. Instead of redirecting the client to provider’s web panel the onlineshop communicates with the provider directly – server to server.

The client is presented with the payment form with the VUP where he has to fill his credit card details.

Some of the providers of this type can also be used with the autorecharge feature.

The onlineshop requires that only one provider of this type is set. To do so edit the CreditCardProvider section and put the name of the chosen provider in the providerName field:

Then, uncomment and configure the section describing the selected provider. Make sure that this is the only enabled provider of the VS.PaymentProvider.CreditCardProvider type.

Still, besides the credit card payments you can let clients select other methods as Paypal, CashU etc. even though some of them support credit card payments too.  

When client selects the credit card option the VUP’s payment form is shown as on the below picture.  

Providers

Below is the current list of supported providers. We keep expanding the list by adding new ones, usually on a request. If you would like to work with for example a local provider please contact us.

Allied Wallet Card

Support for the “through API” model. Storage of the credit card details on the provider’s side supported but not implemented in the onlineshop yet.

Online Back office configuration

Follow the instructions in email sent by Allied Wallet. In this process merchant ID and site ID required for Payments.config will be created.

Payments.config:

• merchantID - merchant ID provided by Allied Wallet (follow instructions in email sent by Allied Wallet to obtain this).
• siteID - site ID provided by Allied Wallet  (follow instructions in email sent by Allied Wallet to obtain this).

Allied Wallet

This provider uses redirection to own payment pages.

Online Back office configuration

Follow the instructions in email sent by Allied Wallet. In this process merchant ID and site ID required for Payments.config will be created.

Payments.config:

• merchantID - merchant ID provided by Allied Wallet
• siteID - site ID provided by Allied Wallet  
• itemName - item name on payment page on Allied Wallet servers (e.g. Account recharge).
• itemDescription - item description on payment page of Allied Wallet - e.g. Your account will be recharged
• allowedIPs - comma separated list of IPs that belong to Allied Wallet servers. Transaction can only be approved when the request with the transaction result comes from one of the IPs set here. 

Beanstream card

Support for the “through API” model.

Payments.config:

• currency - same as in the back office upper right corner
• merchantId - same as in the back office upper right corner

Note: This provider supports through API  model for credit card payments it needs the  CreditCardProvider to be enabled in Payments.config with  ProviderName  set as in the below example:

NMI

Payments.config:

apiKey - to obtain apiKey log in to NMI back office. Proceed to page Settings -> Security keys and copy the Default key

SagePay

Support for the “through API” model. Since this model does not allow for the 3D security this option must be disabled in the backoffice.

Onlineshop's server IP address must be added in the backoffice to allow payments.

Payments.config:

• vendor - vendor name used to log in to the backoffice.
• simulatorMode - set to 1 if vendor points to a simulator account. 

ACI Standard

Payments.config:

• tranPortalID/tranPortalPass - transaction id and password

Adyen

Log into Adyen backoffice  https://ca-test.adyen.com/ca/ca/login.shtml

To see which payment methods are enabled for your account check Settings -> Payment Methods in the CA interface.

To make a test payment follow these steps:

1. Select 'Skins' in the menu on the left after logging on to the CA interface
2. Select 'New' to create a new skin
3. Fill in a 'Description' for the skin
4. Fill in a 'HMAC Key for Test'. You can make up the value for the HMAC Key yourself.(for example "TESTSKIN_##$$##_TESTSKIN")
5. Fill in a "Result URLs" with back link to Onlineshop, like https://domain.com/Onlineshop/adyen.back (for old OnlineShops should be url like https://domain.com/Onlineshop/AdyenBack.aspx
6. Make sure that at least one Merchant Account is selected under 'Valid Accounts'
7. Press 'Create New Skin on Test' to create a new skin

Payments.config:

For tests you can use test cards: https://www.adyen.com/home/support/knowledgebase/implementation-articles.html?article=kb_imp_17

AliPay

Payments.config:

• userID - Unique ID for every AliPay merchant chosen by the merchant at the registration process.
• partner - Partner attribute given by AliPay
• key - Key attribute given by AliPay
• homeUrl - Url of the server, i.e.
  homeUrl="http://192.165.12.11"

Authorize.net

Go to merchant panel at Authorize.net. After logging in, open Account, then Settings menu and find API Login ID and Transaction Key link.

Authorize.net payment gateway can be set in a test mode (Test Mode option) which allows to submit test transactions. To operate in production mode just turn off the Test Mode option.

Payments.config:

Uncomment the section for the AuthorizeCardProvider

• loginID - API login ID
• transactionKey - transaction key from the merchant panel

If you want to allow autorecharge function set  canStoreData="1" in the CreditCardProvider section.

In this section put the AuthorizeCardProvider in the providerName field. There are also some other keys:

• allowCCDelete="1" in CreditCardProvider - allows the customer to remove saved cc data,
• storeCreditCardsLocally="0" in AuthorizeCardProvider - credit card detail can be stored locally or on Authorize.net servers. To store details on the Authorize.net servers the merchant needs to have Customer Information Manager enabled in his Authorize.net account.
• showAutoRechargeAmount - indicates if auto recharge functionality should be used

Auto recharge functionality handles situations when client account balance becomes low. In that case user account could be automatically recharged with selected amount.
To enable auto recharge functionality you have to:

• Set showAutoRechargeAmount attribute for CreditCardProvider to 1 by editing the Payments.config file. If mentioned attribute is not present it can be be added toCreditCardProvider;

If the auto recharge functionality is turned on, client can choose if he wants to use it while making payment with Authorize.net provider.

Barclay CPI ePDQ

http://www.barclaycard.co.uk/business/accepting-payments/epdq-cpi/

In the provider’s backoffice panel set the allowed URL to:

The post URL set as

You need to configure the ClientID, username and password (passphrase) which you receive from the provider in the Payments.config file.

• merchantName  - this name will be presented in the credit card payment form.
• clientID - same id as the one used to log to Barclay backoffice.
• passphrase - same as the passphrase set in Barclay backoffice. 
• currencyCode  - currency code from list below.

Currency codes:

CashU

Payments.config:

• merchantID - unique ID for every CashU merchant
• encryptionKeyword - keyword entered in the provider’s backoffice
• currency - currency of the transaction. The accepted values are USD, CSH, AED, EUR,JOD, EGP, SAR;
• language - interface language for the CashU payment page. The accepted values are en for English interface or ar for Arabic interface;
• displayText - "Payment for VoIP account/recharge." - This text is displayed on the CashU web page after client is redirected by onlineshop.
• servicesName - this is an advanced option, one merchant account can be used on different servers, in the CashU backoffice there is an option to enable multiple checkout where for each server the value from the field Service/Product should be the same as the servicesName, if there is single checkout that field should be left empty

In the backoffice, under the Payment Security menu set the following:

Return URL - link to the onlineshop CashBack.aspx, e.g.:

• Sorry URL – set the link to onlineshop CashUCancel.aspx with parameter cancel=1 , e.g.:

CrediMax

Payments.config:

• merchantName - the unique Merchant Id assigned by the CrediMax
• locale - specifies the language used on the provider’s web page
• accessCode - the access code provided by CrediMax
• secretCode - the secure secret code provided by the CrediMax

CyberSource

Payments.config:

• merchantID - the ID of the merchant given by the CyberSource provider;
• transactionKey - transaction Key generated in the CyberSource Business Center (Account Management->Transaction security keys->Security Keys for the SOAP Toolkit API).

Note: This provider is of the Credit Card Providers type and needs the CreditCardProvider section to be uncommented in the Payments.config with the ProviderName set to the CyberSourceCardProvider:

Dankort 

Payments.config:

• merchantID – the merchant’s unique id
• secretKey - secret key received from the provider
• ccardType - allowed types of credit cards. Set to 0 to allow all.
• currencyCode - currency ID (ISO4217) 208 indicates DKK.

Note: This provider is of the Credit Card Providers type and needs the CreditCardProvider section to be uncommented in the Payments.config with the ProviderName set to the DankortProvider:

• canStoreData - set "1" to store credit card data for future transactions, "0" to not store anything 
• dontShowCardCodeField - this should be set to "0" for this provider

DiamondWebPay

Payments.config:

• merchantId - the merchant ID  given by the DiamondBank
• currency - three-letter currency code to ISO 4217. Examples: GBP, EUR, USD, etc.

Doku

There is no configuration needed in the back-office. Parameters mallId and sharedKey should be delivered by the provider.

Payments.config:

Test credit card:

• Number: 5426400030108754
• CVV2: 869
• Exp: April 2016

Test DokuWallet:

• ID: 1644120706
• Password: DOKUwallet123

Elavon

Payments.config

<add name="ElavonCardProvider"

         type="VS.PaymentProvider.CreditCardProviders.ElavonCardProvider, VS.PaymentProvider"

         description="Pay with Elavon credit card."

         image="Elavon_85x38.gif"

         shortName="elavoncard"

         virtualMerchantID="xxxx"

         pin="xxxx"

         userID="xxxx"
/>

• virtualMerchantID - merchant ID provided by Elavon;
• pin - merchant PIN provided by Elavon;
• userID - merchant user ID;

Note: This provider is of the Credit Card Providers type and needs the CreditCardProvider section to be uncommented in the Payments.config with the ProviderName set to the ElavonCardProvider:

<add name="CreditCardProvider"

         type="VS.PaymentProvider.CreditCardProvider, VS.PaymentProvider"

         description="Pay using credit card."

         enable="1"

         shortName="creditcard"

         providerName="ElavonCardProvider"

/>

ENets

Payments.config:

<add name="EnetsProvider"

         type="VS.PaymentProvider.EnetsProvider, VS.PaymentProvider"

         description="Make payment with ENets."

         enable="1"

         image="enets.gif"

         shortName="ENets"

         merchantID="xx"
/>

• merchantID – merchant ID from eNets

Envoy

Payments.config:

EPay

The backoffice URL: https://ssl.ditonlinebetalingssystem.dk/admin/login.asp

You can turn the test mode on only in the backoffice (not in Payments.config file)

Payments.config:

EWallet

In the provider’s backoffice configure the redirect and callback urls. Both should point to the same URL:

Payments.config

<add name="EWalletProvider"

         type="VS.PaymentProvider.EWalletProvider, VS.PaymentProvider"

         description="Make payments with Unaico eWallet Payment System!"

         enable="1"

         image="Ewallet.png"

         shortName="EWallet"

         merchantId=""

         secretKey=""

         webServiceUsername=""

         webServiceSecretKey=""

         itemDescription="Custom text describing for what user account was charged."

         currency="EUR"

         country="PL"
/>

• merchantId - merchant id provided by Unaico
• currency - currency symbol used in payments
• secretKey - password provided by Unaico
• webServiceUsername - login to Unaico web service
• webServiceSecretKey - password to Unaico web service
• itemDescription - this text will be displayed to the user on the Unaico payment page

FirstData

To install the client certificate the steps presented in paragraph number 22 (page 97) of provider documentation have to be executed.

The certificate can be installed through the command line. If you are in the directory where the certificate file WS100xxxxxxx._.1.p12 is placed run the following command:

where xxxxxxx is the number of the certificate and yyyyyyyyyy is the certificate password.

Payments.config:

• certificatePath - this field contains path and filename of the digital certificate (or PEM file) issued for a given store;
• webServiceLogin - login to the web service specified in the following format WS<store_ID>._.1
• webServicePassword - password to the web service stored in the WS<store_ID>._.1.auth.txt file.

Note: This provider is of the Credit Card Providers type and needs the CreditCardProvider section to be uncommented in the Payments.config with the ProviderName set to the FirstDataCardProvider:

If the FirstData certificate is expired you will get the following error:

iDeal TODO DODAC OBRAZKI http://docs.voipswitch.com:18081/display/doc/iDeal+Provider

Log in to the merchant backoffice  https://i-kassa.rabobank.nl/ . Next step is to open Configuration->Technical information and set the following:

• set up the settings as in figure 1 - Global transaction parameters and 2 - Global security parameters;
• in the Data and origin verification set two links separated with semicolon (Fig. 3)
  http://domain/OnlineShop/Pay.aspx;http://domain/OnlineShop/Pay.aspx?process=true;

• set a password in the Pass phrase field
• Transaction feedback (Fig. 4 and 5) - here check the first checkbox I want to receive transaction feedback parameters on the redirection URLs then in the section Security for request parameters put the password that you set  in the Pass Phrase.

Payments.config:

• pspid - login to account
• passPhrase - password (set in Data and origin verification)
• language - should be set in following format: languagecode_countrycode ie. nl_NL

Example

<add name="IDealProvider"

         type="VS.PaymentProvider.IDealProvider, VS.PaymentProvider"

         description="Make payments with Rabo iDeal Payment System\!"

         enable="1"

         testMode="1"

         image="iDeal.gif"

         shortName="IDeal"

         pspid="arxxxxxxx"

         passPhrase="voipTesxxxx"

         currency="EUR"

         language="en_US "
/>

Internet Secure Provider

Payments.config:

<add name="InternetSecureProvider"

     type="VS.PaymentProvider.CreditCardProviders.InternetSecureProvider, VS.PaymentProvider"

     description="Pay with Internet Secure credit card."

     image="isecure.gif"

     shortName="isecure"

     gatewayID="xxxx"

     currency="xxx"
/>

• gatewayID - unique number associated with the merchant account;
• currency – the currency symbol (ISO).

Note: This provider is of the Credit Card Providers type and needs the CreditCardProvider section to be uncommented in the Payments.config with the ProviderName set to the InternetSecureProvider:

<add name="CreditCardProvider"

     type="VS.PaymentProvider.CreditCardProvider, VS.PaymentProvider"

     description="Pay using credit card."

     enable="1"

     shortName="creditcard"

     providerName="InternetSecureProvider"

/>

JCC

Payments.config:   

<add name="JCCProvider"

        type="VS.PaymentProvider.JCCProvider, VS.PaymentProvider"

        description="Make payments with JCC Payment Systems!"

        enable="1"

        image="JCC.jpg"

        shortName="JCC"

        merchantId="11111"

        acquirerId="402971"

        password="XXXXX"

        currency="978"

        currencyDigits="2"

        country="PL"

 />

• merchantId- merchant ID provided by JCC.
• acquirerId- acquirer ID provided by JCC.
• password - password provided by JCC.
• currency - code of the currency - ISO 4217.
• currencyDigits - Number of digits for the currency.

LiqPay

Payments.config:

<add name="LiqPayProvider"

         type="VS.PaymentProvider.LiqPayProvider, VS.PaymentProvider"

         description="Make payment with LiqPay."

         enable="0"

         image="Liqpay.gif"

         shortName="liqpay"

         merchantID=""

         merchantPassword=""

         currency=""

/>

• merchantID - LiqPay merchant ID.
• merchantPassword - LiqPay merchant password

LPG

Payments.config:

• merchantId - merchant ID provided by LPG;
• terminalId - terminal ID provided by LPG;
• terminalPass - terminal password provided by LPG;

Moneris

Payments.config:

• storeId - ID of the store given by the Moneris provider;
• apiToken - the ApiToken value, given by Moneris;

Note: This provider is of the Credit Card Providers type and needs the CreditCardProvider section to be uncommented in the Payments.config with the ProviderName set to the MonerisCardProvider:

dontShowCardCodeField - Moneris account can be configured not to check CVV code. In this case, this parameter should be '1'. Otherwise, type 0, or omit it.

Moneybookers

Go to merchant tools from "My account" menu to enable Automated Payment Interface and Merchant Query Interface.
For security reasons limit access to Automated Payment Interface and Merchant Query Interface only to IP of your server.

Set API/MQI Password. This is the password that will be used in the Payments.config.

Payments.config:

<add name="MoneyBookersProvider"

     type="VS.PaymentProvider.MoneyBookersProvider, VS.PaymentProvider"

     description="Make payment with MoneyBookers"

     enable="1"

     image="Moneybooker_100x38.gif"

     merchantDescription="SuperVOIP Service\!"

     shortName="moneybookers"

     userEmail="xxxxxxxx"

     password="xxxxxx"

     language="PL"

     currency="USD"

/>

• userEmail - e-mail address of the merchant's moneybookers.com account;
• password - API/MQI password entered  in the Merchant Tools section of the merchant's online Moneybookers account;
• merchantDescription - a description of the recipient, which will be shown on the merchant gateway;
• language - 2-letter code of the language used for Moneybookers' pages. Can be any of EN, DE, ES, FR, IT, PL, GR RO, RU, TR, CN, CZ or NL;

Paradata

Payments.config:

• accountToken - merchant account token;

Note: This provider is of the Credit Card Providers type and needs the CreditCardProvider section to be uncommented in the Payments.config with the ProviderName set to the ParadataCardProvider:

PayGate

Payments.config:

<add name="PayGateProvider"

         type="VS.PaymentProvider.PayGateProvider, VS.PaymentProvider"

         description="Pay with PayGate"

         enable="1"

         testMode="0"

         shortName="paygate"

         image="PayGate.jpg"

         payGateId=""

         payGatePassword=""

         currency="ZAR"

/>

• payGateId - ID of the store given by the PayGate;
• payGatePassword - password given by PayGate;
• currency - currency used in payments. PayGate supports only ZAR (South African Rand)

Paypal PayFlow Pro

Payments.config:

• partner - partner name provided by Paypal;
• merchantLogin - merchant login provided by Paypal;
• user - API Username value provided by PayPal. Important: The API username is different than account name
• password - API password given by PayPal;
• performAVScheck - it enables the AVS check which checks the address and other details
• currency - three letter currency code. Website Payments Pro does not support all currencies. For list of supported currencies, visit PayPal website.

Note: This provider is of the Credit Card Providers type and needs the CreditCardProvider section to be uncommented in the Payments.config with the ProviderName set to the PayPalPayFlowProProvider:

PayPal Standard

In the Paypal’s backoffice set the following:

• Auto Return - must be switched to On
• Return URL -  set the your onlineshop URL  http://IP_or_domain/OnlineShop/PayPal.notify 
• Payment Data Transfer - should be switched on
• Block Non-encrypted Website Payment – set to off to accept Non-Encrypted payments

Set the notification (IPN) URL. Select Instant Payment Notification preferences in the Profile and set the URL to

Note: Paypal IPN System works only on standard ports: 80 or SSL port 443.

Payments.config:

• businessEmail - mail used to log to paypal.com;
• currency- default currency, possible values are: AUD, CAD, CHF, CZK, DKK, EUR, GBP, HKD, HUF, JPY, NOK, NZD, PLN, SEK, SGD, USD;
• country - default language used for customers.

Example

<add name="PayPalStandardProvider"

      type="VS.PaymentProvider.PayPalStandardProvider, VS.PaymentProvider"

      description="Make payments with PayPal - it's fast, free and secure!"

      enable="1"

      testMode="0"

      image="PayPal_60x38.gif"

      businessEmail="PayPal@example.com"

      currency="EUR"

      logo=""

      country="PL"

      manualCapture="0"

      allowedIPs=""

      includeTax="0"

/>

Paypal Website Payments Pro

Payments.config:

• username - API Username value provided by PayPal. Important: The API username is different than account name
• password - API password given by PayPal;
• signature - signature given by PayPal;
• currency - three letter currency code. Website Payments Pro does not support all currencies. For list of supported currencies, visit PayPal website

Note: This provider is of the Credit Card Providers type and needs the CreditCardProvider section to be uncommented in the Payments.config with the ProviderName set to the PayPalWebsiteProProvider:

Note: when "testMode" attribute set to "1", the Paypal system uses "Sandbox" to process payments. 
For testing purposes, log in to PayPal sandbox, to obtain the test API credentials and the test credit card details.

Przelewy24

Configuration in Payments.config:

<add name="Przelewy24Provider"

         type="VS.PaymentProvider.Przelewy24Provider, VS.PaymentProvider"

         description="Przelewy24 - Bezpieczne Transakcje Internetowe"

         enable="0"

         image="Przelewy24_100x38.gif"

         shortName="przelewy24"

         clientID=""

         language="pl"

         feePercentage="0.1"

         feeBase="0.01"

/>

• feeBase - static amount subtracted from payment value
• feePercentage - percentage value of substracted amount
• clientID - id of client provided by przelewy24

Saferpay

Payments.config:

• accountID - unique account ID from the provider
• currency - specifies the transaction currency with a ISO 4217 currency code;
• language - specifies the language for the Virtual Terminal session. Possible values are "en" (English), "de" (German), "fr" (French) and "it" (Italian);
• settingsPath - physical path to the location where configuration generated by the Saferpay Apllication Compoment is stored.

Saferpay Application Component has to be installed  on the merchant's web server where onlineshop is located. The component creates and signs digital offers and verifies confirmation messages received from the Virtual Terminal. This software is delivered by Saferpay. During configuration process certificates needed for signing transactions are created. They should be stored in the path set in the Payments.config file in the settingsPath parameter

Most common error that can be seen in log files is "No Safer Pay software installed". It may be caused by the Saferpay Application Component not being installed or configuration is not stored at the location set in the settingsPath.

SagePay

Payments.config:

• vendorName - the vendorName given by the SagePay;
• vendorEmail - the email used for sending emails after transactions (if enabled in the backoffice)
• currency - three-letter currency code - ISO 4217. Examples: GBP, EUR and USD

Sentry

Payments.config:

• currency - code of the currency - ISO 4217.
• feeBase - amount subtracted from payment value
• feePercentage - percentage value of the subtracted amount
• merID/acqID/merchantPassword - id and password provided by Sentry

Setefi

Payments.config:

• terminalId - ID given to the merchant at the registration process;
• currency – currency symbol in ISO

After installation a library file e24PaymentPipe.dll has to be registered through the command line:

This file should be provided by Setefi.

Seylan

Payments.config:

• currencyCode - ISO code of the currency. 356 for indian rupee
• merchantID-  merchant ID given by Seylan
• pgInstanceId - PG Instance ID given by Seylan
• hashKey - HashKey given by Seylan.

Three last parameters are to be obtained from the Seylan merchant console.

USePay  

The backoffice URL: https://secure.usaepay.com/login (SandBox: https://sandbox.usaepay.com/login)

1. Click Settings - Source Keys - Add Source
2. Fulfill fields which are marked as red below:
3. Add Name and uncheck 'Disabled' in 'Source Info' section
4. Check 'Sale' in 'Allowed Commands  section
5. Choose payment methods which do you want to use in 'Payments Methods' section
6. You can also set which credit card fields should be required in 'Required Fields' section
7. You can also restrict from which IPs USAepay API can be reached in 'Allowed IPs' section 

Payments.config:

WebPay

A provider for Nigeria from Interswitch.

Payments.config:

• productId - provided by Interswitch
• payItemId - provided by Interswitch
• macKey - provided by Interswitch

WorldPay 

The backoffice URL: https://secure.worldpay.com/sso/public/auth/login.html?serviceIdentifier=merchantadmin&languageCode=en&countryCode=GB

Payments.config:

Full logs

For each provider you can set the fullLogs attribute in order to enable detailed logging of all transactions done through that particular provider:

Custom amounts

If, for a particular provider, you want to define charge amounts different than the global ones set in the VSM, you can use customAmounts attribute.

The custom amounts override the charge amounts defined in the VSM.

The amounts should be separated by semicolons. After the amounts should follow the vertical bar sign and then the descriptions, also separated by semicolon: (AMOUNT1;AMOUNT2;AMOUNT3|DESCRIPTION1;DESCRIPTION2;DESCRIPTION3)

The descriptions are shown to clients, the associated amounts are sent in the payment request to the onlineshop.

Currencies

For each provider a currency can be set by adding the following key:

transactionCurrency="EUR"

where EUR is the ISO code of the currency

<add name="PayPalStandardProvider"

       type="VS.PaymentProvider.PayPalStandardProvider, VS.PaymentProvider"

       description="Make payments with PayPal - it's fast, free and secure!"

       enable="1"

       testMode="0"

       image="PayPal_60x38.gif"

       shortName="PayPal"

       businessEmail="paypal@testemail.com"

       token="test-token"

       currency="USD"

       transactionCurrency="USD"

       country="US"
/>

If transactionCurrency is set and is different from the main system currency, the payment is calculated based on the currency ratio configured in the VSM Settings/Billing/Currencies menu. If the client currency is different than the main billing currency (USD), the amount is recalculated using the ratio for the client currency.

• currency - defined in payment provider specific format. It may be standard ISO 4217 alphabetic code (i.e. EUR), numer code (i.e. 978) or any custom format like "01" or "dollar". The default format is ISO 4217 alphabetic code. The currency parameter is required. 
• transactionCurrency defined always in the ISO 4217 alphabetic code (i.e. EUR). It must be the same currency as in the "currency" parameter. Only the format may be different (i.e. currency="978" and transactionCurrency="EUR", currency="001" and transactionCurrency="USD"). This parameter is required. If it is left empty or not present, the default currency from the database is set as the currency of the transaction. This may lead to amount calculation errors if client accounts have different currencies.

Transaction fee

Some providers use transaction fees for online payment. This setting allow to deduct this cost from the transaction amount before crediting the client balance.
A transaction fee can be expressed as a percentage of the charged amount, as a fixed fee or both of these parameters used at the same time.

To configure a transaction fee for a particular payment gateway add the following parameters:

• feeBase - fixed amount
• feePercentage - percentage value of the charge amount

Both parameters are optional.

After a successful transaction the recharge amount to be added to the client balance will be calculated as follows:

ChargedAmount - (feePercentage*ChargedAmount) - feeBase = AddedAmount

Example:

feeBase = €0.5
feePercentage = 0.02 (fee 2%)
TransferedAmount = €10

Calculations:
AddedAmount: 10 - (0.02*10) - 0.5 = €9.3

VAT

The onlineshop implements VAT charging for US and Canada top-ups through SureTax provider. The transaction value is sent to SureTax API. In response the onlineshop gets the VAT amount which is then added to the transaction value and processed further to the payment provider. The client is charged the increased amount however the amount credited to his account is the original transaction’s value, before adding VAT.

The VAT charging feature can be enabled in the AppSettings.config, by default it is disabled. Also you need to have an account with SureTax.

SystemProviders

A separate xml section is for the internal payment methods which include:

• user to user balance transfer
• voucher payment

Example:

By default the system providers are disabled, uncomment to enable the service (remember about restarting the web server).

External providers

This section is intended for a special type of payment providers which process payments directly with customer and top up the client account on voipswitch through onlineshop API. They are usually a systems that accept cash or other forms of direct payments, typically in convenience shops where customers can come and top up the account.

SmartPit Provider

In the SmartPit implementation the CSAS server (on the SmartPit side) sends requests to the onlineshop. A request contains the following fields:

• CORP_ID : Corporate ID : ID for OEM resellers.
• CUSTOMER_INFO : Customer Information : client id from voipswitch.clientshared table
• CARD_NO : Smartpit Card Number
• INCOME_PRICE :  Recharge amount
• TAX : Tax : Tax amount - 6 digits.
• SHOP_NAME : Name of convenience store where customer recharged. Haxadecimaly decoded.
• INCOME_DATE : Recharge date - 14 digits. ( yyyyMMddhhmmss )

The response body:

where STATUS is integer with possible values:

• 0 - success
• 1 - failure

The onlineshop URLs in the CSASAdmin backoffice should be set to:

http://HOST/OnlineShop/,SmartPitPaid.aspx,SmartPitDuplicate.aspx,SmartPitCancel.aspx