Do I need a card terminal to take cards at a car wash?

No. With a payment link or a QR code the customer pays from their own phone with their own card, and no hardware is involved. A terminal's advantage is customer familiarity; its drawbacks are that it is fixed in place and that it never tells your software what it just approved.

Does the money come straight to us?

In a properly built setup, yes: the business connects its own merchant account and the money lands there. In models where funds are pooled and forwarded later, someone else holds your balance and the payout calendar is not yours. This is the first question to ask.

How many fees am I paying?

The payment provider's processing fee always exists and is normal. What matters is whether the software takes a second fee on top — if it does, you should know that before you sign up.

The customer paid but the job didn't close — why?

The most common cause is a test-mode mismatch: if the merchant account is in test mode at the provider while the app is set to live (or the other way round), the payment is not treated as real and never reaches the till. A well-built system says so plainly on screen; once the mode is corrected and the link regenerated, the flow continues.

Should online takings be separated from card in the till?

Yes. If your own terminal's takings and online payments fall into one bucket, the end-of-day cannot separate them — and the two reach your bank on different schedules anyway. Keeping them on separate lines is what makes reconciliation possible.

Does collection stop if the internet drops?

Card collection needs a connection — that is unavoidable. But opening jobs, handing cars over and taking cash must keep working offline. A setup where a dropped line stops the whole business is not acceptable.

For car washes, valeting and detailing shops

Taking card payments at a car wash: terminal, payment link and QR

At a car wash, collecting money is not a till operation — it is a handover operation. The car is pulled up, the customer is standing there, someone's hands are wet, and if it is clear how payment happens the job ends. If it isn't, everybody waits. This page covers the forms card payment takes at a wash and in a detailing shop, which one fits which situation, and what to check before you commit to one.

The question is not "do you take cards". The question is who learns that the money arrived, when, and from where.

What breaks as cash thins out

Change. When the float runs out you either hold the car or round the price. Both cost you.
"I'll pay next time." With no card option, the regular customer slides into credit; the ledger grows and collection slips.
Two records that never meet. The terminal has its own total, your system has another. Reconciling them is manual, and when they disagree nobody can say why.
Delayed handover. The car sits in the yard while the payment method gets sorted out — and so does the job behind it.

Three routes, three different problems

1. A physical card terminal

The familiar one. You get a device from the bank, the card is tapped, a slip prints. Its strength is habit: every customer already knows it.

The difficulty at a wash is that the device is fixed while the work moves. The car is at the exit; the terminal is in the office. And there is the record problem — the terminal says "approved" on its own screen, your software never hears about it, and someone matches the two by hand.

2. A payment link

A link is created for the amount and sent to the customer over WhatsApp; they pay from their own phone with their own card. No hardware.

Its real value shows with a customer who isn't there: they dropped the car off and left, the work is finished, you send the link, and the money is in before the car is handed back. It also fits fleet and corporate work, where the person paying is usually not the person who brought the car.

3. A QR code

The same link, shown on screen. When the customer is standing in front of you this is the fastest route: they lift their phone, scan, pay. No paper, no device, no mistyped amount.

Its quiet advantage is contact — nobody has to hand over a terminal or take the customer's phone with wet hands.

The thing that actually matters: who saw the payment

All three routes face the same test. When the money lands, does your record learn it by itself, or does someone have to go and mark it?

Manual marking goes wrong in both directions:

Handed over unpaid. An attendant assumes it went through and releases the car. It didn't.
Paid but still open. The money arrived and the job was never closed; the day doesn't balance and the customer gets chased a second time.

In a setup that is put together properly, the handover button is never drawn before the money arrives, and once it does nobody has to press anything. Then the category "looks collected but isn't" simply cannot exist.

Seven questions to ask before you choose

1. Whose account does the money land in?

This is the big one. Does the money go straight into your own merchant account, or is it pooled somewhere and forwarded later? In the second case someone else holds your balance and the payout calendar is not yours.

2. How many fees are there?

The payment provider's processing fee always exists; that is normal. What you want to know is whether there is a second fee on top of it. If the software side also takes a cut, find out before you sign up, not after.

3. Is the payment tied to the job record?

Which car, which job does this payment belong to? Without that link you are left with a bank movement, and at month end nobody can work out which job it paid for.

4. Does it sit on its own line in the till?

If online takings and the card payments from your own terminal fall into one bucket, the end-of-day cannot separate them. They should stay apart — not least because the money reaches your bank on different schedules.

5. What happens when a payment doesn't come through?

Customers open a link and change their mind; cards get declined. The screen must not go quiet at that point. Your attendant needs to see why it failed, otherwise they end up arguing with a customer who is certain they paid.

6. Is there a test mode, and can you tell when it's on?

Most providers have a sandbox where a payment looks successful but no money moves. Forgetting to switch to live after testing is the most expensive silent mistake in this whole area. A well-built system says so plainly on screen.

7. What happens with no internet?

Card payment needs a connection — that is unavoidable. But opening jobs and handing cars over must keep working offline, and cash collection must not be blocked. A dropped line stopping the entire business is not an acceptable design.

Which route for which situation

Customer present, car being handed over → QR. Fastest, least handling.
Customer dropped the car and left → payment link. Sent when the work is done; the car is ready to release once the money is in.
Fleet, dealership, corporate → link or a credit account. Somebody else pays, and they will want a statement at month end.
Small amount, regular customer → cash is still the practical one. Card collection is not there to kill cash; it is there to cover where cash falls short.

Detailing and high-ticket work

Online collection actually suits detailing better than a quick wash. The reason is amount and duration:

The amounts are large. Cash covers a wash; nobody carries the price of a ceramic coating in their pocket. Here card payment is not a convenience, it is a requirement.
The customer isn't there. In detailing the car stays for days and the owner drops it off and leaves. "Show the QR to the customer in front of you" is the exception; the normal case is sending a link and waiting for the money.
Deposits matter. On long, material-heavy jobs it is normal to take something up front. A deposit is just a payment link sent when the job is booked — and the slot isn't held until it clears.
The job splits in two. Deposit plus balance on handover is two separate collections, and both have to stay attached to the same vehicle. Otherwise, at month end, nobody can tell which money belonged to which job.

There is also the argument you never want to have: on an expensive job, "I paid" versus "you didn't" is the worst conversation in the shop. When the payment lands inside the record itself, there is nothing left to argue about. For the record-keeping side of detailing specifically, see car valeting and detailing software.

Providers inside and outside Turkey

There is a practical split. For businesses based in Turkey the common route is a local merchant account such as PayTR; Stripe does not open business accounts for Turkish companies. Outside Turkey it is the other way round. Whichever your software supports, you connect your own account in that country — the keys stay yours, held encrypted on the server, and never travel down into the app.

The small test to run before you go live

Before you put a real customer through it, collect a tiny amount (a euro, a lira) with your own card and check three things:

The money actually reached your account — not the sandbox.
The job closed by itself, rather than you closing it manually.
The amount appears on its own line in the end-of-day till.

If all three hold, the setup works. If one doesn't, it will surface on a busy Saturday instead — and today is a much better day for it.