55k+
successful production payments recorded
arrow_backPerno Mechanics
Payment control behind the workshop
See what was requested, who attempted to pay and what happened next.
Perno keeps repair-order and reusable payment attempts visible while the orchestration layer handles provider routing, hosted checkout and status updates.
account_tree
What you get
A consistent payment history across every workshop payment surface.
car_repairPerno Mechanics
account_treePerno Orchestration
account_treePayments and orchestration
Verified platform activity
Built on payment infrastructure already working in production.
A conservative snapshot of Perno's production footprint—not a forecast or an invented customer claim.
3
payment providers represented in live transactions
5
specialist industry payment products
976k+ PLN
processed payment value in the leading production currency
Live database snapshot for 30 October 2026. Values are rounded down and sandbox transactions are excluded. Different currencies are not combined.
Why change
A successful checkout is not enough if the workshop cannot connect it back to the job.
check_circle
Provider dashboards do not show the repair-order workflow.
check_circle
Payment notifications lose the source service or vehicle.
check_circle
Different payment channels produce different operational records.
What you get
Shared payment infrastructure with vertical workshop context.
Workshop context
Keep the customer, vehicle and workshop identity attached to the workflow.
Clear amount
Create a defined amount from a repair estimate or reusable workshop offer.
Hosted payment journey
Give the payer a public Perno page rather than an internal dashboard URL.
Online and counter sharing
Use a direct link or QR code from the same payment context.
Perno Orchestration
Route the payment through the workshop owner's configured infrastructure.
Visible outcome
Keep attempts, statuses and paid state available in the workshop dashboard.
How it works
A consistent payment history across every workshop payment surface.
Step 01
Create from Mechanics
The workshop produces a payment request with its own source context.
Step 02
Route with Orchestration
Perno uses compatible configured merchant accounts and hosted checkout.
Step 03
Return the status
Payment activity and the repair paid state update from the transaction result.
Common uses
One foundation under all workshop collection paths.
check_circleRepair-order payment
check_circleReusable service payment
check_circleRecurring subscription
check_circleDirect public link
check_circleQR collection
check_circlePayment-attempt review
Questions
Payments and orchestration
Must I choose a provider for every payment?add
Perno Orchestration can route through the configured eligible merchant accounts.
Is the original workshop context retained?add
Yes. Payment requests retain source app, source type and source identifier information.