Loading
Loading
Money · CX · AR
PartialUS 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
Cash sits in AR because customers only pay when they pick up, and staff re-key card details over the phone.
Why it matters
Pay links reduce counter friction and after-hours collection.
Portal + invoice path keeps decisions and money on the same job history.
Honest Stripe modes prevent demo lies about live charges.
AR visibility on the owner dashboard only works if payments post correctly.
Proof from the live demo
Captured from the seeded multi-tenant demo. Open the same surface with demo credentials.


Stage sequence
Each stage lists the action, the business why, and the intended outcome. This is how we implement and test the product — not marketing fiction.
Action
Create GST invoice from approved RO lines.
Why this stage
Collection starts from a real tax invoice, not a verbal total.
Action
Send invoice with absolute pay URL (email/SMS adapters).
Why this stage
Customer needs a mobile-friendly path without a staff login.
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.
Action
Payment record updates invoice AR; owner dashboard reflects outstanding.
Why this stage
Books and board stay aligned on cash risk.
Related search intent
FAQ
Structured for buyers and search.
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.