Fall-back Mechanism: In case of Broken receipt verification link

[juliustm]

Some receipt verification links are broken (Not formatted to the TRA standard )
i.e This link -> https://verify.tra.go.tz/1374DB48770 - Which lacks '_time' value at the end.

Possible ways to handle this:

1. Categorize the receipt as 'failed'
2. Upon an Interface calling /receipt submission

• Process and Queue the Current request(receiptphoto or receipturl)
• Query the previous 10 submissions(pushed by this device ) and their status
• This should be well formatted into a HTML interface that can be rendered in a browser with the device Authorization headers pre-set
• The 10 previous receipts interface should:
  a. Display receipts submitted by this interface
  b. For receipts that failed - Those that were a receipturls : Provide the user with all details that were captured earlier and the issue. If it was a URL - give the user the ability to attach a photo of that respective receipt.

Might be best to Have(While thinking about this):

• Make the URL PWA ready (When opened using the browser)
• Find out if the Sreams endpoint can do notification pushes
• This PWDA should immediately give the user to +Scan a receipt QR +takePhoto of Receipt
• A neat and User friendly Interface

[KIWOLY]

Potential solutions for this:

Put the receipt in the "failed" category.
Process and queue the current request (receiptphoto or receipturl) when an interface calls for a receipt submission.
Find out the status of the ten submissions that this device has pushed in the past.
This needs to be properly formatted into an HTML interface that the device's browser can display. Pre-set authorisation headers
The interface for the ten previous receipts should: a. Show the receipts that this interface has submitted; b. For the receipts that didn't work, those that were receipturls: Give the user all the information that was previously recorded, together with the problem. Allow the user to attach a picture of the relevant receipt if it was a URL.