Which instant payment terms turn into acceptance features, and what do they mean?
Most terms in an instant payment rulebook describe how money moves between banks. A few of them become product features once a merchant has to take a payment: the payload that asks for money (a static or dynamic QR code, or a link), the request to pay, the confirmation that funds have arrived, and the back office where the end-of-day close happens. The rest of the rulebook stays inside the bank.
This glossary is for the product team at a merchant's bank. Each entry gives a short definition from the scheme rules, then the acceptance feature it becomes and what that feature is called in miaPOS.
Terms the rail defines
Instant payment
The BIS defines a fast payment as one where the payment message and the final funds reach the payee in real time or near-real time, as close to 24/7 as possible1. The EU sets the limit at ten seconds from the moment the payer presses send2. That also sets the target for acceptance. The seller is standing at the till, so every step around the payment has to run at the same speed.
P2B
Person to business: a payment from an individual to a merchant. A payment between two individuals is P2P. The rail carries both in the same way, and the difference shows up in acceptance, where a P2B payment has to be tied to a merchant, a till and an order. Pix shows how large this flow can get. In September 2026, 46.5% of Pix payments went from a person to a business, and 52% started from a QR code3.
Crediting and settlement
Crediting is the payee's bank posting the funds to the merchant's account. Settlement is how the banks square the amounts between themselves. The merchant only sees crediting, so that is the event an acceptance product should listen for.
Finality
Once the funds are credited, the payer's bank cannot reverse or recall the payment. A refund is a new push payment from the merchant to the buyer, and support for refunds linked to the original payment varies by rail. That makes refunds a separate flow with its own status.
ISO 20022
This message standard lets a payment carry structured data, such as an order reference. miaPOS uses ISO 20022 end to end on MIA, RoPay and SEPA Instant. For acceptance, the messages that matter are pacs.008 (the credit transfer), pain.013 (the request to pay) and camt.054 (the notification that the account was credited).
Terms that become acceptance features
Payload: static QR, dynamic QR, link, NFC tag
A payload is what the payer's app reads to learn whom to pay and how much. A static QR code is printed once and carries the merchant's details, so the payer types in the amount and the seller checks it by eye. A dynamic QR code is generated for each sale and carries the amount and a reference, which lets the credit be matched to the order automatically. A payment link carries the same request into a chat, an invoice or an email. An NFC tag also carries a payload, and it is separate from card tap-to-pay, which runs on the card rail. In miaPOS, payloads are delivered through the app, the web, the API, chat and the cash register. Cash-register integrations carry only the QR payload. On a terminal, the POS API generates a QR code for each sale, cancels it and checks its status.
Request to pay
The payee sends a request, and the payer approves it in their banking app. Invoices and recurring bills are built on it. It exists only where the scheme defines it, so in miaPOS it is rail-dependent and availability varies by market (payment links and request to pay). In the US, FedNow announced a request-for-payment pilot in July 20264.
Confirmation
The seller needs to know that the funds are final and belong to this sale. For online payments, once a payment reaches a final status, the merchant's backend receives an RSA-signed callback from the E-comm API. That signed callback is the source of truth for the payment, and the callback in the browser only redirects the buyer's tab. On a terminal, the seller sees the result on screen. The full flow is in how a checkout learns a payment is confirmed.
Back office
Reconciliation, shift close and refunds are handled here. In miaPOS, every transaction from every channel lands in one merchant back office. The POS API opens and closes shifts and returns a Z-report for each shift. Where the rail supports refunds, each refund is a separate request with its own status.
What stays with the bank
These features do not change who holds what. The merchant's bank is the A2A acquirer: it holds the licence, the scheme membership and the merchant relationship, sets up the terminals and assigns the MCC. miaPOS is the acquiring platform inside the bank's perimeter. It generates the request, receives the confirmation and runs the merchant back office. Your licence, your regulator, your relationship. The roles are set out in What is A2A acquiring.
Read top to bottom, the glossary has two halves. The first is what the scheme already gives every participant. The second is what a bank has to put in front of its merchants before the first coffee is paid for with a QR code.
The rail is done. The counter is not.
Common questions
What is the difference between a static and a dynamic QR code in instant payments?
A static QR code is printed once and carries only the merchant's details, so the payer enters the amount. A dynamic QR code is generated for each sale and carries the amount and a reference. This lets the acceptance system match the incoming payment to the order automatically.
Does accepting instant payments at the point of sale require request to pay?
No. A QR code or a payment link is enough to start a payment at the counter or in a chat. Request to pay adds invoices and recurring bills, and it is only available where the scheme defines it.
When is an instant payment final for the merchant?
The payment is final once the merchant's bank credits the account, and the payer's bank can no longer reverse it. Any refund is a new payment from the merchant to the buyer, handled under the scheme's rules.
Building instant-payment acceptance with your merchants? See how miaPOS works with banks.
For banksSources
- Fast payments: enhancing the speed and availability of retail payments. BIS Committee on Payments and Market Infrastructures, November 2016
- Regulation (EU) 2024/886 on instant credit transfers in euro. Official Journal of the European Union, March 2024
- Pix open data portal. Banco Central do Brasil, accessed October 2026
- FedNow readies cross-border and payment request pilots. PYMNTS, 9 July 2026