Professional Payout Policy

Version 2.0.0 · Effective date of this publication: November 7, 2026. Existing transaction terms and acceptance records remain unchanged; publication alone does not record your acceptance.

1. Schedule and eligibility

For bookings enrolled in the weekly schedule, eligible earnings are released Fridays at 10 AM America/Los_Angeles time, after at least six full days from successful payment capture and after delivery approval. If the hold ends after that Friday’s release time, the next eligible Friday applies. Daylight-saving changes follow the named time zone. Dates in Earnings History are estimates until the transfer is confirmed.

2. Additional conditions

A transfer also depends on a valid Stripe connected account, required verification, available funds, accurate capture evidence and no unresolved payment dispute, refund, support hold or applicable account restriction. Delays may require review. A scheduled date is not a guarantee of funds arriving at the bank. View status in Earnings History or contact support with the reference if an estimate has passed.

3. Transfer versus bank deposit

LNZ’s transfer sends the professional’s net earnings to the connected Stripe account. Stripe’s bank payout is a separate event governed by account settings, verification and banking timing. Deposits may combine several bookings. LNZ is not a bank, escrow provider or insurer, and does not guarantee protection against chargebacks.

4. Fees, disputes and corrections

The transaction breakdown controls the disclosed fee and net amount. Refunds, disputes, duplicate payments and processing errors may require lawful correction or recovery of amounts already transferred. LNZ will not treat a support hold as forfeiture of earnings. Report a disputed balance promptly. Nothing in this policy authorizes an unspecified debit or eliminates nonwaivable payment or consumer rights.

5. Administrative exceptions

Authorized administrators may review and approve an exceptional earlier release or override an internal policy hold where supported by evidence. Such a decision is not a promised entitlement or a change to every booking’s schedule. It must not create duplicate transfers, release nonexistent funds or bypass Stripe’s restrictions. A manual exception can increase payment-recovery risk and must be documented.

6. Acceptance and existing bookings

Acceptance is recorded for the account with the policy document version, content fingerprint and server time, across client and professional views. The scheduling rule identifier is separate from this document version. Updating legal wording does not reset capture dates or move existing bookings into a new schedule. Older bookings requiring policy enrollment are reviewed separately with appropriate notice. Viewing this page alone does not count as acceptance.