> ## Documentation Index > Fetch the complete documentation index at: https://docs.rheon.io/llms.txt > Use this file to discover all available pages before exploring further. # Amounts and currencies > How amounts are expressed, which side of a quote is fixed, and where to look up the currencies and limits that apply to you. Every product prices money the same way: you send an amount as a string, you say which side of the trade it fixes, and you read the currencies and limits that apply to you from the API rather than from this site. This page is the shared convention; the per-product detail is on the product pages. ## How amounts are written Amounts are **decimal strings, never numbers**. JSON has no safe big integers and a float loses precision on an 18-decimal asset, so a figure that leaves your code as a number can arrive as a different figure. | Side | Unit | Example | | ---------------------------------------------------------------- | -------------------------------------------- | --------------------------------------------- | | Token amounts (stablecoin deposits, the crypto side of a payout) | The token's **smallest unit** | USDC has 6 decimals, so `"5000000"` is 5 USDC | | Fiat amounts (cards, bank transfers, virtual accounts, limits) | The currency's **major unit**, with decimals | `"100.00"` is 100 EUR | Two things follow: * **Keep what you receive as a string.** Precision follows the asset, so an 18-decimal figure comes back as an 18-decimal string. Convert to a number only for display, and only after you have stored the string. * **Check the unit before you compare.** A token amount and a fiat amount for the same transfer are in different units. The quote states both sides; do not derive one from the other. ## Which side of a quote is fixed A quote pins down one side of the trade and lets the other flex: * **Fix what the payer spends** (`exact-in` on a deposit quote; the source amount on a payout quote). Whatever arrives, arrives. The default. * **Fix what has to land** (`target-out` on a deposit quote; the destination amount on a payout quote). We solve backwards for what the payer sends. This is the mode for a set price - an invoice, a checkout total. When you fix what has to land, treat the figure as a **floor**: routes target "at least this much", so a little more than you asked for can arrive. Credit what the status reports as delivered, not what you asked for. The same rule holds on the card rail - credit `deliveredAmount`, never the amount that was charged. Fees sit inside the quoted figures, never on top - the structure is on [Fees](/fees). ## Where to look up currencies and limits Coverage moves faster than any page, so read it at runtime. Which lookup depends on the rail: | Product | Currencies | Limits | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Crypto deposits | [`GET /v1/currencies`](/api-reference/reference/chains-funding-assets-and-fiat-currencies) - source networks, funding assets, and the settlement asset | No fixed ceiling. The path is bounded by live liquidity, which is why a quote can answer `no_route` | | Bank transfers and virtual accounts | [`GET /v1/currencies`](/api-reference/reference/chains-funding-assets-and-fiat-currencies) - fiat currencies, their rails, and who may pay in | [`GET /v1/limits`](/api-reference/reference/per-transfer-ceilings-by-currency-and-rail) - per-transfer minimum and maximum, per currency and rail, plus settlement time | | Card payments | [Card currencies](/api-reference/cards/what-a-card-can-pay-in-and-what-it-buys) - what a card can be charged in and what a purchase settles as; [Card countries](/api-reference/cards/where-a-card-payment-may-not-come-from) for where the card can be from | [Card limits](/api-reference/cards/the-card-payment-window-for-a-pair) - the smallest and largest payment for a fiat and crypto pair | | Payouts | The card and bank lookups above, by shape. Card payouts settle in EUR, GBP and USD only | The same limits endpoints, read with the payout direction | The human-readable version of all of it is on [Coverage](/coverage). Validate an amount against the limit **before** quoting - an amount outside the window fails at execution, which is a worse experience than a disabled button. A rail's limit is not a user's limit. A buyer's own ceiling can be lower than the card rail's, depending on their verification tier, so a payment inside the published window can still be declined for that buyer.