Defining Product Promotions
Please wait while you are redirected ....
![]() |
is added when reseller has a customer specific business
Please wait while you are redirected ....
As a Reseller, you need to take the following steps in order to start selling Digital Certificate Product to your Customers and Sub-Resellers.
Signup for the Digital Certificate Product. See details
Set your Selling Price for the Digital Certificate Product for your Customers and Sub-Resellers. See details
Understanding Tax and how you may use the Tax Engine to collect it from your Customers and Sub-Resellers. See details
Following are the steps you need to take within your Control Panel to setup your Domain Registration
Product for your Customers and Sub-Resellers:
Select which TLDs you want to
sell. See details
Set your Selling Price for different TLDs that you are
selling. See details
Specify your Default Settings for the Domain Names Service: You may specify which Name Servers are
pre-filled every time your Customers register a domain
name. See details
Understanding Tax and how you may use the Tax Engine to collect it from your Customers and
Sub-Resellers. See details
If you choose to integrate the domain name registration buy process with your website using our API Kit, then you need to
ensure that you display the Registrar Registrant Agreement for Domain Names Legal document within the
domain name registration buy process on your website.
It is compulsory to display this document as is to your Customers and get them to agree to the terms mentioned
therein, before buying domain names through you. You can view this agreement from within your
Reseller Control Panel by going to Help -> Legal Agreements
in the Menu.
There may be cases when Payment or Add Funds transactions performed by your Customers / Sub-Resellers through a Payment Gateway integrated by you, within your Reseller Control Panel, get stuck at the AuthStarted status. You need to review such transactions and Approve / Decline them manually.
However, if such transactions continue to remain unattended over 45 days, the system would automatically fail them and set the status of these transactions as FailedByCron.
The system has the built-in ability to allow you to integrate any Payment Gateway to allow your Customers / Sub-Resellers to pay you. Obviously every commercial
Payment Gateway has a different integration process. There is no way to build a generic module that can directly talk to any Payment Gateway. Instead, what we have done is, built
a module that can pass parameters to an intermediate bridge on your server, that you can then integrate with any Payment Gateway of your choice.
The logic of the flow in this integration is quite simple:
Any Customer / Sub-Reseller of yours needs to pay you money and selects a Payment Gateway to do so.
We simply create a collection of messages that you will need to charge this Customer / Sub-Reseller. This set of messages would contain things like Order Information, Amount etc. We then redirect
the Customer to your Server with this set of messages.
You then charge the Customer / Sub-Reseller using these messages, and your Payment Gateway.
You then redirect the Customer back to our Server with a status of the transaction as to whether you have successfully charged the Customer / Sub-Reseller.
Once this is done we Add these funds to the Customer / Sub-Reseller account, and/or process any associated Orders.
This interaction can be diagrammatically represented as follows -

