24 Jul 10 Integration process with ANY OTHER Payment Gateway
The System has the built-in ability to allow you to integrate ANY Payment Gateway to allow your Customers and 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 -
Step 1: Any Customer/Sub-Reseller of yours needs to pay you money and selects a Payment Gateway to do so.
Step 2: 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.
Step 3: You then charge the Customer/Sub-Reseller using these messages, and your Payment Gateway.
Step 4: 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.
Step 5: 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
|
[i] What you will Need |
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 3.0 (last updated on 10th March, 2008)
-
IMPORTANT: Must Read for those UPGRADING from any older Kit
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
1. ASP Integration Kit: If you have already integrated this Kit with your website, then you need to simply download the ASP Integration Kit ver 2.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.
2. JSP Integration Kit: If you have already integrated this Kit with your website, then you need to download the JSP Integration Kit ver 2.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:
A. Modifications to paymentpage.jsp
i. Replace the below code from your paymentpage.jsp -
<%@ page import =”java.util.zip.Adler32,
java.math.BigDecimal” %>
<%!
private boolean verifyChecksum(int paymentTypeId, String transId, int userId,
String userType, String transactionType,
String invoiceIds, String debitNoteIds,
String description, double sellingAmount,
double accountingAmount, String key, String checksum)
{
String str = paymentTypeId + “|” + transId + “|” + userId + “|” + userType+ “|” +
transactionType + “|” + invoiceIds + “|” + debitNoteIds +“|” +
description + “|” + sellingAmount + “|” + accountingAmount + “|” + key;
Adler32 adl = new Adler32();
System.out.println(“CheckSumStr: “ + str);
adl.update(str.getBytes());
long adler = adl.getValue();
return (“” + adler).equals(checksum);
}
%>
Replace the above code in your paymentpage.jsp with -
<%@ include file=“functions.jsp” %>
ii. Enclose all occurances of verifyChecksum function call within a try-catch block.
B. Modifications to postpayment.jsp
i. Replace the below code from your postpayment.jsp -
<%@ page import =“java.util.zip.*,java.io.*,java.util.*,java.math.*” %>
<%!
private String generateCheckSum(String transId, double sellingAmount, double accountingAmount, String status,
String rkey, String key)
{
String str = transId + “|” + sellingAmount + “|” + accountingAmount + “|” +
status + “|” + rkey + “|” + key;
Adler32 adl = new Adler32();
System.out.println(“CheckSumStr: “ + str);
adl.update(str.getBytes());
return String.valueOf(adl.getValue());
}
%>
Replace the above code in your postpayment.jsp with -
<%@ include file=“functions.jsp” %>
ii. Enclose all occurances of generateChecksum function call within a try-catch block.
3. PHP Integration Kit: If you have already integrated this Kit with your website, then you need to simply download the PHP Integration Kit ver 2.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
i. Login into your Reseller Control Panel from http://manage.gossimer.biz/reseller
ii. Go to Settings -> Finance and Billing -> Payment Gateway -> List / Add
iii. Click on the Custom Payment Gateway that you are upgrading.
iv. Select the Checksum Algorithm as MD5 and save your changes by clicking on Submit.
|
[ii] Adding your Payment Gateway |
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:
1. Login into your Reseller Control Panel from http://manage.gossimer.biz/reseller
2. Go to Settings -> Finance and Billing -> Payment Gateway -> List / Add
3. Click on the Add Payment Gateway button and then on the Add any other Payment Gateway link.
4. Enter the following Details and save your changes by clicking on 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 and Sub-Resellers – Click here to know more about Payment Gateway Transaction types and Access Levels for your Customers and 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 across to you from our system, after every x number of days, until you either Approve or Decline these payments. Click here to know how to Approve / Decline Payment Gateway transactions >>
-
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.
-
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 [i]. Select Addler 32 only if you are still using an older kit and haven’t yet upgraded.
|
[iii] Preparation on your Server |
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 on 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 on the Generate Key button. You will then have to replace the New Key in your code.
|
[iv] Set the Gateway URL |
You will now need to set the Gateway URL which we skipped earlier while adding the Gateway. The Gateway URL is the full http:// URL that will be used to access the paymentpage.php on your server. So a typical Gateway URL would look like “http://www.yourserver.com/paymentpage.php”
Visit the Settings -> Finance and Billing -> Payment Gateway -> List / Add section and click on the Payment Gateway you added. Click on Modify and enter the Gateway URL as described above. Make sure the URL is entered complete with the “http://” or “https://” all the way up to the name of the page. DO NOT pass any Parameters to the URL
CORRECT GATEWAY URL
http://www.yourserver.com/paymentpage.php
WRONG GATEWAY URLS
www.yourserver.com/paymentpage.php
http://www.yourserver.com/paymentpage.php?someparam=something
|
[v] Testing the Integration so far |
You are now ready to test your integration and verify that it works. Follow the steps below to Test your Integration
1. Click on Settings -> Finance and Billing -> Payment Gateway -> List / Add
2. Click on the Payment Gateway you added
3. Click on Test for Add Funds or Test for Payment, depending upon the type of transaction you wish to test.
This will popup a new window redirect you to the Gateway URL you had specified passing it the following parameters in a POST 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 generate for each transaction |
|
userid |
integer |
This is the ID of the Customer/Sub-Reseller who is doing this transaction |
|
usertype |
string |
This refers to the type of user performing this transaction. The possible values are Customer or Reseller |
|
transactiontype |
string |
This refers to the type of transaction taking place. This could either be ResellerAddFund, CustomerAddFund, ResellerPayment, CustomerPayment (Reference: Payment Gateway Transaction types and Access Levels for your Customers and Sub-Resellers >>) |
|
invoiceids |
string |
This refers to the Comma-Separated list of Invoice IDs which your Customer/Sub-Reseller is paying for. This will have a value only if the transactiontype is ResellerPayment or CustomerPayment |
|
debitnoteids |
string |
This refers to the Comma-Separated list of Debit Note IDs which your Customer/Sub-Reseller is paying for. This will have a value only if the transactiontype is ResellerPayment or CustomerPayment |
|
description |
string |
This refers to the delimiter-separated Text Description of the Invoices and Debit Notes which your Customer/Sub-Reseller is paying for. This will have a value only if the transactiontype is ResellerPayment or CustomerPayment |
|
sellingcurrencyamount |
numeric (up to 3 decimal points) |
This refers to the amount of transaction in your Selling Currency |
|
accountingcurrencyamount |
numeric (up to 3 decimal points) |
This refers to the amount of transaction in your Accounting Currency |
|
redirecturl |
string |
This is the URL on our server, to which you need to send the user once you have finished charging him |
|
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 checksum is calculated on all the data sent to you using your 32 bit Alpha-numeric Key. The same checksum maybe verified at your end to ensure that the data received is valid |
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 |
These variables can directly be accessed in the paymentpage.php. If all goes well, then on 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://manage.gossimer.biz/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 = customer@domain.com
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 Payment Gateway detailed view. Make sure there are no extra spaces or any missing characters. |
|
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 the URL has been correctly set with in the Gateway URL field of your Payment Gateway. Also verify that your web server is working perfectly |
|
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 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.
IMPORTANT
It is imperative that you test your integration so far, by clicking on both the Test for Add Funds and Test for Payment buttons, before continuing to integrate your website with your Payment Gateway provider.
|
[vi] Charging the Customer/Sub-Reseller on your Payment Gateway |
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 then 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 Selling Currency |
|
accountingcurrencyamount |
numeric (up to 3 decimal points) |
This refers to the amount of transaction in your Accounting Currency |
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.
|
[vii] Sending the Customer/Sub-Reseller back to our Server |
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 |
integer |
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 been collected. An N on the other hand, signifies that the Transaction FAILED. When you send us the status as P, it would indicate that this transaction is to be kept Pending until you manually review this Payment Gateway transaction from your Reseller Control Panel. |
|
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 this on your behalf in the postpayment.php file included in the integration kit. |
|
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 checksum is calculated on all the data that you send to us, using your 32 bit Alpha-numeric Key. The same checksum is then verified by us to ensure that the data received is valid. |
|
sellingcurrencyamount |
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 is only used incase the transactiontype is CustomerAddFund or ResellerAddFund. This is explained in detail below. |
|
accountingcurrencyamount |
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 used incase the transactiontype is CustomerAddFund or ResellerAddFund. This is explained in detail below. |
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 sellingcurrencyamount and accountingcurrencyamount fields
In the above table two important fields are the sellingcurrencyamount and accountingcurrencyamount. These fields MUST be passed, but are used only if the transactiontype is ‘CustomerAddFund’ or ‘ResellerAddFund’ (Reference: Payment Gateway Transaction types and Access Levels for your Customers and 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 a 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 sellingcurrencyamount and accountingcurrencyamount 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
sellingcurrencyamount: USD 100
accountingcurrencyamount: 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
sellingcurrencyamount: USD 95
accountingcurrencyamount: 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
1. Click on Settings -> Finance and Billing -> Payment Gateway -> List / Add
2. Click on the Payment Gateway you added
3. Click on 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://manage.gossimer.biz/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 = customer@domain.com
address3 = null
state = NY
faxNoCc = null
faxNo = null
checksum: 8cd2a658d2de2c995fc790b66a508ec3
Clicking on 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://manage.gossimer.biz/servlet/TestCustomPaymentAuthCompletedServlet
List of Variables to send back
transid: 1120
status: Y
rkey: 32423
checksum: 8cd2a658d2de2c995fc790b66a508ec3
Clicking on 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 Gateway detailed view. Make sure there are no extra spaces or any missing characters. |
|
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.
|
[viii] Finishing Steps |
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 -
1. 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
2. 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.
3. 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.
|
[ix] Final Testing |
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 on Tools -> Reload SuperSite and PartnerSite Cache -> SuperSite Payment Preferences. Click here to know what is SuperSite >>
|
[x] Managing your Transactions |
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 your Customer/Sub-Reseller has left our Server and not yet come back from your Server |
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 on 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. Click here to here to find instructions on how to Search / Approve Decline Payment Gateway Transactions >>
Tags: ASP, Asp 3, Break, Bridge, correct Checksum Algorithm, Gateway Server, Generic Module, http, Inr, Integration Kit, Interaction, Java, Jsp, Kit Version, Logic, Money, Parameters, Payment Gateway, payment processing page, Php, Redirect, Reseller Account, Resellers, Server Space, Step 2, Step 3, System Details, the POST, Transactions - Add Funds, United States, USD, Web Server, www.yourserver.com/paymentpage.php
10 Jul 10 About Transecute
Transecute (http://www.transecute.com) is the only complete online payment solution Provider in India today with product/service offerings, that allow Merchants to accept payments from their customers on their website via Credit Cards (VISA/Master). The service is made to allow easy integration (within 2 minutes) and ease-of use. The service is indispensable to any website who wishes to transact online safely and e-enable their web presence.
Gossimer has integrated with Transecute, to allow its Resellers to accept funds online through secure and convenient means. However, this Payment Gateway is available only for Resellers who are based in India.
Some of the useful links are listed below -
Transecute Features: http://www.transecute.com/merchants/features/
Demo Interface: http://www.transecute.com/merchants/interface-demo/
Signup for Transecute Merchant Account: http://www.transecute.com/merchants/sign-up/
Login to the Transecute Merchant Account: https://secure.transecute.com/merchant/index.jsp
Transecute Support & Knowledge Base: http://support.transecute.com/transecute/index.jsp
Tags: Amp, Credit Cards Visa, Gossimer, India, India Today, Interface Demo, Jsp, Knowledge Base, Merchant Account, Merchant Index, Merchants, online payment solution, Payment Gateway, Payment Solution, Resellers, Service Offerings, Solution Provider, Visa Master, Web Presence
06 Jul 10 About PlanetPayment
Planet Payment (http://www.planetpayment.com) is a specialty multi-currency payment processor that enables merchants and cardholders to complete credit card transactions in each party’s preferred currency. The Company is a leader in processing international and foreign currency credit card transactions on behalf of banks, merchants, and cardholders.
Planet Payment offers its services to the payment processing industry, including acquiring banks, transaction processors, gateway and point-of-sale solution providers. Planet Payment also offers its services directly to merchants.
Some of the useful links are listed below –
Find a Planet Payment Partner: http://www.planetpayment.com/Merchants.aspx
Planet Payment Merchant Inquiry: http://www.planetpayment.com/Merchants.aspx
Planet Payment Merchant Login: https://www.planetpayment.net/mweb/index.jsp
Planet Payment Helpdesk: customer-support@planetpayment.com
Tags: Affiliate Login, Banks, Cardholders, Credit Card Transactions, Customer Support, Foreign Currency, Gateway, Helpdesk Support, International Currency, Jsp, leader, Merchant Login, Merchants, multi-currency payment processor, Mweb, Payment Partner, Payment Processing, payment processing industry, Payment Processor, Planet Payment, Point Of Sale, Preferred Currency, Solution Providers, Transaction Processors, www.planetpayment.com/shortform.cfm
04 Jul 10 How do I check the Whois for my Domain Name?
After you have registered your Domain Name, you can check the Whois of the same to confirm its Registration, check the Contact Details and Name Servers of the Domain Name. You can use either of the 3 methods mentioned below, to view the Whois of your Domain Name:
I. From the Storefront -
Visit your Storefront at http://manage.gossimer.biz and there go to Domain Names -> Whois
OR
you can simply click here – http://manage.gossimer.biz/whois.jsp.
Here, you would find 2 text boxes. In the first, you would have to, enter the Domain Name in the form domain.com or mydomain.info etc. and not www.domain.com, and in the second box, enter the Security Key, which appears in the image alongside. On submitting this, you can check the Whois of the Domain Name.
II. From your Control Panel -
- Follow the steps mentioned below to view the Whois from your Control Panel -
- Login to your Control Panel:Resellers, do so from http://manage.gossimer.biz/reseller;
Customers, do so from http://manage.gossimer.biz/customer.
- Customers: Go to Domains -> Domain Registration -> Whois Lookup.Resellers: Go to Products -> Domain Registration -> Whois Lookup.
- Here, you would find 2 text boxes. In the first, you would have to, enter the Domain Name in the form domain.com or mydomain.info etc. and not www.domain.com, and in the second box, enter the Security Key, which appears in the image alongside. On submitting this, you can check the Whois of the Domain Name.
III. From a reliable 3rd party Whois Provider -
When using any third party Whois websites, you need to ensure that you understand the following:
- When verifying the registration details of .com/.net domain names, no 3rd party Whois site will be able to display accurate Whois Details until up to 24 hours after registration. This is so because other Providers need to first query the concerned Registry’s Whois Servers, to acquire the Whois Server URL of the Sponsoring Registrar [before querying the Registrar's Whois Server for complete Whois Details] and the Registry’s Whois Server itself updates its records in that much time.
- When verifying the registration details of any other domain name extension [like .info, .org, .biz, .in, .us], the Registry itself stores all the Registration Details and any 3rd party Whois directly queries the concerned Registry’s Whois Server for such details. Ideally, the Registry’s Whois Server should publish/update this data in every 5 to 10 minutes.
- Most 3rd party Whois sites cache results from previous results of the queried domain names and may misguide you. We would advise you to instead use http://www.drwhois.com, when you wish to have a 3rd opinion of a particular domain name’s registration details.
Tags: Contact Details, Control Panel Login, Domain Lookup, Domain Name, Domain Names, Domain Registration, Domain Resellers, Domain Whois, Jsp, Name Servers, Regis, Registrar, Registration Details, Reseller Customers, Security Key, Server Url, Sponsoring Registrar, Storefront, Text Boxes, Third Party, Whois Provider, Whois Domain, Whois Lookup, Whois Server, Whois Server URL, Whois Servers, www.domain.com
02 Jul 10 Add / Modify 2Checkout version 1 and/or version 2 Credit Card Gateway
Integration of 2Checkout version 1 and version 2 Credit Card Payment Gateway with your Reseller Account is identical. The Integration process does not involve ANY code writing, and all you need to do is fill up a form specifying your Account Details and Payment Collection preferences.
Before you Start
-
You need to ensure that you are an 2Checkout Merchant. You can signup for a Merchant Account from – https://www2.2checkout.com/2co/signup
-
Setup the Return URL within your 2Checkout Merchant Account
a. Login into your 2Checkout Merchant Account
b. Click on the 7. Setting Up Your Site. link
c. Scroll down to the Optional Parameters section and click on the link under Click here
d. Set both your Pending and Approved URLs as:http://<Your_Control Panel_Branded_URL>/reseller/paymentgateway/generic/PostFormGateway.jsp?PGNAME=2checkout
* You need to replace <Your_Control Panel_Branded_URL> with the URL you have set within your Reseller Control Panel under Settings -> Storefront & Control Panel -> URL.
e. Click on the Save Changes button to submit these changes.
Submit your Account Details and Preferences to us
1. Login into your Reseller Control Panel from
2. Click on the Settings -> Finance & Billing -> Payment Gateway -> List / Add
3. Click on the Add Payment Gateway button and then on either the Add a 2Checkout Credit Card Gateway or Add a 2Checkout Version 2 Credit Card Gateway link, depending upon the version of your 2Checkout Merchant Account.
4. Enter the following 2Checkout Details and save your changes by clicking on 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.
Vendor Id - The Vendor Serial Number assigned by 2Checkout when you create a Merchant account with them.
Secret Word - The security code (word) for your Merchant Account with 2Checkout.
Currency – Currently we allow 2Checkout to charge your Customers / Sub-Resellers only in US Dollar (USD).
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 2Checkout Currency, BEFORE we send your Customer to 2Checkout. For this purpose the system needs a 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 CARD that your Merchant Account Supports: You need to select the types of Credit Card that are supported by your 2Checkout Merchant Account. The credit card types available are – Visa, Master, Amex, Discover, Diners Card and JCB. You can also decide the sequence in which you want your Customers / Sub-Resellers to view these Card types.
Payment Gateway Access Level for Customers and Sub-Resellers – Click here to know more about Payment Gateway Transaction types and Access Levels for your Customers and Sub-Resellers >>
Deciding whether a Sub-Reseller and Customer is Credited with the Gross Amount or Net – Your Bank and 2Checkout deducts a fee on a per transaction basis. There are two types of Transactions that can pass through your 2Checkout integration – Invoice/Debit Note Payment, and Add Funds. Click here to know more about Payment Gateway Transaction types and Access Levels for your Customers and Sub-Resellers >>
In case of an Add Funds Transaction, you have the option of crediting your Customers/Sub-Resellers with the NET Amount that 2Checkout 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 per transaction charges from the Transaction Amount. The per transaction charges are calculated by adding the Total Fixed fee charged per transaction and the Total Variable fee charged per transaction.
Total Fixed fee charged per transaction for your merchant account (Per Transaction Fixed Fee charged by your Bank + Per Transaction Fixed Fee charged by the 2Checkout Credit Card Gateway) - Enter the total fixed 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 fixed fee per transaction for different credit card types e.g. a certain fixed fee per transaction for Visa cards and a different fixed fee for American Express cards. In case, the amount of fixed fee is different per credit card type, then enter the highest amount of fixed fees charged per transaction to your account e.g. if the total fixed fee for Visa Cards is 25 cents per transaction and the total fixed fee for American Express cards is 30 cents per transaction, then enter 0.30 in the textbox. If there is no fixed fee charged per transaction then enter 0.
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.
IMPORTANT
If you have selected to credit a Customer/Sub-Reseller with the Net Amount in an Add Funds transaction, then you must submit either a Fixed Transaction fee (greater than 0) or 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 2Checkout Payment Gateway, you can get e-mail reminders sent across to you from our system, after every x number of days, until you either Approve or Decline these payments. Click here to know how to Approve / Decline Payment Gateway transactions >>
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.
IMPORTANT
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 on Tools -> Reload SuperSite & PartnerSite Cache -> SuperSite Payment Preferences. Click here to know what is SuperSite >>
Tags: 2checkout, Account Details, American Express, bank, cent, Code Word, Credit Card Gateway, Credit Card Payment, Gateway Link, http, Jsp, Merchant Account, Optional Parameters, Payment Gateway, Reseller Account, Reseller Control Panel, Resellers, Return Url, Secret Word, Security Code, Serial Number, Storefront, Vendor Id, Visa Master Card
Gossimer in the News
- Gossimer Puts Indian Domain Extensions Up for Sale February 21, 2010Gossimer, the fastest growing domain name registration and web hosting company has announced a sale on Indian domain extensions. During the promotion period, domains ending with .in will be offered at discounted price. [PR.com] […]
- Gossimer Unveils a New & Improved Payment System February 14, 2010The Melbourne-based (Florida) web hosting and domain name registration company Gossimer has announced the inclusion of three more payment options in its system. From today the customers and the web hosting resellers can use AlertPay, WebMoney, and Liberty Reserve to pay for the domain registration as well as web hosting services. Gossimer already offered Pay […]
- Gossimer Has Opened Its Treasure Chest for Webhost Resellers January 16, 2010Gossimer, the fast growing domain name registration and web hosting company has yet again opened its door of their reseller program. This program offers a comprehensive web hosting product portfolio for resellers and resellers of Gossimer’s resellers. [PR.com] […]
- Gossimer Invites Customers to Try Digital Certificates for Free January 2, 2010Gossimer, the fastest growing domain name registration and web hosting company is offering 21 days free trial on digital certificates. This trail will allow webmasters to understand the role Https plays in building visitors’ confidence in their website. [PR.com] […]
- Gossimer Announces Special Domain Name Registration Deals December 25, 2009Gossimer, the fastest growing domain name registration and web hosting company has announced a special deal on 12 top domain extensions and that includes some CTLDs as well. This promotion is available on the registration of new domain names, and you can register as many domains as you want. [PR.com] […]
- Gossimer Announced a Transfer-in Domain Promotion to Allow Customers to Consolidate Their Domains Into One Account November 7, 2009Save money on domain name transfer to Gossimer. Gossimer is currently running an attractive promotion on domain transfer-in that will save a lot of money for the domain portfolio builder. You can transfer as many domains as you wish under this promotion. [PR.com] […]
- Gossimer Became Reseller of the Month for October October 17, 2009October brings another piece of good news for Gossimer. The fastest growing web hosting and domain name registration company has been chosen as the Reseller of the month for October by ResellerClub. [PR.com] […]
- Gossimer Offers One Year Free Extension on Domain Transfer October 3, 2009Gossimer, the fastest growing domain name registration company, is offering one year free extension with every domain name transferred to its system. This service when coupled with other services puts Gossimer in the position of price leadership. The company offers the most economic rate for domain name registration and webhosting services. [PR.com] […]
- New Deals Make Gossimer Bigger, Better and Smarter October 2, 2009October is going to be hot with offers, extended support, and enhanced serviceability, as Gossimer has acquired HiTek Networks, and launched new and improved Support desk. The web hosting world is abuzz by the two important developments in Gossimer. [PR.com] […]
- Gossimer Offers Unlimited E-mails for $1 September 28, 2009Gossimer, the fastest growing domain name and webhosting company, has announced a no-upgrade “The Ultimate Email Plan” that will give the buyer an access to unlimited email accounts for just $1/month. [PR.com] […]
Gossimer Promotions and Announcements
- TechSupport Notifications February 28, 2010Technical support information and notifications […]
- PHP4 Discontinuation - 18th September September 7, 2009As announced earlier, PHP4 will not be supported on our Linux Hosting Servers from the 18th of September, 2009. Please pass on this information to your Customers and Resellers to ensure that they can update their websites to work with PHP5. […]
- .CN Launch - Coming Soon August 16, 2009We are glad to announce the launch of .CN - the most popular and fastest growing ccTLD worldwide. The .CN domain extension has seen an exemplary growth since its launch throughout the world. Earlier this year, .CN crossed over 13 million registrations to become the second most registered domain extension after .COM. Moreover, with China now representing the […]
- Live Chat Product Discontinuation - Moved to 18th August August 16, 2009Based on feedback that we received from several Resellers, we have decided to postpone the Live Chat discontinuation to the August of 18th, 2009 at 12:30 UTC. From the 18th of August, it will not be possible to purchase new Live Chat packages but exisiting packages will continue to function normally. […]