> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nuvera.global/llms.txt
> Use this file to discover all available pages before exploring further.

# Choose Payment Methods

> Select an enabled token and network pair before quoting or creating a payment

Use the crypto reference endpoints before creating a payment quote. Payment methods are the source of truth for enabled token and network combinations. Networks provide metadata about supported blockchains.

You need `CRYPTO_READ`.

## List enabled payment methods

Call `GET /api/v1/crypto/payment-methods` to choose the exact token and network pair for `POST /api/v1/payment/quote`.

```bash theme={null}
TOKEN="<signed-request-jwt>"

curl https://rest-api.nuvera.global/api/v1/crypto/payment-methods \
  -H "x-api-key: $NUVERA_API_KEY" \
  -H "Authorization: Bearer $TOKEN"
```

Each method includes:

| Field             | Use                                                                 |
| ----------------- | ------------------------------------------------------------------- |
| `token`           | Token symbol or identifier to send as `paymentToken`.               |
| `network`         | Network identifier to send as `paymentNetwork`.                     |
| `networkLabel`    | Human-readable network label for your UI.                           |
| `networkFeeUsd`   | Network fee amount represented in USD.                              |
| `contractAddress` | Token contract address for the network.                             |
| `decimals`        | Token decimal precision, useful when showing token amounts exactly. |

Use `token` and `network` together. Do not combine a token from one returned method with a network from another method unless that pair is returned by this endpoint.

## Read network metadata

Call `GET /api/v1/crypto/networks` when you need blockchain metadata for display or reconciliation.

```bash theme={null}
TOKEN="<signed-request-jwt>"

curl https://rest-api.nuvera.global/api/v1/crypto/networks \
  -H "x-api-key: $NUVERA_API_KEY" \
  -H "Authorization: Bearer $TOKEN"
```

Each network includes:

| Field               | Use                                      |
| ------------------- | ---------------------------------------- |
| `id`                | Network identifier.                      |
| `displayName`       | Human-readable network name.             |
| `nativeAssetSymbol` | Native asset symbol used by the network. |

`GET /api/v1/crypto/networks` does not replace `GET /api/v1/crypto/payment-methods` when creating a payment. Use payment methods to decide whether a token and network pair is enabled.

## Use the pair in a quote

Pass the selected values as `paymentToken` and `paymentNetwork` when creating the quote.

```json theme={null}
{
  "fundingType": "CRYPTO",
  "amount": "125.00",
  "currencyCode": "USD",
  "paymentToken": "<enabled-token>",
  "paymentNetwork": "<enabled-network>",
  "paymentSystemId": "<payment-system-id>",
  "customerId": "<customer-id>"
}
```

Partner REST does not expose a payment-system lookup endpoint. Use the payment system ID provided during setup or by Nuvera support.

The later payment creation request uses the quote ID as `paymentQuoteId`. It does not send `paymentToken` or `paymentNetwork` again.

For complete crypto and payment schemas, open the [API Reference](/api-reference/introduction).