171–180 of 195 posts
Earlier quoted context omitted.
There's a few misconceptions in the article beyond that. and the more modern bits are written by banks, credit card companies, and financial middlemen, none of whom are exactly winning hackathons for elegant coding. Hackathon code is never elegant... it's always piecemeal at the end in order to get it "done."
I suspect whoever wrote that sentence has an extremely vague idea of what a hackathon is ("some coding contest??").
Stripe's documentation says that they automatically use the credit card update services of Visa, MC, and Discover to update expiration dates of cards they are storing, so that you don't have to worry about keeping the expiration date up to date.
However, from what I've seen using the Visa and MC updater services, a significant fraction of issuing banks do not support them and when requesting updated information on those cards nothing comes back, and these cards often still actually work fine.
Does Stripe having something equivalent to 0000, so that one can say "try to charge this recurring payment on this card, even if we do not have the current expiration date and the updater service did not give a response"?
[1] The expiration date on a credit card is the date that the card itself expires, not the date that the account expires. For new orders, online or in-person, an expired card should be a red flag because a person actually placing a live order should have their latest card. Seeing an expired card live could mean it is a stolen card.
Earlier quoted context omitted.
As someone that selected stripe to process orders for a product were were launching somewhere around 2012, it was because of the APIs and developer sandbox. Paypal was ugly to work with, felt crufty, etc. Stripe had pip installable modules, awesome documentation (live code samples in docs and sandbox), and was easy to integrate into our tests.
And most importantly: Stripe does not randomly decide your funds are suddenly theirs for the next 6 months to a year.
Earlier quoted context omitted.
And most importantly: Stripe does not randomly decide your funds are suddenly theirs for the next 6 months to a year.
They'll do that sooner or later. Everyone in the money-handling industry has to randomly lock-up funds and not tell you why, because that's what anti-money-laundering laws require.
Earlier quoted context omitted.
Re: migrating customers: I just grandfathered all paying customers to a perpetual free plan. Weren't that many of them. Sadly that app never gained traction. You'd think reliable up/down monitoring of unlimited servers at $4/month would be a good deal.
Maybe you weren't charging enough?
~12 years ago, it was Patrick Collison that was named young scientist of the year for developing a dialect of Lisp called Croma: http://lemonodor.com/archives/001038.html I'm glad to see he has continued to do well.
Thanks for that. I'd like to know why he decided first class macros were a bad idea.
Earlier quoted context omitted.
To expand, it's these 7 lines. (Actually 12) - more or less. Maybe not precisely that, but it's the bit where you add a payment form to your website. It's a nice headline, but it really leaves out the tremendous amount of back-end work that went into making that front end easy to use.
Wait, the /your-server-side-code bit seems like the most difficult. Did Stripe not implement this aspect as well? I would have no idea how to securely process credit card transactions server-side.
Earlier quoted context omitted.
Correct, and the big reason for that is it means you don't have to be PCI compliant since the card never touches your server, only stripes. That's why Stripe blew up, Paypal had no such offering for allowing you to use your own checkout form but not have to pass the card through your server.
Not true, PayPal Payments Pro offered that.
Earlier quoted context omitted.
As someone that selected stripe to process orders for a product were were launching somewhere around 2012, it was because of the APIs and developer sandbox. Paypal was ugly to work with, felt crufty, etc. Stripe had pip installable modules, awesome documentation (live code samples in docs and sandbox), and was easy to integrate into our tests.
And most importantly: Stripe does not randomly decide your funds are suddenly theirs for the next 6 months to a year.
https://news.ycombinator.com/item?id=14463971 (2 months ago)
Stripe launched a fraud detection tool in October 2016; not sure if this comment took that into account.