Payment links tied to traffic-ticket cases

How it works

Workflow steps

1. The attorney reviews case context and fee details.
2. A payment request is created from the case or billing workflow.
3. Payment status, provider blockers, and follow-up signals stay visible to the case team.
4. Hosted payment routes are noindexed and separated from crawlable marketing content.

Capabilities

What this workflow covers

• Attorney billing workspace with Create Request, Requests, Payout History, and Settings views.
• Create payment request workflow for existing case or manual/direct-client billing matter.
• Amount, due date, payment link vs request-only mode, client name, email, phone, state, court, county, matter type, optional client message, internal notes, and optional email delivery.
• Payment request tracking for status, due date, paid date, email delivery, and payment page URL.
• Attorney fee, platform fee, card fee, platform retention, attorney payout, fee payer labels, and payout status.
• Copy/open hosted payment page and sync pending Stripe status.
• Offline payment handling for cases.
• Payout history by case.
• Billing analytics dashboard with MTD/YTD payout metrics, payment counts, Stripe/LawPay payout stats, refunds, service/product breakdowns, and recent payout payments.
• Stripe Connect setup to start/resume onboarding, refresh payout status, open Stripe dashboard, and display requirements due or payout blockers.
• Billing settings for platform fee payer, Stripe processing fee payer, checkout branding, public business name, support email/phone, website, statement descriptor, colors, logo, icon, and retry/sync Stripe branding.
• LawPay merchant ID and settings support.

Traffic-ticket value

Why it matters for citation work

The value is keeping traffic-ticket work organized around the citation and the next case step instead of a generic matter record.