Posted on December 8, 2017 by Colaberry .

The bottom layer is the Core, which manages the consensus over the ledger and the states transitions. It
consists of the most fundamental smart contracts, allowing the creation of different entities and requests for
payments. It also detects when payments have been completed. It is based on immutability (ie. no one
can change the information), the openness of its system (everyone can access information that concerns
them) and an intelligence that allows it to know when an invoice is paid according to the rules in the invoice.
This layer takes place on the Ethereum blockchain, which brings endogenous benefits for Ethereum and
ERC20-labeled invoices, such as automatic detection. Other currencies are also covered via automatic payment
detection through the use of Oracles.
This layer is free to encourage the greatest number to use it and to discourage the development of other
systems. The only costs transmitted are the use of Ethereum gas and the storage of information.
3.2 The Extensions layer
The second layer is the Extensions layer. Most payment requests created today are not as basic as the one
proposed by the Core layer. If the request comes from an enterprise, then it includes rules for calculating
taxes, payment terms, escrows or advances. All of these conditions take the form of available extensions
that can be added to requests. This layer is the gateway to incredible features that do not yet exist, such
as ”continuous bills”. For example, someone could choose this module to break down their rent into
30×24 payments to the landlord, leaving this person with a fluid bank account without large end-of-month
expenses. Taxes would be rerouted in real time to government agencies. With each payment, 20% of VAT
would go to taxes and 80% to the recipient company. The same example would allow everyone to give 1% of all
payments to NGOs (Non Governmental Organizations), or to deposit them into ones own retirement account.
This layer is chargeable, in that each extension will take a fee that will be partially burned and partially
transferred to the extension developers, with the extensions accrued on the same invoice. Costs decrease over
time to remain competitive and discourage alternative systems. The costs of these extensions is estimated
to be between 0.0.5% and 0.5% initially, though as the system grows, the costs will be reduced. More than
5,000 billion dollars in payments are made each day, and in the end it will be enough to finance the network
by less than 0.1%. Nonetheless, the costs will continue to support the security of applications and their
This layer is completely open, whereupon anyone can create their own extensions, with the fees also being
distributed in a way that will interest and encourage the developer and the community.

The topmost layer is the Applications layer, which takes place outside the blockchain. Systems from different
companies can connect to Request to create requests or access information. Accounting, audit, tax, debt recovery
and collection, factoring or payment systems can all be connected. When a payment system connects
to Request (Mycellium, Coinbase, Bank of America, Bankin …), it will be able to access the invoices of the
user and propose to pay them instantly.
The Request team will develop applications, including an interface and an API for creating and accessing
Reputation Application
A reputation system is included in this layer to guard against phishing or bad payers. For instance, a user
will be able to detect whether a company is attempting phishing, in the case that other users have previously
rejected its payments. Conversely, a company that does not pay its invoices on time, after having accepted
them, will also be penalized by means of its reputation. The reputation system may also have other uses; for
example, members of the network with the best reputation will be able to receive cost reductions or access
to custom extensions.
The reputation could be directly entered in the blockchain, but to keep the system light, we have chosen
to keep them in the application layer thus far, since this information can be re-obtained by browsing the

Download the Paper