Raast for restaurants: taking instant bank payments without card fees

Most prepaid restaurant orders in Pakistan still run on two rails: a card (which a minority of customers have, and fewer like using online) or a mobile wallet. Both work. Both also carry fees and failure modes that a bank-to-bank transfer does not. Raast is the third rail, and for a restaurant it is the one most worth understanding, because it fits how your customers already bank.

TL;DR

• Raast is the State Bank of Pakistan's instant payment system. It moves money between bank accounts and wallets in real time, around the clock, using an IBAN or a Raast ID (a mobile number linked to an account).
• No card network sits in the middle, so there is no card-scheme fee on a Raast payment. Your payment provider's own pricing still applies; ask for the rate card.
• In a WhatsApp ordering flow, Raast works through a pay-link: the customer taps, approves in their banking app, and the order flips to paid.
• The biggest win is not the fee. It is replacing cash on delivery, with its float, shortfalls and end-of-shift counting, for every customer willing to prepay.
• Refunds go back to the account the money came from, which is cleaner than handing cash to a rider.

What Raast is

Raast is the instant payment system built and operated by the State Bank of Pakistan. It launched in phases: bulk payments first, then person-to-person transfers, then person-to-merchant payments. Nearly all scheduled banks and the major wallets are connected, so a customer with an account at any bank, or a JazzCash or Easypaisa wallet, can send a Raast payment.

Three properties matter for a restaurant:

• Instant. The payer's account is debited and the payee's account credited within seconds, at any hour, including Sundays and Eid.
• Addressed by Raast ID or IBAN. A Raast ID is a mobile number linked to one account. Customers do not need to type a 24-character IBAN to pay you.
• Low cost by design. SBP has required banks to offer Raast person-to-person transfers free to customers. Merchant-side pricing is set by your bank or payment provider, which is why we say "ask for the rate card" rather than quoting a number.

Why it suits restaurants in particular

Card penetration among food-delivery customers is low and online card checkout is still clunky on a phone. Wallets are everywhere, but a share of customers keep their balance at zero. Almost everyone who orders food online, though, has a bank account and a mobile banking app with Raast built in.

Compare the four ways a customer can pay for a PKR 1,800 order:

None of these is wrong. Raast simply covers the most customers with the fewest moving parts, and keeps a card network out of a transaction that never needed one.

How a Raast pay-link works inside a WhatsApp chat

With Rapid Eats, payment lives inside the same WhatsApp conversation the order came from. The flow is deliberately short:

1. The customer builds the cart from the interactive menu and taps Place order.
2. The bot sends the order summary with the total in PKR and a secure RapidGateway pay-link.
3. The customer taps the link and chooses Raast. They see your business name, the amount and an order reference. Depending on their bank, they pay by scanning a QR in their banking app, approving a request to pay, or transferring to the details shown.
4. The bank app asks for a PIN or fingerprint; the transfer completes.
5. RapidGateway receives the confirmation, matches it to the order by reference, and the order moves to Paid on your kitchen screen. The customer gets a receipt message in the chat.

The important word in step five is reference. Every pay-link carries the order number, so there is nothing to match by hand later. Note that we are describing when the order is marked paid, not when funds settle to your business account; settlement timing depends on your agreement with your payment provider.

The cash-on-delivery pain Raast removes

Owners rarely count the real cost of cash. Here is the list we hear most often:

• Float. Each rider leaves with change money. Ten riders, ten floats, all of it your working capital sitting in pockets.
• Shortfalls. End of shift, the cash is PKR 700 short. Was it a customer who paid less, a rider, or a miscount? You will never know, and the conversation sours a good rider relationship.
• Fake and cancelled orders. A prank order costs you the food, the packaging and the ride. A prepaid order is never a prank.
• Counting and depositing. Someone counts cash every night, someone drives it to the bank in the morning, and both are hours you do not pay for anywhere on the P&L.
• No clean record. When your accountant asks what Tuesday's sales were, the honest answer is a notebook and a drawer.

A Raast payment confirmed before the food is cooked removes every item on that list for that order. Keep cash on delivery available, but watch what happens when the pay-link is the default and cash is the fallback: the prepaid share grows month on month, and reconciliation becomes a report you open rather than a job you do.

Refunds, and why bank-to-bank makes them easier

Refunds are where cash truly hurts: a rider has to go back, or the customer is told "adjust it next time", and nobody writes it down. With Raast the money came from a known account, so a refund is a credit transfer back to that account, full or partial, logged against the same order reference. The customer sees it in their banking app; your settlement view shows the original payment and the refund side by side. Decide a refund policy once (wrong item, late order, cancelled before cooking) and let the console apply it.

Getting it right in your restaurant

• Show your trading name. Customers approve payments faster when the bank app shows the restaurant they ordered from, not an unfamiliar company name. Set this up with your provider before launch.
• Keep the pay-link first, cash second. The bot should offer the pay-link by default and cash on delivery one tap away, not the reverse.
• Train the counter. Staff should know that a Paid tag means money has been confirmed and the order can go to the kitchen without a phone call.
• Reconcile by reference, never by amount. Two orders of PKR 1,800 on the same evening are common; matching by order number is what keeps the books clean.
• Put Raast on your bill. Dine-in customers can pay a printed QR or your Raast ID at the table, with the same reference discipline.

Raast gives a Pakistani restaurant what cards never quite did: a way for almost every customer to prepay from the app they already have, with the money confirmed before the pan is on the stove. If you want to see a Raast payment land against a WhatsApp order on your own menu, book a demo and we will run the flow with you end to end.