Investing In Request (REQ) – Everything You Need to Know

Request (REQ ) Network is an open-source protocol for creating, storing, paying, and reconciling crypto payment requests. Its current focus is direct wallet-to-wallet stablecoin payments for businesses, including cross-chain routing, mass payouts, payment references, and optional wallet screening.

REQ is the Ethereum (ETH ) governance and utility token associated with the protocol. It has two current functions: holders participate in governance, and a portion of REQ is burned whenever a request is stored onchain. REQ is not the currency a customer must use to pay an invoice; businesses usually send and receive stablecoins or other supported assets.

What Is Request Network?

Request Network is a payment-request and reconciliation layer, not a standalone blockchain, bank, or custodial payment processor. A payee creates a request that describes who should be paid, the expected amount, currency, due date, and optional business data. Authorized parties can accept, update, cancel, or pay the request.

The protocol links that structured record with an onchain transfer. This solves a basic limitation of public blockchains: a transaction hash proves that value moved, but it does not automatically explain which invoice, customer, service, or accounting entry the payment belongs to.

Request Network began in 2017 with a broad vision for decentralized invoicing. By 2026, it had narrowed the product around high-volume stablecoin acceptance and payouts, reporting more than $2 billion in wallet-to-wallet volume.

How Payment Requests Are Stored

Request data can be serialized, signed, encrypted when needed, and stored through Request Nodes. Documentation describes request content in IPFS with hashes anchored on Gnosis (GNO ) Chain, while payment execution can occur across several supported chains.

The payee and payer authorize updates with cryptographic signatures. Request logic tracks expected amounts, reductions, increases, acceptance, cancellation, stakeholders, and payment balances. Indexers help applications retrieve and reconcile this history.

The architecture combines multiple systems rather than placing everything in one smart contract. Users depend on IPFS availability, Request Nodes, Gnosis Chain records, chain-specific payment contracts, indexers, RPC providers, and the application interface they choose.

Direct Wallet-to-Wallet Payments

Request Network is designed so funds move from the payer’s wallet to the recipient’s wallet without Request taking custody. The protocol can generate a tamper-evident payment page showing the intended recipient, amount, token, and reference.

Non-custodial settlement reduces the risk that a payment processor freezes or loses funds it holds. It does not eliminate risk. A user can still approve a malicious contract, pay the wrong request, lose private keys, receive a tainted asset, or rely on a bridge or swap that fails.

Payments are normally irreversible after confirmation. Disputes, refunds, chargebacks, and customer-service obligations must be handled through the merchant’s policies or a separate agreement.

Cross-Chain Stablecoin Routing

The current product abstracts differences between supported stablecoins and networks. A merchant can specify the token and destination chain it wants, while the payer can use another supported asset or chain. Routing services perform the required swap and bridge operations before final delivery.

In 2026, Request advertised access to most global stablecoin supply across Ethereum, BNB Chain, Base, Polygon (POL ), Arbitrum (ARB ), Optimism (OP ), and Tron (TRX ). EVM payments can be gas abstracted, and a July 2026 update added a gasless route for USDT on Tron without requiring the payer to hold TRX.

Cross-chain convenience expands the attack surface. A routed payment can depend on price quotes, slippage limits, bridges, routers, relayers, liquidity pools, stablecoin issuers, and multiple networks. The recipient should verify final settlement rather than assuming that a signed request guarantees delivery.

Mass Payouts and Safe Integration

Request’s payout tools let an organization send stablecoins to many recipients from one approval while respecting each recipient’s preferred token and chain. This can reduce manual wallet switching for payroll, contractor payments, grants, or treasury operations.

The network also integrates Safe smart accounts. Organizations can apply multisignature approval rules before executing single or batch payments. The combination is useful for onchain finance teams, but security still depends on signer devices, Safe modules, threshold configuration, address verification, and internal controls.

Mass payouts multiply operational risk. One incorrect spreadsheet, compromised signer, or faulty integration can affect many recipients at once. Teams should test small batches, use address allowlists, and maintain independent reconciliation.

Wallet Screening

Recipients can enable wallet screening before a payer receives the final payment route. Request has integrated risk providers including Hypernative and Merkle Science for sanctions, jurisdiction, spam, and other risk checks.

Screening can help a business reduce exposure to known high-risk addresses, but it is not a guarantee of lawful funds. Analytics providers can make false positives or miss new threats, and their classifications can differ. The merchant remains responsible for whatever compliance, customer due diligence, tax, and reporting rules apply.

Claims that a non-custodial protocol needs no payment or virtual-asset license everywhere should be treated cautiously. Legal status depends on the product, operator, jurisdiction, control over routing, fees, and customer relationship.

Request Network and Request Finance

Request Network is the open protocol and Swiss foundation that stewards it. Request Finance is a separate company that built invoicing, accounts-payable, payroll, and related business products using Request technology.

