What Is Request to Pay? Asking for Money, the Smart Way (2026)

Request to Pay (RtP) is a messaging service that lets a payee send a structured, digital payment request to a payer, who can accept, schedule, decline or query it. It is not a payment in itself: once accepted, the request triggers a credit transfer, usually instant, prefilled with the exact amount and reference.

RtP matters in 2026 because the rails underneath it are finally in place. Instant euro transfers are mandatory for banks in the euro area, the European scheme has been simplified, and the two US instant networks both carry payment requests. India’s decision to switch off peer-to-peer collect requests also shows the other side: a request is only as safe as the checks around it.

What is Request to Pay?

Request to Pay sits between invoicing and payment. The payee sends a request with all the data needed to pay. The payer stays in control and pushes the money, which is the key difference with direct debit, where the payee pulls funds from an account on the basis of a mandate.

• Versus an invoice: the request arrives where the payer pays (a banking app, an e-invoicing portal), and paying takes one click instead of copying an IBAN and a reference.
• Versus direct debit: no standing mandate, no surprise debit, and the payer can ask for more time or decline.
• Versus a card on file: no card expiry, no interchange, but also no chargeback.

Watch the acronym. In the US, “RTP” is the name of The Clearing House’s real-time network, and many people use RTP for real-time payments in general. Requests on those networks are called “Request for Payment” (RfP). For the payment rail itself, see our instant payment decoding.

How Request to Pay works

1. The payee creates a request through its RtP service provider: amount, due date, expiry, reference, and sometimes the invoice itself.
2. The request is routed to the payer’s RtP provider, typically the payer’s bank, and appears in the banking app or e-banking portal.
3. The payer reviews it and responds: accept and pay now, accept and pay on the due date, decline, or (depending on the scheme) pay part of the amount.
4. On acceptance, a credit transfer is sent, ideally an instant one, prefilled with the request data. In the euro area, the payer’s bank first runs a Verification of Payee check.
5. The payee receives a status message and the funds, matched to the original request through its reference.

Request to Pay in numbers (2026)

• SEPA Request-to-Pay (SRTP): by November 2025, three participants and three technical solution providers had been homologated, the first homologation wave under a simplified process was set for 1 February 2026, and some national communities planned to join in 2026.
• The euro rails are ready: instant transfers reached 35.6% of SEPA credit transfer volumes in Q1 2026.
• FedNow: a Request for Payment message costs $0.01 in the 2026 fee schedule, a fee the Federal Reserve set to be paid by the requestor.
• RTP network: more than 1,100 financial institutions were live in February 2026, and RfP is offered by large banks including Bank of America, J.P. Morgan, PNC and Wells Fargo.
• India: NPCI stopped peer-to-peer collect requests on UPI from 1 October 2025 to fight fraud, after a ₹2,000 cap per request had not been enough.

Request to Pay around the world

Europe: the SEPA Request-to-Pay scheme

The European Payments Council runs the SRTP scheme. It defines the messages and rules, not the payment, which can be any SEPA transfer. Rulebook version 4.0, published in November 2024, simplified the scheme and lowered entry barriers. The EPC Board decided against a central fee: it favors a “federated” model in which local communities set their own business models and fees, and plans to reuse the Verification of Payee directory for routing. In June 2026, the Euro Retail Payments Board saw potential for greater SRTP uptake, especially for public administration payments.

United States: Request for Payment on RTP and FedNow

Both instant networks carry RfP messages. Use cases discussed by the industry include bill pay, real estate closings and earned-wage access. Adoption depends on each bank exposing RfP to its customers, so coverage is still narrower than for basic instant transfers.

India: the limits of “collect”

UPI’s collect feature was an early, large-scale form of request to pay. Fraudsters used it to send fake requests that victims approved by mistake. Since October 2025, all peer-to-peer UPI payments are initiated by the payer, for example by scanning a QR code. The lesson for every market: requests from unknown senders need strong identification and clear warnings.

Request to Pay: what changes for PSPs, PayFacs and platforms

Collections without card costs

RtP fits bills, insurance premiums, rent, B2B invoices and public fees: payments where the payer knows the payee and the amount is known in advance. For PSPs, it is a way to offer A2A collection with better data than a plain transfer and lower cost than cards.

Reconciliation by design

Each request carries a unique reference that comes back with the payment. That removes manual matching of transfers to invoices, which is one of the main pains of bank transfers today. Partial payments and “pay later” answers must be handled in the receivables logic.

Fraud and trust

A request can be faked. PSPs onboarding billers must verify who is allowed to send requests (KYB), show the verified payee name to the payer, and monitor request volumes. Because the resulting payment is a push transfer, it is final: there is no chargeback, only a refund by the payee.

RtP, recurring payments and checkout

RtP is a one-off approval. For payments that repeat with changing amounts, the UK uses variable recurring payments and Brazil uses Pix Automático. At checkout, RtP can also appear as a QR code or a push notification. Each of these methods needs its own flow, status codes and fallback, which is why they belong in a payment orchestration layer next to cards and wallets.

Pricing is local

With no central fee in the SEPA scheme, pricing will differ by country and provider. Platforms serving several European markets should expect a patchwork of RtP offers for some time.

NORBr provides the white-label payment infrastructure to route, onboard, pay out and analyze, under your own brand.

Is Request to Pay worth it in 2026?

For billers with recurring invoices, yes: RtP cuts reconciliation work and late payments, and rides on instant rails that now exist everywhere in the euro area and the US. For e-commerce checkout, it is still early. Adoption in Europe depends on banks joining the SRTP scheme and on local pricing. Payment providers that build request flows with strong sender verification today will be ready when volumes arrive.