# FedNow & RTP Request for Payment (pain.013) B2B Guide

> Automate B2B accounts receivable and consumer bill-pay using FedNow and TCH RTP ISO 20022 pain.013 Request for Payment (RfP), pain.014 responses, and pacs.008.

Canonical: https://payclearledger.com/rails/fednow-rfp-request-for-payment-pacs008-b2b-invoice-settlement
Last updated: 2026-11-14T19:39:37.821Z

**Publication:** PayClear Ledger
**Category:** Instant Payment Rails Fednow Sepa Pix
**Published:** 2026-11-13T13:35:25.915Z
**Author:** Claire Beaumont, CAMS, CTP (Certified Anti-Money Laundering Specialist (CAMS), Certified Treasury Professional (CTP))
**Reviewer:** Not recorded

## Answer-first summary

Combining the billing precision of direct debit with the zero-NSF finality of credit push, ISO 20022 Request for Payment (pain.013 -> pacs.008) eliminates 2.9% card MDR and ACH R01/R10 returns.

## Key takeaways

- ISO 20022 Request for Payment (pain.013 -> pain.014 -> pacs.008) on FedNow and TCH RTP delivers a verified digital invoice into the payer’s banking app that converts 1-click approval into an irrevocable credit push.
- Because the payer’s bank verifies good funds before sending pacs.008, RfP eliminates ACH R01 NSF bounces and 60-day R10 clawbacks—enabling instant T+0 buying power on me-to-me wallet top-ups.
- To prevent phishing spam, originating FIs strictly vet corporate/commercial RfP billers under network warranty rules and provide 1-click payer block/opt-out controls.
- Echoing the exact <EndToEndId> and structured invoice metadata from pain.013 into pacs.008 achieves >99.9% zero-touch ERP accounts-receivable reconciliation.

## Related financial entities

- **BCBS 248 Intraday Liquidity Management Framework** (BCBS-248) — license: Supervisory monitoring framework establishing quantitative metrics for banks and payment service providers to measure and manage intraday liquidity risk.
- **Committee on Payments and Market Infrastructures (CPMI)** (CPMI) — company: Global standard-setter for payment, clearing, and securities settlement systems operating under the Bank for International Settlements.
- **ISO 20022 pacs.008 Customer Credit Transfer Standard** (PACS-008) — product: Universal financial industry message scheme defining XML data structures for executing customer credit transfers across commercial banks, RTGS networks, and payment systems.

## Analysis

Corporate Accounts Receivable (`AR`) directors in the United States have long hated a binary trade-off: **Corporate Credit Cards** settle predictably while devouring **`2.4%–3.2%` interchange MDR** (`USD 28,000 lost on a single USD 1M wholesale invoice!`), whereas **ACH Direct Debits (`CCD/WEB`)** cost pennies yet expose billers to **`R01 Insufficient Funds` bounces 2–3 days later and `R10 Unauthorized` revocations up to 60 days later**! **Request for Payment (`RfP`)** across both **FedNow** and **TCH RTP** resolves both flaws simultaneously by delivering a structured **[ISO 20022 `pain.013` Creditor Payment Activation Request](/corridors/iso-20022-pacs008-standard)** directly inside the payer’s banking portal—converting 1-click buyer approval into an **irrevocable, pre-matched `pacs.008` instant credit push**!

## Three-Message ISO 20022 RfP Choreography: pain.013 -> pain.014 -> pacs.008

Understand clearly: **an RfP is NOT a debit pull**—it never touches the payer’s balance without explicit payer authorization! Trace the exact three-message loop across corporate banks (`such as` [Goldman Sachs](/remitters/gs), [Bankers’ Bank](/remitters/bankers-bank), `and` [American Savings Bank](/remitters/american-savings-bank)): **(1) `pain.013` (`Creditor Payment Activation Request`)**: Biller’s FI sends a structured payment request (`carrying invoice number, line-item remittance data / URL link, exact due date, expiry timestamp, and flags allowing or forbidding partial/modified payment amounts!`) over FedNow or RTP (`wholesale network fee: just USD 0.01!`); **(2) `pain.014` (`Creditor Payment Activation Request Status Report`)**: Payer’s FI validates the account and returns real-time status (`RCVD` received, `RJCT` rejected/opted-out, or `ACCP` accepted/scheduled by the payer!).

