Hosted Page - Request for Payments (Mock Demo)
Investor Demo Mode

Hosted RfP™ Checkout for Real-Time Bank Payments

A branded payment experience across TodayPayments, RequestForPayment, and SecureQBPlugin that turns invoices into approval-based, intelligent, real-time payment flows with built-in accounting updates.

TodayPayments
RequestForPayment RfP™
SecureQBPlugin

Request for Payment Flow Simulation "Mock Full Demo"
Invoice (We prefer QBO QuickBooks®)
→
Request for Payment (pain.013 ISO 20022)
→
Approval (Payer acknowledgement)
→
Smart Routing
→
Payment Rail (Real-time Payment or alternatives)
→
QuickBooks Update (Invoice Paid into QBO QuickBooks)
Status: Ready
Pitch Summary

Not just payments. A financial operating system for real-time receivables.

This demo (Request for Payment Flow Simulation "Mock Full Demo") shows how a merchant invoice can become a secure hosted Request for Payment, how the Payer approves it, how the orchestration layer selects the right rail, and how the accounting system updates instantly.

FedNow® - First Choice
RTP® - Backup Alternative

Streamline Payments with Advanced Request for Payment Options: Harness the power of FedNow's Request for Payment system to transform how you manage invoices and remittances. Our platform supports diverse data integration options, allowing Payees to incorporate detailed invoice data directly within the RfP™ message or link to a comprehensive Merchant Page.

Flexible Invoice Details with ISO 20022 Messaging: Leverage the flexibility of ISO 20022 messaging standards in our RfP™ system. You can choose to display crucial payment details directly in the message with a concise 140-character description, or through a dynamic "Hyper-Link" leading to a detailed Merchant Page.

ACH / Card / Wire / Financing
Plaid-Style Bank Login Simulation

The Payer sees a familiar bank-connection and authorization moment. Under the hood, this is the conversion point where the payment request becomes an approved bank payment instruction.

Select bank → fake login → authorize payment
AI Smart Routing Display
Chosen Rail
Waiting for decision...

When the Payer approves, the orchestration layer will evaluate speed, eligibility, amount, cost, risk, merchant preference, and Payer choice.

RfP™ Payee Payment Choices available to their Payees: FedNow® • RTP® • ACH • Same-Day ACH • Card • Wire • Financing

Speed
Prefer FedNow® or RTP®
Cost
Use ACH if urgency is lower
Limits
Escalate to Wire if needed
Payer Need
Offer Financing when cash flow matters
Why This Wins vs Cards
Cards
SettlementDelayed
ChargebacksPossible
Remittance DataOften weak
Approval FlowCard-centric
Bank Checkout via RfP
SettlementInstant or near real-time
ChargebacksReduced exposure
Remittance DataStructured and richer
Approval FlowPayer authorizes before movement
Revenue Model Overlay
FedNow® Rail FeePremium instant payment fee
RTP® Rail FeePremium instant payment fee
ACH / Same-Day ACHLower-cost routing margin
Card / Wire / FinancingAlternative monetization path
Platform RevenueAPI + SaaS + orchestration + reconciliation

This turns the platform from a simple payment acceptance tool into a multi-rail revenue engine with software-style margins layered on top of payment flow.

CFO Dashboard Panel

FedNow® and RTP® with Reverse Positive Pay Today Payments Request for Payment
In FedNow® and RTP®, "Reverse Positive Pay" flips the model: the Payer approves each transaction before funds move.



Outstanding RfP Queue
12
Approved Today
5
Cash Incoming
$18.5K
Aging 0–1 Days4 requests • $5,250
Aging 2–3 Days3 requests • $4,600
Aging 4–7 Days3 requests • $5,900
Expiring Soon2 requests • $2,750
Projected 24h Cash Forecast$11,200
Multi-Payer Queue Dashboard (Payee View)
Total Payers
4
Pending Review
1
Paid / Approved
1
Payer Assigned Amount Status Decision Hosted URL Next Step
ABC Dental Group $2,500.00 Viewed Pay (Accept) /pay/8Kf2Lm91QaX Route to FedNow®
XYZ Ortho $2,500.00 Pending Approval Pend /pay/U7nP4sTz2Be Supervisor Review
Prime Ortho Labs $1,100.00 Declined Decline (Reject) /pay/Qm3Lp9Vk22A Offer Virtual Card
North County Smile Center $850.00 Partial Paid Edit Amount /pay/Ty8Nf1Ab44R Collect Balance

This queue dashboard lets treasury teams, merchants, and bank partners monitor payer-specific outcomes across a shared master RfP while preserving separate URLs, separate audit trails, and separate response logic per payer.


Create a Unique URL per RfP with multiple Payers (Payee View)

