340 transactions this month: $509K gross, $478K net after fees and refunds, 91.5% auth success and $296K in open disputes. Payments shows the rate, the fee on every row, and a priced path to a better rate.
The optimization panel prices its own claim: +4.2 points of auth rate is worth $21K of recovered volume this month, “priced off MTD gross $509K — recovered auths flow straight to gross, fees unchanged.”
payments.cedxsystems.com — live build
Runs on demo data — the optimizer labels its own framing: “A/B framed from the weekly trend”.
2.6% effective fee ratedown 0.12pp · fee and net on every transaction
$524K in transit90 payouts · 11 failed and rerouting
What it is
Acceptance, cost and settlement on one board.
Three levers, priced in recovered dollars
The auth optimizer models three levers against the weekly trend: smart retry timing at issuer-ledger hours (+1.6pp), network route selection per issuer (+1.8pp), and low-risk auth-flow exemptions (+0.8pp). Together they project 91.5% to 95.7% — $21K of recovered volume MTD.
Control 93.8% vs test 95.0% on the bars
Each lever's contribution printed in points
Priced off MTD gross, on screen
payments — overview
Fee and net on every transaction
340 transactions with status, amount, fee, net and method. A $19K charge from North Freight cleared at a $312 fee; a $24K charge sits pending at $460; the disputed rows carry their own state instead of vanishing into a total.
Every active method — card, wallet, ACH, bank debit — carries volume, transaction count, ok%, decline%, optimized% and fee%. Card ··4242 runs 96% ok at 2.70% fee; one wallet rail runs 91% at 3.85% — the fee-leakage alert exists because this table exists.
ok% · decl% · opt% · fee% per rail
High-decline count 31 on a card
$3.57M volume attributed
payments — screen-3
Product tour
Four screens, captured from the running build.
Not a mockup and not a concept deck. This is what opens at /app/payments.
payments.cedxsystems.com
01 — Overview
Acceptance as a number you can move
Gross MTD $509K, net $478K, effective fee 2.6% down 0.12pp, auth success 91.5%. The right rail prices the problems: evidence deadlines closing on 15 disputes at $32K, wallet fee leakage at $5.5K, and $1.1M of bank lines not yet matched.
Auth health ring at 92
22 failed · 48 open disputes counted
Alerts priced in dollars, not severity words
02 — Transactions
The ledger of every attempt
340 rows newest-first with the economics on each: amount, fee, net. Success rate 91.5% with 22 failed is a card above the table, and the disputed $296K has its oldest item — $111K — printed next to it.
Search by txn, customer or last4
340 rows · $509K gross MTD in view
CSV of the filtered view
03 — Methods
Where the declines actually live
The 31 high-decline rows are findable here: one ACH rail at 84% ok with a 3.11% fee, a bank-debit rail at 89%. The optimized column shows what the levers would do per rail — 95.2% on the wallet, 97.5% on the primary card.
48 active rails · avg success 90%
Declines and fees side by side
Card · Wallet · ACH · Bank debit chips
04 — Payouts
Settlement, watched until it lands
90 payouts with status, amount, transaction count, arrival date and bank. $401K arrived MTD, $524K is in transit, and 11 failed payouts are a count on a card with reroute as the next action.
Paid · In transit · Pending · Failed chips
Arrival date per payout
Banks masked to last4
Who runs it
Three roles watch the money move.
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Store and checkout ops
Sees acceptance the way the queue does — declines, retries and which rails are having a bad week, at 91.5% and climbing.
auth 91.5% · target 95.7%
Disputes
Works the 15 evidence deadlines before they lapse — $32K of disputes need a response, and the oldest open dispute is $111K.
15 deadlines · $32K
Treasury
Watches the $524K in transit and the $1.1M of unmatched bank lines — settlement is a cash-forecast input, not a surprise.
$524K transit · 69% reconciled
The shape of it
What the demo workspace actually looks like.
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
Largest rails by attributed volumefrom the methods capture
Card ··4242$420K
Card ··5555$286K
Card ··1005$198K
ACH · operating$168K
Wallet · primary$142K
Auth healthsuccess score · printed on the overview
92
Successful auths · 91.5%
22 failed · 48 open disputes
Settlement reconciledbank match · 37 lines still unmatched
Reconciled · 69%
Unmatched · $1.1M of bank lines
How it runs
A payment's life, in the order it actually happens.
01
Attempt
Every auth lands on the transactions table with its method and outcome — 91.5% succeed, 22 fail, and the failures keep their state.
02
Optimize
The three levers model the recovery: retry timing, route selection, exemption use — priced at $21K of volume this month, A/B framed from the trend.
03
Dispute
Chargebacks become a deadline queue: 15 need evidence, $32K at stake, oldest open at $111K — before they become automatic losses.
04
Settle
Payouts carry arrival dates per bank; failures reroute. Reconciliation sits at 69% with the unmatched $1.1M visible until it clears.
One record
The charge is one record across the estate.
These captures come from one demo workspace — Northline Systems — so the customers and amounts here are the same ones the rest of the finance apps carry.
Finding this out on the third call is worse for you than reading it here, and worse for us.
Payments is not generally available. What opens today is the live build running on demo data — the 340 transactions and 48 rails are the demo book, not your processing history.
We have no named customers to show you, so this page shows none. Northline Systems in the captures is the software's demo workspace, not a reference.
The 95.7% projection is the optimizer's own A/B-framed estimate, labelled as such on screen. We are not claiming your auth rate will move by 4.2 points.
We are not claiming to be a payment processor or to hold funds: the captures show rails and banks by masked identifier, and no money-movement licence is asserted here.
No audit or compliance certification (including card-scheme audits) has been issued for Payments. What we can evidence about hosting, encryption and access is on the security page.
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/payments. It runs on demo data.
How does the auth optimizer work?
Three named levers, each with its contribution printed: smart retry timing at issuer-ledger hours (+1.6pp), network route selection per issuer (+1.8pp), low-risk auth-flow exemptions (+0.8pp). The projection is A/B framed from the weekly trend — control 93.8%, test 95.0% — and priced off MTD gross.
Where do the fee figures come from?
From the rows. Every transaction carries amount, fee and net; every rail carries its own fee% — from 0.54% on one ACH rail to 3.85% on the wallet. The 2.6% effective rate is the aggregate of those, down 0.12 points.
What happens to a failed payout?
It is counted and rerouted. The payouts screen shows 11 failures as a card-level figure with the failed state on each row, alongside the $524K in transit and its arrival dates.
Is Payments audited or certified?
No certification has been issued, including card-scheme audits. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
The board is live. Go and look at it.
Live build, demo data, no card. Then pull your own auth rate and see what 4.2 points would be worth.