Finish the job. Get paid.

A customer should see what work was performed, what was approved, what is owed, and any deposit already collected. A well-written invoice or payment request reduces confusion before a payment even starts.

Some customers prefer a secure link on their phone. Others want to pay while the technician is on site. A business may also need to issue a payment reminder or record an offline payment. Each option has different card-security and provider requirements; verify available methods before promising them.

Owners need to distinguish issued invoices, partial payments, refunds, and amounts still due. Finance needs enough history to reconcile settlements and investigate exceptions. A payment should never be treated as complete just because a customer clicked a button.

Illustrative example: a $620 repair with a $150 deposit leaves $470 before any further adjustments. A failed payment attempt must leave that balance open; a refund needs its own record.

Card details should go through an approved payment provider instead of being stored in ordinary job notes. Confirm the exact checkout flow, processing terms, refund handling, and what staff can view. Never encourage staff to photograph a customer's card as a shortcut to processing.

• Verify which payment methods the real provider currently accepts in the target market.
• Check deposit, partial payment, duplicate event, failed card and refund cases.
• Confirm that raw card details never appear in ordinary job records, logs or message history.
• Compare the bank settlement to the invoice and provider transaction history.