Shopping Cart System using Blockchain's new Receive Payments API v2 BIP32 xpub

[coinableS]

BC.info is phasing out their version 1 receive payments API on Dec 7th. Their new version is out, the main difference is HD BIP32 xpub instead of payment forwarding. I have tested it out, and I must say I enjoy it much more than the previous version.

In the process of testing it out I created a shopping cart system that small merchants can use to sell whatever they want on their website, so I thought I'd throw it up on github. https://github.com/coinables/Blockchain-Receive-Payments-API-Shopping-Cart

What you'll need:
- Blockchain.info API key for their new receive payments API. Request one here https://api.blockchain.info/v2/apikey/request/
- A website and host that supports PHP, and MySQL databases. Preferably cPanel with PHPmyAdmin.
- Download the files in the repository at github https://github.com/coinables/Blockchain-Receive-Payments-API-Shopping-Cart
- Create and configure a database on your webserver
- Import the included SQL database files using PHPmyadmin or similar database manager
- Open the config.php file and update the fields
- Upload the files to your server.
- Goto login.php in the directory where you uploaded your files to access your admin panel and start adding products!

Want a preview?  I go over it in this video starting at 6:25  https://youtu.be/D2__AFoOdec?t=6m24s

[TheGrimm]

Thanks for taking time to do this.

But sadly I do not think anyone should use this for a production site, from my quick glace there is 0 security in this, it looks like sql injections are possible.

I could be wrong, I am not a security expect but just looking out for everyone.

[coinableS]

Thanks for taking time to do this.

But sadly I do not think anyone should use this for a production site, from my quick glace there is 0 security in this, it looks like sql injections are possible.

I could be wrong, I am not a security expect but just looking out for everyone.

That's not true at all.
All inputs are designated to charset utf8 and then escaped before being inputted to the DB. Although PDO or objects would be safer it's open so anyone can change it if they feel the need for a higher level of security.