Paul Screen, [20.03.20 00:21]

I'm going to keep highlighting this, an Invoicing Module dApp built on the Nexus blockchain... https://github.com/Nexusoft/Nexus-Interface-Invoice-Module/releases

​

We will talk more about it in the next zoom - perhaps Kendal and I can do demo of it

​

This is basic invoicing system with invoice data captured in a register on chain. You can create an invoice in the wallet module, add invoice items, and then send that invoice to the recipient to be paid. Ownership of the invoice is transferred to the recipient BUT (and this is the really cool bit) the transfer has a conditional contract attached which prevents the recipient from claiming the transfer until a debit for the invoice amount is made to the sender's nominated address. This is in essence how the DEX works.

​

Until it is paid, the recipient will see the invoice in their outstanding invoices list.

And of course there is a function in the module to be able to pay the invoice from your chosen account

​

Now, two cool features...

​

Firstly invoices can be issued in NXS or any other token created on the Nexus platform. So this dApp is not limited to invoices in NXS. You could use this to track payments in your own token if you wish

​

Secondly, the invoices API allows the creation of invoices to be fully extensible in terms of the data you wish to store in the invoice. There are a small number of mandatory fields - a recipient, a payment account, and an array of invoice items (each with a unit amount and quantity) but beyond this you are free to include any fields in the invoice JSON that you wish. So our Invoice Module includes things like description, invoice number, reference, due date, sender details, recipient details, item descriptions. But it would be trivial for someone to extend the wallet module (or write their own dApp) to include things like purchase order number, payment terms, item references, or any other arbitrary data (up to the current 1Kb max register size) - the API just stores the JSON invoice data verbatim in the register. And then regurgitates this data verbatim when you retrieve an invoice. So the invoice API is very flexible.