FROM DISK = '<dbname.bak file path on local machine>' /*e.g. 'c:\dbname.bak' */
WITH REPLACE
| ALL_HTTP | Returns all HTTP headers sent by the client. Always prefixed with HTTP_ and capitalized |
| ALL_RAW | Returns all headers in raw form |
| APPL_MD_PATH | Returns the meta base path for the application for the ISAPI DLL |
| APPL_PHYSICAL_PATH | Returns the physical path corresponding to the meta base path |
| AUTH_PASSWORD | Returns the value entered in the client's authentication dialog |
| AUTH_TYPE | The authentication method that the server uses to validate users |
| AUTH_USER | Returns the raw authenticated user name |
| CERT_COOKIE | Returns the unique ID for client certificate as a string |
| CERT_FLAGS | bit0 is set to 1 if the client certificate is present and bit1 is set to 1 if the cCertification authority of the client certificate is not valid |
| CERT_ISSUER | Returns the issuer field of the client certificate |
| CERT_KEYSIZE | Returns the number of bits in Secure Sockets Layer connection key size |
| CERT_SECRETKEYSIZE | Returns the number of bits in server certificate private key |
| CERT_SERIALNUMBER | Returns the serial number field of the client certificate |
| CERT_SERVER_ISSUER | Returns the issuer field of the server certificate |
| CERT_SERVER_SUBJECT | Returns the subject field of the server certificate |
| CERT_SUBJECT | Returns the subject field of the client certificate |
| CONTENT_LENGTH | Returns the length of the content as sent by the client |
| CONTENT_TYPE | Returns the data type of the content |
| GATEWAY_INTERFACE | Returns the revision of the CGI specification used by the server |
| HTTP_<HeaderName> | Returns the value stored in the header HeaderName |
| HTTP_ACCEPT | Returns the value of the Accept header |
| HTTP_ACCEPT_LANGUAGE | Returns a string describing the language to use for displaying content |
| HTTP_COOKIE | Returns the cookie string included with the request |
| HTTP_REFERER | Returns a string containing the URL of the page that referred the request to the current page using an <a> tag. If the page is redirected, HTTP_REFERER is empty |
| HTTP_USER_AGENT | Returns a string describing the browser that sent the request |
| HTTPS | Returns ON if the request came in through secure channel or OFF if the request came in through a non-secure channel |
| HTTPS_KEYSIZE | Returns the number of bits in Secure Sockets Layer connection key size |
| HTTPS_SECRETKEYSIZE | Returns the number of bits in server certificate private key |
| HTTPS_SERVER_ISSUER | Returns the issuer field of the server certificate |
| HTTPS_SERVER_SUBJECT | Returns the subject field of the server certificate |
| INSTANCE_ID | The ID for the IIS instance in text format |
| INSTANCE_META_PATH | The meta base path for the instance of IIS that responds to the request |
| LOCAL_ADDR | Returns the server address on which the request came in |
| LOGON_USER | Returns the Windows account that the user is logged into |
| PATH_INFO | Returns extra path information as given by the client |
| PATH_TRANSLATED | A translated version of PATH_INFO that takes the path and performs any necessary virtual-to-physical mapping |
| QUERY_STRING | Returns the query information stored in the string following the question mark (?) in the HTTP request |
| REMOTE_ADDR | Returns the IP address of the remote host making the request |
| REMOTE_HOST | Returns the name of the host making the request |
| REMOTE_USER | Returns an unmapped user-name string sent in by the user |
| REQUEST_METHOD | Returns the method used to make the request |
| SCRIPT_NAME | Returns a virtual path to the script being executed |
| SERVER_NAME | Returns the server's host name, DNS alias, or IP address as it would appear in self-referencing URLs |
| SERVER_PORT | Returns the port number to which the request was sent |
| SERVER_PORT_SECURE | Returns a string that contains 0 or 1. If the request is being handled on the secure port, it will be 1. Otherwise, it will be 0 |
| SERVER_PROTOCOL | Returns the name and revision of the request information protocol |
| SERVER_SOFTWARE | Returns the name and version of the server software that answers the request and runs the gateway |
| URL | Returns the base portion of the URL |
If you are an Indian startup and you have an e-commerce component to your application, you will need to review, evaluate and shortlist a payment gateway that can handle online payments via credit and debit cards. And most likely this will not be an easy or fast process. In its current form, there are just a handful of payment gateway service providers in India. Access to information related to a few them is non-existent on the web.
I'm hoping that this post will help folks to do an easy and quick comparison between the various service providers.
Before we move on to the comparison, let's consider some of the criteria that are important while evaluating a payment gateway:
1) Cost:
All payment gateways have an intial setup cost and then charge a small percentage of the transaction. Few have an annual maintainence cost (AMC) as well. The initial setup cost is a one time charge only and is mostly non-refundable. The annual maintainence cost is an annually recurring charge. The transaction cost (TDR) is charge per transaction and is generally anywhere between 4-7% of the transaction amount. The higher the volume, the more you can negotiate the transaction cost.
2) Support:
How helpful and responsive is the service provider when you run into a problem ? Do they provide off hours support ?
3) Chargeback policy and disputes:
What is the policy for chargebacks and refunds ? What is the policy for disputes ?
4) Ease of Integration:
Does the service provider provide an easy way to integrate the gateway into your app ? Do they provide alternate means for integration if tomorrow your architecture changes for some reason ?
Beyond these basic criteria, you'll also need to consider additional factors (depending on your requirements) like – what credit cards / banks are supported by the payment gateway ? Do they provide mobile banking option ? What is their rate of successful transactions etc ?
One often raised point is why not use PayPal as your payment gateway ? After all, they provide a great API for integration, there are plenty of code samples already available and their rates are quite competitive.
Well, the reason why PayPal may not suit everyone's requirements is because they do not provide you the option to charge customers in Indian Rupees. If using one of the PayPal supported currencies meets the requirements of your app, great. If not, you'll need to consider using a payment gateway that will allow payments in Indian Rupees.
So, here's a comparison of the major Indian online payment gateways (had to publish as a PDF since the spreadsheet wont fit on the blog). The list includes a comparison of CCAvenue, DirecPay (operated by TimesMoney group), EBS (collaboration with Axis bank), ABC Payments (operated by IndiaMart), HDFC, ICICI Payseal andTransecute.
The troublesome part of it was trying to locate the correct pricing plans for the various payment gateways, especially for DirecPay, HDFC and ICICI. DirecPay, HDFC and ICICI for whatever stupid reason choose not to list their pricing plans on their websites. You need to contact them via email or snail mail (ICICI) with your business details and only then, based on the nature of your business, transaction volume etc. do they send you a pricing plan. Sheer incovenience — I mean, so much ground work to simply get info on their pricing plans ? Its been 3-4 days since I emailed DirecPay and HDFC for details about their plans and am yet to hear back from them. I fail to see why they dont provide a simple price info on their website rather than to go through this archaic process.
The comparison document is by no means complete just due to the sheer difficulty in locating correct information on the web. I'm keeping this document 'live' – in the sense that if you have any input / update suggestions to add any additional payment gateway to the list or to update info related to any of the ones already listed in the document, please send them in to me and I will continue updating the document.
So which payment gateway should an Indian startup use ?
To begin with, you should obviously analyse the various payment gateways on some of the criteria that I listed above. On top of that, if you need to review data related to the success rate, average time to refund etc. for some of these gateways, I would suggest reviewing the statistics revealed by IRCTC – India's biggest e-commerce site. They release monthly data related to transactions and payments, which includes how much each payment gateway contributed in terms of number of transactions, the amount contributed by each as well as the number of days to refund etc. For instance, only 53% of the transactions using the HDFC gateway completed successfully while ICICI gateway handled 17% of all the transactions that were done on the IRCTC website. The data also provides great insight into what are some of the main banks / debit cards being used by customers. For instance, 8.10% of all net banking transactions were attempted by ICICI customers while only 0.32% of all transactions were done by Bank of India customers.
Based on my research, if I were to use an Indian payment gateway today, I would personally go with either CCAvenue or EBS – for the simple reason that they make it very easy to get the needed information, have good online documentation and support wide range of credit/debit cards. In case of the other providers, its like a black hole – you try to seek out information and become a customer — and they try to make it that much harder to access that information.
If you have used / worked with and Indian payment gateway, I'd like to know how your experience has been ? If you were to recommend one to others, which one would it be ?
| Pricing & Purchase | UTI Bank | CCAvenue | Paypal | 2Checkout | ||||||||||||
| | ||||||||||||||||
| | ||||||||||||||||
| | ||||||||||||||||
| Pricing Options 1 |
|
|
|
| ||||||||||||
| Pricing Options 2 |
|
| ||||||||||||||
| Pricing Options 3 |
| |||||||||||||||
| Credit Card Accepted | UTI Bank | CCAvenue | Paypal | 2Checkout | ||||||||||||
| | ||||||||||||||||
| Visa Card | ||||||||||||||||
| Mastercard | ||||||||||||||||
| American Express | | |||||||||||||||
| Diners Club International | ||||||||||||||||
| JCB Card | ||||||||||||||||
| Citibank E-Cards | | |||||||||||||||
| Discover | ||||||||||||||||
| Netbanking & Others | UTI Bank | CCAvenue | Paypal | 2Checkout | ||||||||||||
| | ||||||||||||||||
| Centurion Bank of Punjab | ||||||||||||||||
| Citibank | ||||||||||||||||
| HDFC Bank | ||||||||||||||||
| ICICI Bank Ltd. | ||||||||||||||||
| IDBI Bank | ||||||||||||||||
| IndusInd Bank | ||||||||||||||||
| Kotak Mahindra Group | ||||||||||||||||
| Oriental Bank of Commerce | ||||||||||||||||
| Punjab National Bank (PNB) | ||||||||||||||||
| UTI Bank | ||||||||||||||||
| The Bank of Rajasthan | ||||||||||||||||
| YES Bank | ||||||||||||||||
| Paymate (Mobile Payment) | | |||||||||||||||
| Itz Cash | ||||||||||||||||
| Payment Withdraw Method | UTI Bank | CCAvenue | Paypal | 2Checkout | ||||||||||||
| | ||||||||||||||||
| Payment Withdraw Method | Direct deposit in UTI Account | Direct deposit in any Indian Bank Account | Manually Cheque Request or Direct Deposit in any US / Indian Accounts | Wire transfer in any Indian Bank Account or Direct Deposit in any US Accounts | ||||||||||||