It's a proof of concept implementation of the ideas I discussed here:
http://groups.google.com/group/agile-banking/browse_thread/thread/160fa389154b4f3d#
The basic idea is that the bank (or asset provider) doesn't issue
cards itself. Rather independent (perhaps vetted) card issuers issue
cards that act as plastic OAuth Access Tokens.
The user can link a card to his or her account and revoke that link
again. Ideally things like daily transaction limits etc should be a
setting on the AccessToken. This isn't yet implemented in
OpenTransact, but will be soon.
So CapCard lets you create virtual cards that can be linked to your
Nubux account. They can then withdraw money. Which is basically a
money transfer to the card issuers nubux account. In the real world
all sorts of stuff would then take place clearing it within the
regular banking system.
Just like Nubux, CapCard is OSS and is hosted on github:
http://github.com/opentransact/capcard/tree/master
It was quite a useful exercise to perform oauth based OpenTransact
calls. The core of this is done here:
I wrote it in a separate module to make it easy to form the base for a
new OpenTransact ruby gem.
I'd like to welcome people using other languages to try and duplicate that code.
Anyway, I'd like some feedback.
Also feel free to fork it in GitHub and create your own variations.
P
--
http://agree2.com - Reach Agreement!
http://extraeagle.com - Solutions for the electronic Extra Legal world
http://stakeventures.com - Bootstrapping blog