Administration
Control the consumer VHP product safely
Configure VHP launch, price, Stripe mapping, gifts, promotions, dealer credits, ownership support, refunds and release readiness.
The consumer product has a separate launch control from the workshop VHP module. Keep public launch off until product configuration, Stripe mapping, vehicle-data readiness and the controlled release checks have passed.
Stripe setup
- Configure the Stripe publishable key and protected secret credentials in the dedicated Stripe settings area.
- Create and map the one-time consumer product and price, plus any dealer credit-package products and prices.
- Use TEST mode for staging and confirm that MotoDesk shows the intended account mode.
- Confirm that the required Stripe payment and refund events are connected through the approved operator setup.
- Never copy real secret values into documentation, screenshots, support tickets or ordinary data records.
Launch readiness
- Consumer product, public signup and checkout have independent switches.
- MotoDesk blocks paid launch when product/price mapping or Stripe credentials are missing.
- TEST and LIVE are visibly distinct and normal staff cannot switch them.
- The existing workshop VHP remains independent when consumer launch is off.
Complimentary activation channels
A qualifying garage-customer activation requires a same-tenant real vehicle, real customer relationship and completed qualifying job. Staff-benefit credits are a separate configurable garage ledger and do not require a job. Admin gifts require recipient, vehicle, reason and explicit confirmation. A full free promotion never fabricates a Stripe transaction.
Dealer and staff credit ledgers
Dealer purchases, grants and redemptions are separate from garage staff-benefit allowances and adjustments. Do not edit mutable balances. Each usable balance is derived, tenant-scoped and cannot go negative; funding and handover are transactional and idempotent.
Refunds and ownership support
A refund changes commercial entitlement state and marks support review. It does not delete the Passport or vehicle history. Ownership claim decisions require a recorded reason; registration, email matching, a public QR or a dealer credit alone cannot prove ownership.
Prelaunch operator checklist
- Verify the protected Stripe credential state without displaying secret values.
- Verify DVLA/DVSA service readiness without changing live customer information.
- Complete the current VHP data-integrity and release-readiness checks.
- Complete the approved product, payment, public-page and documentation validation.
- Keep public launch OFF during deployment and controlled internal checks.
- Enable only after explicit commercial approval.