RTP Request for Payment: How to Review a Bank-App Payment Request Safely

Separate the request message from the actual transfer

The Clearing House operates the RTP network, which supports immediate bank-to-bank credit transfers and additional messages, including Request for Payment. A biller or supplier can send an RfP through participating financial institutions, and the bank may display it for the payer to review. The request itself does not take money from a bank account simply because it appears in the inbox. The payer can choose to pay or decline, subject to the specific bank's interface. The Clearing House describes RfP as leaving the payer in control of when payment occurs. Treat a request as a prompt to check a claimed obligation, not evidence that the sender is automatically trustworthy.

For example, a utility might request $185 for an invoice. You may see the company name, requested amount, due date and reference. Before approving, compare those details with the actual bill and your known utility account. A scammer may exploit the familiarity of an instant-pay feature by sending an unsolicited request that imitates a real vendor. A bank-branded screen can indicate the message traveled through a supported channel, but it does not prove the payment is owed. Never let the absence of a pending debit convince you that a request is harmless to approve.

Know what happens after the payer approves

A properly executed RTP credit transfer is a different event from the request that preceded it. The Clearing House emphasizes that settlement on its network is final and irrevocable, and the sender generally cannot cancel or recall a submitted payment in the way a scheduled ACH transfer might be stopped before processing. Network messages may request the return of mistaken or fraudulent funds, but an issuer's ability to ask does not give the payer an unconditional right to get them back. This is why bank interfaces should make clear when the customer is viewing a request and when the customer is authorizing the actual credit.

A $900 request mistakenly approved for a fraudulent invoice can result in immediately available money at the receiving institution. Calling the bank minutes later is still essential for possible recovery actions, but it is not a promise of reversal. By contrast, a request left pending or explicitly declined has not itself settled a payment. Verify the status, transfer identifier and recipient before communicating with the merchant. If you schedule payment for a later date, the precise controls may depend on the bank's own service, not on the underlying network's standard instant settlement once the transfer actually occurs.

Authenticate the biller with an independent record

The strongest defense against fraudulent RfPs is matching the request to an independently known obligation. Inspect the legal biller or merchant name, amount, invoice number and bank-provided context. If a familiar contractor suddenly requests a different amount or a new beneficiary, call the number from the original contract—not the number embedded in the request or an email containing a changed invoice. Make a habit of comparing the invoice to a purchase order, service completion or monthly statement. If a request is unexpected, decline it or leave it unapproved while you investigate. An RfP is an invitation to pay, not a legal command to transfer.

Consider a repair company with a genuine $2,400 invoice. A fraudulent RfP for $2,400 may be more convincing than a random $6,000 request because it matches the expected payment size. Ask whether the recipient identifier and invoice reference correspond to the company, not merely whether the number is plausible. Use payment alerts and dual review for significant transfers where the bank offers those features. A legitimate merchant should tolerate a short verification call; pressure to approve 'within five minutes to avoid an account lock' is a strong reason to stop and verify.

Compare RfP with autopay, ACH and card invoices

RTP RfP is not a traditional standing ACH authorization allowing a biller to pull each month's funds automatically. Nor is it a card credential stored with a merchant. It is a payment-request workflow that can be answered with a customer-authorized credit transfer. Some banks integrate payment requests into billing interfaces with reminders or future-date scheduling, but those user experiences do not alter the core distinction. An automatic recurring bill may require a different agreement, and a merchant invoice by email does not necessarily include an RTP payment request at all. Understand which account will send the credit, when it will settle, and what notification will confirm receipt.

Suppose a gym asks to replace a $60 monthly ACH debit with individual instant-payment requests. The household now has to approve each one unless a separate authorized automation service is genuinely established. That provides control but increases the risk of forgetting a due date. It may also change how payment disputes and reconciliation work. If a business receives RfP payments, it should match each settled credit transfer to an invoice and not mark an invoice paid simply because an RfP was delivered. Payment-request status, customer authorization and final credit are three different records.

Respond rapidly when a request or payment is suspicious

If you receive an unrecognized request, capture the displayed details and report it through the bank's fraud channel. Do not contact the purported sender using details supplied only in the suspicious message. If you already approved a mistaken or fraudulent transfer, call the sending bank immediately, supply the transfer reference and request available recovery actions. The Clearing House's RTP documentation includes messages for requesting the return of funds, but a request for return is not a guaranteed reversal. Also consider account security if someone accessed the banking app or initiated transfers without authorization; that situation requires a different fraud review than a knowingly approved but deceitfully solicited payment.

Review the bank's service agreement for RfP and RTP transfer limits, consumer protections and complaint procedures. Retain the invoice, request, approval screen and settlement confirmation. If a bank reports that the beneficiary was credited, ask what additional evidence is available rather than assuming that a merchant has applied the amount to the correct invoice. The decision point with the greatest leverage occurs before you authorize the credit. A few minutes spent confirming a recipient can be more valuable than the network's few seconds of payment speed.

Editorial Verdict

An RTP Request for Payment should be treated like a digital invoice arriving through a bank, not like money already withdrawn or a legally verified bill. Approval is the critical step: once a real-time credit transfer is sent, the network's settlement finality substantially limits ordinary cancellation options. Check the recipient and invoice independently, especially when vendor bank details change or the request feels urgent. A trustworthy bank interface should distinguish 'received request,' 'approved instruction' and 'completed transfer.' Customers benefit from the flexibility of paying when ready, but should never mistake the security of a network message for verification of the sender's underlying claim.

Frequently Asked Questions

Does an RTP RfP automatically debit my bank account?

No. A request message is separate from a credit transfer that the payer may authorize.

Can I cancel an RTP payment after it is sent?

Generally not through ordinary recall; the bank may request return of funds, with no guarantee the recipient will return them.

Can I decline a legitimate biller's request?

You can decline the payment request, but any underlying contractual obligation to pay still needs to be handled separately.

Sources and verification

Last editorial review: 2026-10-12. Product-specific terms and policies can change. The cited material supports the described rules; hypothetical amounts are illustrations, not live bank quotes.

• The Clearing House: RTP RfP Availability
• The Clearing House: RTP Technical Documentation
• The Clearing House: RTP Document Library

Category: Payments · Primary query: RTP request for payment bank app safety · Publication: not yet integrated into the site.