“Website par JazzCash aur card payment lagani hai” sounds like a one-line task. It is usually a three-week task, and most of those three weeks are paperwork, not code. This guide explains what payment gateway integration in Pakistan actually involves in 2026: which gateways exist, what they ask for before they approve a merchant, what they charge, how each one connects to Shopify, WooCommerce or a custom site, and the failures we see most often on launch day.
It is written for business owners commissioning a store or a booking site, and for the person on their team who will be chasing the bank. For platform choice and overall store costs, read our guide to ecommerce website development in Pakistan first; this article picks up where its payments section stops.
What is not available, so you stop looking
Stripe does not onboard Pakistani businesses. PayPal does not offer merchant accounts in Pakistan. Shopify Payments is not available here. Any tutorial built around those three does not apply to you. Some businesses route through a company registered abroad or a relative’s foreign account; that creates tax and ownership problems we do not recommend, and it does not work for PKR sales anyway.
Everything below is what does work for a business registered in Pakistan, selling in PKR to customers in Pakistan.
The gateways, one by one
JazzCash merchant account. Direct integration with the largest mobile wallet. Customers pay from their JazzCash wallet, by JazzCash-linked card, or through a voucher paid at any agent. Best reach among wallet users. Onboarding is through Jazz’s merchant team and takes the longest in our experience; API documentation is workable but support is slow.
Easypaisa merchant account. The second wallet, same idea. Wallet payments, Easypaisa-linked cards and over-the-counter vouchers. Direct integration is similar in effort to JazzCash. If you only integrate one wallet directly, you lose a meaningful share of customers, which is why most stores go through an aggregator instead.
PayFast. An aggregator: one integration gives you Visa and Mastercard, local debit cards, JazzCash and Easypaisa wallets, and bank account payments. Onboarding is faster than the wallets directly, plugins exist for WooCommerce and Shopify, and settlement is predictable. This is what we integrate most often for small and mid-size stores.
Safepay. Another aggregator, developer-friendly, with clean APIs, hosted checkout, subscriptions and good Shopify support. Slightly more expensive on some plans, better documentation. Our pick when a custom site or a subscription model is involved.
Bank gateways. Several banks offer their own card gateways to business account holders. They work, but the integration is older, the approval is tied to your relationship with the branch, and you still need a wallet integration separately. Worth considering only if you already have a strong banking relationship and high card volume.
Bank transfer and COD. Not gateways, but still most of the volume for many stores. Bank transfer needs a manual confirmation step; cash on delivery needs a verification flow, which we covered in the ecommerce guide.
What every gateway asks for before it approves you
The paperwork is the schedule. Start it on the day you sign off the website, not the week before launch.
- Business registration: sole proprietorship, partnership or SECP company documents.
- NTN, and for most aggregators a sales tax registration if you are required to have one.
- A business bank account in the same name as the registration, for settlements.
- CNIC of the owner or directors, and a proof of address.
- A live or staging website with pages the compliance team will actually read: privacy policy, terms and conditions, refund and return policy, a contact page with a physical address and phone number, and prices in PKR. Sites without these get bounced back.
- SSL on the domain and a checkout that does not collect card numbers on your own pages (see security below).
Realistic timelines in 2026: aggregators one to three weeks once documents are complete; direct wallet accounts two to six weeks. If a proposal promises live card payments in a week from signing, the person writing it has not done it.
What it costs
- Per transaction: roughly 2 to 3 percent on cards, and a fixed or percentage fee on wallet payments, depending on the gateway and your volume. Bank transfer and COD are free at the gateway but cost you time and courier cash-handling fees.
- Setup and monthly: some aggregators charge a one-time setup fee and no monthly; others have plan tiers. Direct wallet accounts usually have no monthly fee but negotiate rates by volume.
- Settlement: typically one to three working days to your bank account, minus fees. Ask for the exact schedule in writing; it decides your cash flow in the first month.
- Refunds: most gateways do not return the original fee when you refund. Build that into your return policy.
Put the transaction fee into your product pricing from day one. Stores that discover the 2.5 percent after launch tend to push customers back to COD, which costs more.
How the integration works on each platform
Shopify. The gateway’s app is installed from the Shopify App Store or through a manual payment provider setup, connected with the keys from your merchant account, and switched from test to live once approved. Customers are sent to the gateway’s hosted page to pay and return to the order confirmation. Two to four hours of work once the account is approved. Our Shopify development projects include this and a real test order per method.
WooCommerce. Official or vetted plugins exist for PayFast, Safepay and the wallets. Install, configure keys, map order statuses (pending, processing, failed), and set the webhook so the store hears about payments that complete after the customer closes the tab. The most common WooCommerce failure is a missing or mis-configured webhook, which leaves paid orders stuck on “pending”.
Custom sites and apps. Direct API integration: create a payment request, redirect or open the hosted checkout, verify the callback signature, then confirm the order server-side only after the gateway’s callback, never on the browser’s return alone. This is the part that needs an engineer; it is where duplicate orders and “paid but not recorded” bugs come from when done casually. Our custom development team builds these with idempotency keys, signed callbacks and a reconciliation report.
Security: what you must not do
Never collect card numbers on your own pages, in your own database, or in a form your developer built. Use the gateway’s hosted checkout or its tokenised fields. That keeps you outside most of the PCI DSS scope, and it is a condition of every gateway’s agreement. Keep API keys out of the code repository, use HTTPS everywhere, and log payment events without logging card data. If a freelancer proposes storing cards “for convenience”, that is the moment to stop the project.
What breaks on launch day
- Sandbox works, live fails. Test credentials left in place, or the live account not yet activated for the specific method (cards approved, wallets still pending).
- OTP and 3D Secure on mobile. Customers on slow connections time out during the bank OTP step and the store shows a failed order while the bank shows a charge. Fix: proper callback handling and a clear “payment processing” state, plus a reconciliation check.
- Duplicate orders. Customer taps pay twice or refreshes. Fix: one payment reference per order and idempotent order creation.
- Amount mismatch. Discount or shipping changed after the payment request was created. Fix: create the payment request as the last step.
- Refund confusion. Nobody on the team knows how to refund from the gateway dashboard. Fix: a one-page refund procedure and a test refund before launch.
- Compliance bounce. The gateway suspends the account weeks later because the refund policy page was removed in a redesign. Keep those pages.
The launch checklist we use
- Every payment method tested with a real PKR 100 order, and one refund per method.
- Webhook or callback verified on the live domain, not only on staging.
- Order statuses correct in the store, the gateway dashboard and the confirmation email.
- Test credentials removed; live keys stored outside the code.
- Privacy, terms, refund and contact pages live and linked in the footer.
- Someone on your team logged in to the gateway dashboard and shown where settlements and refunds are.
- A weekly reconciliation habit: gateway settlements against store orders and bank credits.
How Fox Logic handles payment integration
Payment setup is part of every store and booking site we build in Lahore, Karachi and Islamabad, and available on its own for existing sites. We tell you on the first call which gateway fits your business, send the document list the same day so the paperwork starts immediately, integrate and test every method with real transactions, and hand over a written refund and reconciliation procedure. If your current site has a broken or half-finished integration, we can audit and fix it; see our maintenance plans for ongoing checks after every platform update.
Need payments on your site? Request a quote or message us on WhatsApp with your platform and the methods you want to accept. We reply within one working day.
