Quick read on each piece. Don't treat anything below PENDING or [to confirm] as working.
| Piece | Status | Note |
|---|---|---|
| Stripe available on the Scoro plan | CONFIRMED | Verified in the live Scoro instance 2026-06-04 — present, not paywalled. |
| The Stripe account is healthy & can take payments | CONFIRMED | Mhondoro Capital Partners, LLC (Bluevine-associated). Card + ACH active; has processed real charges. |
| Native "Connect Stripe" works for the account owner | CONFIRMED | Mack connected it himself 2026-06-12 (owner login). |
| Connected to the right Scoro entity | PENDING | Connected to legacy julieh, not the V2 promount target. Awaiting Mack's re-connect on promount. |
| Pay-now button live on invoices | PENDING | Templates not yet edited; needs a snapshot first. |
| End-to-end test charge passed | PENDING | No full pay → invoice-marked-paid test completed yet. |
| Exact Scoro fee in USD | [to confirm] | Scoro docs quote fees in EUR only; the USD figure shows only after connecting. |
| Pay-now appears on regular invoices but not prepayments | [to confirm] | Stated in Scoro docs; can't be checked in-instance until connected. |
Sources (in the 018-stripe-payments research worktree — not yet merged to main; this runbook reconciles with them when Stripe goes live): specs/018-stripe-payments/spec.md; .data/architecture/stripe-payments-research-2026-06-04.md; scoro-stripe-live-ui-verify-2026-06-04.md; stripe-bluevine-checkout-apikey-finding-2026-06-11.md.
Once it's live, the everyday flow is short:
These are the real reasons it's not live. Each is being worked; none is "done."
julieh entity, but V2 invoicing runs on promount. The fix is a 2-minute disconnect-and-reconnect that Mack has to do (owner login required). Lisa asked him 2026-06-12; we're awaiting it.apiKey is not set error during testing turned out to be a generic Stripe one-shot-URL quirk (a pay link visited twice), not a block from the bank. Standalone Stripe payments do work on this account. CONFIRMED 2026-06-11.This is being done in three steps, in order — confirmed with Mack on the 2026-06-11 call. We build the simple thing first, then add automation later.
Native Scoro + Stripe, card and ACH. This is the core win and the only part Scoro supports natively. PENDING go-live.
Prepayment + final handled as two regular invoices, each with a pay-link. The deposit math is done by hand — as Mack put it, "somebody's just going to need a calculator." See the Deposits section.
An automatic prepayment-to-final link is deferred and re-decided later — not urgent now. Would be custom build work.
Until Phase 3, a deposit job is handled as two regular invoices, and both can carry a pay-link. Here's the difference from "all automatic":
One "prepayment" invoice with a Pay-now button
Scoro can't put a pay-link on a prepayment invoice. Phase 3 only.
1. Regular invoice for the deposit (e.g. 50%) → pay-link
2. Regular invoice for the balance → pay-link
Deposit math done by hand. A calculator, basically.
Heads up: because both are regular invoices, you'll track the deposit-vs-balance relationship yourself for now. That's the trade-off for shipping online payments sooner. PENDING — exact step-by-step for the two-invoice flow will be written once Phase 1 is live and verified.
Today Mack already adds a flat 3% to invoices by hand and then sends a payment link, and already offers ACH. CONFIRMED on the 2026-06-11 call. That stays the same in v1 — nothing automatic is being built to add the 3% for you.
Stripe is connected in Scoro through a one-click "Connect with Stripe" button (an OAuth login — not pasting an API key). The account owner has to be the one who connects.
promount entity, not julieh. The Stripe connection is entity-scoped — it only exists on the entity you connect from. CONFIRMED 2026-06-12 by live check.julieh. Disconnecting/reconnecting is a structural change — capture a snapshot of the connected state first (snapshot rule + Principle IX). Already-issued invoices keep their pay-link even after a disconnect.Once connected, the Pay-now button is added to invoice PDF and email templates. With ACH on, it shows Card + Wallet + Bank; without, just Card + Wallet.
.data/snapshots/pdf-templates/{date}-stripe-paylink/ and commit it before editing.[to confirm] the exact field name and that it renders the expected buttons — confirmable only after connect.
Go-live happens only after these pass in test mode. This is the guard against the QBO mistake.
QuickBooks stays the accounting system. The rule that prevents double-counting: Scoro is the single hub — Scoro sends the invoice to QuickBooks, and there is no separate per-charge connector pushing the same payment in again.
For v1 these are manual — there's no automatic write-back. CONFIRMED (Scoro docs don't cover it). At Pro Mount's volume this is rare enough to do by hand.
A full step-by-step for the manual refund flow will be added once Phase 1 is live.