Interesting story: We started with a public service, but it was having reliability issues at the time. We decided to stay up all night last week and roll our own. Basically it's bitcoind running on an AWS EC2 instance, talking JSON RPC with our back-end network. bitcoind has been reliable. It crashed once but we had a simple monitoring script in place that restarted it.
Next up should be some sort of calculator with a currency lock to allow customers to deposit the precise amount of BTC they will need to pay for their order.
Enjoy La Parrilla.
Cool, for the trouble I might have to pick up the rest of the crew's tabs as well.
0.002 is a bit high, I set mine there because I like my sports bets to post quickly. 0.001 would probably cover more than 80% of the transactions fees headed your way. A middle ground of a 0.0015 rebate might cover 90-95% of people's fees. I'm something of an outlier when it comes to fees...
Currency locking can be a bit tricky. Especially since any exchanges tend to either fold or lag when the DDOS's hit. Depending on how brave your team is using MPEX futures either through MPEX.co itself or Coin.br could maybe do quite a bit to mitigate your foreign exchange risk. There are other avenues for hedging, but a lot of them are built on broken and recycled code. Anywhere you might decide to hedge the FX risk is going to be iffy, but of all the futures options available at this time MPEX's seem the most solid (disclaimer: I am not a licensed broker, attorney, or agent of any sort). Not hedging and just holding extra coin you can't immediately unload at cost on the other hand to sell later might just be viable if you have the capital on reserve to wait before converting back to dollars.