CTO here. Feel free to ask API questions here.

Tons of uses for this "little" features. Profit sharing, revenue splits, forced savings, etc...

I know this pay button seems like simple stuff, but I like to think we've done it next-level style:

- Crypto only but you can price in fiat (USD, etc) - Super private: our payment flow (hate that word) works over Tor with Javascript and Cookies disabled (Tor browser's highest setting). [although you can't collect email/refund addresses in that mode]

Made this for a hackathon. Running on GAE, Twilio for voice calls, Coinkite BitKit API for money handling.

Lets you use a true hardware wallet (Ledger Nano) with your multisignature account on Coinkite.

Here's a "gist" for demo:

https://gist.github.com/peter-conalgo/c31e134e3213949bef70

Just want to say that implementing a client for a binary protocol like Obelisk clears the head after too many JSON and wishy-washy web protocols.

Fixed-width binary fields, framed as 0MQ message frames/messages. Relaxing.

Code's author here: please be kind it's only my 3 or 4th Angular program. Angular is funky stuff (but powerful).

I love the idea, but to me bitmessage is a better fit for the control interface. Doesn't help with the marketing part tho.

I've considered adding this before, so I just threw a ticket up for it: https://github.com/StackMonkey/utter-pool/issues/31

There are lots of simpler ATM's, like the Lamassu that have not gone overboard with the ID stuff.

Of course, these are really just dispensers (or bitcoin vending machines) and only support a single transaction type.