Payments
A payment keeps a request to be paid and every step that pays it in one place. Say a merchant asks for 129 USD and lists the stablecoins it accepts. The payer’s institution pays on chain in one step, or through intermediaries such as a liquidity provider, where each step is a transfer like the ones you already send.
Those transfers go through the same checks as any other. Your policies run on the payment as well, and Notabene never holds the funds.
The Payments API is in beta. To take part, contact your Solutions Engineer or [email protected].
Payment flow
Every payment has two institutions, the merchant’s and the payer’s. You can be either one.
- The merchant’s institution creates the payment, with the amount, the assets it accepts and the payer’s institution.
- Notabene sends it to the payer’s institution. Each institution’s policies approve it, flag it for review or reject it.
- The payer’s institution names the asset it pays with. It asks its customer first when its account requires the customer’s approval.
- The payer’s institution moves the money. It pays on chain in one step, or adds a transfer for each intermediary on the way.
- When every transfer has settled, the payer’s institution records the transaction hash, and both institutions see the payment as
Settled.
A payment has the same statuses as a transfer, which Statuses lists.
API or ISO 20022
You can start a payment in two ways.
| Option | You send | You get back |
|---|---|---|
| Payments API | One POST/ call for each payment | The paymentId and the payment’s status |
| ISO 20022 | A pain.001 message, with a payment for each credit transfer instruction in it | A pain.002 status report, with the status of each instruction |
| Option | You send | You get back |
|---|---|---|
| Payments API | One POST /api/v1/payments call for each payment | The paymentId and the payment’s status |
| ISO 20022 | A pain.001 message, with a payment for each credit transfer instruction in it | A pain.002 status report, with the status of each instruction |
Notabene is designed to accept pain.001 and to answer with pain.002, so you can keep the files your payment systems already produce.
Updated 2 days ago
