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

# Assets, networks, and payment routes

> Separate what moves, how it moves, and where it arrives.

An asset identifies what you hold or move. A route identifies how it reaches its destination.

## Asset vs. network or payment rail

An **asset** is a currency or token, such as EUR or USDC. A **network** is the blockchain carrying a crypto transfer. A **payment rail** is a banking system used to move funds, such as SEPA for euro payments.

An asset symbol alone doesn't select a route. For example, conversion rules for USDC on Ethereum and Polygon use different network settings and separate inbound addresses.

## Funding method vs. destination

A **funding method** identifies a deposit or withdrawal option. Its metadata can describe the asset, network, payment rail, and requirements. Use the account's available methods and limits to determine whether you can use it.

A **destination** identifies where funds arrive: a bank account or wallet address. Some networks also require a tag or memo to identify the intended recipient. Keep the destination details with their route.

See [Deposits and withdrawals](/tabs/developer-documentation/payments/deposits-and-withdrawals) and [conversion routes](/tabs/developer-documentation/payments/conversion-rules#supported-rails-and-networks).

## Asset amount vs. display value

An asset amount counts units of that asset. A value in a **quote asset** expresses their worth in another asset, such as a display currency. Obviously, changing the display currency doesn't exchange the funds (see the next page for that).

Follow each endpoint's decimal-string and precision requirements. Keep display rounding separate from the amount you send. See [Assets](/tabs/developer-documentation/market-data/assets) for funding and trading precision.