White-Label Solution Overview
Open-Banking Positive Pay via FedNow® and RTP®
A unified, white-label platform that allows payers to pre-authorize payments across multiple bank accounts using real-time settlement over the Federal Reserve FedNow® and RTP® Services. This live mockup presents a Reverse Positive Pay dashboard, multi-page workflow, digital treasury tools, identity resolution, invoice-driven RfP creation, API wiring, and Open-Banking hooks.
Bank-agnostic authorization layer
Pre-payment approval engine
Real-time settlement rail
FedNow® + RTP® interoperability
QBO remains system of record
CFO & Treasury Benefits
✔
One approval layer across all banks
Centralized review across multiple institutions and accounts.
Centralized review across multiple institutions and accounts.
🛡
Eliminate check fraud and ACH returns
Nothing settles until the payer approves.
Nothing settles until the payer approves.
⚡
Real-time cash visibility
AI dashboards show balances, queues, volume, and rail performance.
AI dashboards show balances, queues, volume, and rail performance.
How It Works (Treasury View)
1
Aggregate all bank relationships
Multiple bank accounts, balances, and routing data in one place.
Multiple bank accounts, balances, and routing data in one place.
2
Receive ISO 20022 RfP messages
pain.013 requests carry payee, amount, due date, and remittance detail.
pain.013 requests carry payee, amount, due date, and remittance detail.
3
Apply approval policy
Vendor whitelist, tolerances, maker/checker, duplicate screening.
Vendor whitelist, tolerances, maker/checker, duplicate screening.
4
Authorize → settle instantly
pain.014 decisions drive final, irrevocable settlement.
pain.014 decisions drive final, irrevocable settlement.
Outstanding RfP Queue
128
41 require same-day action
Approval Rate
92.4%
▲ +3.1% vs prior week
Real-Time Settlement Today
$4.6M
Across FedNow® and RTP®
Duplicate Requests Blocked
17
Risk layer prevented release
Reverse Positive Pay Overview
Request for Payment replaces the Positive Pay file entirely✔ It includes creditor identity, amount, due date, invoice reference, and structured ISO 20022 remittance data.
✔ Nothing settles until the payer approves. This gives payers pre-settlement control across every connected bank account.
✔ Pain.013 in, pain.014 out. The hosted page becomes the approval and orchestration layer between invoice approval and release of funds.
1
Vendor Invoice (QBO)QBO remains the system of record.
2
Approval RulesQBO + RTP layer evaluates controls.
3
AuthorizationRTP® / FedNow® becomes the settlement rail.
4
Auto-ReconciliationStructured remittance syncs back to accounting.
AI Treasury Dashboards
Power Pivot, Excel, and Google Sheets readyAI-powered treasury dashboards provide CFO-ready analytics across FedNow® and RTP® transactions, including Outstanding RfP queues, payment approval trends, rail-level volume, and aging analytics.
Outstanding RfP Aging
Track pending, expiring, and expired requests.
Track pending, expiring, and expired requests.
Rail-Level Volume
Compare FedNow® vs RTP® eligibility and usage.
Compare FedNow® vs RTP® eligibility and usage.
Approval Trends
Accept, decline, pend, and partial decisions.
Accept, decline, pend, and partial decisions.
Audit & Reconciliation
Map to invoice data and settlement confirmations.
Map to invoice data and settlement confirmations.
Dashboard Positive Pay Worksheet — FedNow® & RTP®
Multiple banks with multiple accounts for one payer| Financial Institution | Account #1 | $ Balance | Routing | Total RfP's Count | Payer's Solicit Action | Unique Message Identifier | Creation Date & Time | Settlement Rail Indicator | Reconciliation & Audit | Alias (Phone/Email/Token) | Purpose Code | Request Type | Unique Request for Payment ID | Due Date / Request Execution | RfP Expiration Date | Requested Amount | Currency | Payee Name | Payee account identifier | Payee financial institution | Payer Name | Payer Account Identifier (or Alias) | Payer Financial Institution | Invoice or Payment Description | Pay / Decline / Partial Allowed | Required response date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Pacific Treasury Bank | •••• 4501 | $1,240,551 | 121000358 | 24 | Approve Ready | MSG-FT-240328-001 | 2026-03-28 08:41 PT | FedNow® | QBO Match Pending | ap@vendorflow.com | SUPP | One-time | RFP-900114 | 2026-03-28 10:00 PT | 2026-03-28 16:00 PT | $48,225.00 | USD | VendorFlow Supply Co. | VF-00291 | First Commercial CU | North Coast Manufacturing | treasury@northcoast.com | Pacific Treasury Bank | Invoice 44591 / structured remittance attached | Pay / Decline / Partial / Pend | 2026-03-28 12:00 PT |
| Horizon Business Bank | •••• 1178 | $482,910 | 322271627 | 11 | Pend Review | MSG-RT-240328-104 | 2026-03-28 09:03 PT | RTP® | Supervisor Queue | +1-555-218-8841 | RENT | Recurring | RFP-900115 | 2026-03-29 07:00 PT | 2026-03-29 23:59 PT | $96,480.00 | USD | Urban Logistics Group | ULG-81102 | Metro Settlement Bank | North Coast Manufacturing | alias:NC-TREASURY | Horizon Business Bank | Warehouse lease / monthly recurring RfP | Pay / Decline / Different Account | 2026-03-29 09:00 PT |
| Summit National | •••• 9920 | $2,881,441 | 026009593 | 17 | Duplicate Flag | MSG-FT-240328-141 | 2026-03-28 09:12 PT | FedNow® | Duplicate Detection Triggered | token:9f8c-1120-xp | UTIL | One-time | RFP-900116 | 2026-03-28 11:30 PT | 2026-03-28 15:30 PT | $18,940.30 | USD | WestGrid Utilities | WG-44011 | Utility Treasury Bank | North Coast Manufacturing | acct •••• 9920 | Summit National | Energy invoice / same amount seen within 2 hours | Decline / Block / Pend | 2026-03-28 12:45 PT |
| Pacific Treasury Bank | •••• 2204 | $664,208 | 121000358 | 7 | Partial Allowed | MSG-RT-240328-182 | 2026-03-28 09:27 PT | RTP® | Open Remittance Mapping | vendor.ap@steelworks.io | MATL | One-time | RFP-900117 | 2026-03-28 14:00 PT | 2026-03-28 18:00 PT | $125,000.00 | USD | SteelWorks Industrial | SW-00918 | North Harbor Bank | North Coast Manufacturing | acct •••• 2204 | Pacific Treasury Bank | Partial shipment invoice / balance retained pending QA | Pay / Partial / Pend / Different Account | 2026-03-28 13:30 PT |
Minimum ISO 20022 Request for Payment Mandatory Fields
All minimum RfP fields using FedNow® & RTP®Message Identification
Primary request message identity.
Primary request message identity.
Creation DateTime
Origin timestamp for audit and sequencing.
Origin timestamp for audit and sequencing.
Creditor Name and Account
Payee identity and account destination.
Payee identity and account destination.
Debtor Name and Account or Proxy
Payer identity, account, or alias reference.
Payer identity, account, or alias reference.
Requested Amount and Currency
Approval and liquidity context.
Approval and liquidity context.
Expiration DateTime
Controls automatic request expiry.
Controls automatic request expiry.
Remittance Information
Structured invoice-level reconciliation detail.
Structured invoice-level reconciliation detail.
Unique Transaction Identifier
End-to-end tracking across workflows and rails.
End-to-end tracking across workflows and rails.
Services — Positive Pay Pro™
Payer services, solutions, benefits, and features• Payer Services: Receive ISO 20022 pain.013 messages, approve or reject through pain.014 responses, pre-authorize payee lists, perform multi-account funding selection, and run fraud detection.
• Solutions: Reverse Positive Pay automation, intelligent RfP routing, Positive Pay API integration, accounts payable automation, and multi-bank interoperability infrastructure.
• Benefits: Pre-authorize every payment across every bank, eliminate check-based fraud exposure, centralize payee validation, maintain instant approval control before settlement, and surface AI-powered treasury dashboards.
• Features: Single-user and enterprise deployment, pain.013 intake, pain.014 orchestration, partial payments, supervisor approval queues, block/ignore controls, duplicate detection, and multi-bank payment governance.
Clickable Activity Decisions by a Payer Using ISO 20022 pain.014
Click a button to preview the action state1. Pay (Accept)
Settle instantly via FedNow® or RTP®.
2. Decline (Reject)
Cancel, redirect, expire, or fail under payer control.
3. No Action
Request expires automatically after the response deadline.
4. Pend
Queue for supervisory review or scheduled approval.
5. Edit Amount
Execute a partial payment when business rules allow.
6. Pay via Different Account
Select an alternate approved funding account.
7. Block / Ignore Sender
Prevent future payment requests from a payee or alias.
Top 10 Feature-Rich Reasons to Choose Premier FedNow® and RTP®
Enterprise positioning1. Instant settlement 24/7/365
2. Structured ISO 20022 remittance data
3. Reverse Positive Pay authorization control
4. Multi-bank interoperability
5. AI treasury dashboards
6. Automated reconciliation tools
7. Multi-MID enterprise activation
8. Partial payment flexibility
9. Real-time liquidity visibility
10. Embedded approval APIs
Product Positioning Summary
Live full multi-page demoVendor Invoice (QBO)
↓
Approval Rules (QBO + RTP Layer)
↓
RTP® / FedNow® Authorization
↓
Instant Settlement
↓
Auto-Reconciliation (QBO)
Outstanding RfP Queue
Approve, reject, pend, partially pay, or change funding accountRFP-900114 · VendorFlow Supply Co.
Invoice 44591 · MSG-FT-240328-001 · alias ap@vendorflow.com
FedNow®
Requested: $48,225.00
Approve Ready
Response by 12:00 PT
Funding: •••• 4501
Pacific Treasury Bank
RFP-900115 · Urban Logistics Group
Recurring warehouse lease · alias NC-TREASURY
RTP®
Requested: $96,480.00
Pend Review
Supervisor required
Funding: •••• 1178
Horizon Business Bank
RFP-900116 · WestGrid Utilities
Energy invoice · duplicate amount detected within 2 hours
FedNow®
Requested: $18,940.30
Duplicate Flag
Risk review mandatory
Funding: •••• 9920
Summit National
RFP-900117 · SteelWorks Industrial
Partial shipment invoice pending QA review
RTP®
Requested: $125,000.00
Partial Allowed
Response by 13:30 PT
Funding: •••• 2204
Pacific Treasury Bank
Supervisor workflow: maker/checker rules route high-value, recurring, or risk-flagged requests into controlled approval tiers.
Expiring requests surface response deadlines, funding account availability, and auto-expire timers tied to the RfP expiration datetime.
Duplicate filtering compares alias, payee, amount, invoice reference, and submission timing before any payment is released.
Identity Directory UI
EIN / alias / phone lookupDirectory Result
Resolved business payment identity
North Coast Manufacturing
EIN: 84-3319042 · Primary Alias: NC-TREASURY · Phone: +1-555-218-8841
Primary Bank
Pacific Treasury Bank
Pacific Treasury Bank
Fallback Bank
Horizon Business Bank
Horizon Business Bank
Approved Funding Accounts
•••• 4501, •••• 1178, •••• 2204
•••• 4501, •••• 1178, •••• 2204
Policy Profile
Dual approval above $75,000; whitelist-only first-time payees
Dual approval above $75,000; whitelist-only first-time payees
Directory Architecture
Business payment identity layerEntity Record
Business legal name, DBA, EIN, status, and compliance profile.
Business legal name, DBA, EIN, status, and compliance profile.
Alias Registry
Email, phone, token, or directory alias mapped to debtor or creditor identity.
Email, phone, token, or directory alias mapped to debtor or creditor identity.
Bank Routing Layer
Approved financial institutions and preferred settlement paths.
Approved financial institutions and preferred settlement paths.
Policy Hooks
Purpose codes, thresholds, whitelist rules, and payment rail permissions.
Purpose codes, thresholds, whitelist rules, and payment rail permissions.
Use Cases
Consumer & SMB usability• EIN lookup: identify the business payment profile before sending or approving an RfP.
• Alias resolution: map email, phone, or token to the correct business account set.
• Multi-bank routing: choose the permitted funding or receiving institution based on policy and rail eligibility.
Create RfP Flow from Invoice Data
Generate a pain.013-ready request from ERP or QBO invoice data• Payee Name
• Payee Account Identifier
• Payer Alias / Account
• Invoice / Payment Description
• Requested Amount
• Currency
• Due Date / Execution
• Expiration DateTime
• Purpose Code
• Request Type
Generated Request Preview
Live hosted payment page data model{
"messageIdentification": "MSG-FT-240328-001",
"creationDateTime": "2026-03-28T08:41:00-07:00",
"requestForPaymentId": "RFP-900114",
"creditor": {
"name": "VendorFlow Supply Co.",
"accountIdentifier": "VF-00291",
"financialInstitution": "First Commercial CU"
},
"debtor": {
"name": "North Coast Manufacturing",
"accountOrProxy": "NC-TREASURY",
"financialInstitution": "Pacific Treasury Bank"
},
"requestedAmount": {
"currency": "USD",
"amount": "48225.00"
},
"dueDateTime": "2026-03-28T10:00:00-07:00",
"expirationDateTime": "2026-03-28T16:00:00-07:00",
"purposeCode": "SUPP",
"requestType": "ONE_TIME",
"remittanceInformation": "Invoice 44591 / structured remittance attached"
}
Mock Developer API Wiring
Sample payloads and responsesPOST /api/v1/rfp/create
Content-Type: application/json
{
"invoiceId": "INV-44591",
"payerAlias": "NC-TREASURY",
"payeeName": "VendorFlow Supply Co.",
"payeeAccountIdentifier": "VF-00291",
"requestedAmount": "48225.00",
"currency": "USD",
"dueDateTime": "2026-03-28T10:00:00-07:00",
"expirationDateTime": "2026-03-28T16:00:00-07:00",
"purposeCode": "SUPP",
"remittanceInformation": "Invoice 44591 / structured remittance attached"
}
Mock API Response
Developer portal previewHTTP/1.1 201 Created
{
"status": "created",
"messageIdentification": "MSG-FT-240328-001",
"requestForPaymentId": "RFP-900114",
"approvalState": "pending_payer_review",
"eligibleRails": ["fednow", "rtp"],
"dashboardUrl": "/dashboard/rfp/RFP-900114",
"nextAction": "route_to_positive_pay_policy_engine"
}
Endpoint Group
RFP Creation
Generate ISO-aligned request payloads from invoices.
Endpoint Group
Decisioning
Submit pain.014 actions for accept, decline, pend, partial, or block.
Endpoint Group
Directory & Hooks
Resolve identity, ingest events, and export dashboard updates.
Recommended Target Architecture
Positive Pay Pro™ Stack for Bank Connectivity, Treasury Workflow, RfP History, and QBO Reconciliation
This target architecture shows how a white-label Reverse Positive Pay platform can sit between accounting systems, identity resolution, bank connectivity, approval workflows, and real-time settlement rails. It is designed for CFOs, treasurers, controllers, financial institutions, and embedded treasury product teams.
Bank connectivity layer
Treasury workflow layer
RfP history store
QBO reconciliation layer
FedNow® + RTP® orchestration
Layered Architecture Diagram
End-to-end operating model
Layer 1 — User & Channel Layer
CFO / Treasury Dashboard
Outstanding RfP queue, balances, approvals, analytics, and rail visibility.
Outstanding RfP queue, balances, approvals, analytics, and rail visibility.
Hosted Payment Page
Payer-side approval interface with Pay / Decline / Pend / Partial / Different Account actions.
Payer-side approval interface with Pay / Decline / Pend / Partial / Different Account actions.
Bank Portal / White-Label UI
Embedded workflow inside digital banking or FI treasury experiences.
Embedded workflow inside digital banking or FI treasury experiences.
Developer Portal / API Clients
ERP, middleware, and partner apps connect through API endpoints and hooks.
ERP, middleware, and partner apps connect through API endpoints and hooks.
↓
Layer 2 — Treasury Workflow Layer
Positive Pay Policy Engine
Vendor whitelists, amount tolerances, maker/checker controls, duplicate detection, and block lists.
Vendor whitelists, amount tolerances, maker/checker controls, duplicate detection, and block lists.
Approval Orchestration
Maps payer decisions into pain.014 responses and settlement instructions.
Maps payer decisions into pain.014 responses and settlement instructions.
Funding Account Selector
Chooses payer bank account based on policy, balance, and rail eligibility.
Chooses payer bank account based on policy, balance, and rail eligibility.
Notification & Task Layer
Alerts, reminders, escalations, and expiring-request workflows.
Alerts, reminders, escalations, and expiring-request workflows.
↓
Layer 3 — Identity Directory Layer
EIN / Alias Registry
Business payment identities mapped to legal entity, alias, phone, email, or token.
Business payment identities mapped to legal entity, alias, phone, email, or token.
Routing Directory
Maps identity to approved banks, accounts, and preferred settlement paths.
Maps identity to approved banks, accounts, and preferred settlement paths.
Compliance Profile
Purpose codes, KYC/KYB references, limits, and account governance metadata.
Purpose codes, KYC/KYB references, limits, and account governance metadata.
Multi-Bank Relationship Graph
Supports one business across multiple financial institutions and accounts.
Supports one business across multiple financial institutions and accounts.
↓
Layer 4 — Bank Connectivity & Rail Layer
Payment Hub / Bank Connectivity
API, MQ, file, or partner gateway connections to banks and payment hubs.
API, MQ, file, or partner gateway connections to banks and payment hubs.
FedNow® Messaging
Receive RfP requests and submit approvals, routing, and status updates.
Receive RfP requests and submit approvals, routing, and status updates.
RTP® Messaging
Real-time settlement and request orchestration across supported institutions.
Real-time settlement and request orchestration across supported institutions.
Open-Banking Hooks
Inbound and outbound event pipelines for queue updates and downstream sync.
Inbound and outbound event pipelines for queue updates and downstream sync.
↓
Layer 5 — Data, History, and Audit Layer
RfP History Store
Persists current and past requests, approvals, expirations, settlement outcomes, and remittance data.
Persists current and past requests, approvals, expirations, settlement outcomes, and remittance data.
Operational Database
Queue state, policy outcomes, users, permissions, and identity mappings.
Queue state, policy outcomes, users, permissions, and identity mappings.
Audit Ledger
Immutable timeline of message IDs, actions, timestamps, and downstream confirmations.
Immutable timeline of message IDs, actions, timestamps, and downstream confirmations.
Analytics Warehouse
Feeds Power Pivot, Excel, Google Sheets, BI dashboards, and CFO reporting.
Feeds Power Pivot, Excel, Google Sheets, BI dashboards, and CFO reporting.
↓
Layer 6 — Accounting & ERP Reconciliation Layer
QBO / ERP Source Records
Invoices, vendor files, GL references, dimensions, and customer records remain system-of-record data.
Invoices, vendor files, GL references, dimensions, and customer records remain system-of-record data.
Settlement Mapping
Matches message IDs and remittance data back to invoice and bill records.
Matches message IDs and remittance data back to invoice and bill records.
Auto-Reconciliation
Posts paid, partial, pending, or expired statuses into accounting workflows.
Posts paid, partial, pending, or expired statuses into accounting workflows.
Export / Download Layer
Current and historical RfP data can be exported to treasury tools, spreadsheets, or ERP interfaces.
Current and historical RfP data can be exported to treasury tools, spreadsheets, or ERP interfaces.
Recommended Software Roles
What each stack component should doCustom App / Portal
The HTML/React front end for dashboard, queue, identity directory, and hosted payment pages.
The HTML/React front end for dashboard, queue, identity directory, and hosted payment pages.
Workflow Engine
Handles approval paths, thresholds, maker/checker, escalations, and exception states.
Handles approval paths, thresholds, maker/checker, escalations, and exception states.
Payment Hub / Connectivity Engine
Connects to banks, FedNow®, RTP®, and open-banking interfaces.
Connects to banks, FedNow®, RTP®, and open-banking interfaces.
Operational Database
Stores live queue state, users, accounts, aliases, and approval policy configurations.
Stores live queue state, users, accounts, aliases, and approval policy configurations.
RfP Ledger / History Store
Keeps all current and past Request for Payments, decisions, expiries, and settlement outcomes.
Keeps all current and past Request for Payments, decisions, expiries, and settlement outcomes.
Reconciliation Adapter
Bridges QBO or ERP invoice data with settlement events and remittance payloads.
Bridges QBO or ERP invoice data with settlement events and remittance payloads.
Recommended Data Objects
Core records for Positive Pay Pro™• Identity Object: EIN, alias, phone, token, legal entity, compliance status, approved banks.
• RfP Object: message ID, creation datetime, payee, payer, amount, currency, due date, expiration, purpose code, remittance information.
• Decision Object: accept, reject, no action, pend, partial, different account, block sender.
• Settlement Object: rail, funding account, status, timestamps, confirmation IDs, finality state.
• Reconciliation Object: invoice linkage, bill linkage, GL code, posting status, audit reference.
Current and Past RfP Upload / Download Model
Operational answer for treasury and banksInbound Upload to Dashboard
Bank or payment hub sends current RfP messages, events, and statuses into the platform through APIs or hooks.
Bank or payment hub sends current RfP messages, events, and statuses into the platform through APIs or hooks.
Internal Persistence
Platform stores the event in the operational queue and in the long-term RfP history store.
Platform stores the event in the operational queue and in the long-term RfP history store.
User Decision & Orchestration
Payer approves, declines, pends, partially pays, or switches accounts.
Payer approves, declines, pends, partially pays, or switches accounts.
Outbound Download / Push
Decision, settlement, and reconciliation results are pushed back to bank systems, ERP systems, and reporting tools.
Decision, settlement, and reconciliation results are pushed back to bank systems, ERP systems, and reporting tools.
Historical Replay / Export
Past RfPs can be queried, exported, replayed, or analyzed from the RfP history store and analytics warehouse.
Past RfPs can be queried, exported, replayed, or analyzed from the RfP history store and analytics warehouse.
Why This Architecture Fits the Mockup
Product rationale• The dashboard stays treasury-first. CFOs see queue, cash, and control in one place.
• The app remains white-label. Banks and enterprises can embed it in their own digital experiences.
• The history layer avoids bank lock-in. Your platform keeps its own current and past RfP record of truth.
• QBO reconciliation remains clean. Accounting stays in the ERP while real-time settlement is orchestrated outside it.
• The identity layer becomes strategic. EIN, alias, and phone-based lookup improve routing, usability, and governance.