Back to use cases

Ride, airport, and transfer payments

Taxi and Transfer Payments

Let drivers or dispatch teams collect fixed transfer fares, airport rides, and private routes by QR or payment link before the trip is closed.

Practical guide

Let riders pay transfers and private rides by QR without making drivers handle wallet details.

Transportation payments happen at the edge of the business: airport curb, hotel lobby, car door, dispatch desk, or after a pre-booked ride.

Crypto can fit private transfers, tourist rides, airport pickups, chauffeur bookings, and higher-value routes where customers ask for wallet payment.

MakePay can create QR or payment link requests so drivers and dispatchers check a clear status instead of copying wallet addresses.

The key is to keep the flow short enough for a ride handoff but structured enough for dispatch and accounting.

Payment examples

Airport transfer prepayment
Driver QR after ride
Private route invoice
Hotel shuttle booking payment

Why it works

Works from dispatch chat, booking forms, or driver phones
Clear status before a reserved transfer is assigned
Wallet payments fit international travelers
Merchant wallet settlement avoids driver-side custody confusion

Problems solved

Drivers should not copy wallet addresses from messages
Airport transfers need confirmation before the car is reserved
Foreign cards may fail for visitors
Private routes often require payment before dispatch

Guide

Why transport crypto must work in the field

A driver cannot troubleshoot payment for ten minutes while waiting at arrivals. The payment request must be quick to show and easy to verify.

At the same time, the operator needs the ride reference, route, driver, and amount recorded for accounting and support.

Drivers need a simple screen

Paid status should be obvious without crypto expertise.

Pre-booked rides fit well

Links can collect deposits or balances before pickup.

Tourists may prefer wallets

International riders can avoid card and FX friction.

Guide

Where MakePay fits taxi and transfer workflows

Dispatch can send a payment link before the ride, or the driver can show a QR code for an in-person payment at pickup or drop-off.

The payment can be tied to the ride ID, booking reference, route, or driver record so finance is not reconstructing the trip later.

QR for in-car payment

Useful for customer-requested crypto payments.

Links for prepayment

Collect airport or chauffeur bookings before dispatch.

Direct settlement

The operator keeps wallet-based settlement control.

Guide

What dispatch should decide

Define whether payment is due before pickup, before drop-off, or after invoice. Different ride types may need different rules.

Train drivers on the exact paid status and who to call if a payment is stuck or underpaid.

Use ride references

Attach booking, driver, and route details where possible.

Define waiting policy

Staff should know what to do if payment is not complete.

Keep refunds centralized

Do not make drivers decide refund handling in the field.

Setup path

Start with one clear payment moment.

Step 1

Create the ride request

Start from a fare, booking, route, or deposit.

Step 2

Send link or show QR

Use dispatch links before the ride or driver QR in person.

Step 3

Check status at the right moment

Confirm paid status before pickup, drop-off, or invoice closure based on policy.

Step 4

Record the ride

Keep payment references with driver and route records.

Questions

Plain answers before you launch.

Should every driver accept crypto?

Start with trained drivers, airport transfers, or private bookings before full fleet rollout.

Can this work for pre-booked transfers?

Yes. Payment links are well suited to deposits and balances before pickup.

What if the rider underpays?

Dispatch should handle exceptions, not the driver improvising at the curb.

More use cases

Explore nearby merchant types