Open Payments
Last reviewed: Aug 21, 2026
Rhyza follows the Open Payments standard to enable third-party clients to securely retrieve account information and authorize payments from an FSP’s customers’ accounts with the customer’s consent. The standard describes a uniform way to create and manage grants and resources for incoming payments, quotes, and outgoing payments.
Rhyza provides Open Payments functionality through standalone services that expose the necessary APIs for clients to securely retrieve account information and initiate payments.
A wallet address is a unique URL that identifies an Open Payments-enabled account and is a service endpoint for gaining access to the Open Payments APIs. Rhyza will assign each customer account a wallet address on behalf of the FSP.
Wallet addresses must be a valid HTTPS URL (for example, https://wallet.example.com/alice).
See Wallet addresses for more information.
The Open Payments resource server is a standalone service that exposes the endpoints defined in the Open Payments specification. It acts as a stateless translation layer that validates incoming requests and interfaces with Rhyza’s backend to manage resources like incoming payments, quotes, and outgoing payments.
The Open Payments authorization server is a standalone service that implements the Open Payments authorization server specification. It’s responsible for delegating authorization (via grants) to clients, resolving public keys for authentication, and managing access tokens. Open Payments leverages the Grant Negotiation and Authorization Protocol (GNAP) for delegating authorization.
Learn more about Rhyza’s system architecture
An FSP’s customer uses a third-party app that allows them to create budgets and monitor their spending. To get the information it needs, the app uses the Open Payments APIs to request the customer’s transaction history from their FSP.
An FSP’s customer begins a purchase from an online merchant. Since the merchant has implemented Open Payments, the customer can enter their wallet address into the merchant’s checkout form instead of their credit card details. The merchant’s server uses the Open Payments APIs to communicate with the FSP to set up the payment and get the customer’s consent for the purchase.
Peer-to-peer payments (for example, remittances)
Section titled “Peer-to-peer payments (for example, remittances)”An FSP’s customer uses a third-party remittance app to send money from the US to their family in Mexico. They want their father to receive an exact amount in Mexican pesos, regardless of how much it will cost in USD. Since the app developer has implemented Open Payments, the customer can enter the wallet address for themselves and their father instead of entering bank account details. The app uses the Open Payments APIs to communicate with the customer’s FSP to set up the payment and get their consent for the payment.
We strongly encourage you to familiarize yourself with the Open Payments standard. Extensive documentation is available on the Open Payments website. We recommend you start by reviewing all the pages in the Intro to Open Payments section. Here are a few links to get you started.