**(3) Linked `pacs.008` (`FIToFICustomerCreditTransfer`)**: the moment the payer clicks *"Pay Now"* (`or on the payer’s scheduled due date`), the Payer’s FI originates a standard `pacs.008` **copying the exact End-to-End ID (`<EndToEndId>`) and structured remittance tags (`<RmtInf><Strd>`) from the original `pain.013`**—guaranteeing **100.0% automated ERP cash-application match**! Compare both US switches in [FedNow vs TCH RTP limits & routing](/rails/fednow-vs-tch-rtp-transaction-limits-prefunding-master-accounts) and our [FedNow, RTP, SEPA Instant & cross-border interlinking guide](/rails/fednow-rtp-sepa-instant-vop-cross-border-interlinking-guide).

## Anti-Spam Bill-Spamming Controls: Payee Certification, Warranties & Consumer Opt-Out

If anyone could blast `pain.013` requests at random bank accounts for $0.01, fraudsters would flood Americans’ mobile banking apps with fake *"IRS Tax Due $1,800 — Click Approve!"* popups! That is why **both FedNow and TCH RTP enforce ironclad Originating FI RfP Sender Underwriting**: **(a)** generally **only vetted commercial/corporate billers** (`utilities, lenders, B2B suppliers, brokerages`—or strictly verified me-to-me wallet funding flows) are permitted to originate `pain.013` messages (`not unvetted retail P2P users`), **(b)** the Biller’s FI provides **network legal warranties** that an underlying relationship/consent exists, and **(c)** payers hold **1-click "Block This Biller" and "Opt Out of All RfPs"** controls inside their bank UI!

![ISO 20022 Request for Payment pain.013 to pain.014 to pacs.008 B2B invoice settlement workflow on FedNow and TCH RTP](/api/figure?type=flow&title=ISO%2020022%20Request%20for%20Payment%20%28%60pain.013%20-%3E%20pacs.008%60%29%20Loop&subtitle=Zero-NSF%20credit%20push%20pre-populated%20with%20immutable%20ERP%20invoice%20remittance%20tags&steps=1.%20Biller%20Sends%20pain.013%3A%3AVetted%20corporate%20biller%20sends%20invoice%20amount%2C%20due%20date%20%26%20%3CEndToEndId%3E%20%28%240.01%29%7C2.%20Bank%20UI%20%2B%20pain.014%3A%3APayer%20sees%20verified%20bill%20inside%20bank%20app%3B%20FI%20returns%20pain.014%20RCVD%2FACCP%7C3.%20Payer%20Approves%20Push%3A%3APayer%20clicks%20Pay%20Now%20%28or%20schedules%20due%20date%29%20-%3E%20bank%20originates%20pacs.008%7C4.%20100%25%20Zero-Touch%20AR%20Match%3A%3ABiller%20ERP%20auto-closes%20invoice%20via%20echoed%20%3CEndToEndId%3E%20in%20%3C4%20seconds!&metrics=RfP%20Network%20Fee%3A%3AUSD%200.010%3A%3APlus%20%240.045%20when%20pacs.008%20pays%7CNSF%20%2F%20R01%20Risk%3A%3A0.00%25%3A%3APayer%20bank%20checks%20good%20funds!%7CAR%20Auto-Match%3A%3A99.9%25%2B%3A%3AImmutable%20echoed%20invoice%20ID%7CCancel%20message%3A%3Acamt.055%3A%3ABiller%20revokes%20unpaid%20RfP)

## High-ROI Production Use Cases: Me-to-Me Wallet Top-Ups, Auto-Loan Cure & B2B Net-30

Where is `pain.013` scaling fastest right now? **(1) Instant Brokerage & Wallet Account Funding ("Me-to-Me RfP")**: instead of pulling a risky Plaid + ACH debit (`forcing a 3-to-5-day withdrawal hold against R01/R10 fraud!`), a wealth or remittance app sends a `pain.013` to the user’s own Chase/BofA/regional bank app—the user approves via FaceID in their bank app, and **good irrevocable `pacs.008` funds arrive in 4 seconds with 0% chargeback/NSF risk**! **(2) Delinquent Auto/Mortgage Cure** (`keeping a borrower out of late-fee default at 10:00 PM Sunday night`), and **(3) B2B Wholesale Net-30 Dynamic Discounting** (`offering "2% 10 Net 30" directly inside pain.013 discount tags`).

