Skip to content
Network ExplorerNews All news

NewsGuidesXRP

Blockchain knowledge

XRP Ledger Transaction Fees, Validation and Finality

On the XRP Ledger (XRPL), a submitted transaction is not final simply because a server tentatively accepts it. Its result becomes final when included in a validated ledger, or when the protocol rules establish that it can never be included.

Reference guide · Reviewed · XRP news

Validated ledgers versus provisional results

A server may show a provisional result while validators are working toward agreement. For a trustworthy final outcome, look up the transaction in a validated ledger and inspect its metadata.

A validated transaction with the result code tesSUCCESS succeeded. A validated tec-class transaction did not achieve its intended purpose but still destroyed the transaction fee. A provisional tesSUCCESS is not yet final.

XRPL does not use Bitcoin-style proof-of-work block confirmations. Checking validated status is more useful than waiting for six confirmations.

Why the fee is expressed in drops

One XRP equals one million drops. The normal minimum transaction cost has historically been small, but network load and special transaction types can require higher costs. The actual requirement should be obtained from a current XRPL server.

The transaction cost is destroyed rather than paid to a validator as a reward. Do not confuse that transaction fee with an XRP account reserve or an exchange withdrawal fee; they serve different purposes.

Important fields to inspect

A transaction hash is the unique identifier you use to search. Ledger index indicates the validated ledger that included it, while transaction metadata shows the result code and changes to ledger state.

Many XRP deposits to exchanges or custodial providers require a destination tag in addition to the destination address. If the recipient supplies a tag, verify it carefully before sending; a missing or incorrect tag can complicate account crediting.

What a failed result really means

A temporary error or a tentative failure is not always the final result. Conversely, an initial success message is not enough to prove the payment was completed.

When a transaction is absent from a particular server’s history, it may be missing from that server, pending inclusion or permanently unsuccessful. Consult a server with appropriate ledger history and check LastLedgerSequence where relevant.

A practical verification checklist

Confirm the destination, optional destination tag, transaction hash, validated status, result code and delivered amount as applicable. For token payments or path payments, consult the delivered_amount field rather than assuming the requested amount was delivered.

On a custodial service, the platform’s deposit credit can still be delayed after the on-ledger result is final. Follow the recipient’s published support process if credit has not appeared.

Primary sources

For the latest network settings and exact fees, consult the protocol documentation rather than treating a guide as a live quote.

Educational information only. Not investment or financial advice. Always verify current network conditions with primary sources.