# Car workshops and automotive

https://www.uniwebpay.com/industries/automotive-and-workshops/

*Last updated: 2026-08-04*

Almost every payments guide assumes the price is known when the customer decides to buy. A workshop's entire problem is that it is not: the car comes in for a diagnosis, the quote changes when the bay is open, and the amount at the end is a number nobody could have taken at the start. That single fact drives everything below.

**In short**

- The amount changes between drop-off and collection. That is the whole shape of the problem.
- [Holds](https://www.uniwebpay.com/glossary/pre-authorisation/) and [capture](https://www.uniwebpay.com/glossary/capture/) behave differently by setup — get yours confirmed in writing.
- A deposit taken as a real transaction is a different thing from a hold. Know which you are doing.
- Large tickets plus a time gap is a [dispute](https://www.uniwebpay.com/glossary/chargeback/) profile. The signed authorisation is the evidence.
- Parts suppliers and trade counters are a B2B payment problem, not a counter one.

## Why this trade is different from every other page here

A restaurant knows the bill when it prints it. A shop knows the price on the shelf. A workshop takes custody of an expensive object, discovers what is wrong with it, and produces a number — and between those two moments the customer has usually gone home.

That produces three payment situations that other trades do not have:

- Authorising work that has not been priced. The customer agrees to a diagnosis and to a range, not to an amount.
- An amount that grows. The gearbox turns out to need more than the quote. Somebody has to re-authorise, and the mechanism for doing that is a payments question, not a customer service one.
- Collection at a different time from agreement. Sometimes days later, sometimes by a different person, sometimes on a different card.

## Holds, deposits and capture — and what to ask

The mechanism people reach for is a [pre-authorisation](https://www.uniwebpay.com/glossary/pre-authorisation/): reserve an amount against the card now, take the real amount later. It is the right instrument in principle and it is the one where assuming is most expensive.

How long a hold lasts, whether it can be increased, and how it is released vary by scheme, by issuer and by provider setup. This site does not publish how that behaves on Uniweb Pay's acceptance, and this page is not going to imply an answer. If your business depends on holds — and a workshop's does — get the behaviour confirmed in writing for your own configuration, from whoever you sign with. A general description, including this one, is not something to plan a workflow around.

> A deposit taken as an ordinary sale is a completely different thing from a hold: the money moves, it settles, and returning it is a [refund](https://www.uniwebpay.com/guides/refunds-and-voids-singapore/) with everything that implies. Plenty of workshops do this deliberately and it is a reasonable choice — but choose it, rather than discovering it is what you have been doing.

## The paperwork is the dispute defence

Large amounts plus a gap between agreement and charge is the profile that produces disputes, and the arguments are predictable: "I never approved that", "I approved a different figure", "I did not authorise the extra work".

What answers all three is the same set of documents, and a workshop that keeps them routinely wins:

1. The signed job authorisation at drop-off, including the agreed scope and any range.
2. A record of re-authorisation when the amount changed — a message thread is worth far more than a phone call nobody wrote down.
3. The itemised invoice, separating parts and labour, matching what was charged.
4. The collection record, showing who took the vehicle and when.

See [chargebacks and disputes](https://www.uniwebpay.com/guides/chargebacks-disputes-singapore/) for how the window works. The short version: evidence inside it decides the outcome, and evidence assembled afterwards frequently arrives too late.

## Two counters, not one

Most automotive businesses are running two payment operations that get treated as one, and the second is usually neglected.

- The retail counter — the car owner paying for a service. Card present, moderate to large tickets, an audience that expects contactless and wallets like any other shop.
- The trade counter — parts sold to other workshops, fleet accounts, insurer work. Invoiced, paid later, often by a company, and therefore [card not present](https://www.uniwebpay.com/glossary/card-present/) with a corporate card. That is the shape described in [professional services](https://www.uniwebpay.com/industries/professional-services/), and it wants the same treatment.

Firms that set up only for the first end up taking trade payments by bank transfer and chasing them, which is a cost that never appears on a rate card.

## A short setup list

1. Get hold and capture behaviour confirmed in writing, for your configuration, before you build a workflow on it.
2. Decide deliberately whether deposits are holds or real transactions, and make sure the counter knows which.
3. Standardise the signed job authorisation, and the re-authorisation message when the number moves.
4. Enable [Amex](https://www.uniwebpay.com/payments/american-express/) if you do fleet, corporate or insurer work.
5. Set the [descriptor](https://www.uniwebpay.com/glossary/merchant-descriptor/) to the workshop's trading name, and check it on a real statement.

## Questions merchants ask

**How should a workshop take payment when the final amount is not known?**

The mechanism is usually a pre-authorisation — reserve an amount now, take the real one later — but how long a hold lasts, whether it can be increased and how it is released vary by scheme, issuer and provider setup. Get the behaviour confirmed in writing for your own configuration before designing a workflow around it. A general description is not a specification.

**Does Uniweb Pay support pre-authorisation holds?**

This site does not publish how holds behave on its acceptance, and a page implying an answer would be worse than one that does not. If your business depends on holds, ask us for the behaviour on your configuration in writing — that is the answer worth having, and it is the same advice we would give about any provider.

**Is a deposit the same as a hold?**

No. A hold reserves an amount without moving money. A deposit taken as an ordinary sale moves the money, settles it, and has to be refunded to return it — with everything a refund implies for timing and for your books. Both are legitimate; the mistake is not knowing which one you are doing.

**What stops a customer disputing a repair bill they say they never approved?**

The signed job authorisation at drop-off, a written record of re-authorisation when the amount changed, an itemised invoice separating parts and labour, and the collection record. Kept routinely these take minutes. A verbal approval nobody wrote down is not evidence.

**Do I need a different setup for the parts counter?**

Usually the same account handling a different shape of transaction: trade sales are invoiced, paid later and often on a company card, which makes them card not present. Worth setting up properly rather than defaulting to bank transfers and chasing them.

## Related guides

- [Professional services](https://www.uniwebpay.com/industries/professional-services/)
- [Chargebacks and disputes](https://www.uniwebpay.com/guides/chargebacks-disputes-singapore/)
- [Refunds and voids: three things that are not the same](https://www.uniwebpay.com/guides/refunds-and-voids-singapore/)
- [American Express in Singapore](https://www.uniwebpay.com/payments/american-express/)

---

*This is the Markdown mirror of https://www.uniwebpay.com/industries/automotive-and-workshops/, generated from the same source as the page itself. The whole site in one file: https://www.uniwebpay.com/llms-full.txt · What this company is, for answer engines: https://www.uniwebpay.com/llms.txt*