Quote from: DNotes on July 02, 2018, 07:51:47 PM

Quote from: DCEBrief on July 02, 2018, 05:34:59 PM

DNotes Smart Invoicing - Merchant Services Built into the Blockchain

https://dcebrief.com/dnotes-smart-invoicing-merchant-services-built-into-the-blockchain/

Well done Brandon! Good timing as well.

We have just added a few invoice API's to the ABE block explorer. You may view them here:
https://explorer.dnotescoin.com/chain/DNotes/q

Invoice related API's added:
invoice - amount paid and number of confirmations for a particular invoice and recipient address.
invoiceamount - amount paid for a particular invoice and recipient address.
invoiceconfirmation - number of confirmations for a particular invoice and recipient address.

We've also added:
address_history - returns the history of the address balance and transactions.

Example:
https://explorer.dnotescoin.com/chain/DNotes/q/invoice/DNOTESADDRESS+INVOICENUMBER
https://explorer.dnotescoin.com/chain/DNotes/q/invoice/SZ84u9Riadtq6WQAxj7MGgtfXae7f91f96+213091203012983asdjasdnasidn
Returns
10,2674
Meaning that 10 DNotes were paid to that address and invoice number and there are 2674 confirmations.

This will make it easy to verify an invoice from a simple Abe block explorer API call. The invoice number integration has multiple applications and will assist in automated multiple facets of business, payments, and accounting, however we are focusing on a narrow range of simplified use cases right now. They will make it possible to accept decentralized payments while keeping your wallet safely offline, create new payment models that were previously not possible, and make accepting automatic payments available to a greater number of people especially those with more limited resources.

One of the most amazing things about decentralized digital currency is it provides people with many choices and options that can fit their needs.

There will be different options and proof of concepts made available on our github open source directory.

The first proof of concepts will be the highest ease of use and integration capabilities, with the least possible requirements. I will describe the process in more detail below.

The second proof of concepts will be slightly more complicated to use and integrate, however we will add in some security features needed for more commercial use applications. These will still be easier to integrate than most payment system available today, still won't require a third party, however won't have the same requirements and overhead as the corporate version of cryptocurrency payment integration.

Then we will work on integration into popular payment systems already available and move into the third round of proof of concepts.

The third round of proof of concepts will be the full blown integration that will be needed for corporation and big business integrations. This is where most of the industry is focused right now, as well as middle man integrations, in terms of creating solutions, because that is where the big money is. However, we are more interested in making access available to everyone with the least hassle and least cost as our first objective.

Just a note, I cannot provide a timeline just yet, we will likely have to work on other things in between.

First Round of Proof of Concepts Examples

Selling a digital product online:
Examples - Ebooks, Audio and Music, Information Products, Software, virtually anything digital works.
Description - As with below, this will allow the seller to sell a product for whatever they want, even it's only a $0.05 product, that was not previously possible with traditional payment models unless you wanted charge $0.80 with $0.75 paid in fees.
-The seller will need a website, easily configure 5 variables in the script and upload the script to their website, and add any design to it that they like. This can be done in just a few minutes of time, and there is nearly no technical experience required.
-The buyer will be directed to the webpage where the script is located, be shown a payment address (with the invoice number attached), and an amount of DNotes to pay (on the back end it will determine and convert the dollar amount configured into an amount of DNotes to pay via exchange API calls). The website will continue to call the explorer API and determine if the payment has been made and how many confirmations, once it reaches the number of confirmations specified by the seller, it will release the digital product to the user to download immediately. If the confirmations is set to 0, it will be instantly delivered.
Though 0 confirmations is not very secure, because theoretically that makes it vulnerable to double spend attacks, it may not matter to the seller. There is no guaranteed way to secure digital products right now, if they want to steal it, they will find a way. 0 confirmations just makes it more convenient for those that are willing to pay for the product.

Selling Software Pay Per Use / Period
Description - This is the part I mentioned before about new payment models that were not previously possible or feasible. If you are a software developer and your users would like to use your software occasionally, you can have an option that allows them to pay for 1 hour / 1 day / 1 week / 1 month / forever or whatever they want. This is a superior and potentially more profitable model for the seller while offering the buyer the ability to use and pay on their terms. It gives them the ability to use a fully functioning software the way they want, without having to worry about fees, processing micro payments, and actually making it possible to sell $1.00 worth of something without it costing you more in fees and middle men than you get out of it.
-The seller in this case incorporates our open source scripts and configures a couple variables. Doesn't even need a website or a server.
-The buyer will be prompted with the payment options and then be presented a payment address (with the invoice number attached), and an amount of DNotes to pay (on the back end it will determine and convert the dollar amount configured into an amount of DNotes to pay via exchange API calls). The program will continue to call the explorer API and determine if the payment has been made and how many confirmations, once it reaches the number of confirmations specified by the seller, it will release access to use the software immediately.

Smart very smart! Good djob thank you

MECHETO

Posts

Merits