How to Integrate JazzCash and Easypaisa in Your Mobile App. Any Pakistani mobile app that collects money from users needs JazzCash and Easypaisa. There is no practical alternative for reaching the majority of Pakistani digital payment users in 2026. 21JazzCash has 40 million registered users and processes roughly a million transactions per day, making it Pakistan’s most widely used mobile wallet. 10JazzCash has 55 million plus customers and 20.6 million monthly active users. Together the two wallets cover the overwhelming majority of Pakistan’s active digital payment users, and a checkout flow that does not include both will lose sales to the gap.
This guide walks through the accounts you need, the integration methods available for each wallet, the security requirements, and the sandbox testing you must complete before going live.
Understanding the Integration Landscape: Direct vs. Unified Gateway
Before writing a line of code, decide which integration path you are taking. There are two options.
Direct integration means applying to JazzCash and Easypaisa separately, maintaining two merchant accounts, two sets of API credentials, and two reconciliation dashboards. 21If a merchant pursues a direct JazzCash merchant agreement, they enter a process that involves a separate application, documentation requirements, compliance review, and their own set of API credentials. The same applies to Easypaisa. Direct integration gives you the deepest native control but doubles the onboarding and maintenance work.
Unified gateway integration routes both wallets through a single API. 10A unified payment gateway API, one that connects Easypaisa, JazzCash, cards, and IBFT in a single integration, resolves the fragmentation problem entirely. Platforms such as Simpaisa, Rapid Gateway, and PayFast operate as licensed aggregators that handle the direct relationships with JazzCash and Easypaisa on your behalf. 10When you integrate with a unified gateway, Easypaisa acceptance is included with no separate merchant account application with Easypaisa, no parallel KYC process, and no second set of API credentials to manage.
For most Pakistani app developers, the unified gateway path is faster to ship and cheaper to maintain. Direct integration makes sense when you need custom settlement terms, very high transaction volumes, or specific API capabilities that aggregators do not expose.
Pre-Integration Requirements: Accounts, Documents, and Credentials
Whether you go direct or through a unified gateway, the document requirements are largely the same.26 For sole proprietors, you need a CNIC, an FBR NTN certificate, and a Pakistani bank account. For companies, you need the NTN, SECP incorporation certificate, and the business bank account. A live website or app URL is also required by both JazzCash and Easypaisa at the merchant application stage. 23 If your website or app is not yet live, JazzCash sometimes accepts a temporary URL while you prepare for launch.
On the JazzCash side, 24any Pakistani with a valid CNIC who runs a business can apply in the JazzCash Business app. Registration, maintenance, SMS alerts, and statements are all free. 20Business account registration is free for merchants and business account maintenance carries no fee.
For Easypaisa, 10submit your business application and documents through Easypaisa’s merchant registration portal, complete KYC verification and due diligence covering business ownership and compliance checks, and once approved, receive your Store ID, API credentials, and access to the sandbox environment.
Once merchant approval is granted, both platforms issue a set of credentials you will need throughout integration:
For JazzCash: your Merchant ID, password, and integrity salt. The integrity salt is the key used to generate the HMAC-SHA256 hash that signs every transaction request. Treat it as you would a private key.
For Easypaisa: your Store ID and account number, plus the hashing credentials specific to your merchant account.
JazzCash Integration Methods Explained

