N/ANight Ash
Back to collection
Research

RLUSD Access Through an Interface and an API

Minting, redemption and payment authorization remain distinct.

Published Updated
Two people inspect a sealed gray parcel on a harbor promenade.
Technical illustration

Ripple's institutional RLUSD material describes access, minting, redemption and management through both a user interface and an API. A shared account surface does not make these the same custody event. Minting and redemption need distinct records, while a proposed payment is not yet an authorized or settled payment. An automated client needs a defined recipient scope, spending ceiling and expiry; repeated API calls must not release value twice. Final state and recovery responsibility need to be visible before another instruction compounds an error.

References