| Collection Rail | All-In Cost on $50,000 B2B Invoice | Settlement Finality | NSF / Chargeback Risk | ERP Invoice Auto-Reconciliation |
| :--- | :--- | :--- | :--- | :--- |
| Commercial Credit Card (`B2B`) | **USD 1,325.00** (`~2.65% MDR`) | T+1 / T+2 batch | 90–120 day card chargeback window | High (`if Level 3 data passed`) |
| ACH Direct Debit (`CCD / WEB`) | USD 0.25 – 1.50 (`plus return fees`) | T+1 / SDA (`provisional!`) | **R01 NSF (2d) & R10 Unauth (60d consumer)** | Medium (`addenda often truncated`) |
| Customer-Initiated Wire / Check | USD 15.00 – 35.00 + lockbox labor | Same-day wire / 5–8d check | Low (`check kiting / fraud risk`) | **Poor** (`missing invoice # -> suspense`) |
| **FedNow / RTP `pain.013` RfP** | **USD 0.50 – 2.00** (`bank flat fee`) | **< 4 seconds 24/7/365** | **0.00% (`Irrevocable good-funds push`)** | **100% (`Echoed <EndToEndId> + <Strd>`)** |

## Comparing US pain.013 RfP Against SEPA Request-to-Pay (SRTP) & Australia PayTo

Globally, US `pain.013` RfP aligns closely with Europe’s EPC **SEPA Request-to-Pay (`SRTP`)** (`paired with` [SEPA VoP](/rails/sepa-verification-of-payee-vop-epc-iban-name-matching-api)) while stopping just one step short of [Australia NPP PayTo](/rails/npp-australia-payto-singapore-fast-hkma-fps-apac-instant-rails) (`which embeds pre-authorized recurring mandate agreements directly on the instant switch`). Model DSO cash-conversion gains in our [Nostro SOFR prefunding carry calculator](/calculators/nostro-sofr-prefunding-carry-calculator) and visit the [Instant Payment Rails topic hub](/topics/instant-payment-rails-fednow-sepa-pix).

![Annual payment acceptance, bad-debt return, and AR reconciliation cost across USD 200 million B2B billing volume](/api/figure?type=bars&title=Annual%20AR%20Collection%20Cost%20on%20USD%20200M%20B2B%20Volume&subtitle=4%2C000%20wholesale%20invoices%20%28%2450K%20avg%29%20across%20Card%2C%20ACH%20Debit%2C%20Paper%2FWire%2C%20and%20ISO%2020022%20RfP&steps=Commercial%20Card%20%2840%25%20Share%29%3A%3AUSD%202%2C120K%20%2F%20yr%20%E2%80%94%202.65%25%20interchange%20eats%20wholesale%20gross%20margin%7CCheck%20Lockbox%20%2B%20Manual%20Wire%3A%3AUSD%20380K%20%2F%20yr%20%E2%80%94%206-day%20mail%20float%20%2B%20%2414%2Fcheck%20AR%20cash-app%20labor%7CACH%20Pull%20%28Plaid%20%2B%20Nacha%29%3A%3AUSD%20215K%20%2F%20yr%20%E2%80%94%201.1%25%20R01%2FR02%20return%20losses%20%2B%203-day%20risk%20holds%7CFedNow%20%2F%20RTP%20pain.013%20RfP%3A%3AUSD%2018K%20%2F%20yr%20%E2%80%94%20flat%20per-tx%20bank%20fee%2C%200%25%20NSF%2C%20instant%20ERP%20sync!&metrics=Amount%20Mod%20Flag%3A%3ATrue%20%2F%20False%3A%3AAllow%2Fblock%20partial%20payment%7CExpiry%20Timer%3A%3AISO%20Timestamp%3A%3AAuto-expires%20stale%20quotes%7CMe-to-Me%20Hold%3A%3A0%20Days%20%28vs%204d%29%3A%3AInstant%20brokerage%20buying%20power%7CDiscount%20Tag%3A%3A2%2F10%20Net%2030%3A%3ANative%20ISO%2020022%20early-pay)

