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

# Fee Breakdowns

> Where to read fee details in routes, payment search, and status responses

## Overview

Fee breakdowns provide itemized cost details returned by reconciliation and routing endpoints.

Use this page to understand where fee data appears and how to consume it reliably.

## Where Fee Breakdowns Appear

### Payment Routes

* Endpoint: [GET /v2/request/{requestId}/routes](https://api.request.network/open-api/#tag/v2request/GET/v2/request/\{requestId}/routes)
* Fields include:
  * `fee`
  * `feeBreakdown[]`

Route-level fee breakdowns are useful before execution (quote/comparison stage).

### Payment Search

* Endpoint: [GET /v2/payments](https://api.request.network/open-api/#tag/v2payments/GET/v2/payments)
* Field includes:
  * `fees[]`

Payment-level fee breakdowns are useful after execution (reconciliation/reporting stage).

### Request Status (when applicable)

* Endpoint: [GET /v2/request/{requestId}](https://api.request.network/open-api/#tag/v2request/GET/v2/request/\{requestId})
* May include fee information in enriched status outputs.

## Fee Types

Common fee `type` values in API responses:

* `protocol`
* `gas`
* `platform`
* `crosschain`
* `crypto-to-fiat`
* `offramp`

## Route Fee Stages

For route responses, `feeBreakdown` can include stage-level attribution:

* `sending`
* `receiving`
* `proxying`
* `refunding`
* `overall`

## How to Use in Reconciliation

<Steps>
  <Step title="Store raw fee objects">
    Persist fee arrays exactly as returned (`fees[]` or `feeBreakdown[]`) before deriving reporting values.
  </Step>

  <Step title="Normalize by type and provider">
    Group by `type`, `provider`, and currency to build accounting-friendly summaries.
  </Step>

  <Step title="Keep idempotent processing">
    When replaying jobs or webhooks, deduplicate with stable identifiers (`requestId`, `paymentReference`, tx hash, delivery IDs).
  </Step>
</Steps>

## Example Shapes

### From routes endpoint

```json theme={null}
{
  "fee": 0.0021,
  "feeBreakdown": [
    {
      "type": "gas",
      "stage": "sending",
      "provider": "request-network",
      "amount": "0.0012",
      "currency": "USDC"
    },
    {
      "type": "crosschain",
      "stage": "overall",
      "provider": "lifi",
      "amount": "0.0009",
      "currency": "USDC"
    }
  ]
}
```

### From payments endpoint

```json theme={null}
{
  "fees": [
    {
      "type": "protocol",
      "provider": "request-network",
      "amount": "0.05",
      "currency": "USDC"
    },
    {
      "type": "platform",
      "provider": "request-network",
      "amount": "0.50",
      "currency": "USDC"
    },
    {
      "type": "gas",
      "provider": "ethereum",
      "amount": "0.002",
      "currency": "ETH"
    }
  ]
}
```

## Related Pages

<CardGroup cols={2}>
  <Card title="Platform Fees" href="/api-features/platform-fees">
    Configure integrator fees with feePercentage and feeAddress.
  </Card>

  <Card title="Protocol Fees" href="/api-features/protocol-fees">
    Understand protocol-level fee policy, rate, and cap.
  </Card>
</CardGroup>

## API Reference

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