Stablecoin transactions are now
simple, global, safe and decentralized

You connect your wallet and set one preferred settlement chain and stablecoin. Request Network generates a payment link for each transaction. Your payer opens the link, connects their wallet, and pays with the stablecoin they hold. Funds move directly from their wallet to yours: Request Network never holds them. You receive the exact amount you requested, with a transaction reference attached so you know what was paid.

You can reach 95% of the global stablecoin supply through the most common EVM chains (Ethereum, BNB Chain, Base, Polygon, Arbitrum, Optimism) and Tron. Payers can pay in USDC or USDT from any supported chain. You set one preferred settlement destination, the chain and stablecoin you want to receive, and the protocol routes the payment to it automatically. Neither side needs to know which chain the other is using.

No. Request Network is a protocol, not a payment service provider. It does not hold funds, process money on your behalf, or act as an intermediary in the payment flow. Because funds move directly between wallets, there is no custodial layer, so there is no VASP registration or payment institution licence to obtain. This is a structural property of how the protocol works.

No. Funds move directly from your payer's wallet to yours. Request Network has no access to them at any stage. The protocol facilitates the transaction; ownership stays with you throughout.

There is a flat fee of 0.9% per transaction, charged on transaction volume and capped at $500 per payment regardless of size. There are no setup fees, monthly fees, service surcharges, or minimum volume requirements. When the recipient enables wallet screening, it is included in the 0.9% at no extra cost. The 0.9% fee is the same on every chain and you never need to hold gas. On EVM chains gas is included. On Tron, the payer pays a flat $3.99 per transaction to cover the Tron network cost. Operators and platforms building on Request Network can add their own markup on top of the base rate without taking custody of funds.

Wallet screening is an optional layer the recipient can turn on per payment link. The screening comes at no extra cost to you. It is already included in the 0.9% of the transaction volume. When it is active, the paying wallet is checked by Hypernative against sanctions, money-laundering, and terror-financing signals before your wallet address is shown. If the wallet fails the check, your address is never revealed and funds never move. If it passes, the payment proceeds as normal. A screening report is stored for every screened payment, which you can share with your off-ramp provider when you convert to fiat.

Yes. Request Network provides an API that generates payment requests programmatically. You can integrate it into any web application, e-commerce platform, or back-office workflow. Payment status is returned by webhook on confirmation or failure. Each payment carries a reference you set, so reconciliation is automatic. There is also a no-code dashboard if you want to create payment links manually without writing any code.

Yes. The payment page interacts only with Request Network's smart contracts. It cannot be altered, spoofed, or redirected to a malicious contract. What your payer sees is exactly what you configured, even if Request Network itself were attacked.

Yes. Recurring payments use a single authorisation: your payer signs once, and scheduled payments then execute automatically at daily, weekly, monthly, or yearly intervals, with cancel, pause, and unpause supported. You can also create a payment link per billing cycle and automate it through the API. Webhook notifications confirm each payment as it arrives.

They cannot. The protocol enforces exact amounts: a payer can only complete a payment for the precise figure in the payment request. Overpayments and underpayments are both blocked by design.

No. You set one preferred settlement destination: the chain you want to receive on and the stablecoin you want to receive in. Your payer chooses the chain and currency they pay from. The two can be completely different. If you want USDC on Base and your payer pays USDT on Polygon, the protocol routes the payment automatically, and any bridging fee is shown to the payer upfront before they confirm. Neither side needs to manage wallets on multiple chains.

No. Each payment link locks the moment a payment is initiated, before the transaction confirms on-chain. If your payer refreshes the page or tries again while the funds are in transit, nothing happens: the link stays locked until the payment settles. You receive one payment per link, with its reference attached, and there is never a duplicate to refund.