Bitcoin Payment Gateway 5

This project is based on uc_bitcoin module and bitcoin_address module from Drupal 7. The objective of assignment is to ease the workload of admin especially "view orders". A live website is at [login to view URL] and you will be given those set of codes (my version) for further improvement because there is still some known bugs:- Milestone1: [50%] #. (User) "Bitcoin amount" is not shown in Review order during checkout #. (User) Email Invoice didn't have the qrcode shown up #. (User) Received two duplicates email notification about "Your order at [login to view URL]" and "File Download for Order# 999" #. (User) Let's say wanna print out a copy of invoice. It should be a compact version, preferably in a single A4 size paper, simple wording, proper formatting instead of the current one, see attachment #. (User) Got to notify user once "payment received" or "completed" already #. (User) Micropayment didn't work e.g. total checkout of $0.50 #. (User) Copy to Clipboard work in certain browsers only #. (User) left:float alignment in Order Complete has to be closer to the left as portrait view of mobile site makes the bitcoin address a bit lengthy and out of page It is compulsory to have code delivered to me before proceeding to next milestone. Milestone2: [50%] #. (Admin) Order status is wrongly shown as "completed" even though invoice is invalid and payment received after timeout #. (Admin) Order status failed to change from "pending" to "abandon" even though no payment received after 60 minutes timeframe, in the absence "confirm payment" interaction #. (Admin) Order status failed to change from "pending" to "completed", in the absence of "confirm payment" interaction #. (Admin) Payment/Logs registered duplicate entry about order status and current balance #. (Admin) For a valid and successful transaction, non-shippable item should mark as "completed" in order status whereas shippable item or mixture item should mark as "payment received" in order status. I noticed the code uses client side countdown timer, which is incorrect. The time is an important parameter and should be taken care of in case of security. The best timestamp would be the reference where the moment user turns from "In checkout" to "Pending", That 60 minutes is all you have.