Request

Request Network is an open-source payment protocol designed to let people and businesses request, accept, and send cryptocurrency directly between wallets. Its current product documentation describes payment settlement across EVM-compatible networks and Tron, while the public SDK repository describes the underlying system as a decentralized network originally built on Ethereum.

The protocol is exposed through three practical products: a no-code Dashboard for payment destinations and links, a hosted Secure Payment Page at pay.request.network, and an API for programmatically creating destinations, payment links, payouts, and webhooks. Payment references and status callbacks are intended to make on-chain payments easier to reconcile with invoices and business records.

REQ is the native ecosystem token. The official token page describes two primary functions: governance participation by REQ holders and a burn mechanism associated with requests stored on-chain. Request Network says it has been live since 2017 and is stewarded by a community-owned foundation; Request Finance is a separate company that built a product on the protocol.

Crypto payments are fragmented across chains, tokens, wallets, and payment interfaces. A payer may hold USDT on one network while a recipient wants USDC on another, and businesses can otherwise be forced to manage multiple wallets, manually reconcile transaction hashes, or reject customers who cannot use the recipient's exact chain and currency.

Traditional crypto payment processors can introduce custodial exposure, account freezes, intermediary risk, and higher processing costs. Request Network's stated approach is to keep funds moving wallet-to-wallet, attach payment references, route supported cross-chain payments, and optionally screen a payer wallet before the recipient address is revealed or funds move.

A recipient connects a wallet, chooses a settlement chain and stablecoin, and creates a payment request or hosted link. The payer opens the link, connects a supported wallet, and selects an eligible source currency and network. The payment page enforces the requested amount, so underpayments and overpayments are not accepted.

When source and destination differ, Request Network's payment flow can route the payment through supported bridge and swap infrastructure so the recipient receives the configured settlement asset. The documentation and homepage describe support for common EVM networks and Tron, with USDC and USDT as the principal payment currencies. The protocol is non-custodial: the official description says it does not hold user funds, and the recipient receives the settlement directly in its wallet.

Integrators can create payments through the API and receive webhook notifications when payments settle or fail. Each payment can carry a merchant-defined reference for reconciliation. Optional wallet screening checks the payer before the recipient address is disclosed; the homepage says screened payments can be checked against sanctions, money-laundering, and terror-financing signals, with the screening report retained for the payment.