Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.request.network/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Standard payments are same-currency payments where invoiceCurrency and paymentCurrency match. Use this type when you want straightforward crypto settlement without conversion or crosschain routing.

​
Native Currency Payments

Pay with network native currencies (for example ETH on Ethereum-compatible networks). Characteristics:
  • no ERC20 allowance step
  • one payment transaction in most cases
  • payer covers gas in native token

​
ERC20 Token Payments

Pay with ERC20 tokens such as USDC, USDT, and DAI (depending on chain support). Characteristics:
  • may require approval before payment
  • API can return approval calldata when needed
  • payment then executes with token transfer transaction(s)

​
How It Works

1

Create request or initiate payout

Use either:For standard payments, set matching values for invoiceCurrency and paymentCurrency.
2

Get payment calldata

Fetch payment payload with GET /v2/request//pay when using request-first flow.The response includes:
  • payment transaction calldata
  • approval calldata when token approval is required
  • metadata such as stepsRequired and needsApproval
3

Execute transactions

For native payments, execute the payment transaction.For ERC20 payments, execute approval first if needed, then execute the payment transaction.

​
Supported Networks & Tokens

Chains & Currencies

Choose valid chain/token pairs from the supported currencies and chains catalog.

Token Types

Supports native currency payments and ERC20 token payments.
Use Supported Chains and Currencies and Request Network Token List for current availability.

​
Used In

No-code payment links

Simple crypto invoices via the Dashboard

Programmatic payment links

Server-side payment links via the API

​
API Reference

For full endpoint schemas and examples, see Request Network API Reference.