Wallet addresses

Last reviewed: Oct 5, 2026

Each payment account belonging to an FSP’s customers must have at least one associated wallet address for the account to send and receive payments over Interledger and Open Payments. A wallet address serves as a publicly shareable standardized ID for a payment account.

Wallet addresses are created and hosted in Rhyza. However, the mapping of a wallet address to a customer account stays with the FSP and is never stored in Rhyza’s database tables.

Wallet address requirements

Rhyza must be set up with at least one asset before wallet addresses can be created as each wallet address must have an asset assigned to it.
Wallet address structure is determined by the financial service provider (FSP). Consider whether a chosen naming convention could disclose personal data, such as issuing addresses using a first and last name.
Wallet address URLs are treated as case-insensitive, meaning that both lowercase and uppercase variations of the same address are recognized as identical.

Once the wallet address base (WALLET_ADDRESS_URL) is set, it can’t be changed.

Create wallet addresses

Wallet addresses can be created using the POST /wallet-addresses route via the Admin API. However, an FSP can still create a script for bulk wallet address creation.

Bulk creation via script

One way to batch-create wallet addresses for existing account holders is to write a script that loops through the FSP’s list of accounts.

Ensure the script calls the POST /wallet-addresses endpoint of the Admin API.

Request
Response

// POST /wallet-addresses
{
  "address": "example.wallet.com/sarah",
  "assetCode": "USD",
  "publicName": "Sarah Marshall"
}

Store both id and address. Use id for wallet-entity Admin operations such as key registration, and address for payments, quotes, and payment intents.

{
  "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "address": "example.wallet.com/sarah"
}