Almost every ecommerce project in Pakistan slips on the same item, and it is never the code. Integrating a payment gateway is roughly a week of engineering. Getting approved to use one takes three to six weeks, and nobody puts that on the Gantt chart.
Here is what the process actually involves, what each option costs, and the failures that show up after launch.
The options
Mobile wallets: JazzCash and Easypaisa
The widest consumer reach in Pakistan by a distance. If you sell to the general public, you need at least one of these, because a large share of your customers do not have a card.
Good for: consumer ecommerce, services, small ticket purchases.
Watch for: settlement timing, reconciliation reports that need manual handling, and transaction limits per wallet.
Card gateways and aggregators
Local aggregators bundle cards, wallets and bank transfer behind one integration. One contract, one integration, one reconciliation. For most businesses this is the sensible route.
Good for: anyone who wants more than one payment method without three separate integrations.
Watch for: the total fee once every method is counted, and what happens to your money between capture and payout.
Direct bank gateways
Lower fees at volume, and more credible for large B2B transactions. Heavier onboarding and usually older documentation.
Good for: established businesses with real volume.
Watch for: integration effort, which is commonly two to three times an aggregator.
International gateways
If you sell to customers outside Pakistan, you will likely need a foreign entity to use the major international processors. Many Pakistani software and service exporters set this up deliberately for that reason. Verify the current position with your accountant rather than relying on forum advice, because this area changes.
What integration actually involves
Assume a standard hosted checkout flow:
- Merchant onboarding. Company documents, bank account, tax registration, sometimes a site review. Three to six weeks, and it is the long pole.
- Sandbox integration. Three to five days of engineering. Redirect, callback, response handling.
- Server side verification. One to two days, and the step people skip.
- Reconciliation logic. Two to four days. Matching gateway settlements against your own orders.
- Live testing. Two to three days with real small transactions, because sandbox never matches production exactly.
Engineering total: roughly one to two weeks. Calendar total: four to eight weeks. Plan around the second number.
The four mistakes that cause real losses
1. Trusting the browser redirect
The single most dangerous mistake. When the gateway redirects the customer back with a success parameter, that parameter arrives through the customer’s browser and can be altered.
Always verify server to server. Take the transaction reference, call the gateway’s verification endpoint from your backend, and only then mark the order paid. Anything else means someone will eventually get free products by editing a URL.
2. Not handling the callback properly
Gateways send a server to server notification, and they retry it. Your endpoint must be idempotent, so processing the same notification five times does not create five orders or send five confirmation emails.
It must also respond quickly. Do the minimum, acknowledge, and queue the rest.
3. Ignoring the in between states
Payments are not binary. A transaction can be pending, under review, timed out, partially captured, refunded or charged back. A system that only understands success and failure will strand real customer money and generate support tickets nobody can resolve.
4. No reconciliation
Gateway settlement reports and your order records will disagree. Every business discovers this in month two. Build the daily comparison from the start, or you will be reconstructing three months of transactions by hand later.
What it costs
Transaction fees vary by method, volume and negotiation, so treat any published figure as a starting point and negotiate once you have volume. Wallets and cards differ meaningfully, and bank transfer is usually cheapest.
Build cost for integration, as part of a project:
- One gateway, hosted checkout: 60,000 to 150,000 PKR
- Two or three methods with unified reconciliation: 150,000 to 350,000
- Subscriptions and recurring billing: add 100,000 to 250,000, because the state handling is genuinely harder
- Marketplace with split payouts to vendors: 300,000 and up
For where this sits in a full build, see our breakdown of website development cost in Pakistan.
How to shorten the timeline
- Start onboarding in week one of the project, before any code is written. This alone removes most of the delay.
- Have the documents ready: registration, bank details, tax registration, and a live site the reviewer can open.
- Launch with one method, add the second after you have real transactions. One working gateway beats three half tested ones.
- Keep cash on delivery available while you get approved. For a large share of Pakistani buyers it remains the preferred option anyway.
Frequently asked questions
Which payment gateway is best for a Pakistani ecommerce store?
For consumer reach, a wallet such as JazzCash or Easypaisa plus card acceptance through an aggregator covers most customers with one integration effort. Direct bank gateways make sense once volume justifies the lower fees.
How long does merchant approval take?
Typically three to six weeks depending on the provider and how complete your documents are. Start it before development, not after.
Can I accept international payments from Pakistan?
Domestic gateways handle local cards and wallets. For international customers most exporters use a foreign entity with an international processor. Confirm the current regulatory position with your accountant.
Do I need PCI compliance?
If you use a hosted checkout where the gateway captures the card details, your burden is much lighter because card data never touches your server. Never store raw card numbers yourself.
Ezitech has integrated payments for ecommerce, marketplace and subscription platforms across 10 or more industries. Tell us what you need to accept and we will scope it honestly, onboarding time included.