## Corporate AR Cost Savings Formula: pain.013 RfP vs Commercial Cards & ACH Debit

Replacing B2B commercial card acceptance (`2.65% MDR`) and exception-prone ACH/check lockbox workflows (`unmatched remittance stubs + NSF returns`) with `pain.013 -> pacs.008` transforms EBITDA margins on high-ticket wholesale invoices (`up to $10M on RTP / $1M+ on FedNow`).

Below is the B2B Accounts Receivable unit-cost comparison equation.

```formula
Annual_RfP_AR_Savings = (V_card_shifted * m_card_mdr) + (N_ach_shifted * p_nsf_r10 * L_return_loss) + (N_unmatched * C_ar_manual) - (N_rfp_total * c_bank_rfp)

Where:
 V_card_shifted * m_mdr = USD 45,000,000 B2B invoices shifted off 2.60% cards (even w/ 0.50% buyer instant rebate -> 2.10% net save = USD 945,000)
 N_ach * p_nsf * L_loss = 60,000 funding pulls * 0.85% R01/R10 fraud-NSF rate * USD 185 avg write-off = USD 94,350 saved
 N_unmatched * C_manual = 4,800 unreferenced wires/checks * USD 16.50 AR clerk matching = USD 79,200 saved
 N_rfp_total * c_bank = 110,000 pain.013 + pacs.008 cycles * USD 0.65 commercial bank API tariff = USD 71,500

Worked Net Annual EBITDA Uplift:
 Annual_RfP_AR_Savings = USD 945,000 + USD 94,350 + USD 79,200 - USD 71,500 = +USD 1,047,050/year
```

## Frequently asked questions

### Can a biller use FedNow pain.013 Request for Payment to pull money automatically every month like ACH Direct Debit?

Standard US FedNow and RTP pain.013 requires payer authorization (either clicking "Pay Now" per bill or configuring an automated standing approval rule inside the payer’s own banking portal)—the biller alone cannot unilaterally debit the payer’s account without payer-bank consent.

### What happens if a customer pays an invoice via check after we already sent a pain.013 Request for Payment?

Before the payer approves the pending RfP, the biller’s ERP immediately dispatches an ISO 20022 camt.055 (Customer Payment Cancellation Request / RfP Cancellation) via its bank to withdraw the open pain.013 from the customer’s banking UI, preventing duplicate payment!

### Why are retail stock-trading and crypto apps switching from Plaid ACH pulls to "Me-to-Me" RfP?

When pulling USD 5,000 via consumer ACH debit, fraudsters exploit the 2-to-4-day settlement lag ("free-riding" or filing fake 60-day R10 claims after withdrawing assets). Sending a pain.013 to the user’s bank app triggers an instant, irrevocable pacs.008 credit push with zero NSF/R10 exposure.

### Can a B2B supplier forbid a customer from short-paying an invoice inside pain.013?

Yes! The ISO 20022 pain.013 Payment Condition block (<PmtCond><AmtModAllwd>false</AmtModAllwd>) explicitly instructs the payer’s banking app whether the customer is permitted to edit the requested dollar amount or must pay the exact invoice balance in full.


## Source URLs

- https://www.frbservices.org/financial-services/fednow
- https://www.theclearinghouse.org/payment-systems/rtp
- https://www.nacha.org/content/same-day-ach-resource-center

## Citation

- APA: Claire Beaumont, CAMS, CTP. (2026). FedNow & RTP Request for Payment (RfP): ISO 20022 pain.013 / pain.014 B2B Invoice Settlement. PayClear Ledger. https://payclearledger.com/rails/fednow-rfp-request-for-payment-pacs008-b2b-invoice-settlement
- Canonical article: [FedNow & RTP Request for Payment (RfP): ISO 20022 pain.013 / pain.014 B2B Invoice Settlement](https://payclearledger.com/rails/fednow-rfp-request-for-payment-pacs008-b2b-invoice-settlement)
- Site research index: [PayClear Ledger](https://payclearledger.com/llms-full.txt)
