Digital assets: RLUSD

Ripple USD (RLUSD) is a US dollar-backed stablecoin issued by Ripple.

Supported blockchains

Blockchain	Financial instrument type	`supportedCorridors` value
Ethereum	`ETH_WALLET`	`ETH_RLUSD`

Supported use cases

Use case	Beneficiary type	Originator type
B2B	Business	Business
B2B2B	Business	Business
B2C	Individual	Business
B2B2C	Individual	Business
C2B2B	Business	Individual
C2B2C	Individual	Individual

Beneficiary identity

When creating a beneficiary identity for RLUSD payments, provide the following fields. See Create and manage identities for the API workflow.

The required fields depend on whether the beneficiary is a business or an individual.

Business beneficiary

Applies to B2B, B2B2B, and C2B2B use cases. Submit a business identity.

Field	Required	Type	Constraints
`businessName`	Required	STRING	1–140 characters. The legal name of the beneficiary business.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	1–140 characters.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.
`registration`	Required	ARRAY of OBJECT	Each item: `number` (3–35 characters) and `type` (one of `INCORPORATION_CERTIFICATE`, `TAX_ID`). At least one registration entry is required.

Individual beneficiary

Applies to B2C, B2B2C, and C2B2C use cases. Submit an individual identity.

Field	Required	Type	Constraints
`firstName`	Required	STRING	1–140 characters.
`lastName`	Required	STRING	1–140 characters.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	1–140 characters.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.

Beneficiary financial instrument

When creating a financial instrument for RLUSD payouts, set financialInstrumentType: ETH_WALLET and currency: RLUSD. Provide the following fields in the ethWallet payment rail object. See Create and manage financial instruments for the API workflow.

Field	Required	Type	Constraints
`walletAddress`	Required	STRING	Exactly 42 characters. Pattern: `^0x[a-fA-F0-9]+$`. The beneficiary's Ethereum wallet address.
`cryptoInstitutionName`	Required	STRING	The venue holding the beneficiary's crypto wallet. Supported venues are configured for your account. Contact your Ripple representative for the value to use in this field.

When you retrieve the financial instrument, the response includes the following read-only fields:

network: ETHEREUM
country: ZZ (ISO 3166-1 user-assigned code, used because crypto wallets have no country jurisdiction)
supportedCorridors: [ETH_RLUSD]

Originator identity

When creating an originator identity for RLUSD payments, provide the following fields. The required fields depend on whether the originator is a business or an individual.

Business originator

Applies to B2B, B2B2B, B2B2C, and B2C use cases. Submit a business identity.

Field	Required	Type	Constraints
`businessName`	Required	STRING	1–140 characters.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	1–140 characters.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.

Individual originator

Applies to C2B2B and C2B2C use cases. Submit an individual identity.

Field	Required	Type	Constraints
`firstName`	Required	STRING	1–140 characters.
`lastName`	Required	STRING	1–140 characters.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	1–140 characters.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.

Transaction fields

No additional transaction-level fields are required for RLUSD payments beyond the standard payment object (quote ID, payer identity, beneficiary identity, financial instrument). See Create a payment for the API workflow.

Verifying requirements for your scenario

For the exact fields required for your specific use case and blockchain, use the Payload Schema Utility.