Request (REQ)

Request (REQ): An Ethereum-Based Payment and Invoicing Network

Request Network is designed to let users create, share, and settle blockchain-based payment requests without relying on conventional payment processors. REQ is the network’s ERC-20 utility token, while the project’s payment records and fee model depend on underlying blockchain infrastructure.

Request Network turns payment requests into blockchain records

Request Network is described as a decentralized payment system built on Ethereum. Its core process begins when a user creates a payment request, identifies the destination address, and specifies an amount. Additional conditions can be added so that the request functions as an invoice rather than a simple transfer instruction.

The resulting request can be shared with the intended counterparty, who can detect it and pay it in a peer-to-peer transaction. project materials says that the steps involved in creating, tracking, and settling invoices are recorded on the Request network. This is intended to give the participants a persistent record for accounting and payment-history purposes, although the practical experience depends on the wallets, blockchains, and applications used by both sides.

Push-based invoicing limits the information a payer must disclose

Request presents its payment flow as push-generated rather than pull-generated. In this model, the recipient creates the request and the payer authorizes a payment to a specified address, rather than granting a third party continuing access to an account or payment method. The project identifies this structure as a way to avoid sharing account information with an intermediary.

The claimed benefit is a simpler peer-to-peer payment process with fewer processor-dependent steps. That does not remove every operational dependency: a transaction still has to be broadcast to an underlying blockchain, and the payer must use a compatible wallet or service. Network fees, wallet support, and the counterparty’s willingness to use the request format remain practical conditions for settlement.

REQ supplies the utility-token layer and fee mechanism

REQ is an ERC-20 token launched in 2017 and described as the utility token supporting the performance and stability of Request Network. project materials states that REQ can be spent to use the network. It also describes a fee model in which part of the REQ fee is burned, with the burn rate determined by the token’s supply and its exchange rate against other currencies.

The payment process also involves blockchain transaction fees. These are presented as costs required to broadcast changes to the relevant blockchain and, in project materials, as compensation for the parties that help reach consensus. The token-burn design therefore should not be confused with the underlying transaction fee: one relates to the project’s stated REQ fee mechanism, while the other is a network-level cost associated with blockchain activity.

Ethereum and Polygon are the recorded network relationships

project materials centers Request Network on Ethereum and states that requests using REQ are stored on an immutable digital ledger. Ethereum is also the stated base for the ERC-20 token. YearBull’s recorded project categories include both the Ethereum Ecosystem and Polygon Ecosystem, and the recorded networks are Ethereum and Polygon PoS.

Those records indicate that both ecosystems are relevant to the project page, but project materials does not explain how each network is used, which payment flows are available on Polygon, or whether all Request features operate identically across the two networks. Those implementation details matter because settlement costs, supported assets, confirmation behavior, and wallet compatibility can differ between chains.

Accounting, privacy, and compliance are stated design objectives

Request describes blockchain storage, including Ethereum and IPFS, as a way to support security, privacy, and user data ownership. Its ledger is also presented as evidence for auditing. These are design objectives and project descriptions rather than independent findings about every deployment or user workflow.

The source further claims that Request is integrated with legislation across countries so that it can remain compliant with local trade laws. public materials does not specify the jurisdictions covered, the responsible legal entities, the scope of that integration, or how compliance obligations are handled by users and counterparties. Those questions are material for businesses considering the system for invoicing or cross-border payments.

Founding history and historical market context

Request was launched on October 7, 2017, according to the recorded genesis date. project materials names Christophe Lassuyt and Etienne Tatur as founders, identifying Lassuyt as chief financial officer and Tatur as chief technical officer at the time described. It also associates both with the founding of MONEYTIS and identifies prior roles for Tatur at QOBUZ. These are supplied biographical claims, not independently assessed employment findings.

YearBull’s historical observations show that REQ’s recorded market behavior has varied substantially across the observation window. The strongest sequential rank was 19 and the weakest was 4,477, while the dominant cycle label was Early. The recorded median absolute daily move was 1.6%, and the window’s drawdown from its high was 51.67%. This context describes historical variability; it does not establish how Request Network is used or predict future token behavior.

Key takeaways

• Request Network is designed around blockchain-based payment requests that can be expanded into invoices with amounts, destination addresses, and conditions.
• The project presents push-based payments as a way to avoid sharing account information with third-party processors.
• REQ is an ERC-20 utility token associated with network use and a stated fee-burning mechanism.
• Ethereum is central to project materials, while YearBull also records Polygon PoS as a related network.
• Ledger-based records are intended to support payment tracking and auditing, but actual workflows depend on wallets, supported chains, and counterparties.
• The project makes broad privacy, data-ownership, and cross-border compliance claims whose scope requires further verification.

Risks and unresolved questions

• public materials does not establish which Request features, assets, or payment flows are currently available on Ethereum versus Polygon PoS.
• The scope and operation of the stated REQ fee and burn mechanism are not detailed, including how fees are calculated in specific transactions.
• Blockchain transaction costs, wallet compatibility, and counterparty adoption may affect whether the invoicing workflow is practical for users.
• The project’s claims about privacy, data ownership, auditing, and security are not accompanied here by independent testing or a detailed threat model.
• The stated integration with laws across countries lacks jurisdiction-by-jurisdiction detail and does not clarify user or business compliance responsibilities.
• The relationship between invoice data, IPFS storage, and on-chain records is not fully explained, including what information is public or difficult to remove.