Why do instant payments push instead of pull?

Everything else follows from the direction of the request

With a card the merchant pulls. The payer hands over credentials, or a token standing in for them, and the merchant's acquirer asks the issuing bank for the money. Because the merchant starts the transaction, the cardholder can dispute it afterwards with their issuer.

With an instant payment the payer pushes. The BIS Committee on Payments and Market Infrastructures defines a fast payment system as one in which "the transmission of the payment message and the availability of the final funds to the payee occur in real time or near-real time and on as near to a 24/7 basis as possible"¹. The EU wrote a figure into law: ten seconds from the moment the payer confirms the payment².

Three operational consequences follow.

No card credentials sit on the merchant side, so the type of fraud that relies on stolen card details does not apply there.
Once the funds have arrived, the payment is final. There is no chargeback process behind it, and a refund is a new payment back to the payer, initiated by the merchant.
Payer protection moves upstream, into the payer's bank and the scheme rules. Verification of Payee before sending has been mandatory in the euro area since October 2025². UK banks must reimburse victims of authorised push payment scams, and 88% of in-scope losses were repaid between October 2024 and March 2026, mostly within five business days³.

What acceptance has to supply instead

A rail moves money between banks. A merchant needs a working checkout, and the distance between the two is measurable. Mexico launched its QR payment product CoDi in 2019 on a fast, modern rail; fourteen months later it had processed just over a million transactions, far short of the central bank's target, with an analyst at Moody's observing that "very few small stores have implemented it"⁴. FedNow settled around 5 million payments worth $275 billion in the second quarter of 2026, an average of roughly $55,000 each, which points to business and treasury transfers⁵. Even in Brazil, where Pix is the most used means of payment⁶, Pix was about 7% of the transactions running through card terminals in 2025⁷.

What the push model requires at the acceptance layer is a short, concrete list:

a way to ask for money: a QR code, a payment link, or a request sent to the payer;
a state the merchant system can read: created, paid, expired, cancelled;
a confirmation solid enough to release goods against;
reconciliation, so a payment is matched to an order, a shift and a till;
a return path, where the scheme provides one.

In September 2026, 52% of Pix payments started from a QR code⁸. Payments from a person to a business were 46.5% of the total⁸. Refund windows belong to the scheme: Stripe documents 90 days for Pix⁹ and 60 days for UPI¹⁰, with disputes raised only for fraud.

How miaPOS assembles it

At the counter, the POS API carries that sequence. A sale generates a QR for that sale, the terminal checks its status or cancels it, the transaction can be read back with its receipt, and the shift opens and closes with a Z report. Returns have their own endpoints, with reason codes and a status to check, where the scheme provides a return path. Hardware POS terminals and SoftPOS apps use the same interface, and cash register software can invoke miaPOS through an Android Intent on the same device, a Windows CLI on the till PC, or the REST API.

Online, the same shape appears with the browser kept out of the trust path. The merchant's backend creates the payment and fixes the amount server-side; the browser holds only an opaque payment identifier, enough to render the QR on desktop or a deep-link button on mobile. The source of truth for the payment is the callback on the merchant's backend: the body carries the result object and an RSA signature over it, and the merchant verifies that signature with the public key published by the API before fulfilling the order. The success callback in the browser redirects the buyer's tab and does nothing else.

Request-to-pay and refunds work where the underlying scheme provides them. The rest is constant across channels: terminal, SoftPOS, payment link, chat, cash register and online checkout all land in one merchant back office.

The roles are worth stating plainly, because a push rail distributes them differently from card acquiring. The payer authorises the payment in their own bank's app. The scheme moves the money. The merchant's bank is the acquiring participant in that scheme and holds the licence, the membership and the merchant relationship. miaPOS is the acceptance software inside that bank's perimeter: it issues the request, receives the confirmation and runs the merchant back office. The industry term for that work is A2A acquiring.

Common questions

Can a merchant pull an instant payment from a customer's account?

No. On a push rail the payer's own bank sends the money after the payer authorises it in their banking app, so the merchant cannot initiate the debit. The merchant's side of the flow is to issue the request, as a QR code, a link or a request sent to the payer, and to wait for the confirmation.

What replaces chargebacks on an instant rail?

An instant payment that has settled is final, so there is no card-style dispute process behind it. Refunds are new payments back to the payer, initiated by the merchant, and the window is set by the scheme: Stripe documents 90 days for Pix⁹ and 60 days for UPI¹⁰. Payer protection sits with the payer's bank and the scheme rules, through name checks before sending and, in some markets, reimbursement duties.

What does a merchant system need before it releases the goods?

A confirmation it can trust, tied to the specific order. At the counter that is the terminal reading the status of the QR it generated for that sale; online it is the signed callback on the merchant's backend, verified against the published public key before the order is fulfilled.

A2A acquiring with miaPOS

Building instant-payment acceptance with your merchants? See how miaPOS works with banks.

For banks

Sources

Written by Ghenadie Cernei, Founder, Finergy. 14 October 2026.

Why do instant payments push instead of pull?

Everything else follows from the direction of the request

What acceptance has to supply instead

How miaPOS assembles it

Common questions

Sources

Read next