Accepting Payments Online in Pakistan: JazzCash, EasyPaisa, Cards and Cash
What each payment method actually costs, how long settlement takes, and why cash on delivery still decides your checkout design.
· 3 min read · Business
In short: Most Pakistani businesses need three payment paths, not one: mobile wallets, cards, and cash on delivery. The technical work is the easy part. The decisions that matter are about settlement timing, failed payments and what happens when a customer pays but your system never hears about it.
The three paths, and who uses them
- Mobile wallets — JazzCash, EasyPaisa. The widest reach by a distance, especially outside the big cities and among customers without a card. Usually the highest-converting option.
- Cards. Expected by urban and corporate buyers, and necessary for anything B2B or recurring. Lower volume for most consumer businesses than owners expect.
- Cash on delivery. Still the default for a large share of ecommerce. It is not a payment integration — it is an operational commitment, with returns and reconciliation attached.
What it costs
Rates move, so confirm before you commit, but the shape is stable: wallets and cards sit in low single-digit percentages per transaction, with wallets typically cheaper than cards. Some providers add a monthly or setup fee. Cash on delivery looks free and is not — courier fees, failed deliveries and returns routinely cost more per order than a gateway does.
The number that actually matters is settlement time. Money arriving in your account in two days versus two weeks changes how you buy stock, pay staff and plan. Ask every provider this directly, in writing.
The failure everybody hits
The customer pays. The payment succeeds at the bank. Your system never finds out, because the callback failed, or the customer closed the tab before being redirected back. The order sits unpaid while the money has left their account.
The fix is not clever code, it is design. Treat the callback as unreliable and reconcile independently:
- Record the order as pending the moment payment is initiated, before the customer leaves your site.
- Accept the provider's callback when it arrives, but never depend on it alone.
- Poll the provider for the status of anything still pending after a few minutes.
- Run a daily reconciliation against the provider's settlement report, and flag anything that does not match.
- Make sure a double-submitted payment cannot create two orders. Use a single order reference throughout.
Skip this and you will spend your first busy week manually matching screenshots sent on WhatsApp against your order list.
Designing the checkout
- Show the payment options you genuinely support, with their logos, before the customer fills in a long form. Wallet users will abandon a card-only checkout.
- If you offer cash on delivery, say clearly what it costs and where you deliver. Hiding it until the last step is how carts get abandoned.
- Explain a failed payment in plain language and let them retry with a different method without re-entering everything.
- Send a confirmation the customer can keep — SMS or WhatsApp, not only email. Many buyers never open the email.
Before you integrate anything
Have your business registration and bank account ready — every provider requires them, and this is usually the slow step, not the code. Decide who reconciles payments weekly and give them a report that makes it possible. And test with real money, in small amounts, on a real phone, on mobile data, before you launch.
We build payment flows for ecommerce and service businesses across Pakistan, including the reconciliation that keeps them honest. Tell us what you are selling and we will tell you which methods are worth the effort.