What do you get when you cross a Payments API with …?

on Mar20

I see a lot of fantastically innovative applications out there, where creative developers take APIs and make all kinds of new functionality with them.  A stop by ProgrammableWeb shows so many great ideas–every day there are new web applications (or “mashups”) built by simply combining two or more APIs in a new, sometimes unexpected way.

 

creditcard-keyboard-flickrphotosfosforix3007393167-smlWell, we’re wondering what people might do with the Intellivative Payments API. The goal of our payments API is to simplify adding payment functions (e.g., credit card, debit card, echeck transactions; recurring payments; card on file) to business applications–making it easier to integrate payments into whatever it is you might want to build.

 

So what WOULD you get if you crossed a payments API with a:

  • billing API, an e-mail service, and an SMS messaging service?
  • travel service and a map?
  • claims processing system?
  • movie?
  • retail store, SMS messaging service and shipping API(s)?
  • Twitter?

Perhaps none of these are groundbreaking ideas–some of them I’m sure have already been done. But maybe you have a business idea that hasn’t been done, or maybe a way to do something that has been done, only better. Or perhaps you have a new twist on an old business idea? Whatever it is, we’d like to hear it.

 

Are you a developer? Would you like us to feature your work on our blog? Tell us–What would you build with the Intellivative Payments API?  We’d love to tell your story.

 

(Add a comment below by clicking on the little thought bubble thingy.)


Related Posts

back

Add your comment