EscrowCancel
Return funds from an expired escrow to its sender.
Example EscrowCancel JSON
{
"Account": "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn",
"TransactionType": "EscrowCancel",
"Owner": "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn",
"OfferSequence": 7,
}EscrowCancel Fields
In addition to the common fields, EscrowCancel transactions use the following fields:
| Field | JSON Type | Internal Type | Description |
|---|---|---|---|
Owner | String - Address | AccountID | The account that funded the escrow payment. |
OfferSequence | Number | UInt32 | Transaction sequence (or Ticket number) of EscrowCreate transaction that created the escrow to cancel. |
Any account may submit an EscrowCancel transaction.
- If the corresponding EscrowCreate transaction did not specify a
CancelAftertime, the EscrowCancel transaction fails. - Otherwise the EscrowCancel transaction fails if the
CancelAftertime is after the close time of the most recently-closed ledger.
Error Cases
Besides errors that can occur for all transactions, EscrowCancel transactions can result in the following transaction result codes:
| Error Code | Description |
|---|---|
tecNO_AUTH | The transaction failed because authorization requirements were not met. For example, the issuer requires authorization and the sender is not authorized. |
tecNO_LINE | The sender does not have a trust line with the issuer. For Trust Line Tokens only. |
tecNO_ENTRY | The sender does not hold the MPT. |
tecINSUFFICIENT_RESERVE | Unable to create a trust line or MPToken due to lack of reserves. |