Let us break down the process you need to carry out in order to complete integrating your Payment Gateway with our system.
You will need the following before you begin integrating your Payment Gateway with the System:
Details on the process of integrating with your Payment Gateway
Server space on your server
Download the appropriate integration kit from the below list depending on what your Server supports for the integration
ASP Integration Kit version 3.0 (last updated on 10th March, 2008)
JSP Integration Kit version 3.0 (last updated on 10th March, 2008)
PHP Integration Kit version 4.0 (for PHP version > = 5.2.0) (last updated on 7th August, 2014)
If you have downloaded any of the Payment Gateway Kits prior to 25th August, 2006, then it is recommended that you upgrade to the latest version with
MD5 Checksum Algorithm, by following the two step process listed below:
Step 1: Upgrade your Payment Gateway Integration Kit:
ASP Integration Kit: If you have already integrated this Kit with your website, then you need to simply download
the ASP Integration Kit version 3.0 and extract the functions.asp file. Then, replace the old file that you have uploaded on your server with this
new functions.asp file.
JSP Integration Kit: If you have already integrated this Kit with your website, then you need to download the
JSP Integration Kit version 3.0 and extract the functions.jsp file. Then, upload this new functions.jsp file on your server and make the
following modifications to your paymentpage.jsp and postpayment.jsp:
Modifications to paymentpage.jsp
Replace the below code from your paymentpage.jsp:
Replace the above code in your paymentpage.jsp with:
Enclose all occurances of verifyChecksum function call within a try-catch block.
Modifications to postpayment.jsp:
Replace the below code from your postpayment.jsp -
Replace the above code in your postpayment.jspwith:
Enclose all occurances of generateChecksum function call within a try-catch block.
PHP Integration Kit: If you have already integrated this Kit with your website, then you need to simply
download the PHP Integration Kit version 4.0 and extract the functions.php file. Then replace the old file that you have uploaded on your server
with this new functions.php file.
Step 2: Select the correct Checksum Algorithm within your Reseller Control Panel:
Login to your Reseller Control Panel. See details
In the Menu, point to Settings -> Finance and Billing -> Payment Gateway and click List / Add.
Click the Manage button next to the Custom Payment Gateway that you are upgrading.
Select the Checksum Algorithm as MD5 and save your changes by clicking Submit.
Next, you need to Add your Payment Gateway to our system.
You can Add or Modify your current/preferred Payment Gateway within your Reseller account by following the steps given below:
Login to your Reseller Control Panel. See details
In the Menu, point to Settings -> Finance and Billing -> Payment Gateway and click List / Add.
Click the Add a Gateway link.
Click the Add any other Payment Gateway link.
Enter the following details and save your changes by clicking Submit:
Gateway Name: This is the heading for your Payment Gateway and it will be displayed to your Customers / Sub-Resellers
on the Payment page within a dropdown of options. A typical heading could be VISA/MasterCard/AMEX in order to signify that your Customer / Sub-Reseller can pay using those modes
if they select this particular option.
Gateway URL: This is the URL on your server to which we will redirect the Customer / Sub-Reseller. This is explained in detail
further ahead. Currently, simply fill in some URL. We will change this later to the correct URL.
Payment Gateway Access Level for Customers / Sub-Resellers: Select appropriate Access Levels for your Customers / Sub-Resellers.
Payment Gateway Transaction types and Access Levels for your Customers / Sub-Resellers
Send me a Reminder if a transaction is pending for more than x days: In case you have not yet accepted a payment sent to you via
this Payment Gateway, you can get e-mail reminders sent to you daily after x number of days from the payment date, until you either Approve or Decline these payments.
Display Position: If you plan on adding multiple Payment Gateways you can select the position in which you wish to display this
Gateway on your Payment Page.
Checksum Algorithm: Select MD5 if you have downloaded the latest Integration Kit (version 2 or above) or have followed
the upgrade instructions listed in Step 1. Select Addler 32 only if you are still using an older kit and haven't yet upgraded.
On your own server, upload the corresponding files from the integration kit you downloaded. We will use the PHP Kit as an example in this document. You will typically have
the following files:
paymentpage.php: This is the page that we will redirect your Customer / Sub-Reseller to. From this page, you need to collect the data we send and use the data to charge your
Customer / Sub-Reseller. After you have charged the Customer / Sub-Reseller you will then redirect the Customer / Sub-Reseller to postpayment.php.
postpayment.php: This page simply redirects your Customer back to our Server after you have charged him, with appropriate variables required by our Server.
functions.php: This is just a functions file used by the other pages for certain calculations.
Both the paymentpage.php and the postpayment.php pages contain a variable called KEY. For instance, in the above two files you will find a line as follows:
$key = "eF9dmG8288OFd9pzzTeHJ3mNvR26xN"; //replace ur 32 bit secure key , Get your secure key from your Reseller Control panel
You need to replace this value in both the files with the KEY we generated for you at the time of adding the Gateway. You can check it from the
Settings -> Finance and Billing -> Payment Gateway -> List / Add section by clicking the Payment Gateway that you added.
If at anytime you feel that you may have compromised the security of this Key, you can regenerate a new one from this section by clicking the Generate Key button. You will
then have to replace the New Key in your
code.
You will now need to set the Gateway URL which we skipped earlier while adding the Gateway. The Gateway URL is the full https:// URL that will be used to access
the paymentpage.php on your server. So a typical Gateway URL would look like "https://www.yourserver.com/paymentpage.php".
Visit the Settings -> Finance and Billing -> Payment Gateway -> List / Add section within your Reseller Control
Panel and click the Manage button next to the Payment Gateway you added. Click the Modify button and enter the Gateway URL as described above. Make sure the URL is entered complete with the "https://" or "https://" all
the way up to the name of the page. DO NOT pass any Parameters to the URL.
CORRECT GATEWAY URL:
https://www.yourserver.com/paymentpage.php
WRONG GATEWAY URLS:
www.yourserver.com/paymentpage.php
https://www.yourserver.com/paymentpage.php?someparam=something
You are now ready to test your integration and verify that it works. Follow the steps below to Test your Integration:
Login to your Reseller Control Panel. See details
In the Menu, point to Settings -> Finance and Billing -> Payment Gateway and click List / Add.
Click the Manage button next to the Payment Gateway you added.
Click Test for Add Funds or Test for Payment, depending upon the type of transaction you wish to test.
This will popup a new window to redirect you to the Gateway URL you had specified, while passing it the following parameters in a GET request.
| Parameter KEY | Type | Description |
|---|---|---|
|
paymenttypeid |
integer |
This is the Id assigned to your Payment Gateway. You can see it in the Payment Gateway Detailed View. |
|
transid |
string |
This refers to a unique transaction ID which we |
|
userid |
integer |
This is the ID of the Customer / Sub-Reseller who is |
|
usertype |
string |
This refers to the type of user performing this |
|
transactiontype |
string |
This refers to the type of transaction taking ResellerPayment, CustomerPayment Additional Information
Payment Gateway Transaction types and Access Levels for your Customers / Sub-Resellers |
|
invoiceids |
string |
This refers to the Comma-Separated list of Invoice or CustomerPayment. |
|
debitnoteids |
string |
This refers to the Comma-Separated list of Debit |
|
description |
string |
This refers to the delimiter-separated Text |
|
sellingcurrencyamount |
numeric (up to 3 decimal points) |
This refers to the amount of transaction in your |
|
accountingcurrencyamount |
numeric (up to 3 decimal points) |
This refers to the amount of transaction in your |
|
redirecturl |
string |
This is the URL on our server, to which you need to |
|
checksum |
string |
This refers to a Random Alpha-Numeric String generated using a Mathematical Algorithm (a complex quadratic equation) to ensure that data is not tampered |
Besides, we also pass the following details which allow you to pre-fill the Customer's / Sub-Reseller's details on the Payment Gateway page:
| Parameter KEY | Type | Description |
|---|---|---|
|
name |
string |
This will pass the Customers / Sub-Resellers Name. |
|
company |
string |
This will pass the Customers / Sub-Resellers Company Name. |
|
emailAddr |
string |
This will pass the Customers / Sub-Resellers Email Address. |
|
address1 |
string |
This will be the first line of the Address. |
|
address2 |
string |
This will be the second line of the Address. |
|
address3 |
string |
This will be the third line of the Address. |
|
city |
string |
The Customer's / Sub-Reseller's city |
|
state |
string |
The Customer's / Sub-Reseller's state |
|
country |
string |
The Customer's / Sub-Reseller's Country |
|
zip |
string |
The Customer's / Sub-Reseller's zip |
|
telNoCc |
string |
The Country code of the telephone number of the Customer / Sub-Reseller. |
|
telNo |
string |
The telephone number of the Customer / Sub-Reseller |
|
faxNoCc |
string |
The Country code of the fax number of the Customer / Sub-Reseller. |
|
faxNo |
string |
The fax number of the Customer / Sub-Reseller |
|
resellerEmail |
string |
This will pass your Reseller Email Address |
|
resellerURL |
string |
This will pass your Reseller Branded URL - http://account.techzoneindia.com |
|
resellerCompanyName |
string |
This will pass your Reseller Company Name |
These variables can directly be accessed in the paymentpage.php. If all goes well, then clicking the Test PG Integration button you should see the
following output on your browser in a separate window:
File:
paymentpage.php
Checksum Verification ........ Verified
List of Variables Received as follows
paymenttypeid: 202
transid: 1120
userid: 1
usertype: Customer
transactiontype: CustomerAddFund
invoiceids:
debitnoteids:
description:
sellingcurrencyamount: 5
accountingcurrencyamount: 10
redirecturl:
http://account.techzoneindia.com/servlet/TestCustomPaymentAuthCompletedServlet
address1 = 213 Main St.
company = My Solutions
address2 = null
zip = 17541
name = Customer Name
city = NYC
telNoCc = 1
country = US
telNo = 45784126
emailAddr = [email protected]
address3 = null
state = NY
faxNoCc = null
faxNo = null
checksum: 8cd2a658d2de2c995fc790b66a508ec3
We will stop here right now. If you get the above output in your browser window then you have perfectly followed the steps so far.
If you get any of the following results instead then you can appropriately refer back to see if you have correctly set the following data:
| Result | Possible Solution |
|---|---|
|
ERROR: Checksum Mismatch |
This can only happen if the key you used is incorrect. Open the paymentpage.php file and verify that the value of the Key is exactly the same as the Key displayed in your |
|
Page Not Found/Displayed |
If no page is found or displayed then the URL could be incorrect. Verify that the URL in the browser window is the correct path to your Payment Page on your Server. Verify that |
|
Other Possible Issues |
Verify that variables passed to your script through the GET method are working appropriately and your web server supports the same. |
If you do not get this output then you should revert back and check if you have properly inserted your key in the paymentpage.php file, and that the Gateway URL is properly set.
Make sure you proceed ahead only after you get the above output for your specific integration kit.
Let us try and understand what we have achieved so far. Basically a set of parameters are passed from our Server to your Server, along with a checksum. If you open your corresponding
paymentpage.php page you will see the following code in it -
if(verifyChecksum($paymenttypeid, $transid, $userid, $usertype, $transactiontype, $sellingcurrencyamount, $accountingcurrencyamount, $key, $checksum))
{
// YOUR CODE GOES HERE
}
else
{
echo "ERROR: Checksum Mismatch";
}
Similar code will exist in the ASP and JSP integration kits. Your goal is to simply put your code inside the braces of the Verify Checksum. Within these braces you will put in code to
register these variables in a session, or put them in your local database and then proceed ahead with charging your Customer.
The VerifyChecksum function simply validates that the data you have received is valid and is sent by OUR SERVER. If the VerifyChecksum function, fails then you must
not
proceed with the transaction.
It is imperative that you test your integration so far, by clicking both the Test for Add Funds and Test for Payment buttons, before continuing
to integrate your website with your Payment Gateway provider.
You have now successfully achieved the integration steps up to sending the Customer / Sub-Reseller to your server. You now need to charge this Customer / Sub-Reseller. At
this stage you have the list of variables that were passed to you in the paymentpage.php. It is recommended that you either store these variables in some local database of
yours or store them in a session, before proceeding ahead, so that you can access these variable values at the time of sending the Customer / Sub-Reseller back after charging him. Storing
these is explained in the previous section. After doing so, you must charge this Customer / Sub-Reseller. In doing so, the following values are important for you:
|
sellingcurrencyamount |
numeric (up to 3 decimal points) |
This refers to the amount of transaction in your |
|
accountingcurrencyamount |
numeric (up to 3 decimal points) |
This refers to the amount of transaction in your |
The above amounts are the amounts you need to charge your Customer / Sub-Reseller. If your Payment Gateway Currency is the same as any of the above you may freely use one
of the above values. If on the other hand the Currency your Gateway uses is different you will need to put in code to convert the amount we send to the amount you wish to charge.
Once you have finished charging your Customer / Sub-Reseller you will need to then send the Customer / Sub-Reseller back to our Server along with the status of the transaction, in order
to allow us to Add those Funds to his account and process any associated Orders.
You have now finished the steps required to charge your Customer / Sub-Reseller. You will then send the Customer / Sub-Reseller back to our Server. You will use the
redirecturl parameter that was sent to your Gateway URL for this transaction to pass the Customer / Sub-Reseller back to our server.
You will pass the following parameters to the redirecturl in a POST request:
| Parameter KEY | Type | Description |
|---|---|---|
|
transid |
string |
Pass the same transid which was passed to your Gateway URL at the beginning of the transaction. |
|
status |
character |
This can be either Y or N or P. A Y signifies that the Transaction went through successfully and that the amount has |
|
rkey |
numeric |
This refers to a random numeric key that you must generate and pass when redirecting the User from your side to our Server. We have included sample code which generates |
|
checksum |
string |
This refers to a Random Alpha-Numeric String generated using a Mathematical Algorithm (a complex quadratic equation) to ensure that data is not tampered along the way. A |
|
sellingamount |
numeric (upto 3 decimal points) |
This value must be greater than 0 and less than or equal to the original sellingcurrencyamount we sent to your paymentpage.php. This value MUST be passed, but |
|
accountingamount |
numeric (upto 3 decimal points) |
This value must be greater than '0' and less than or equal to the original accountingcurrencyamount we sent to your paymentpage.php. This value MUST be passed, but is only |
The sample code for achieving the above process successfully is shown in the postpayment.php file. You simply need to copy this code in the file in which you do your
Payment Processing. This page retrieves the transid and redirecturl from the session and expects a status to be available to it in
the session. A simple inspection of the code in postpayment.php will give you an idea of the right way to redirect your Customer / Sub-Reseller to our server.
Explanation of sellingamount and accountingamount fields
In the above table two important fields are the sellingamount and accountingamount. These fields MUST be passed, but are used
only if the transactiontype is CustomerAddFund or ResellerAddFund.
Payment Gateway Transaction types and Access Levels for your Customers / Sub-Resellers
For every transaction performed through the Payment Gateway, a Receipt is created in the Customer / Sub-Reseller account.
The amount of the Receipt created incase of transactiontype CustomerAddFund or ResellerAddFund is dependant on this figure. The Receipt amount will be
equivalent to the figure you send us for both these values. The reason for allowing you to send us these values is to allow you to deduct any Credit Card Processing charges for Advance
Payments made by your Customers / Sub-Resellers in their account.
Lets take an example of an Add Funds transaction performed by your Sub-Reseller -
Sub-Reseller A
Your Selling Currency: USD
Your Accounting Currency: INR
Conversion Rate: 50
Amount to add in USD: 100
Amount to add in INR: 5000
When this Sub-Reseller leaves our system and comes to your paymentpage.php, we will send along the two amounts i.e. USD 100, INR 5000, to allow you to charge his card with an
equivalent amount. After the transaction is completed, you will send the Sub-Reseller back to our system with a sellingamount and accountingamount figure. We will then
credit that amount to his account. You may choose to send the same figures we sent to you, thus crediting the Sub-Reseller with the exact amount that was charged to him/her. Alternatively,
you may choose to deduct a certain processing amount for Credit Card Transactions and send a reduced amount. Thus you could have the below two scenarios.
Scenario 1 - Values sent by your postpayment.php page
sellingamount: USD 100
accountingamount: INR 5000
In this scenario we sent you USD 100 and INR 5000, and you sent the same figures back. We will therefore credit the Sub-Reseller with the same amount.
Scenario 2 - Values sent by your postpayment.php page
sellingamount: USD 95
accountingamount: INR 4750
In this scenario, we sent you USD 100 and INR 5000, and you sent back USD 95 and INR 4750 (deducting 5% processing charges). We will therefore credit the Sub-Reseller with USD 95,
INR 4750.
Completing the Integration process using the postpayment.php page
We have a special built-in test mechanism for testing the interaction between the postpayment.php on your Server and our Server. The steps below assume you have finished all previous
instructions until this step. Follow the steps below to test your integration further:
Login to your Reseller Control Panel. See details
In the Menu, point to Settings -> Finance and Billing -> Payment Gateway -> List / Add.
Click the Manage button next to the Payment Gateway you added.
Click Test For Add Fund or Test For Payment.
This should result in a page as follows -
File:
paymentpage.php
Checksum Verification ........ Verified
List of Variables Received as follows
paymenttypeid: 202
transid: 1120
userid: 1
usertype: Customer
transactiontype: CustomerAddFund
invoiceids:
debitnoteids:
description:
sellingcurrencyamount: 5
accountingcurrencyamount: 10
redirecturl:
http://account.techzoneindia.com/servlet/TestCustomPaymentAuthCompletedServlet
address1 = 213 Main St.
company = My Solutions
address2 = null
zip = 17541
name = Customer Name
city = NYC
telNoCc = 1
country = US
telNo = 45784126
emailAddr = [email protected]
address3 = null
state = NY
faxNoCc = null
faxNo = null
checksum: 8cd2a658d2de2c995fc790b66a508ec3
Clicking any of the above button submits to the same page where the value of status is set in the session and then you are redirected to postpayment.php, and you should see the
below display:
File: postpayment.php
redirecturl:
http://account.techzoneindia.com/servlet/TestCustomPaymentAuthCompletedServlet
List of Variables to send back
transid: 1120
status: Y
rkey: 32423
checksum: 8cd2a658d2de2c995fc790b66a508ec3
Clicking this button will redirect you to our Server and you should see the following display on our Server -
Checksum Verification ........ Verified
List of Variables Received as follows
transid: 1120
status: Y
rkey: 32423
checksum: 8cd2a658d2de2c995fc790b66a508ec3
If you see the above display this means that your integration is complete. You simply now need to modify the files and put in your own code to charge your Customer / Sub-Reseller.
If you get any of the following results instead then you can appropriately refer back to see if you have correctly set the following data:
| Result | Possible Solution |
|---|---|
|
ERROR: Checksum Mismatch |
This can only happen if the key you used is incorrect. Open the postpayment.php file and verify that the value of the Key is exactly the same as the Key displayed in your Payment |
|
Other Possible Issues |
Verify that variables passed to your script through the POST method are working appropriately and your web server supports the same. |
If you do not get this output then you should revert back and check if you have properly inserted your key in the postpayment.php file. Make sure you proceed ahead
only after you get the above output for your specific integration kit.
We have completed the process of Sending a Customer / Sub-Reseller to your Server and then receiving the Customer / Sub-Reseller back. You now need to modify up the files on your
server to process the transaction. The process that you will follow is:
Modify the paymentpage.php file and insert your code to charge the Customer / Sub-Reseller in the block shown below:
if(verifyChecksum($paymenttypeid, $transid, $userid, $usertype, $transactiontype, $sellingcurrencyamount, $accountingcurrencyamount, $key, $checksum))
{
// YOUR CODE GOES HERE
}
The Code that you insert here may involve any or all of the following steps:
Saving the variables to a local database/session
Converting the amount to the currency used by your Payment Gateway
Redirecting the Customer / Sub-Reseller to another page which will obtain input from the Customer (e.g. his Credit Card details) and charge them
Once you have made the above changes then after the transaction you need to redirect the Customer back to our server. This task is handled by postpayment.php.
Before postpayment.php can redirect the Customer / Sub-Reseller it needs to have transid, redirecturl and status available in the
session. While transid and redirecturl will be available in the session if they have been put in by paymentpage.php, status will have to be separately put into the session.
Do not pass a status to the postpayment.php page. This can allow the Customer / Sub-Reseller to modify the status. You must put the status value in session and
retrieve the same from the session, or directly copy the code of postpayment.php inside your payment processing page.
Clean up the Code in the files. We have put in test related code which you may wish to remove. You can clean up the code at this stage removing all the procedures you
do not need.
Attempt a live transaction from one of your Customer / Sub-Reseller accounts to verify everything is working fine. Make sure you try all types of Transactions - Add Funds,
Payment of an Invoice, Payment of multiple Invoices/Debit Notes, etc.
The SuperSite contains information about the various Payment options you offer to your Customers and also presents these options at the time of purchasing Products and Services. This
data is downloaded to your SuperSite from your Control Panel and cached (stored) on the SuperSite Server. Hence, you would need to refresh the cache of your SuperSite once you have
completed the above process. You can accomplish this from within your Control Panel itself by
clicking Tools -> Reload SuperSite and PartnerSite Cache -> SuperSite Payment Preferences.
Every live transaction attempted through your Payment Gateway is recorded by the system. You can list all Transactions and search through them using
the List Transactions and Search Transactions
buttons in your Payment Gateway toolbar. The following fields are important with respect to each Transaction:
| Field | Type | Description |
|---|---|---|
|
transid |
string |
This is a unique transaction ID generated by us and sent to your Server for every Transaction attempted. |
|
status |
character |
This can be either Processing,Successful or Failed. The status Processing denotes any transaction for which |
There may be occasions when your Customer / Sub-Reseller will be redirected to your Gateway but never comes back to our Server because of loss of connectivity or other issues. In
this circumstance our System will not know whether the
Transaction was Successful or Failed. You will have to tell that to the System yourselves. This can be easily achieved by Searching Transactions from the Payment
Gateway toolbar and clicking AuthStarted transactions. This will allow you to list all transactions which are yet processing. From here you can state whether they
were Successful or Failed. Incase of a successful transaction the System will add those funds to your Customer / Sub-Reseller and process any related Orders. Incase of failed transactions
the System will simply mark the transaction as failed.
Integrating the Skrill (earlier Moneybookers) Credit Card Gateway with our system is a breeze. You do not have to write any code. You simply have to fill in a form specifying your preferences and Account details.
You will need to know your Skrill Email Address (the one you use to enter while logging into your Skrill Merchant Account), before you can add this Payment Gateway option in your Reseller Account.
Login to your Reseller Control Panel. See details
In the Menu, point to Settings -> Finance & Billing -> Payment Gateway and click List / Add.
Click the Add a Gateway link.
Click the Add a Skrill (earlier Moneybookers) Payment Gateway link.
Enter the following details and save your changes by clicking the Submit button:
Gateway Name: This Gateway Name would be shown to your Customers / Sub-Resellers, when they are about to make Payment. You can use something like Credit Card Payment or Visa/Master Card, etc..
Enter Your User [email protected] (Skrill Email Address): This is the email address that you enter while logging into your Skrill Account.
Currency: Select the Currency in which you want to charge your Customers / Sub-Resellers. Your Merchant Account needs to support the Currency that is selected.
Currency Exchange Rate: If the Currency you selected in the previous option varies from your Selling Currency, we will have to convert the Invoice value to the Skrill Currency, before we send your Customer / Sub-Reseller's details to Skrill. For this purpose, the system needs an exchange rate between the two.
You may choose to maintain this exchange rate yourselves or let us maintain it for you. We download FOREX rates on a daily basis from a recognized source and update exchange rates for you. If, however, you wish to update the rates
yourselves then you may do so by selecting the I would like to Maintain the currency exchange rate myself. checkbox AND entering your own conversion rates.
Select the types of CREDIT CARDS that your merchant account supports: You need to select the types of Credit Card that are supported by your Bank. The credit card types available are - Visa, Master and Amex. You can also decide the sequence in which you want your Customers / Sub-Resellers to view these Card types on the payment page.
Payment Gateway Access Level for Customers / Sub-Resellers: Select appropriate Access Levels for your Customers / Sub-Resellers.
Payment Gateway Transaction types and Access Levels for your Customers / Sub-Resellers
Credit a Customer / Sub-Reseller with the Net Amount in an Add Funds transaction.: Skrill deducts a fee on a per transaction basis. There are two types of Transactions that can pass through your Skrill integration - Invoice/Debit Note Payment and Add Funds.
Payment Gateway Transaction types and Access Levels for your Customers / Sub-Resellers
In case of an Add Funds Transaction, you have the option of crediting your Customers / Sub-Resellers with the Net amount that Skrill credits you with, or choose to credit them with the Gross funds and bear the charges yourselves. The Net amount is calculated by subtracting the Total Variable fee charged per transaction from the Transaction Amount.
Total Variable fee charged per transaction for your merchant account: Enter the total variable fee that is charged per transaction in the given textbox. This information is primarily used to calculate the Net amount that your merchant account is credited with, if you choose to credit your Customer / Sub-Reseller with the Net amount in an Add Funds transaction. Your bank and/or your gateway may be charging you a different amount of variable fee per transaction for different credit card types, e.g., a certain variable fee per transaction for Visa cards and a different variable fee for American Express cards. In case, the amount of variable fee is different per credit card type, then enter the highest amount of variable fees charged per transaction to your account, e.g., if the total variable fee for Visa Cards is 2.50% per transaction and the total variable fee for American Express cards is 3.00% per transaction, then enter 3.00 in the textbox. If there is no variable fee charged per transaction then enter 0.
If you have selected to credit a Customer / Sub-Reseller with the Net amount in an Add Funds transaction, then you must submit a Variable Transaction fee (greater than 0).
Send me a Reminder if a transaction is pending for more than x days: In case you have not yet accepted a payment sent to you via the Skrill Payment Gateway, you can get e-mail reminders sent to you daily after x number of days from the payment date, until you either Approve or Decline these payments.
Display Position: If you plan on adding multiple Gateways, you can select the position in which you wish to display this Gateway on your Payment Page.
The SuperSite contains information about the various Payment options you offer to your Customers and also presents these options at the time of purchasing Products and Services. This data is downloaded to your SuperSite from your Control Panel and cached (stored) on the SuperSite Server. The cache of your SuperSite will be reloaded automatically, once you have completed the above process. This way, the updated details will be downloaded to your SuperSite from your Control Panel.
With Skrill (earlier Moneybookers), people can send and receive payments through the Internet – all that is needed is an email address. Skrill supports domestic funding options in over 30 countries.
To integrate the Skrill Credit Card Gateway in your Reseller Account, there is no limitation at Skrill about the type of account you should be holding. You can have either of these accounts:
Personal Account - for individual users, or
Company Account - for legal entities. If you choose to open this account, you would need your company registration number and information for a principal contact at your business. If your business is not registered, we advise you to register as an individual user or contact [email protected] for assistance.
The applicable Merchant Fees are displayed under Credit Card Payments at https://www.moneybookers.com/app/help.pl?s=m_fees.
To accept Credit Cards from your Customers, you would need to apply for this Service by emailing [email protected] with the following information:
Your website URL
Description of your business
Your Skrill account email address or if you are not yet a customer, your country of residence