Definition and scope
Understanding XRPL Transaction Result Codes addresses a distinct part of developer guides. Distinguish success, retry, fee-claimed failure, malformed, local, and failure result families.
Reliable XRPL applications do more than submit JSON. They choose appropriate server connections, manage pagination and subscriptions, construct and sign transactions safely, interpret tentative and validated results, and recover cleanly from interruption. Applications must preserve exact amounts, protect signing material, handle retries idempotently, and reconcile against validated ledgers.
How it works
XRPL result families include tes success, tec applied failures that usually claim a fee, ter retry outcomes, tem malformed inputs, tef final failures, and tel local-server conditions.
- tes: verify this field, object, or component against the cited protocol documentation.
- tec: verify this field, object, or component against the cited protocol documentation.
- ter: verify this field, object, or component against the cited protocol documentation.
- tem: verify this field, object, or component against the cited protocol documentation.
- tef: verify this field, object, or component against the cited protocol documentation.
- tel: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
A submission service classifies the provisional engine result, but waits for validated metadata or expiry before choosing success, retry, correction, or operator review.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
The prefix alone is not a complete retry policy. Some codes are provisional at submission, and a tec result included in a validated ledger is final despite not performing the intended action.
Applications must preserve exact amounts, protect signing material, handle retries idempotently, and reconcile against validated ledgers.
Current network status
Network-independent guidance. This guide explains an operational or representational concept. Confirm live server values and service-specific behavior before relying on it in production.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.