Site Engagement Roundup [Week ending June 17th]
Some of the awesome comments/insights shared by Pluggd.in readers, whom we often call as the extended team members!.
PayU vs. ccavenue:
IMO it’s better than CCAvenue on these fronts -
1) lower TDR, 1.1) Lowest setup fee for each slab
2) Easier process (you get PG in 2 weeks flat if you send documents on time…got ours in 10 days),
3) T+2 settlement even in the worst case. CCAvenue takes longer if you don’t have account in certain banks
4) Clean page with no unnecessary details like billing, shipping, bank name etc to be filled by the customers. CCAvenue page is lengthy and cumbersome
Good points standalone. Not enough data to compare with CCAvenue
1) Good relationship managers
2) Above-average and quick technical support
CCAvenue scores on these points:
1) PayU has less number of payment options…very few banks in Netbanking (on brighter side – these few banks cover almost 75% of all netbanking customers). Most customers have multiple bank accounts. Hasn’t been a problem for us. CCAvenue accepts almost all banks netbanking and Debit/ATM card. They basically cover the longtail of buyers – cash cards, mobile payments.
1.1) International payment options including intl netbanking on CCAvenue. Advantage depending who your customers are
2) PayU is relatively new in India and hence some customers dont know about it. Some (very small percentage of) users may cancel the payment. Provide good customer support on phone and you are sorted. People trust people (strange as it may sound). It hasn’t been a problem for us thus far.
3) CCAvenue has more out-of-the-box solutions thanks to their longer existence in market. PayU has simple single-click extensions for most popular eCom platforms including Magento. Again, not a big concern unless you are using some obscure eCom platform. PayU however provides quick technology support (developers actually working with you/for you) if you don’t know how to integrate. I have heard it’s not that quick at CCAvenue should you need manual help.
Hope this info helps.
Great article, excellent recommendations on caching and using reverse proxies. One thing I don’t agree with is the recommendation to use Java, in 2012. Also – being on the cloud makes little sense unless you are building flash sales site. Do you really have the kind of traffic variation and bring servers up and down all the time? I had rather not recommend the cloud simply because most cloud vendors are not located in India, and Indian e-commerce companies should host somewhere close to where the audience is.
Good to see someone taking a stride away from the open source solutions to actually building your own platform. I seriously feel that building your own platform is the way to go ahead and scale and sustain in the future. Open source is a great way to get started, but if you have a long term vision then by all means build your platform.
I am happy to propose a challenge – use PayU and its full offering for 2 weeks. If your success rates don’t improve, we will give the payment gateway free of cost for life i.e. no transaction charges. we will bear that from our own pocket.
[Nitin Gupta/Post: Interview with PayU Country Head, Nitin : Our conversion rates are 12% higher than other payment Gateways]
As a web based product development company we found 5-10 project daily only for eCommerce development. They don’t know anything about operations but want to create eCommerce portal like flipkart, myntra, jobang :) This article will really help them to analyze requirement and complexity.