Skip to content
Local Lead Legend Docs

Checkout & Onboarding

Local Lead Legend has an in-CRM payment-link generator and a public token checkout that turns an offer into a provisioned client account plus a charge — replacing the manual spreadsheet flow.

The pieces

Section titled “The pieces”
  • Offers — the priced rungs of the growth ladder (agency-owned, seeded from the offer catalog).
  • Checkout links — one unguessable, single-use token per offer × billing mode. A link moves through active → opened → paid and records the idempotent provisioning state.

The flow

Section titled “The flow”
  1. Generate a link. An operator creates a checkout link for an offer and billing mode (agency-only checkout-admin routes).
  2. Client opens the link. The public checkout resolves the token, collects the client’s details and payment method.
  3. Complete checkout. One idempotent transaction: ensure the Supabase user → create the CRM org, owner member, and tenant (provision) → create the Stripe customer → attach the payment method → run the billing mode → stamp the onboarding key → mark the link paid.

Idempotency is layered: a paid link short-circuits, the provisioned org / customer / user are reused, and Stripe idempotency keys are derived from the token.

Billing modes

Section titled “Billing modes”

The checkout supports several billing modes — monthly, quarterly (with a free month), a card-on-file trial, ACH (with a small discount), annual (prepaid), and a partial down payment with a scheduled balance. The recurring modes attach metered usage prices alongside the flat base, so a client’s monthly invoice is the flat base plus measured SMS / AI / voice usage. See the Rebilling Money Model.

Manual provisioning

Section titled “Manual provisioning”

A client provisioned outside the checkout flow (for example, billed via an old Stripe link) is provisioned by hand: create the org, owner, and tenant, then attach billing via the operator go-live fallback route.