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

# Conversion Payments

> Requests denominated in one currency and settled in another with conversion at payment time

## Overview

Conversion payments let you denominate a request in one currency (for example USD) and collect payment in a different currency (for example USDC or ETH).

This is useful when you want stable invoicing amounts while still collecting crypto on-chain.

## How It Works

<Steps>
  <Step title="Create a request with different invoice and payment currencies">
    Create the request with [POST /v2/request](https://api.request.network/open-api/#tag/v2request/POST/v2/request):

    * `invoiceCurrency`: currency you want to denominate the request in (for example `USD`)
    * `paymentCurrency`: currency you want to receive on-chain (for example `USDC-base`)

    The API stores both values and computes payable amounts using the configured rate source.
  </Step>

  <Step title="Fetch payment calldata and execute payment">
    Use [GET /v2/request/{requestId}/pay](https://api.request.network/open-api/#tag/v2request/GET/v2/request/\{requestId}/pay) to get transaction payloads, then execute on-chain.

    At payment time, the converted amount is applied so the request can be settled in `paymentCurrency`.
  </Step>

  <Step title="Check payment status and conversion details">
    Use [GET /v2/request/{requestId}](https://api.request.network/open-api/#tag/v2request/GET/v2/request/\{requestId}) to inspect status fields such as:

    * `amountInUsd`
    * `conversionRate`
    * `rateSource`
    * `conversionBreakdown` (for multi-payment or partial-payment scenarios)

    When a request is paid in multiple parts, conversion details are returned in the breakdown instead of a single conversion rate value.
  </Step>
</Steps>

## Conversion Behavior

* Single-payment requests can expose a direct `conversionRate`
* Multi-payment or partial-payment requests return detailed `conversionBreakdown`
* Rate source metadata is returned by the status endpoint

## Supported Currencies and Chains

Use [Request Network Token List](/resources/token-list) and [Supported Chains and Currencies](/resources/supported-chains-and-currencies) to choose valid `invoiceCurrency` and `paymentCurrency` pairs.

<Info>
  Conversion behavior depends on the selected currency pair and network support.
</Info>

## Used In

<CardGroup cols={2}>
  <Card title="No-code payment links" href="/use-cases/no-code-payment-links">
    Professional invoices in fiat
  </Card>

  <Card title="Multi-chain checkout" href="/use-cases/multi-chain-checkout">
    Cross-chain e-commerce pricing
  </Card>
</CardGroup>

## API Reference

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