A payment fails with a generic error
An XRP payment on the XRP Ledger fails for one of a few ledger rules: the destination is new and needs 1 XRP, it requires a destination tag, or the payment would dip into your reserve. Other tokens and sends to other networks go through NEAR Intents instead and fail for different reasons.
How it shows up
- Something went wrong when sending
- Transaction failed
- The send spins for over a minute and then errors
- I can't send 0.5 XRP to a new wallet
- Sending XRP to my exchange fails
- It says destination tag required
- It says the amount is too small to activate the recipient
Support can resolve this in chat
Follow the steps below; the support agent can walk you through them.
Check it yourself
- Which applies: what you were sending?
- If XRP, to an XRP Ledger address (it starts with r, or X for some exchanges), continue with step 2.
- If another token (USDC, USDT, BTC and so on), or anything to another network (Base, Ethereum, Solana and so on), read "Sending a token, or to another network, fails".
- Which applies: what the app says when it fails?
- If that the address is invalid, or the address field does not turn green, read "Is the address correct?" below.
- If anything else: a generic error, it spins, or it fails after you confirm, continue with step 3.
- Search the address you were sending to on xrpscan.com.
- If it says "Account not found", continue with step 4.
- If it shows a balance, continue with step 5.
- Look at the amount you tried to send.
- If it is less than 1 XRP, read "Is the recipient account new?" below.
- If it is 1 XRP or more, continue with step 7.
- Search the address you were sending to on xrpscan.com and look at its Flags.
- If they include "Require Destination Tag", continue with step 6.
- If they do not, continue with step 7.
- Which applies: whether you added the destination tag the recipient gave you?
- If no, or not sure, read "Does the recipient require a destination tag?" below.
- If yes, I added their tag, continue with step 7.
- Search your own address on xrpscan.com. From the balance, subtract 1 XRP and 0.2 XRP for each item in Owner Count, and compare what is left with the amount you tried to send.
- If the balance covers the amount, but what is left after the reserve does not, read "Would the payment dip into your reserve?" below.
- If the amount is more than the whole balance, read "Is the amount more than your balance?" below.
- If what is left covers the amount, contact support from Settings, then Support.
Have this ready if you contact support
- What you were sending: XRP, or another token or network
- The recipient address and whether it is an exchange
- The amount you tried to send
- A screenshot of the error
Known issue, tracked by the team as xrp-mobile#198.
Check these four things
Is the recipient account new?
A brand new XRP Ledger address does not exist until it receives at least 1 XRP. A payment of less than 1 XRP to it is rejected by the ledger. Send 1 XRP or more the first time.
Does the recipient require a destination tag?
Exchanges and some services set their account to refuse payments without a tag. Go back, tap Add destination tag and enter the number from their deposit page (some exchanges call it Memo). See Send with a destination tag.
Would the payment dip into your reserve?
You cannot spend the 1 XRP base reserve, and the network fee comes out of your spendable balance too. Use the Max button, which already accounts for both, or send a little less.
Is the amount more than your balance?
The amount is more than all the XRP in your account, so the payment cannot go through. Check it again, and check the decimal separator: depending on your phone's language, a comma or a dot marks the decimals, so 1.000 can mean one or a thousand. The amount screen shows how the app read it before you confirm.
Is the address correct?
The field turns green when the address is valid on the XRP Ledger. Valid is not the same as right: compare the first and last characters with whoever expects the payment.
XRP Mobile takes classic addresses, the ones that start with r. Some exchanges show an X-address instead (it starts with X and packs the address and the destination tag together), and the app reports it as invalid. On the exchange's deposit page, look for the classic address and the destination tag (sometimes called memo), and enter them separately.
Sending another token, or to another network
Only XRP sent to an XRP Ledger address travels on the XRP Ledger. Other tokens, and anything sent to another network, go through NEAR Intents, so the checks above do not apply: see Sending a token, or to another network, fails.
Why the app takes so long to tell you
When the ledger rejects a payment outright, the app currently keeps waiting for confirmation until it times out, then shows a generic error. The team is fixing this so the real reason appears at once. In the meantime, the four checks above cover almost every case.
Not one of the four
Contact support with the details at the top of this page. If a payment shows as sent in Activity but the recipient disagrees, send them the transaction hash from the receipt: it settles the question on the public ledger.
My referral code, follow or points are not working
The Share tab runs the referral campaign: codes, tasks and points. Most problems are timing (verification is not instant) or an account that has not been activated yet. Some are known bugs the team is tracking.
I sent XRP and the recipient says it never arrived
An XRP payment settles in seconds. If it succeeded, the XRP is at the address it was sent to, whoever owns it. The question is whether that is the address the recipient is looking at.