Skip to content
Workshop Wrench

Money · CX · AR

Partial

Collect after-hours without re-typing card numbers

US leaders package text-to-pay tightly. Workshop Wrench ships payment records and pay URLs on invoices, portal pay path, and Stripe Checkout that is Stub without keys and live when configured — never Connected theatre by default.

Primary persona: Advisor / owner

The problem

What breaks without this process

Cash sits in AR because customers only pay when they pick up, and staff re-key card details over the phone.

Why it matters

Rationale — profit, risk, and shop floor truth

  1. 01

    Pay links reduce counter friction and after-hours collection.

  2. 02

    Portal + invoice path keeps decisions and money on the same job history.

  3. 03

    Honest Stripe modes prevent demo lies about live charges.

  4. 04

    AR visibility on the owner dashboard only works if payments post correctly.

Proof from the live demo

Real UI — not a pitch mockup

Captured from the seeded multi-tenant demo. Open the same surface with demo credentials.

live demo capture
GST invoices list with payment status
Tax invoices and AR from approved work. AU-first money path.
live demo capture
Customer portal estimate line approval without a shop login
Approve or decline lines from a token link. The customer never needs a staff account.

Stage sequence

Step-by-step use case

Each stage lists the action, the business why, and the intended outcome. This is how we implement and test the product — not marketing fiction.

  1. 01

    Issue tax invoice

    Action

    Create GST invoice from approved RO lines.

    Why this stage

    Collection starts from a real tax invoice, not a verbal total.

    Surface: Invoices / ROOutcome: Invoice issued
  2. 02

    Share pay path

    Action

    Send invoice with absolute pay URL (email/SMS adapters).

    Why this stage

    Customer needs a mobile-friendly path without a staff login.

    Surface: Comms / invoiceOutcome: Link delivered or copyable
  3. 03

    Checkout or portal pay

    Action

    Customer opens pay link — Stripe Checkout when keys set; stub otherwise. Portal pay reuses PaymentsService honesty.

    Why this stage

    PCI offload; status must match env keys.

    Surface: Portal / StripeOutcome: Paid or honest stub
  4. 04

    Record & AR

    Action

    Payment record updates invoice AR; owner dashboard reflects outstanding.

    Why this stage

    Books and board stay aligned on cash risk.

    Surface: Invoices / dashboardOutcome: AR truthful

Related search intent

  • text to pay auto repair
  • invoice pay link workshop
  • stripe shop invoice

FAQ

Questions on this flow

Structured for buyers and search.

Is Stripe live in every demo?+

No. Without STRIPE_SECRET_KEY the path is an honest stub. With keys, Checkout can run in that environment — SaaS subscription billing is a separate stub.

Run this flow in Workshop Wrench

Start a trial or open the seeded multi-tenant demo — same processes, real data.