Customer Approval and Payment

This scenario starts after inspection findings are ready.

Steps

1. Service Advisor creates or revises the estimate.
2. Service Advisor sends the estimate for customer approval.
3. Customer opens Approvals from the labeled sidebar or mobile navigation menu, or chooses Review estimate from the plate-first portal overview or a safe tenant link.
4. Customer confirms the plate, vehicle, service package charge, additional work total, and current version, then reviews every customer-visible finding, evidence indicator, quantity, discount, tax, and line total.
5. Customer chooses exactly one Approve or Reject decision for every available line, adds optional bounded notes, and submits the complete decision set once.
6. Approved work continues only when the current estimate has at least one approved line. An all-rejected response stays recorded and requires a new revision before work can start.
7. Staff creates an invoice from the exact current approved estimate version, or creates a payment request when payment is needed.
8. Customer opens Invoices, selects the invoice, and reviews the total, paid amount, balance, line items, recorded payments, and PDF state. When the invoice is settled, no further payment is requested even if an older attempt remains in its payment history.
9. If PayHere-backed online payments are ready, customer chooses Pay online, confirms the prepared amount, then explicitly chooses Continue to secure payment. Checkout is not auto-submitted.
10. Customer returns to the Motornauts payment page after the provider step. The public link can show only an active pending, processing, or review state while it remains valid. Use Check status to request a fresh backend result; the page does not poll or infer success from the browser return.
11. If the validated backend result is terminal or the link expires, the public capability becomes unavailable. The customer uses the authenticated portal or contacts the service center for final status; authorized staff use the protected payment workspace.
12. For an invoice-linked attempt started from the customer portal, return or cancel opens the exact authenticated invoice/payment-result page. Choose Check status again for a fresh saved-state read. Legacy invoice flows continue to return to invoice detail during rollout. Neither browser destination proves payment; use the backend result or contact the service center.

Understand the price before approving

The approval page separates the Service package charge from the Additional work total. Total if all work is approved adds the current package charge to every proposed additional work line. For example, a LKR 2,500 service package plus LKR 2,500 of additional work projects LKR 5,000 if all the work is approved.

Your line decisions apply to the additional work. Rejecting a line does not remove the service package charge. The invoice includes the package charge and the additional work you approved; review its final lines and total before paying. A package with no separate charge is labeled No separate charge.

If the package charge is unavailable or the package and additional work use different currencies, the page asks you to confirm the full price with the service center before approving. It does not show a combined total in that case. This price summary uses the current package charge; it is not a historical invoice or a promise that the charge cannot change.

Safe handling

Customers should not see provider technical details or staff-only notes. Staff should not alter payment amounts after link creation.

Historical estimate versions remain available for review, but their approval and billing controls are disabled. Refresh if Motornauts reports that a version was superseded.

If the estimate document is unavailable, use the customer-visible line items on the page and ask the Service Advisor for clarification. Do not treat a missing PDF as permission to guess a decision. If submission reports a changed version or expired customer session, refresh or sign in again and review the current lines before retrying.

PayHere hosts the card/payment entry step when online payments are ready. Motornauts does not store card numbers. A browser return from PayHere does not by itself mean the payment succeeded; the Motornauts page follows validated backend status from callback or reconciliation while the public link is active. A terminal callback revokes that link instead of turning it into a public receipt. The page removes the link credential from the address bar and keeps it only in the current tab. A temporary load retry checks status only; it never resubmits the payment. The authenticated invoice result is Motornauts confirmation state, not a PayHere tax receipt. It does not display provider orders, transactions, signatures, callbacks, readiness evidence, or raw checkout fields.