Amazon does it again: Flexible Payments Service
I still don’t know exactly what it is, but I’ve posted about it a couple of times. Amazon has an eye for building an underlying layer of services to empower the new web. From their storage service (S3), to the Elastic Computing Cloud (EC2) – both of which we use on Goplan, our project management solution -, to the Simple Queue Service (SQS) and now their Flexible Payment Service (FPS). No wonder I think these guys rock (and Amazon stock does seem to agree).
What is the Flexible Payment Service
FPS allows you to accept payments ranging from cents to thousands of dollars by leveraging their API. Amazon is pretty much making their payment system (used to charge for S3, EC2 and the other services) available to developers, for their own apps. Here’s the rundown in the words of Jeff Barr (via the Amazon WS blog):
We’ve taken all that we know about dealing with credit cards, bank accounts, fraud checking and customer service and wrapped it all up into one convenient package.
In much the same way that S3 and EC2 allow developers to forget about leasing space in data centers, buying servers and negotiating for bandwidth, FPS shields developers from many of the messy and complex issues which arise when dealing with money. Once again, we take care of the “muck” and developers get to focus on being innovative and creative.
Some example uses for FPS
If you think about it, it’s really easy to think of ways you can use FPS to build really cool services that would otherwise be hard to bill for. Here’s a few examples, off the top of my head:
- Twitter could use FPS for a pay-per-use pricing model (hey, so they stop losing money every month). You would pay based on the messages you send. This is by no means my recommendation to twitter, but hey, it’s an idea.
- We could start using FPS on Goplan to charge people flexibly by number of projects and users, instead of the fixed plans we have now. Should make it much more interesting for people who want to pay based on usage.
- Online music stores could use FPS to help kids have music allowances that they could use to get new music whenever they wanted, easily.
There’s really a lot you can do with this kind of flexibility, and while I haven’t gone through the FPS documentation myself, if this is as flexible as S3 and EC2, I know this is a winner.
Amazon kicks ass. This could be the only conclusion here, but I’ll continue by saying I’m both pretty excited about trying out FPS on our own services (and those we build for clients), as well as see what other people come up with.
Services like S3 have proven Amazon – despite being a retailer – is also the clear leader when it comes to infrastructure. These guys are helping other developers actually pave the way to new services, not just locking them in like others are. Very smart – definitely very Amazon. I love that company.