Smart Phone + HTML Mockup Demo
Full HTML page viewer paired with a mobile payer screen, designed for Request for Payment flows and ISO 20022 action handling.
New Request for Payment received from North Bay Medical Group
The payer has received a digital invoice with settlement preference, due date, expiration, reference data, and remittance details.
Open Request for Payment items awaiting decision
The payer can approve, decline, pend, partially pay, schedule, route internally, or block future requests from a sender.
Select which bank and account will fund this Request for Payment
The payer now chooses the source account, desired rail, timing, and response action that will become the outgoing pain.014 instruction.
Payment authorized and sent successfully
The payer approved the request. Funds were released after authorization and the platform generated a settlement confirmation tied to pacs.008 style transfer data.
$12,480.00 paid to North Bay Medical Group
Payment reconciled into QuickBooks® workflow
The payer now sees the accounting result: matched invoice, cleared payable, settlement reference, and synchronization into accounting records.
Finalize the payer's response instruction
This screen lets the payer complete the response with action, amount, schedule, remarks, and fallback method before submission.
Desktop HTML Page Viewer
This side documents the same journey being shown on the smartphone. It is intended for product review, architecture planning, white-label demos, and business stakeholder walkthroughs.
Flow Summary
| Step | User Purpose | ISO / Rail Mapping |
|---|---|---|
| 1. Receive RfP™ | Payer receives invoice and request detail from payee | pain.013 inbound request |
| 2. Queue Actions | Payer reviews all currently open items and selects an action | pre-response workflow |
| 3. Choose Bank | Payer selects bank account and desired rail | pain.014 response composition |
| 4. Paid | Authorized payment is executed and confirmed | FedNow® / RTP® with pacs.008 transfer concept |
| 5. Reconcile | Post payment result to accounting and match invoice | SecureQBPlugin + QBO |
| 6. Complete Response | Payer finalizes accept, partial, pend, or decline details | pain.014 final outbound response |
Payer Decisions Supported
Approve now, schedule payment, partially pay, pend for supervisor review, decline, block sender, switch funding account, choose alternate rail, or redirect to financing. This makes the queue behave like a payer-side approval engine rather than an automatic debit flow.
Alternative Payment Paths
Alongside FedNow® and RTP®, the mockup includes ACH, Credit Card, Wire, and Customer Financing as alternate payer completion methods. That keeps the digital invoice and audit trail consistent even when the payer changes rails.
Key Data Elements Displayed in the Mockup
| Displayed Element | Example in Mockup | Why It Matters |
|---|---|---|
| Payee Name | North Bay Medical Group | Confirms the request origin and vendor identity |
| Invoice Number | INV-804422 | Supports AP matching and reconciliation |
| Amount Requested | $12,480.00 | Primary payer approval amount |
| Preferred Rail | FedNow® | Helps drive smart settlement routing |
| Response Outcome | Accept / Partial / Decline / Pend | Maps into payer action handling and pain.014 outcome |
| Settlement Proof | FN-240408-9901442 | Provides audit trail and accounting references |