JazzCash offers three integration methods for mobile apps.1 The three main JazzCash integration options are: hosted or redirect checkout where the customer is redirected to a JazzCash-hosted payment page, API-based flows for token and direct pay patterns depending on the product, and a mobile SDK for integrating inside a mobile app.
Hosted checkout is the lowest-effort option. Your app opens a WebView or redirects to a JazzCash-hosted payment page. JazzCash handles the UI, the MPIN entry, and the OTP. Your server receives a callback with the transaction result. No MPIN or sensitive data ever passes through your app.
REST API (Mobile Wallet) is the direct integration. 2This method uses the JazzCash DoMWalletTransaction v2.0 REST API for direct payment processing. Your backend initiates a payment request by sending the customer’s mobile number, hashed credentials, and transaction details to the JazzCash API. JazzCash pushes a PIN prompt to the customer’s phone. The customer enters their MPIN. JazzCash sends the result to your callback URL.
Mobile SDK is available for Flutter and native Android and iOS. 3The SDK provides a comprehensive solution for integrating JazzCash credit and debit card payments into Flutter apps with native support for both Android and iOS platforms.
Step-by-Step: JazzCash API Integration
Step 1: Set up your environment
Add your JazzCash credentials to your environment variables, not to your source code. The three values you need are your Merchant ID, your password, and your integrity salt. 2The base API URLs are sandbox at https://sandbox.jazzcash.com.pk/ApplicationAPI/API/ for testing and production at https://payments.jazzcash.com.pk/ApplicationAPI/API/ for live transactions.
Step 2: Build your transaction payload
Each JazzCash API request requires a standard set of parameters: your Merchant ID, a unique transaction reference you generate, the transaction amount, a timestamp in the format YYYYMMDDHHmmss, the transaction currency set to PKR, the customer’s mobile number, and your hashed security string.12 Amounts are in PKR major units, meaning whole rupees, not paisa. The value 4250 means Rs. 4,250. 12 Customer phone numbers must be in E.164 format beginning with +92. The wallet apps reject other formats.
Step 3: Generate the HMAC-SHA256 hash
Every JazzCash request must include a signed hash that proves the request has not been tampered with. The hashing process works as follows: collect all request parameters into a key-value map, sort the keys alphabetically, concatenate the values with an ampersand separator, prepend your integrity salt with an ampersand, then run the full string through HMAC-SHA256 using your integrity salt as the key. The resulting hash goes into the pp_SecureHash field of your request.8 JazzCash provides a Redirection API which can be used for processing payments in your app. For Flutter apps specifically, the hashing and platform channel setup for native Android and iOS can be handled through method channels.
Step 4: Handle the callback
JazzCash sends a POST request to your callback URL when the transaction completes, is declined, or times out. Always verify the response hash before updating your order status. A response with a valid hash and a pp_ResponseCode of 000 indicates a successful payment.4 For recurring wallet payments, the sandbox endpoint is https://sandbox.jazzcash.com.pk/ApplicationAPI/API/4.0/purchase/domwallettransactionviatoken and the production endpoint is https://payments.jazzcash.com.pk/ApplicationAPI/API/4.0/purchase/domwallettransactionviatoken.
Easypaisa Integration Methods Explained
13 The types of custom code integration available for Easypaisa are redirection via post method for credit card transactions and REST API for mobile and over-the-counter transactions.
Hosted checkout (redirect) works the same way as JazzCash’s redirect option. Your app opens a payment session on Easypaisa’s servers and the customer completes payment on Easypaisa’s interface. Your backend receives a notification via callback when the transaction resolves.
REST API (Mobile Account) is the server-side direct integration. 17The customer enters their Easypaisa mobile number and confirms the payment with a one-time password. Your backend initiates the request, Easypaisa pushes the OTP to the customer’s phone, and the result is sent to your callback URL.16 To use direct checkout via REST API, call the sendRequest() function. To use hosted checkout via the redirection method, call the sendHostedRequest() method to redirect the user to the Easypaisa page for payment.
Step-by-Step: Easypaisa API Integration
Step 1: Access the sandbox15 Easypaisa has introduced its API Developer Portal, which is now live and can be used by third parties for integration, sandbox, and production movement for standard integration. Register at the Easypaisa developer portal using your merchant credentials to access the sandbox environment and full API documentation.
Step 2: Build your payment request
An Easypaisa mobile account payment request requires your Store ID, a unique order reference, the transaction amount in PKR, the customer’s mobile account number, a timestamp, and your hashed security string. 15The API gateway enables businesses and partners to handle money transfers, IBFT, bill payment, and other Easypaisa services on their applications and websites.
Step 3: Hash and sign the request
Easypaisa uses the same general HMAC-SHA256 signing pattern as JazzCash. Parameters are sorted, concatenated, and hashed using your merchant secret. Never send an unsigned request to the production endpoint.
Step 4: Handle the OTP and callback
After your backend sends the initiation request, Easypaisa sends the customer an OTP via SMS. The customer enters the OTP in your app’s payment confirmation screen. Easypaisa then sends the transaction result to your callback URL. Verify the response signature before marking any order as paid.
HMAC-SHA256 Hashing and Security
Both JazzCash and Easypaisa use HMAC-SHA256 request signing. The pattern is consistent across both platforms and you should implement it as a reusable utility in your codebase.
The correct sequence is: build your parameter map, sort all keys alphabetically, concatenate the corresponding values joined by an ampersand, prepend your integrity salt followed by an ampersand, then run the full string through HMAC-SHA256 using your integrity salt as the HMAC key.
Store your merchant credentials in environment variables, never in source code or client-side files. A compromised integrity salt allows anyone to forge valid-looking payment requests against your merchant account. Rotate credentials immediately if you suspect exposure.
On the response side, always verify the hash in every callback before taking any action. An unverified callback that triggers order fulfillment is a fraud vector. The verification process is the same as the signing process: rebuild the hash from the response parameters and compare it against the hash in the response. If they do not match, reject the callback and log it for investigation.
Sandbox Testing: What to Cover Before Going Live
1 Sandbox testing should cover success, failure, timeout, duplicate callback, and refund and inquiry cases. 1 Going live is not just a switch. Your logs, signatures, and reconciliation process must be production-ready.
Run every test case in the sandbox environment before requesting production access. The minimum test coverage for any Pakistani payment integration is:
Successful payment: a complete end-to-end transaction that resolves with a success response code, a valid hash, and a confirmed order update in your system.
Failed payment: a transaction where the customer enters the wrong MPIN or the payment is declined. Your app must handle this gracefully without marking the order as paid.
Timeout: a transaction where the customer does not respond to the OTP or MPIN prompt within the allowed window. Your app must not leave the order in a permanent pending state.
Duplicate callback: the same transaction result delivered twice to your callback URL. Your handler must be idempotent, meaning it processes a given transaction ID only once regardless of how many times the callback fires. 12If your endpoint returns a 5xx error, the gateway will retry. Make sure your handler is idempotent and processes the same event ID only once.
Refund and inquiry: confirm that your system can query transaction status and initiate a refund through the API before going live. Both platforms support inquiry endpoints that let you verify the status of any transaction by its reference ID.
Common Gotchas That Break Pakistani Payment Integrations
12 Always set the Idempotency-Key header to your order ID. Without it, double-submits create duplicate payments. 12 Settlement T+1 is Pakistan Standard Time business days. Saturday transactions settle on Monday. Build this into your settlement reconciliation logic so your finance team is not surprised by weekend delays.
Timestamp format errors are among the most common causes of hash mismatches. Both JazzCash and Easypaisa require timestamps in a specific format. A single character out of place causes the hash to fail and the transaction to be rejected. Generate timestamps server-side, not client-side, so timezone mismatches cannot affect them.
Amount formatting is another common failure point. 12Amounts are in PKR major units, whole rupees, not paisa. Sending paisa values instead of rupee values results in transactions being processed for one-hundredth of the intended amount.
Phone number format must be validated before sending. 12Customer phone should be in E.164 format beginning with +92. The wallet apps reject other formats. Sanitize all phone number input to strip spaces, dashes, and leading zeros before constructing your API request.
Frequently Asked Questions
Do I need separate merchant accounts for JazzCash and Easypaisa?
Not if you use a unified payment gateway. 10A unified gateway’s infrastructure is already integrated with both payment rails. When you integrate with a single API, Easypaisa and JazzCash acceptance are both included with no separate merchant account application, no parallel KYC process, and no second set of API credentials to manage. If you go direct with both platforms separately, you do need two independent merchant accounts, two onboarding processes, and two reconciliation workflows.
How long does JazzCash or Easypaisa merchant approval take?25
JazzCash merchant onboarding typically takes 3 to 5 business days. 27 Your account will be verified and you will receive a confirmation SMS. Opening charges are free. Easypaisa follows a similar KYC review process. Approval speed depends on how quickly your documents pass the compliance review. Having your CNIC, NTN certificate, bank account details, and business registration documents prepared in advance avoids the most common delays.
What are the transaction fees for JazzCash and Easypaisa in 2026?25
JazzCash and Easypaisa are on the lower end at around 2 to 3 percent with no setup fees. 24 Raast QR payments cost the merchant 0.25% of each sale. 23 The per-transaction MDR is 1.5 to 2.5 percent, negotiable based on volume, and settlement runs T+1 to T+2, meaning 1 to 2 working days after the transaction. Rates vary by payment method and can be negotiated downward at higher monthly transaction volumes.
Can I integrate JazzCash and Easypaisa in a Flutter app without native code
For the hosted checkout or redirect flow, yes. Your Flutter app opens a WebView pointing to the JazzCash or Easypaisa hosted payment page, the customer completes payment on the hosted page, and the result is delivered to your backend callback URL without any native code on your side. For the direct REST API flow, 3a comprehensive solution for integrating JazzCash credit and debit card payments into Flutter apps uses native support for both Android and iOS platforms through method channels connecting Flutter to native Android and Swift implementations. For most standard wallet payment scenarios, the hosted redirect flow in a WebView is the simplest and most maintainable approach in Flutter.
What should I do if my callback URL stops receiving payment notifications?
First, confirm your callback URL is publicly accessible and returns a 200 HTTP response on successful receipt. Both JazzCash and Easypaisa require a publicly reachable URL. A localhost address or a URL behind a firewall will never receive callbacks. Second, check your server logs for incoming POST requests from the gateway’s IP range. If requests are arriving but your handler is returning errors, the gateway’s retry logic will continue sending them. 12If your endpoint returns a 5xx error, the gateway retries. Make sure your handler is idempotent and processes the same event ID only once. Third, use the transaction inquiry API to manually check the status of any payment where the callback was not received, so you can update your order records accurately without waiting for a retry.
Conclusion
JazzCash and Easypaisa integration is not optional for any Pakistani app that handles payments. Together they cover the dominant share of Pakistani digital wallet users, and a checkout flow missing either one creates a drop-off point that costs real revenue. The integration process for both platforms follows the same core pattern: register a merchant account, obtain credentials, build signed API requests using HMAC-SHA256, handle callbacks with idempotent logic, and test every transaction scenario in the sandbox before switching to production. For most teams, a unified gateway reduces that work to a single API integration while covering both wallets, cards, and IBFT from one contract. For teams that need direct API access and custom settlement terms, the direct integration path is fully documented and achievable with a backend developer familiar with REST APIs and HMAC signing.
Mark X Media helps Pakistani businesses build the digital infrastructure around their app launches, from digital marketing and user acquisition to content and web presence that converts awareness into installs and active users. If you are launching a payment-enabled app and need a go-to-market strategy to match, explore what Mark X Media offers.
Mark X Media is a full-service digital marketing agency helping businesses grow through strategic SEO, performance advertising, social media management, web development, and content, delivering data-driven results to clients across Pakistan, the UAE, and the USA.





