Worker tips that everyone can verify.

The tip object, honestly

From src/lib/types/backend.ts: a Tip has workerId, tipAmount, callbackUrl, status, grossAmount, feeAmount, netAmount, paymentReference, paymentUrl, qrCodeUrl. Owners see gross/fee/net at /dashboard/owner/tips; workers at /dashboard/worker/tips; users at /dashboard/user/tips.

How a tip flows

1. Worker exposes QR (or PayPal.me where enabled) — the QR encodes the worker's tip endpoint.
2. Customer enters tipAmount and callbackUrl. POST /api/tips returns paymentUrl and reference.
3. After payment, PATCH /api/tips/{id}/paid can mark paid where the flow requires manual confirmation.
4. Owner reviews tip detail: gross (what customer paid), fee (platform fee), net (worker receives). Nothing is hidden in rounding.

Withdrawals without confusion

POST /api/tips/withdrawals and /api/transactions/withdrawals create withdrawal records with grossAmount, feeAmount, netAmount, status, createdAt. Owners track them at /dashboard/owner/withdrawals. Status is the source of truth — don't rely on screenshots.

Common mistakes

Tip QR doesn't resolve

Verify the worker's profile has a tipQrCodeUrl and that the workerId is valid. Worker accounts must be created by the Owner before tips work — self-registered workers can't appear without business linkage.

Callback URL missing

callbackUrl is required. It tells the tip service where to redirect after payment. Use an HTTPS URL you control, or the platform's default return URL shown in the tip form helper.

Fee looks wrong

Compare gross vs net, not tipAmount alone. Platform fees are computed server-side and exposed as feeAmount — the UI never calculates fees locally.

Links

• Barcode inventory — pre-tip: sell correctly first.
• Affiliate referrals — another earnings flow with visible fees.