Definition and scope
Deposit Authorization on the XRP Ledger addresses a distinct part of compliance, identity, and interoperability. Control whether an account can receive unsolicited payments and understand the exceptions.
XRPL includes tools for controlled deposits, issuer compliance, public identity, and cross-network systems. Several features in this category are amendment-dependent or evolving, so every eventual article must verify current Mainnet status and distinguish protocol capability from a particular service's legal obligations. Protocol controls can support a policy but do not establish identity, trustworthiness, regulatory compliance, or legal permission by themselves.
How it works
DepositAuth is an AccountRoot flag that generally blocks unsolicited incoming value. Approved senders or credential holders can be permitted through DepositPreauth, with protocol-defined exceptions for certain payments and account operations.
- DepositAuth: verify this field, object, or component against the cited protocol documentation.
- DepositPreauth: verify this field, object, or component against the cited protocol documentation.
- AccountSet: verify this field, object, or component against the cited protocol documentation.
- preauthorization: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
An account enables DepositAuth, preauthorizes a known counterparty or credential, tests permitted and rejected payments, and monitors authorization-object reserve and expiry behavior.
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
Deposit authorization is a ledger receipt control, not identity verification or legal compliance. Exact exceptions matter, and enabling it can break integrations that expect open deposits.
Protocol controls can support a policy but do not establish identity, trustworthiness, regulatory compliance, or legal permission by themselves.
Current network status
Enabled on XRPL Mainnet. DepositAuth was enabled on XRPL Mainnet in feature responses from both official public servers at review time. Client and service support can still vary.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.