successful production payments recorded
Turn every repair order into a clear path from diagnosis to payment.
Perno Mechanics keeps the customer, vehicle, estimate, workshop status and payment together. Your team works from one repair record while customers get a simple public status and payment journey.
Volvo V60 · brake service
Jan Driver · diagnosis complete
Estimate ready
linkCustomer, vehicle, work and payment stay connected
Built on payment infrastructure already working in production.
A conservative snapshot of Perno's production footprint—not a forecast or an invented customer claim.
payment providers represented in live transactions
specialist industry payment products
processed payment value in the leading production currency
Live database snapshot for 29 October 2026. Values are rounded down and sandbox transactions are excluded. Different currencies are not combined.
A repair order in one tool and its payment in another leave your team joining the dots.
When customer details, vehicle history, work items and payment confirmations are disconnected, every handoff creates another question.
Approvals in messages
The customer decision is separated from the estimate and repair status.
Payments without repair context
A transfer or terminal receipt does not explain which vehicle or order it belongs to.
Scattered vehicle records
Customer, vehicle and repair details are copied between notes, sheets and inboxes.
Collection happens too late
Parts, deposits and completed work are harder to collect when payment starts after the handover.
Keep the commercial context attached from intake to paid repair.
Perno Mechanics gives the workshop a focused operating layer while Perno Orchestration handles the payment foundation beneath it.
Find the customer quickly
Search workshop customers by name, business, email or phone and load only their vehicles.
Build the repair record
Keep the issue, diagnosis, work, employee and status on one order.
Price the work clearly
Add labor, parts and other costs so the total follows the estimate.
Collect in context
Create a hosted payment request connected to the customer, vehicle and repair.
From vehicle intake to confirmed payment in three steps.
Create the customer and repair
Choose the customer, their vehicle and the employee responsible for the order.
Add work and price
Record diagnosis, labor, parts and other items while the order total updates.
Request and track payment
Share a hosted payment link and see the result return to the repair order.
A workshop workflow with payments built in—not bolted on later.
Explore the public profile, customer and vehicle records, repair orders, reusable payments and orchestration layer.
Workshop profile
Publish a branded workshop page with contact details, services and direct payment options.
Customers and vehicles
Keep each workshop customer connected to their vehicles, contact information and repair orders.
Repair orders and estimates
Track diagnosis, work, employees, statuses and priced estimate items on one automotive repair order.
Payment links and QR codes
Collect repair and workshop payments remotely or at the counter through hosted links and QR codes.
Recurring payments
Offer monthly, quarterly or yearly automatic card payments for workshop and fleet services.
Payments and orchestration
Review workshop payment attempts and route them through the shared Perno Orchestration foundation.
For automotive businesses that need each payment to explain what it is paying for.
Independent workshops
Manage repair orders and remote payment collection without enterprise overhead.
Tyre and service centers
Collect defined services and keep each payment tied to the right customer.
Specialist repairers
Build detailed estimates for diagnostics, parts and specialist labor.
Fleet service partners
Keep company customers, vehicles and recurring service payments organized.
Replace disconnected workshop admin with one traceable payment journey.
Customer and vehicle reselected from a long list
Fast customer search followed by only that customer's vehicles
Estimate in a note and payment in a separate system
Priced repair items connected to one payment request
Generic transfer title with no workshop context
Customer, vehicle, order and payment kept together
Payment links created differently each time
Reusable links and QR payments on the same orchestration layer
Start with one repair flow and expand as your team adopts it.
Does the customer need a Perno account?add
No. Public workshop, repair-status and payment pages do not require the customer to log in.
Can I connect more than one vehicle to a customer?add
Yes. Vehicles belong to the customer, and repair-order selection shows only that customer's vehicles.
How is the repair total calculated?add
The order total is calculated from labor, parts and other estimate items with quantity and unit price.
Can I share a payment outside the repair order?add
Yes. Workshop payment options provide reusable public payment links and QR codes.
Does Perno replace my payment provider?add
Perno Orchestration connects the workshop flow to configured payment providers and records the result in one consistent model.
Give your team one repair record—and your customer one clear next step.
Set up the workshop, add your first customer and vehicle, then take a repair order from estimate to payment.