Three easy places to start:
a) Simplify the UI - Make it as simple as possible for people to enter their payment details - large fonts, cross-browser tested, minimal pages, optimized for the lowest screen resolution of your average user on up.
b) Reiterate TRUST messaging - testimonials or buying popular symbols (Verign /McAfee / etc) and even dialing in the PLACEMENT of those logos is high-value eg http://www.conversionvoodoo.com/blog/2010/07/proper-placemen...
e) Implement a Cart Abandon strategy - either sending "instant discounts" via email good for 24hrs to complete order, calling dropped carts, or hitting a pop-up of live help or similar is easy money.
Add to this all the usual - proper messaging on buttons, lightning fast response times, mobile optimized version too, etc and you instantly gain a massive advantage over your competitors.
Some of the common tactics that have worked for our customers:
- Providing a summary of what they have ordered and making sure there are no hidden surprises (extra taxes or shipping charges)
- Adding trust indicators like Verisign seal (yes, they really work!)
- Not requiring them to create an account just to checkout
- Adding phone number and physical address that customers can reach out in case they need help
- Good looking design (people subconsciously associate good design with higher trust. If you have an odd color, or a grammatical mistake, or a dangling element, it tells how careless you are at designing the most critical page, so you would be careless with their money as well)
> e) Implement a Cart Abandon strategy - either sending "instant discounts" via email good for 24hrs to complete order,
Training users to haggle at checkout and not trust the list prices
> calling dropped carts.
harassing people offline after they leave your store?
> or hitting a pop-up of live help
Does anyone believe in live help? All I ever see it do it block content I am trying to read, providing the equivalent of menu-driven CLI (the scripts agents follow) when I already have a powerful GUI in front of me.
One thing I've been seeing recently is that some implementations using Stripe DO have the CC details hitting their server. The most common case being when Javascript is disabled the form posts to the website because the developer didn't design with graceful degradation, a dangerous mistake when mixed with credit card numbers.
It doesn't appear to be a problem for you (your payment page for CC info doesn't gracefully degrade with JS disabled and is impassible - you might want to fix that!) but I've seen it on other sites, and it's especially a problem when other sites don't use SSL as a fail safe for this sort of case which I have also seen. For Stripe it might perhaps be worth considering denying all payments from non HTTPS pages for this reason. It forces the merchants to have an SSL failsafe.
Also with CC info being entered on your site, it's presumably trivial for the site itself to record the CC numbers. Trust is the issue here, I'm not going to be entering my CC number on a site I've never heard of, with no reputation. Stripe doesn't solve this issue, Paypal does. Stripe looks wonderful, but it's not going to be suitable for everyone.
Only if you do it wrong. From the Stripe docs: "The only thing to note is how input fields representing sensitive card data (number, CVC, expiration month and year) do not have a 'name' attribute. This prevents them from hitting your server when the form is submitted."
> It doesn't appear to be a problem for you (your payment page for CC info doesn't gracefully degrade with JS disabled and is impassible - you might want to fix that!) but I've seen it on other sites, and it's especially a problem when other sites don't use SSL as a fail safe for this sort of case which I have also seen.
Again, SSL is covered by the docs. Stripe says you need it. Not that you should consider it, or that it's a bonus, but that you need it. https://stripe.com/help/ssl
No putting them in a DB, no putting the in a log file (not even the last four or something like that), nothing. So if your form takes the numbers in, you make an API call, and then you blank them in memory you were OK.
If you put them in the user's session, you were in trouble.
It's all insanely complicated, and the only good solution is "don't do it." There's a good reason people use things like Stripe, PayPal, Authorize.net's CIM (where they store it and certify that they are PCI compliant).
Stop reminding me I can't use Stripe all the time.
http://www.businessinsider.com/stripe-square-international-e...
Still using it. Great product. But I had to file an extension and crap to get it all sorted out, which was highly annoying.
[Update:] So, the background here is that 1099 reporting rules changed last year. A lot of companies—including some of our partners—didn't yet have their infrastructure in place to properly handle them. A lot has been written about the change in the law (search "2011 1099 confusion" for a small sample), and there's been a fair amount of ambiguity and confusion overall (Citibank issued 1099s for frequent flyer miles; whether this was necessary isn't yet clear). Due to this confusion, the IRS actually backed off plans to require the reconciliation of Form 1099K in tax returns filed for 2011.
In Stripe's case, one of our banking partners responsible for the filings was unable to meet the original filing date for all 1099s. While they filed a proper extension with the IRS, this meant that receipt of your 1099 was delayed.
As you point out, we should have done a much better job communicating this at each step -- and, obviously, receiving tax forms in mid-April is not an acceptable outcome regardless. We are working on controlling the process much more closely ourselves next year so that this does not happen again.
But the bottom line is: sorry. We built Stripe to make this kind of hassle go away, and we're doing everything we can to make sure that this was a one-off blip.
If I'm not mistaken, Google Checkout and PayPal did not send me 1099 - I just had to report all the revenue received from them myself.
My guess is that a lot of customers don't know what Paypal is and don't realize they can just use their credit card.
If, like me, you don't like the idea of loading someone else's javascript into your own domain, the "web page" side of things can also be done by dropping a single <iframe> tag into your HTML.
You can see the big jump in May-July (although the jump for July is 32%, not 53%)
This is going on my "best of" list of HN-related excerpts
I am not easily emotionally moved by git command lines, but this is clearly somebody who understands me and what I need in life
I can't believe the good old 'computer was hit by a lightning bolt' wasn't in one of your test cases, Patrick! I mean it's so obvious :P
More seriously, that is one of the wildest reasons for a bug I think I've ever heard.
I would love to do a redesign for Appointment Reminder if you're interested :)
but great customer service is still great, no matter what.
Here are some advantages to FastSpring: FastSpring works with developers and companies located anywhere US companies are authorized to do business, handles global tax compliance and tax payment management including for VAT, enables end users to pay using their localized currency to avoid bank/exchange fees and a poor US/USD-centric user experience, provides an order page localized in 20+ languages, has PayPal integrated, lets you skip the PCI Assessment Questionnaire, offers fraud prevention, a built-in shopping cart, Google Analytics and marketing ad campaign tracking integration, an unlimited number of easy to setup post-order notifications, designs an order page to match the look and feel of the other pages of the developer’s website, offers merchandising features for cross and upselling to maximize the average order size and optimizer order conversion, built-in notifications, a future bill testing GUI, pre-bill notifications for annual subscriptions, reseller and affiliate management, user role mgmt. & change tracking, consulting for SEO/PPC/Affiliate marketing/Online marketing/order page optimization, one-time purchases in addition to recurring billing, among other advantages. Hope that's helpful with your comparison.
Fast Spring is 5.9% plus $.95 or 8.9% flat per order.
Stripe 2.9% + 30 cents.
This is a very interesting result. I would have thought that additional payment options would boost sales on the margin i.e. increase conversion by a couple of percent (not percentage points ;) for e.g. international customers, or people who already have accounts with GG/PP.
Patrick: Any chance you could elaborate a little more here? Would be very interesting to see some more detailed stats on this aspect.
My bank account is in the states, but I need to be able to charge Europeans in euros, Brazilians in reais, Japanese in yen, etc...
I think this is more "people who are on the margin where they MIGHT be interested in paying for more cards can be convinced when they hit the pretty checkout page". If you don't need more than 15 cards, you probably don't have a burning need for the paid version.
"Currently Stripe is US only..."