Back to use cases

Reception and workshop counter payments

Offline Service Counter Payments

Give reception desks, workshops, salons, and repair counters a payment link or QR that confirms service invoices before the customer leaves.

Practical guide

Give front-desk staff a crypto payment flow they can check before the customer walks away.

Service counters need payment clarity at the exact moment the customer is standing there. A repair pickup, document fee, appointment balance, or service deposit should not become a manual wallet lesson.

MakePay lets the counter team show a QR code or send a payment link for the exact invoice, then wait for a clear paid status before releasing goods or marking the service complete.

This works best when the service value is high enough to justify crypto and the customer already asks for wallet payment.

The goal is a calm front desk: staff know what to show, customers know what to pay, and records stay tied to the job.

Payment examples

Phone repair pickup invoice
Appointment booking deposit
Tattoo session balance
Workshop service counter QR

Why it works

Counter staff can show the same payment flow every time
Deposits and final balances stay tied to the customer ticket
Paid and pending status is visible without wallet detective work
Settlement routes to the business wallet instead of a platform balance

Problems solved

Reception teams do not have time for pasted addresses
Deposits are easy to lose when collected through chat
Customers may stand at the desk waiting for confirmation
A finished job should not be released on unclear payment proof

Guide

Why counter payments need simple confirmation

The customer is often waiting in front of staff, so the payment flow has to be visible and quick. Anything that requires a manager to interpret a blockchain transaction will break the rhythm.

A payment request tied to the job or invoice gives both sides a cleaner record than a wallet address written on paper.

Goods may be released

Staff need paid status before handing over repaired items or documents.

Customers need confidence

A branded page is easier to trust than an address from a note.

Receipts matter

The payment should attach to a ticket, appointment, or invoice.

Guide

How MakePay fits the front desk

Use a QR request for in-person payment or a link when the customer is remote. The same basic process can cover deposits, balances, and final pickup.

The business keeps settlement directed to its wallet while staff use a focused payment status instead of a raw crypto workflow.

In-person and remote

The same payment flow can work at the counter or after a phone call.

Clear job reference

Attach repair tickets, invoice IDs, or appointment references.

Controlled settlement

Merchant funds route outside platform custody.

Guide

What to prepare for staff

Create a short checklist for payment creation, status check, receipt handling, and exceptions. The person at the desk should not need to improvise.

Decide which services are eligible for crypto and which still use card or cash because the amounts are too small.

Train one status screen

Staff should know exactly what paid looks like.

Use ticket IDs

Every request should point to a real service record.

Define refunds

Service disputes and refunds should have a simple process before launch.

Setup path

Start with one clear payment moment.

Step 1

Create the service request

Use the invoice, repair ticket, appointment, or deposit amount.

Step 2

Show or send payment

Give the customer a QR or link with the correct amount.

Step 3

Wait before release

Release goods, documents, or service completion after paid status is clear.

Step 4

Close the ticket

Attach payment confirmation to the job record.

Questions

Plain answers before you launch.

Is this only for retail shops?

No. It fits repair desks, clinics, agencies, service offices, and any counter that collects invoices.

Can the customer pay later?

Yes. Send a link by email or SMS when the customer is not present.

What should staff check?

They should check MakePay payment status, not screenshots or copied transaction hashes.

More use cases

Explore nearby merchant types