Launch readiness score next to ledger view

Launch readiness is a score beside the prepaid ledger — not a vanity chip on a separate ops page. Product and finance must see the same red or green next to money rows. If wallet floor, webhook heartbeat freshness, or coverage honesty fails, the score stays red.

IOSOR is white-label prepaid CPaaS. USD 20 is the pilot floor; soft review near USD 1,000/month is not a green waiver. Not a day-1 runway or debit↔delivery rewrite. Related: Day-1 runway: what must be green, traffic_ok gate before pilot volume, When launch is blocked: status without lying, Wallet stop-lines before production.

Readiness score is not a vanity chip

Score aggregates hard gates: vault present, fresh webhook heartbeat (stale ≡ blocked), wallet floor and stop-lines proven, coverage honesty on quoted corridors, and one Live channel smoke that delivered.

Ledger view must show gates beside money

Put readiness chips in the same viewport as top-ups, holds, debits, and stops. Product owns chip labels; finance owns money rows; both read one screen. Do not hide a red wallet chip behind a green channel badge on another tab. When a debit posts, the adjacent score still reflects gates — not “money moved, so Live.” Keep Zone vs WORLD gate before production in the same loop as the ledger score.

Red when wallet heartbeat or coverage fails

Three non-negotiable reds: (1) prepaid below floor or stop-lines never forced; (2) webhook HB stale — same severity as missing vault; (3) coverage gap on routes you already priced. Any one keeps the score red and pilot volume at zero.

Fresh HB is not “200 once last week.” Correlation IDs must match ledger rows; silent drops keep traffic_ok blocked. Wallet red includes failed holds and unproven stop-lines — see Wallet stop-lines before production. No yellow “almost ready” for sales. See also Debit rows vs delivery status ledger.

One shared screen for product and finance

Split screens create split truths: product Live, finance blocked. One ledger-with-score: one reason code, one freshness timestamp, one export row (score, reason, HB age, wallet, coverage, smoke). Override needs a named owner, written reason, and a new smoke before green. Near USD 1,000/month, mismatched chip and ledger is a reconciliation incident. See When launch is blocked: status without lying.

Buyer checklist for readiness on ledger

1. Are readiness chips beside top-ups, holds, and debits — same viewport?
2. Does wallet red (floor, hold, stop-line) force the score red?

Start with IOSOR

Open the IOSOR ledger console and anchor the readiness score widget directly alongside your active balance, holds, and debit rows. Verify that stale webhook heartbeats or unproven stop-lines immediately turn the score chip red in the main viewport. Run a single live channel smoke test to validate that reason codes and freshness timestamps update in real time for both product and finance teams.

IOSOR takeaway

Placing hard readiness gates on the same screen as financial debits guarantees that traffic cannot flow under silent failures.