The two teams spun apart. Investors should not attribute Request Finance customers, revenue, financing, or product decisions automatically to the Request Network Foundation or REQ token.

The ecosystem also includes independent applications and integrations. Open-source composability is a benefit, but a third-party product can change providers or stop using the protocol.

REQ Token Utility

REQ is an ERC-20 token with two functions emphasized by Request Network in 2026:

• Protocol burn: a portion of REQ is removed from supply whenever a request is stored onchain; and
• Governance: holders can influence the direction of the protocol and the community-owned foundation.

Users do not need to denominate invoices or payments in REQ. A Request Node or service can handle protocol costs while customers pay in stablecoins. This improves usability but weakens any assumption that payment volume creates one-for-one REQ buying pressure.

The burn ties token supply to protocol usage, yet its economic effect depends on the number of requests, burn amount, REQ market price, and whether usage is paid for by sustainable customer revenue. A small burn cannot offset weak demand or large market sales.

REQ Supply and Governance

One billion REQ was created at genesis, with no continuing inflation or scheduled future token unlocks. The original allocation was roughly 49.97% to the public sale, 20.01% to early contributors, 18.01% to the team and advisers, and 12.01% to the foundation.

Burns have reduced total supply below the original one billion. Circulating supply is lower still because foundation, treasury, exchange, and inactive balances may not be liquid. Investors should verify current supply, treasury wallets, burns, and holder concentration on Ethereum.

Governance participation does not confer equity, a claim on processing fees, or ownership of stablecoins moved through the protocol. Practical influence depends on proposal rules, turnout, delegates, foundation powers, and implementation.

Benefits of Request Network

• Working payment infrastructure: the protocol has operated since 2017 and reports more than $2 billion settled.
• Non-custodial design: funds move directly between user-controlled wallets.
• Payment context: structured requests connect onchain transfers with invoices and accounting records.
• Cross-chain abstraction: payers and recipients can use different supported stablecoins and networks.
• Mass payouts: businesses can send many payments through one approval workflow.
• Compliance tools: optional wallet screening occurs before the recipient address is exposed for payment.
• Developer access: APIs, SDK packages, webhooks, and open-source components support integrations and DApps.
• Fixed token supply: no new REQ issuance is scheduled, while network usage causes burns.

Risks to Consider Before Investing in REQ

• Value-capture risk: payments can be made in stablecoins without end users buying REQ.
• Burn-scale risk: token burns may be economically immaterial relative to trading and treasury supply.
• Foundation dependency: product, API, marketing, integrations, and governance depend on the foundation’s execution.
• Cross-chain risk: bridges, swaps, routers, relayers, and host networks can fail or be exploited.
• Stablecoin risk: USDC, USDT, and other assets can depeg, freeze addresses, or face issuer and reserve problems.
• Data-availability risk: Request Nodes, IPFS, Gnosis Chain, indexers, and RPC services must remain available.
• Compliance risk: screening does not eliminate licensing, sanctions, tax, AML, and consumer-protection obligations.
• Irreversibility: mistaken or fraudulent blockchain payments generally lack chargebacks.
• Smart-account risk: Safe modules, signers, permissions, and batch logic can be misconfigured or compromised.
• Competition: payment processors, wallets, stablecoin issuers, exchanges, and other protocols offer overlapping services.
• Governance risk: low turnout and concentrated balances can limit community control.
• Brand confusion: Request Finance results do not automatically accrue to REQ or Request Network.

What Investors Should Monitor

Important indicators include payment and request volume, unique payers and recipients, repeat business customers, revenue-generating API use, request-storage count, REQ burned per period, treasury balances and spending, supported chains and stablecoins, cross-chain completion rates, bridge incidents, wallet-screening adoption, mass-payout volume, Safe integrations, developer releases, governance turnout, and customer retention after the 2026 product relaunch.

Gross payment volume alone is incomplete. Investors should ask how much volume uses the Request protocol, how much is recurring, what fees are collected, and how much REQ is actually removed as a result.

How to Buy Request (REQ)

REQ is available through selected centralized exchanges and Ethereum DeFi markets.

Coinbase – Lists REQ for eligible customers.

Kraken – Offers REQ markets in supported regions.

Binance – Offers REQ trading where available.

Buyers using a decentralized exchange should verify the official Ethereum contract, pool liquidity, price impact, and token approvals.

Request Network Outlook

Request Network has moved beyond its older invoicing-only narrative. Its current product addresses stablecoin acceptance, cross-chain settlement, screening, reconciliation, and mass payouts while keeping funds in user-controlled wallets. The 2026 releases and reported transaction history show an active protocol rather than an abandoned 2017 concept.

REQ offers unusually clear utility through governance and request-linked burns, but the connection is not automatic. Stablecoin volume matters only when it creates stored requests and meaningful token burns or strengthens sustainable protocol economics. Investors should evaluate recurring usage, real fees, burn magnitude, treasury discipline, and cross-chain reliability rather than assuming all crypto payments benefit REQ.