Pakistani Payment Gateways: A Builder's Guide to JazzCash, Easypaisa, HBL and Meezan

JazzCash's hosted checkout (HTTPPost) takes about a day to wire up against their sandbox. Their REST API is well documented but the IPN callback can arrive up to 60 seconds after the user redirects back — your webhook handler must be idempotent.

Settlement is T+2 for most merchant categories. Refunds are a manual portal action; there is no programmatic refund API, which catches teams used to Stripe off guard.

Easypaisa's mobile-account flow is the cleanest in the market — a single OTP and the customer is done. Conversion rates we have measured are 4–7 points higher than card-based flows on the same store.

Merchant onboarding is the bottleneck. Plan four to six weeks for KYC, account binding and live credentials. Start the paperwork the day you start the build.

Bank-direct gateways win on customers paying with debit and credit cards, especially at higher average order values. 3DS challenge rates are high (40–60%) so design your checkout to gracefully handle the redirect.

Reconciliation files arrive by SFTP daily. Build the import pipeline on day one — chasing two-week-old payment mismatches is the single biggest support tax we see.

Once you cross roughly PKR 5M in monthly volume, MDR savings from intelligent routing — sending wallet-eligible customers to JazzCash/Easypaisa and card customers to HBL — typically outweigh the cost of a routing layer within two months.

A simple rules engine (wallet number prefix → wallet gateway; card BIN → bank gateway) is enough to start. ML-based routing is overkill until you are well into eight-figure monthly volumes.