With multiple Payers, each one may:

  • pay
  • decline
  • pend
  • partially pay
  • choose a different account
  • ignore the request

Use this structure:

  • one master RfP
  • one Payer record per recipient
  • one unique tokenized URL per payer

Save one hosted URL per payer:

hosted_url = f"https://pay.requestforpayment.com/pay/{token}"


Example:

Master RfP: rfp_9001
Payer A link: https://pay.requestforpayment.com/pay/8Kf2Lm91QaX
Payer B link: https://pay.requestforpayment.com/pay/U7nP4sTz2Be

Payer A
NameABC Dental Group
Assigned Amount$2,500.00
StatusViewed
Hosted URL/pay/8Kf2Lm91QaX
Payer B
NameXYZ Ortho
Assigned Amount$2,500.00
StatusPending Approval
Hosted URL/pay/U7nP4sTz2Be

One master RfP can fan out into multiple payer invitations, but each payer gets a separate token, separate URL, separate audit trail, and separate decision path.

Multi-Payer Hosted Payment Experience (Payee View)
Master RfPRFP-9001
InvoiceINV-7788
Total Amount$5,000.00
Payer LinksUnique tokenized checkout page per payer
Payment ChoicesFedNow® • RTP® • ACH • Card • Wire • Financing

One master RfP can fan out into multiple payer invitations, but each payer gets a separate token, separate URL, separate audit trail, and separate decision path.

Payer Queue Decision Actions (ISO 20022 pain.014)

When a Payer receives a Request-for-Payment message, the following decision actions can be executed through ISO 20022 pain.014 messaging.

1. Pay (Accept)Payment executed through RTP® sent by the Payee
2. Decline (Reject)Payment request rejected or forwarded to alternative settlement such as virtual card processing
3. No ActionRequest expires automatically after a defined timeout
4. PendPayment placed into a review queue or scheduled supervisory approval cycle
5. Edit AmountPartial payment authorized by the Payer
6. Pay via Different AccountAlternate funding account selected
7. Block or Ignore SenderSender restricted from future payment requests
Payer-Side Controls

The Payer is not forced into a single yes-or-no decision. The queue supports review, edit, alternate account selection, rejection, blocking, and approval timing controls.

RfP™ Lifecycle States: Draft (03/25/2026)


→ Created
→ Delivered
→ Viewed
→ Accepted
→ Rejected
→ Cancelled
→ Expired
→ Paid
→ Settled
→ Reconciled
→ Closed

ISO 20022 pain.014 Logic

This panel demonstrates how Payer responses can be normalized into a structured response model for RfP lifecycle handling, orchestration rules, and accounting triggers.

Bank Presentation Value

Shows supervisory review, queueing, sender controls, and alternative settlement paths that matter to banks, treasury teams, and risk officers.

Investor Presentation Value

Turns the product from a payment button into a workflow platform with approvals, policy controls, intelligence, and multi-rail monetization opportunities.

Why This Matters

The queue is the control layer.

A real Request-for-Payment platform is not just about sending a payment request. It is about giving the Payer a governed decision framework, capturing that decision in a structured response model, routing the outcome intelligently, and synchronizing the result into treasury and accounting systems.

Productization Mode
FrontendReact app with hosted checkout UI
BackendFake sandbox APIs for demo and partner testing
Developer PortalBank / partner sandbox access
Core APIsRfP create, approve, route, pay, webhook
Accounting LayerQuickBooks sync + reconciliation engine
Multi-Payer ModelMaster RfP + payer-level tokens + payer-level actions
OpenAPI + PostgreSQL Architecture Snapshot
POST /v1/rfpsCreate master RfP
POST /v1/rfps/{rfp_id}/payersAdd multiple payers
GET /v1/pay/{public_token}Load payer-specific checkout page
POST /v1/pay/{public_token}/actionCapture payer response
Tablesrfps, rfp_payers, rfp_payer_actions, payments, webhook_events
Positioning Statement

One approval flow. Multiple rails. Real-time accounting.

The Payer experiences a simple branded checkout page. The merchant gains orchestration, visibility, and instant accounting outcomes.

Navigation and Copyrights

Today Payments
Apply Now
Terms of Use
Privacy Policy
Sitemap
Copyright © Today Payments, Inc. All Rights Reserved.
Request for Payment is a website owned by Today Payments, Inc.
RfP™ ™ is a Trademark of Today Payments, Inc.
Trademark of The Clearing House RTP®
Trademark of U.S. Federal Reserve FedNow ®
QuickBooks ® is a registered service mark of Intuit.
Today Payments, Inc., is an Elavon Payments Partner & Registered Partner/ISO of Elavon, Inc. Georgia, [a wholly owned subsidiary of U.S. Bancorp, Minneapolis, MN]