> ## 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.

# Standard Native & ERC20 Payments

> Simple crypto-to-crypto payments using native currencies and ERC20 tokens

## 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

<Steps>
  <Step title="Create request or initiate payout">
    Use either:

    * [POST /v2/request](https://api.request.network/open-api/#tag/v2request/POST/v2/request) for request-first flows
    * [POST /v2/payouts](https://api.request.network/open-api/#tag/v2payouts/POST/v2/payouts) for payment-first flows

    For standard payments, set matching values for `invoiceCurrency` and `paymentCurrency`.
  </Step>

  <Step title="Get payment calldata">
    Fetch payment payload with [GET /v2/request/{requestId}/pay](https://api.request.network/open-api/#tag/v2request/GET/v2/request/\{requestId}/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`
  </Step>

  <Step title="Execute transactions">
    For native payments, execute the payment transaction.

    For ERC20 payments, execute approval first if needed, then execute the payment transaction.
  </Step>
</Steps>

## Supported Networks & Tokens

<CardGroup cols={2}>
  <Card title="Chains & Currencies" icon="globe">
    Choose valid chain/token pairs from the supported currencies and chains catalog.
  </Card>

  <Card title="Token Types" icon="coins">
    Supports native currency payments and ERC20 token payments.
  </Card>
</CardGroup>

Use [Supported Chains and Currencies](/resources/supported-chains-and-currencies) and [Request Network Token List](/resources/token-list) for current availability.

## Used In

<CardGroup cols={2}>
  <Card title="No-code payment links" href="/use-cases/no-code-payment-links">
    Simple crypto invoices via the Dashboard
  </Card>

  <Card title="Programmatic payment links" href="/use-cases/programmatic-payment-links">
    Server-side payment links via the API
  </Card>
</CardGroup>

## API Reference

For full endpoint schemas and examples, see [Request Network API Reference](https://api.request.network/open-api).