Account Merge operation.
Learn more about the Account Merge operation.
ACCOUNT_MERGE_SUCCESS
Account succesfully merged.
ACCOUNT_MERGE_MALFORMED
The operation is malformed because the source account cannot merge with itself. The destination must be a different account.
ACCOUNT_MERGE_NO_ACCOUNT
The destination account does not exist.
ACCOUNT_MERGE_IMMUTABLE_SET
The source account has AUTH_IMMUTABLE flag set.
ACCOUNT_MERGE_HAS_SUB_ENTRIES
The source account still has non-signer subentries (trustlines, offers, or data entries). Signers are not a blocker — they are removed automatically as part of the merge.
ACCOUNT_MERGE_SEQNUM_TOO_FAR
Source account sequence number is too high.
ACCOUNT_MERGE_DEST_FULL
The destination account cannot receive the balance of the source account and still satisfy its lumen buying liabilities.
ACCOUNT_MERGE_IS_SPONSOR
The source account cannot be merged because it is sponsoring reserves. This covers two cases: it is already sponsoring reserves for other accounts (
numSponsoring > 0), which must be revoked first; or it has an open is-sponsoring-future-reserves relationship earlier in the same transaction, which must be ended with EndSponsoringFutureReserves (there may be no created reserve to revoke in this case). Merely being sponsored by another account is not a blocker.