Pay-by-bank, built for the books
Most payment tools hand you money and a mess to reconcile. Simpli-FI Pay attaches the invoice and its purpose to the payment before it moves — so what lands is already coded, matched, and audit-ready.
Not a wallet. Not a checkout button.
A consumer app is built for the moment money moves. Simpli-FI Pay is built for everything that has to be true after: the right member, the right invoice, the right accounting category, the recurring authorization, and the record that proves it. All of it travels with the payment.
What it does
Turn on what an organization needs; each piece takes another manual step off the desk.
Each code resolves to a governed request for one specific thing — dues, an invoice, an event, a sponsorship, a donation. It carries the verified payee, the approved item, the accounting code, and where support goes. No raw bank data ever rides in the QR.
Scan, confirm the organization and the item, choose checking or savings, approve, keep the receipt. Pay once or set it recurring. The app stays calm because the business did the setup first.
Build a request with a live QR and link preview, an item catalog, approvals, an owner, an expiration, and QuickBooks-ready coding — before it ever goes live. The context you normally chase later is set up front.
Requests can be paused, expired, reviewed, supported, and audited. No stale codes floating around, no mystery links that outlive their purpose.
Every payment maps to its item, member, and event with a QuickBooks-ready CSV export mapped to your chart of accounts. CSV first; a direct sync follows once the accounting-integration controls are in place.
Owner, finance, operations, and a read-only auditor each see exactly their part. Every change is written to an append-only record, so the proof is there when someone asks for it.
Anatomy of a verified payment object
A number by itself tells you a payment happened. The object tells you what it was for, who it went to, how it should book, and how to prove it — the part no wallet, no checkout button, and no bank transfer can carry.
What the money is for. One specific item — not a blank amount into a blank account.
Who it goes to. The organization is confirmed before a single code is issued.
How it books. Pre-mapped to your chart of accounts, so revenue codes itself.
Where it stands. Draft, approved, paid, receipted, or expired — always current.
Who answers for it. A named route for questions, attached to the request.
How you prove it. A signed, append-only record — the layer that earns the gold.
Why you can trust it
Handling other people’s payments is a responsibility, not a feature. Simpli-FI Pay is designed so that’s true by construction.
The architecture is built to move money directly between bank accounts, so the platform is designed to avoid holding your funds in between. The payer chooses a linked checking or savings account — not a stored balance.
A QR carries the request, never raw bank details. Account information is entered by the payer, in their own banking step, and never travels in the object.
Requests, approvals, edits, and payments are written to an append-only audit trail. Access is scoped by role, and the read-only auditor can see it all without touching anything.
Independent SOC 2 Type II assurance is on the roadmap and shaping how it’s built — a standard we’re working toward, not a badge we claim today.
Who it’s for
Where it stands, honestly
Simpli-FI Pay is a working prototype in active development. Here is exactly what that means today, with nothing dressed up.
Pay-by-bank and the verified payment objectThe payer flow and the payee dashboard exist as a prototype on sandbox data.
No fee to the person payingThe payer app is free. An optional concierge setup for organizations is a flat one-time fee, arranged outside the app.
Real money movementLive bank-to-bank settlement is gated behind the payment-rail structure, a written payments-counsel opinion, and production controls. It is not enabled.
Direct accounting sync and SOC 2Export is CSV first; direct QuickBooks sync and independent SOC 2 assurance are roadmap targets, not current features.
Simpli-FI Pay is forming its first controlled pilots. Join the early-access list to help shape a payment layer that arrives ready for the books — and be first in when it opens.
Get early access