Identify the source of each amount before comparing it
| Amount or field | What it describes | Use in the funding review |
|---|---|---|
| Ledger XRP balance | The XRP held by the account in the selected ledger state | Do not automatically enter it as a sendable amount |
| Base and owner reserve requirements | Account funding requirements, including reserve-bearing objects | Review the current account-specific requirement |
| OwnerCount | An account field contributing to the owner reserve calculation | Not a number of XRP tokens or a withdrawal fee |
| Hosted platform withdrawal review | The platform’s current rules and amount it will send | Compare the actual outgoing payment with the exchange input |
An old base-reserve note may not describe the whole account
The XRP Ledger reserve documentation distinguishes a base reserve from an owner reserve linked to objects owned by the account. The AccountRoot reference describes OwnerCount as contributing to that owner reserve. A remembered base-reserve value alone therefore does not establish the available payment amount for an account with additional reserve-bearing state.
Use the current network requirements and the actual wallet review. This page does not freeze a numerical reserve value into an exchange instruction or assume that every object is treated identically in every case. Protocol exceptions and an account’s current state belong in that review. A lower maximum amount is not, by itself, evidence that the exchange retained the difference.
Prepare the input from the sender’s actual payment workflow
- Establish whether you control a ledger account or a platform balance
For a personal account, use the wallet’s current account state and payment review. For a custodial holding, inspect the platform’s withdrawal calculation and restrictions. Your platform balance is not necessarily an independent ledger account with a reserve you can calculate yourself.
- Read the amount reaching the issued recipient
Compare the proposed XRP payment with the exchange instruction, including any destination tag actually issued. Keep the transaction cost and any platform withdrawal charge identifiable. Do not silently reduce or increase the order’s input because the top-level balance looked larger.
- Resolve a shortfall before sending
If the available amount cannot fund the intended input, review the order amount or the source workflow before payment. There is no need to delete the XRP account, remove trust lines or alter owned objects as a routine exchange step. Such account-management decisions require their own review.
Keep the source remainder separate from the ETH payout
A reserve-related remainder concerns the account funding the XRP leg. The amount of ETH received belongs to the quote and payout record. Do not label the XRP left in a source account as ETH withheld by the exchange. Compare the actual paid amount and the output instruction instead of mixing those two balances.
If a payment has already been attempted, preserve its network reference and status. Investigate that transfer before making a second one. An unsuccessful send, an amount blocked in the wallet review and a validated XRP payment are different states; only the actual payment record can establish what left the account.
Questions about spendable XRP input
- Can I subtract only an old base-reserve value from every XRP balance?
- Not reliably. Current reserve requirements include account-specific owner state and protocol rules. Use the present wallet payment review.
- Is OwnerCount the amount of XRP I can sell?
- No. It is an account field contributing to the owner reserve requirement, not a token quantity or an exchange withdrawal charge.
- Must I delete my XRP account to make this exchange?
- Account deletion is not a routine funding step. Prepare an ordinary payment from the actual available amount and review account-management decisions separately.
XRP Ledger account documentation
Reviewed: