01What
Issues an on-chain credential about another account — for example, 'this account passed KYC' — signed by you as the issuer. It becomes valid only after the subject accepts it.
02Why you'd use it
Compliance without paperwork exchange: a licensed verifier checks a customer once, issues a credential, and any app that trusts the verifier can now recognize that customer on-ledger.
03How
- 1Enter the Subject Address — the account the credential is about.
- 2Enter a Credential Type — a short label like KYC (up to 64 bytes; hex-encoded automatically).
- 3Optionally set Expires After in seconds (31536000 = 1 year) and a URI linking to supporting documentation.
- 4Submit as the issuing account and confirm tesSUCCESS.
- 5Tell the subject to run Accept Credential — until then it is pending, not valid.
Watch out
- An unaccepted credential is worthless — verification checks require the accepted flag.
- The credential is public: anyone can see that issuer X attested type Y about subject Z. Keep the details off-chain, linked by the URI.
- The credential object locks 0.2 XRP of owner reserve — yours as issuer until the subject accepts, the subject's after.
- Your attestation is only as valuable as your reputation as an issuer — this is a trust product, not just a transaction.
For example
A licensed KYC provider verifies a customer's documents off-chain, then issues a KYC credential to the customer's account, expiring in one year. Once accepted, a regulated trading platform admits the customer with zero additional paperwork.