Definition and scope
XRPL Credentials Explained addresses a distinct part of compliance, identity, and interoperability. Represent issuer-provided claims that accounts can use in permission-aware ledger features.
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
An XRPL Credential is an issuer-created ledger object linking a subject account to a typed claim. The subject accepts it before use, and expiration or deletion can affect permission-aware protocol features.
- CredentialCreate: verify this field, object, or component against the cited protocol documentation.
- CredentialAccept: verify this field, object, or component against the cited protocol documentation.
- CredentialDelete: verify this field, object, or component against the cited protocol documentation.
- CredentialType: verify this field, object, or component against the cited protocol documentation.
- Issuer: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
An issuer verifies a subject off-ledger, creates a narrowly typed credential, the subject accepts it, and a permissioned service checks issuer, type, acceptance, and expiry.
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
A credential records an issuer's claim; it does not make the claim true or the issuer trustworthy. Consumers must define trusted issuers, evidence, revocation, privacy, and legal processes.
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. Credentials 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.