Ir al contenido

Payment intents and payments

Última revisión: 13 oct 2026

Esta página aún no está disponible en tu idioma.

A payment intent is a resource the receiver’s financial service provider (FSP) creates to signal that a wallet address is ready to receive funds, before any money has arrived. The sender’s FSP then requests a quote against that payment intent, and creates a payment that references both the quote and the intent to actually send the funds. Both terms are specific to Rhyza’s Admin API. The Open Payments standard describes the same underlying resources using its own terminology, which Rhyza’s public-facing Open Payments APIs continue to use. See Relationship to Open Payments for how the two sets of terms relate.

Payment intents are created via the Admin API’s Create Payment Intent endpoint. The response includes an openPaymentsUrl - the same resource’s address on the public Open Payments API, which a third-party client uses to interact with the payment intent directly, as an incoming payment.

Before creating a payment, the sender’s FSP must first create a quote, which commits to delivering the requested amount to the receiver.

Payments are created via the Admin API’s Create Payment endpoint, referencing both the quote and the payment intent they fulfill.

Payment intents and payments are Rhyza’s Admin API names for resources the Open Payments standard calls incoming and outgoing payments:

Open Payments termRhyza Admin API termCreated at
Incoming paymentPayment intentReceiver’s FSP
Outgoing paymentPaymentSender’s FSP

The two sets of terms describe the same resources from different perspectives. Rhyza’s Admin API terms describe what the resource means operationally for the FSP running the instance: a payment intent is an intention to receive funds, not yet a completed transaction.

See the Glossary for full definitions of all four terms.