It makes sense to separate verification from the ordering process. The payment extension will only need to generate and display a new address for every order, which can be done in PHP. The extension can generate public keys using a deterministic wallet algorithm. The corresponding private keys can be generated locally on operator's computer. This scheme does not need a hot wallet or a third-party service.

Well, friends, I have some bad news. It appears the Blockchain.info JSON-RPC API can not play nice with my payment module in its current incarnation. The payment module relies upon immediate acknowledgement of a transaction (0 confirmations) in order to function properly. There is a delay between sending payment to a Blockchain.info MyWallet address and Blockchain's acknowledgement of the transaction. It appears to wait until 1 confirmation. This means that it is impossible to do a slick immediate recognition of payment (as my payment module is programmed to do) with the Blockchain.info API at the present.

I could write an extension that would accept any order regardless of whether payment was ever sent, OR I could write an extension that would instruct the user to wait 10 or 15 minutes to see if their order went through. Both sound like a rather silly way of doing business, but unfortunately that's all that would be possible with the Blockchain.info JSON-RPC API (until they improve it).

Sure. Well I'm using Electrum and it's possible to add a description to your payment. Will have to check if that's standard.

Eventually jga's module is what I need, because it's the only way to automate things. For small scale I think it can be done my way as well..

With the current amount of orders I should be good for now  . But I'll instruct my customers to add the ordernumber as a description. anyone can add a description to their payments right?

As for everyone else, if you're still having issues with my extension, email me at support@btcgear.com and I'll see what I can do. I can make a test site and/or test bitcoind server available to one user at a time which can make troubleshooting much easier.

Yes, it is my intention to be independent of the middle men. I haven't been as brave as you to try and install the payment module, and I'm not skilled enough to help you sorry. As my shop is just starting I'm thinking about just providing a fixed bitcoin address. I don't think that's any different from providing details about a bank account. for business it is cheaper though. Before I do that I want to be able to charge the customer for the transaction costs - to make it clear what the difference is between say paypal and bitcoin. I just learned paypal forbids you to separately add the transaction costs, and I'm curious if they're going to cut me off  

As far as I know, when you specify "https://" you should automatically connect with SSL enabled (I'm not a PHP programmer). You can check it by connecting to non-ssl site (e.g. you own local webserver) using "https://" prefix, if it gives error then it works fine.

I'm dying for a module like this because if the strong fluctuations.. it only works if the standard valuta is USD - but mine has to be EUR.. I recon it's not too difficult to fork this module for the european market? I emailed the guy, and I just hope someone can explain me how to do it sooner rather then later

Use https instead of http or your password is passed in plain text.

Thanks for the feedback!  I'm testing out my payout system.  If you could let me know if you received payment and that your stats were updated on the website that would be fantastic!

As long as there were no hiccups with my payment system she's ready to go live!