There is a version of this post that is about convenience: customers like tapping their phone, cash is annoying, get a QR code. That version is true and it is not the reason to care.
The reason to care is that a business taking payment digitally produces a record of every transaction, automatically, at zero marginal effort. That record is the input to your accounts, your tax position, your ability to borrow, your ability to catch theft, and your ability to know on a Tuesday what happened on Monday. A cash-only business produces none of it and pays for the absence in ways that never appear on any invoice.
That is the argument. Everything below is the implementation.
The short version
- Raast is the State Bank's instant payment rail. Transfers settle in real time between bank accounts and wallets, and a Raast ID lets a customer pay you using a mobile number rather than an account number.
- The business case is documentation and reconciliation, not customer convenience. Convenience is what makes customers adopt it. Documentation is what makes you money.
- Your stack has four layers: a business bank account, an instant transfer identity, an in-person acceptance method, and an online gateway. Most businesses have the first and stop.
- The step everyone skips is matching payments to orders automatically. Without it you have swapped a cash drawer problem for a spreadsheet problem.
- Plan for fake payment confirmation fraud from day one. It is the most common attack on small Pakistani merchants and it is defeated by one rule.
What Raast is, in one paragraph
Raast is Pakistan's instant payment system, operated by the State Bank of Pakistan. It moves money between participating banks and wallets in real time rather than in batches, at a transaction cost that is deliberately low, and it supports a Raast ID, a mobile number linked to an account so a payer does not need your account details. It has rolled out in stages, person to person first, then bulk payments, then person to merchant. The consumer-facing experience lives inside your bank's own app, so most customers are using it without knowing the name.
For a business, the practical meaning is: a customer can pay you instantly, from their bank app, using your phone number, and the money is in your business account before they leave the counter.
Why cash-only is now a structural disadvantage
Four costs, none of which show up as a line item:
You cannot prove revenue. Which means you cannot borrow against it, cannot sell the business on it, and cannot defend it in an assessment. Undocumented revenue is revenue that only exists while you are standing next to it.
You cannot see the business. The four numbers a founder should know cold every Monday are unknowable in a cash business without manual counting, and manual counting is done late, badly, or never. We wrote that discipline up in the five numbers every Monday.
Leakage. Cash handled by staff leaks. Not usually through dramatic theft, through small, constant, unprovable shrinkage. Digital payment removes the opportunity rather than policing it.
You are invisible to the formal economy. Every counterparty with their own compliance obligations, corporate clients, lenders, platforms, insurers, requires a documented trading history. No history, no relationship.
The four-layer stack
Layer 1: a business bank account in the business's name. Not a personal account, not a family member's. If you have not done this, nothing else in this post helps you.
Layer 2: an instant transfer identity. Register the business's Raast ID against the business account and publish it. This is the zero-cost path for invoiced payments, deposits, and any customer who would otherwise ask for account details over WhatsApp.
Layer 3: in-person acceptance. A displayed QR code is the cheapest option and works for the majority of walk-in transactions. A card terminal becomes worth its cost once your average ticket is high enough or your customers expect cards, which is location and segment dependent. Most small retailers should start with QR and add a terminal when the customer mix demands it. Our retail shop setup work treats this as part of the store design rather than an afterthought.
Layer 4: online acceptance. A payment gateway integrated into your website or store. This is a bigger decision than it looks, because the gateway determines your settlement time, your refund workflow and your reconciliation quality. We cover it as part of ecommerce store setup.
| Method | Cost to you | Settlement | Reconciliation quality | Best for |
|---|---|---|---|---|
| Cash | "Free", plus leakage, counting, deposit trips | Immediate | Poor, manual | Nothing you want to scale |
| Raast transfer / QR | Very low | Real time | Good, if you capture a reference | Walk-in, invoiced, recurring |
| Card terminal | Higher, per transaction | Batched | Good | Higher ticket, card-expecting customers |
| Online gateway | Highest, per transaction | Delayed, provider dependent | Best, order-linked | Any online selling |
| Cash on delivery | Highest hidden cost of all | On delivery, if it happens | Poor, high dispute rate | Only where the market demands it |
The step everyone skips: matching payments to orders
Here is the failure mode we see constantly. A business adopts digital payments, feels modern, and three months later the owner is sitting with a bank statement and a notebook trying to work out which of forty-one transfers was which customer.
Digital payment without reconciliation is not an upgrade. It is the same problem in a new format.
The fix is unexciting and decisive:
- Every transaction gets a reference. An order number, an invoice number, a customer code. Ask the customer to put it in the payment reference, or generate a per-order QR if your provider supports it.
- One person owns the daily match. Ten minutes, every day, not two hours every month.
- Payments land in the same system as customers. If your customer records live in a CRM and your payments live in a bank app and never meet, you will keep doing this by hand forever.
- Exceptions get chased the same day. An unmatched payment at day three is a puzzle. At day thirty it is a write-off.
The fraud you should plan for
Fake payment confirmations. The most common attack on small Pakistani merchants by a distance. A customer shows a screenshot of a completed transfer, takes the goods, and the money never arrives. The screenshots are convincing, they circulate as templates, and staff under time pressure accept them.
One rule defeats it: goods leave when the money is in your account, confirmed in your own app or by your own SMS alert. Never on the customer's screen. Write that rule down, tell every member of staff, and back them when a customer objects. The occasional lost sale is enormously cheaper than the pattern of losses.
Social engineering of your staff. Calls claiming to be from the bank, from the payment provider, or from you, asking staff to confirm a code or reverse a transaction. Nobody from any bank will ever need a code from your employee. Say so explicitly in your staff policy, in the same document as your device rules, which we set out in corporate device security for distributed teams.
Refund and chargeback abuse online. Define your refund policy before you launch, publish it, and apply it consistently. Inconsistent refunds are how disputes escalate.
A thirty-day plan
| Week | Action |
|---|---|
| 1 | Business bank account confirmed, Raast ID registered against it and published |
| 2 | QR acceptance live at every point of sale, staff briefed on the confirmation rule |
| 3 | Daily reconciliation routine assigned to a named person, reference convention agreed |
| 4 | Online gateway scoped if you sell online, refund policy written, first monthly close run against digital records |
Frequently asked questions
What is Raast and how is it different from a bank transfer?
Raast is the State Bank's instant payment rail. Transfers settle in real time rather than in batches, the cost is deliberately low, and a Raast ID lets someone pay using a registered mobile number instead of account details. You use it through your existing bank's app.
Can a small business accept Raast payments?
Yes. Register a Raast ID against the business account and accept transfers, or display a QR code for in-person payment. The setup is a bank-side process and your bank's business banking team will walk you through the current requirements.
Is a QR code or a card terminal better for a Pakistani retailer?
Start with QR. It is cheaper, faster to deploy and covers most customers. Add a card terminal when your average transaction value or your customer segment justifies the cost, not before.
How do I stop fake payment screenshot scams?
Release goods only when the payment is visible in your own account, in your own app or bank alert. Never on the strength of a customer's screen. Make this a written staff rule so employees can enforce it without fear.
Does going digital increase my tax exposure?
It makes your revenue visible, which is the point. In practice, most businesses that formalise find the documented position is worth more than the informal one, because it unlocks credit, corporate clients and eventually a sale price. The alternative is a business that can never be anything other than what it is today.
Where to go next
If you are setting up a store, physical or online, payment acceptance should be designed in rather than bolted on: see retail shop setup and ecommerce store setup. If the payments are working but the reconciliation is not, that is an operations fix and usually a fast one. Tell us what your month-end looks like.
