Back to use cases

Delivery, takeaway, and phone-order links

Food Delivery and Takeaway Payments

Send a payment link before the driver leaves, or show a QR at handoff, so delivery and takeaway orders are paid without card disputes or chat confusion.

Practical guide

Collect takeaway and delivery payments before the kitchen cooks or the driver leaves.

Delivery and takeaway payments happen under time pressure. The restaurant wants payment before food is prepared or handed to a driver, and the customer wants a link that works quickly.

Crypto is useful for repeat customers, international guests, group orders, catering trays, and locations where wallet payments are common.

MakePay can turn the order total into a branded payment link or QR request with a clear paid status for the kitchen, cashier, or dispatcher.

The best first rollout is not every small order. Start with larger preorders, catering, repeat crypto customers, and delivery zones where payment confirmation matters.

Payment examples

Phone-order payment link
Driver QR at the door
Takeaway prepayment before pickup
Event food order deposit

Why it works

Payment can happen in chat before preparation starts
Drivers and counters see a simple paid status
Large catering orders can be confirmed with a deposit
Funds settle to the restaurant wallet without custody delays

Problems solved

Drivers cannot wait while customers troubleshoot cards
Phone orders often need a cleaner payment step
Chargebacks are painful after food has been delivered
Catering prep should not begin on vague payment proof

Guide

Why food orders need payment before motion

Once food is cooked or sent out, the merchant has already spent time, ingredients, and delivery capacity. Payment uncertainty turns into waste quickly.

A clear payment link lets the customer pay before preparation or dispatch while keeping the order reference visible.

Preparation has cost

Paid status can decide whether the kitchen starts a large order.

Drivers need certainty

Delivery should not leave while payment is unclear.

Groups fit well

Large shared orders are more likely to justify crypto payment.

Guide

How MakePay fits takeaway and delivery

Send a link after the order is confirmed or show a QR at pickup. The payment request should match the order total, delivery fee, and reference.

The merchant can keep settlement wallet-first while staff check a simple payment status instead of interpreting wallet transfers.

Links before cooking

Useful for preorders and catering-sized takeaway.

QR at pickup

Works when customers arrive and request crypto payment.

Order references

Keep kitchen, cashier, and support aligned around the same order ID.

Guide

What operators should set

Decide whether crypto orders start cooking before payment, after payment, or after manager approval. The rule should be obvious to staff.

Set accepted assets and timeout rules so customers know when an unpaid order may be canceled.

Choose order types

Start with large preorders, catering, or repeat customers.

Define dispatch rules

Make payment status part of the driver handoff checklist.

Handle substitutions

Know how to adjust payment if an item is unavailable.

Setup path

Start with one clear payment moment.

Step 1

Confirm the order

Lock menu items, delivery fee, and timing before sending the request.

Step 2

Send the delivery payment link

Include order ID and amount so the customer knows exactly what is due.

Step 3

Check before cooking or dispatch

Use the paid status to decide when the order moves.

Step 4

Attach to the order

Keep payment confirmation with kitchen and delivery records.

Questions

Plain answers before you launch.

Is this good for small delivery orders?

Usually not first. Larger preorders and catering are easier starting points.

Can customers pay at pickup?

Yes. QR or payment links can work at the counter if staff can check status quickly.

What if payment is late?

The restaurant should define whether the order waits, cancels, or needs manager review.

More use cases

Explore nearby merchant types