Payment Methods & Rails

Request to Pay

What Is Request to Pay? Definition and How It Works

Definition

Request to Pay (RtP) is an open banking messaging overlay that allows a payee to send a structured, real-time payment request directly to a payer's banking application or interface. The payer can review the request and choose to pay in full, pay in part, defer, or decline, all within their banking app, before any funds are moved. Request to Pay is a pre-payment communication layer, not a payment rail itself.

How it works

Request to Pay operates as a messaging layer on top of existing instant payment rails. The payee (a biller, merchant, or individual) initiates an RtP message through their bank or payment provider, specifying the amount, due date, reference information, and payee account details. The message is transmitted through a secure messaging network, in the UK, Pay.UK's Request to Pay service; in the EU, the SEPA Request-to-Pay (SRTP) scheme run by the European Payments Council provides similar functionality, to the payer's bank, which presents it in the payer's banking app as an actionable notification.

The payer responds within their banking app. If they choose "Pay in full," their bank executes an instant credit transfer over Faster Payments or SEPA Instant. If they choose "Pay in part," a partial payment is initiated and the remaining balance can be settled subsequently. "Defer" sends a message back to the payee. "Decline" closes the request without payment. All interactions happen within the payer's banking environment; the payer never needs to visit the payee's website or provide payment credentials to a third party.

From a data perspective, RtP messages carry structured information about the underlying obligation: invoice number, description, due date, and line items. This data travels with the resulting payment when it is made, enabling automated reconciliation at the payee's end without manual matching.

Why it matters

Request to Pay addresses three specific pain points in business-to-consumer and business-to-business billing. First, it reduces failed payment rates: payers who lack funds at a billing date can defer or partially pay rather than having a direct debit fail and triggering retry cycles and penalty fees. Second, it reduces dispute rates: the structured, transparent payment request, with clear invoice data, gives payers full context before paying, reducing "I didn't recognise this charge" disputes. Third, it improves reconciliation: structured remittance data in the RtP message and the resulting payment enables automated matching.

For high-value irregular payments, invoices, legal fees, property transactions, RtP provides a secure, bank-authenticated channel for presenting and approving large payments without card limits or the operational overhead of wire transfers.

RtP also provides an audit trail: both the payment request and the payer's response are retained as structured records, supporting dispute resolution and compliance documentation.

With PXP

PXP supports merchants and partners across the payments value chain. To talk through Request to Pay as part of your payment strategy, get in touch with our team.

Talk to a payments specialist

Frequently asked questions

Is Request to Pay the same as a payment link?

No. A payment link is a URL that directs the payer to a hosted checkout page where they enter payment credentials. Request to Pay is a bank-to-bank messaging protocol: the request is delivered directly to the payer's banking application, and the payer approves payment from within their bank account infrastructure without entering credentials anywhere. The payment executes over instant bank transfer rails, not card rails.

Can Request to Pay replace direct debit?

RtP can supplement or replace direct debit for specific use cases, particularly irregular or variable-amount invoices where direct debit mandates are impractical. For regular, fixed-amount recurring payments, Variable Recurring Payments (VRPs) are a closer A2A analogue to direct debit. RtP is most valuable for one-off or irregular billing where the payer needs to review and approve individual transactions.

Where is Request to Pay currently available?

The UK's Pay.UK Request to Pay framework launched in 2020 and is available through participating banks and payment providers. SEPA Request to Pay (SRTP) was launched by the European Payments Council in 2021 and is being adopted across EU markets. FedNow in the US includes a Request for Payment message type, enabling similar functionality for US institutions connected to FedNow.