S
Spreedly Blog
blog.spreedly.com · Company blog · on HN since 2009
Spreedly's company blog covers payment vaulting, PCI compliance, pricing changes and engineering practices such as git workflows.
What HN saysHN commenters link it for PCI SAQ A-EP guidance, Spreedly's pricing and a post on git am versus merge pull requests.
21HN people shared it
7linked it in comments
63stories submitted
506story points
9 years agolast shared
2009people per year2026
Most-shared posts
- 1Merge Pull Request Considered Harmful4 people · 275 points · first shared 2014 · 111 comments on HN
- 2Spreedly sells off subscriptions business, focuses on Spreedly Core3 people · 5 points · first shared 2013 · discussion on HN
- 3Spreedly Pricing Change2 people · 5 points · first shared 2009 · 2 comments on HN
- 4API Docs by Request2 people · 2 points · first shared 2017 · discussion on HN
- 5SAQ-A-EP: A big shakeup for online merchants?2 people · 1 points · first shared 2014 · discussion on HN
- 6Spreedly. Funding, expanding our horizons, pivoting1 people · 40 points · first shared 2013 · 26 comments on HN
- 7Vaulting Credit Cards1 people · 34 points · first shared 2013 · 12 comments on HN
- 8Cofounders1 people · 22 points · first shared 2009 · 9 comments on HN
- 9Spreedly Core, PCI-DSS, Gateway Autonomy and commerce. A Guest Post on our blog1 people · 14 points · first shared 2012 · 12 comments on HN
- 10Spreedly for classic applications1 people · 10 points · first shared 2015 · 1 comments on HN
- 11Spreedly's take on Apple Pay1 people · 8 points · first shared 2014 · discussion on HN
- 12Spreedly Core now supports Dwolla1 people · 5 points · first shared 2012 · discussion on HN
- 13Spreedly + DigMyData = Subscriptions Metrics1 people · 4 points · first shared 2013 · 1 comments on HN
- 14Killing redirect payment pages for meta search sites1 people · 4 points · first shared 2014 · discussion on HN
- 15Spreedly now supports Stripe Connect and marketplace onboarding1 people · 4 points · first shared 2013 · discussion on HN
What HN people wrote when they linked it
grhmc · 2016-07-16
For fixing simple stylistic / spelling problems, I really like the take taken with `git am`: https://blog.spreedly.com/2014/06/24/merge-pull-request-considered-har…
grandalf · 2015-01-01
more details here:
https://www.pcisecuritystandards.org/documents/SAQ_A-EP_v3.pdf
http://blog.spreedly.com/2014/03/26/saq-a-ep-a-big-shakeup-for-online-…
If you want to use a PAAS and want to be able to pass any kind of infrastructure audit, the fastest path is probably via Aptible (YC S14)
jusben1369 · 2013-09-26
Or you could use Braintree with Spreedly to keep your options open: http://blog.spreedly.com/2013/09/26/braintree-payments-a-port-in-the-s…
jakem · 2010-02-11
Spreedly is storing data [ http://blog.spreedly.com/2010/2/10/three-new-gateways ]. Others may only be transmitting, but I think PCI applies even if data is only transmitted?
raghus · 2009-11-18
Spreedly updated their pricing recently: http://blog.spreedly.com/2009/11/12/improved-spreedly-pricing
nathany · 2014-11-14
I'm really curious to give Gerrit a try. Is it like the existing Rietveld system used for Go?
- I've been using the "apply mail" flow to avoid merge commits and to squash commits when appropriate (based on Nathaniel Talbott's post http://blog.spreedly.com/author/ntalbott/#.VGVhz5PF_Zs). It will be nice to have something automatic.
- At least contributors with the commit bit can just create a feature branch and a pull request from there. Some open source projects give out the commit bit almost immediately, but with GitHub there's still that initial fork and pull request to prove oneself.
Interested to see how Gerrit addresses this. GitHub doesn't have any way to disable pull requests. :-(
- I've completely disabled email notifications for this reason. There still can be a huge number of notifications in app or via third-party mobile apps. Rietveld is a lot more sane, I only saw notifications for things I was actively working on.
- I usually end up reviewing just the new commits individually. But that requires figuring out which ones I had already reviewed. Not so bad with only a few branches, but I can see it getting out of hand.
I really hope people from GitHub are reading this thread as they are working to improve their tools. :-)
marcusbrown · 2013-08-19
We chose Spreedly for our startup and it was really easy to integrate. I like the idea of having the customer's credit cards details saved independently from the Payment Gateway and Merchant account, so that you're free to switch any time you want if you find a better deal in just 5 minutes via the control panel.
Beside this though we found 2 main problems along the path:
1) Setting up a merchant account for multi currency (we charge in USD and get paid in EUR) is a nightmare and it takes a lot of time (in the end it took more than 3 months!). Things get much more complicated and costs can rise quickly. Also, you have to register with American Express separately and you have to do it for 2 separate accounts (one for euros and one for dollars).
So you end up with lots of different accounts (one for Spreedly, one for the payment gateway, one for the Visa+Mastercard merchant account, one for American Express) and this makes things much more complicated to manage.
2) Spreedly decided in the last months to focus just on the Spreedly Core (vaulting the credit card data in a secure place) and sold the subscription part to Pin Payments
http://blog.spreedly.com/2013/07/15/pin-payments-purchases-spreedly-su…
So this means that the developing of new features was dropped and their minimal control panel stayed the same over the last couple of years. Not sure if this is going to change in the future with Pin Payments, but it's always a big question mark for the future.…