QR Code Payments for Mobile and Field Businesses

The field payment problem

If you work away from a counter — a driveway, a curb, a chair, a stall, a lot — the hardest part of getting paid isn't the work. It's the last ten seconds. That's when the payment gets soft: “I'll Venmo you later.” “I don't have cash.” “Can you send an invoice?” “Do you take card?”

Every one of those sentences moves the payment somewhere else — later, another app, another follow-up — and some of those payments never come back. A field business needs a way to take the payment right there, on whatever the customer already has in their hand.

Comparing the ways field businesses get paid

None of these options is wrong — they break in different places. The question is what happens in the seconds when the customer is standing in front of you.

What QR checkout actually is

Plain language: a QR checkout is a code that opens a payment page. The customer points their phone camera at the code, a checkout opens in their browser, they see what they're paying for — a tip, a named charge, or a product — and they pay with a card or the wallet already on their phone. Done.

Valetfy's three flows: tips, charges, products

Valetfy is not a tipping app. It runs three kinds of QR payment terminals, and an operator can use any or all of them from one wallet:

Tip Terminal

A scannable tip jar. The customer scans, picks an amount (or types their own), and pays from their phone browser. Built for the “no cash” moment.

Service / Charge Terminal

You name the exact price — “$40 detail,” “$15 cut” — and show or send the code. The customer pays that charge, with optional gratuity on top. You receive the full amount you named.

Product Terminal

Products become QR codes. The customer scans, reviews a lightweight cart, and buys — no account, no app, no register.

Every payment runs on Stripe and settles to the operator's connected Stripe account. The customer pays in the browser with Apple Pay, Google Pay, Link, PayPal, or any major card.

Where QR payments work well

QR checkout fits any work where the customer is physically present but there's no counter, no register, and no appetite for hardware:

• Valets and parking staff
• Mobile detailers and car washers
• Mobile dog groomers
• Barbers and stylists — in the shop or on the move
• House and office cleaners
• Market and street vendors
• Food trucks and pop-ups
• Event and venue staff
• Delivery and service workers
• Solo operators of every kind

Where QR payments are a bad fit — honestly

A QR code is not the answer to everything. Skip it, or keep a backup, when:

• The customer has no phone — or a dead battery. No phone, no scan.
• You work in poor-signal areas — underground garages, remote sites. The checkout page needs a connection.
• You need a full POS — inventory, staff permissions, accounting integrations. That's a point-of-sale system, not a QR code.
• Your counter POS already works — if you're never away from it, you don't need mobility.
• Printed codes you can't supervise — a sticker in an uncontrolled spot can be tampered with or covered by someone else's code. Place codes where you or your staff can see them, and glance at the address bar: Valetfy checkouts open on valetfy.com domains.

How the worker presents the QR

The code works anywhere it can be seen and scanned. Common setups:

• Apple Wallet pass — the operator's QR lives in the wallet, one tap away.
• Printed badge or lanyard — worn during the job; customers scan the person who served them.
• Sticker or sign — on the stand, the window, the truck, the booth.
• Phone screen — pull the code up and hold it out.
• Counter or table card — where the handoff happens.
• Vehicle or window placement — for mobile rigs that are their own storefront.
• Booth checkout card — one card at the front of a market stall.

How the guest pays, start to finish

1. They point their phone camera at the code.
2. A checkout page opens in their browser — no app store.
3. They see what they're paying: a tip amount they choose, the exact charge you named, or the product in their cart.
4. They pay with Apple Pay, Google Pay, Link, PayPal, or a card.
5. They get a confirmation, and the payment lands in your Valetfy wallet, settling to your connected Stripe account.

Why “no app, no account, no reader” matters

• Less setup for you — nothing to buy, charge, pair, or update. Sign in with your phone number, connect your payout account, and the code is ready.
• No hardware failure modes — no dead reader batteries, no Bluetooth pairing screens, no lost dongles.
• Less friction for the customer — nobody installs an app to pay someone once. A browser page asks nothing of them but the payment.
• More ways to pay than any single app — wallet, card, Link, PayPal — instead of betting the payment on whether they have one specific P2P app.
• Right-sized for field work — occasional, mobile, and in-the-field payments don't justify POS hardware. A code does.

Implementation checklist

1. Choose your flow — tips, exact charges, products, or a mix.
2. Create the QR terminal from your Valetfy wallet — it takes seconds.
3. Test it with a small payment yourself before the first customer does.
4. Print and place the code where the handoff actually happens — badge, sign, sticker, counter card.
5. Train the script — one sentence, said the same way every time (see below).
6. Keep a backup — cash still exists; a dead phone shouldn't kill the payment.
7. Review fees, receipts, and payouts in your wallet so you know exactly what settles and when.
8. Watch what customers actually use — and put the code wherever that behavior says it should live.

The one-sentence worker script

That's the whole pitch. It names the action (scan), the payment methods (card or wallet), and removes the objection (no app) before it's raised. Say it while presenting the code, then stop talking.

Frequently asked questions