TEM Codes

These codes indicate that the transaction was malformed, and cannot succeed according to the Xahau protocol. They have numerical values in the range of -299 to -200. The exact code for any given error is subject to change, so don't rely on it.

Tip: Transactions with tem codes are not applied to ledgers, and cannot cause any changes to the Xahau state. A tem result is final unless the rules for a valid transaction change. (For example, using functionality from an Amendment before that amendment is enabled results in temDISABLED; such a transaction could succeed later if it becomes valid when the amendment is enabled.)



An amount specified by the transaction (for example the destination Amount or SendMax values of a [Payment][]) was invalid, possibly because it was a negative number.


The key used to sign this transaction does not match the master key for the account sending it, and the account does not have a Regular Key set.


The transaction improperly specified a currency field. See [Specifying Currency Amounts][Currency Amount] for the correct format.


The transaction improperly specified an expiration value, for example as part of an [OfferCreate transaction][]. Alternatively, the transaction did not specify a required expiration value, for example as part of an [EscrowCreate transaction][].


The transaction improperly specified its Fee value, for example by listing a non-XAH currency or some negative amount of XAH.


The transaction improperly specified the issuer field of some currency included in the request.


The [TrustSet transaction][] improperly specified the LimitAmount value of a trust line.


The [NFTokenMint transaction][] improperly specified the TransferFee field of the transaction. (Added by the [NonFungibleTokensV1_1 amendment][].)


The [OfferCreate transaction][] specifies an invalid offer, such as offering to trade XAH for itself, or offering a negative amount.


The [Payment transaction][] specifies one or more Paths improperly, for example including an issuer for XAH, or specifying an account differently.


One of the Paths in the [Payment transaction][] was flagged as a loop, so it cannot be processed in a bounded amount of time.


The [Payment transaction][] used the tfLimitQuality flag in a direct XAH-to-XAH payment, even though XAH-to-XAH payments do not involve any conversions.


The [Payment transaction][] included a SendMax field in a direct XAH-to-XAH payment, even though sending XAH should never require SendMax. (XAH is only valid in SendMax if the destination Amount is not XAH.)


The [Payment transaction][] used the tfNoDirectRipple flag for a direct XAH-to-XAH payment, even though XAH-to-XAH payments are always direct.


The [Payment transaction][] used the tfPartialPayment flag for a direct XAH-to-XAH payment, even though XAH-to-XAH payments should always deliver the full amount.


The [Payment transaction][] included Paths while sending XAH, even though XAH-to-XAH payments should always be direct.


The transaction is references a sequence number that is higher than its own Sequence number, for example trying to cancel an offer that would have to be placed after the transaction that cancels it.


The signature to authorize this transaction is either missing, or formed in a way that is not a properly-formed signature. (See tecNO_PERMISSION for the case where the signature is properly formed, but not authorized for this account.)


The Account on whose behalf this transaction is being sent (the "source account") is not a properly-formed account address.


The TransferRate field of an AccountSet transaction is not properly formatted or out of the acceptable range.


The sender of the [DepositPreauth transaction][] was also specified as the account to preauthorize. You cannot preauthorize yourself.


The transaction improperly specified a destination address as the Account sending the transaction. This includes trust lines (where the destination address is the issuer field of LimitAmount) and payment channels (where the destination address is the Destination field).


The transaction improperly omitted a destination. This could be the Destination field of a [Payment transaction][], or the issuer sub-field of the LimitAmount field fo a TrustSet transaction.


The transaction is otherwise invalid. For example, the transaction ID may not be the right format, the signature may not be formed properly, or something else went wrong in understanding the transaction.


The transaction includes a TicketCount field, but the number of Tickets specified is invalid.


The transaction includes a Flag that does not exist, or includes a contradictory combination of flags.


Unspecified problem with the format of the transaction.


The transaction would do nothing; for example, it is sending a payment directly to the sending account, or creating an offer to buy and sell the same currency from the same issuer.


[Removed in: rippled 0.28.0][]


The [Payment transaction][] includes an empty Paths field, but paths are necessary to complete this payment.


The [SignerListSet transaction][] includes a SignerWeight that is invalid, for example a zero or negative value.


The [SignerListSet transaction][] includes a signer who is invalid. For example, there may be duplicate entries, or the owner of the SignerList may also be a member.


The [SignerListSet transaction][] has an invalid SignerQuorum value. Either the value is not greater than zero, or it is more than the sum of all signers in the list.


Used internally only. This code should never be returned.


Used internally only. This code should never be returned.


The transaction requires logic that is disabled. Typically this means you are trying to use an amendment that is not enabled for the current ledger.


The transaction CreateCode field contains more than 256 bytes.

Last updated