Describe the product and merchant structure
Share your website, company jurisdiction, product description and expected PKR order amounts. State whether customers buy digital content, goods or another service, and identify the company responsible for fulfilment and support. Method eligibility depends on the reviewed business and route.
If you operate a platform, explain who the underlying merchants are and how transactions are attributed to them. Do not route new, unreviewed merchant traffic through an existing approved account.
Write down the wallet checkout steps
| Step | Decision required |
|---|---|
| Create order | Unique merchant reference, PKR amount and expiry |
| Show instructions | Approved Easypaisa or JazzCash customer flow |
| Wait for result | Pending message, return path and support instructions |
| Confirm payment | Documented backend verification and final state |
| Reconcile | Provider reference, confirmed amount and exception history |
Ask how the flow behaves inside an app, a mobile browser and a desktop browser. Confirm the supported experience instead of assuming every wallet integration uses the same redirect or authorization process.
Avoid false success and duplicate fulfilment
Separate the customer-facing return page from the backend confirmation. Follow the approved documentation for notification verification, status queries and acknowledgements. A browser reaching the success page is not sufficient evidence that funds were received.
Use a test order to check delayed callbacks, repeated notifications and a request timeout. Your order system should keep a stable reference and fulfil only once after the documented final result.
Request collection and payout confirmation independently
PAYJN’s Pakistan coverage discusses Easypaisa and JazzCash. Describe whether you need collections, payouts or both and obtain written confirmation for each requested direction. Do not infer a supported payout destination from a collection logo.
Ask for current fees, limits, funding and settlement terms. Provider approval and merchant eligibility must be resolved before publishing payment promises to your customers.
Use a concrete pre-launch review
- Approved business and wallet flow recorded.
- Customer instructions tested on the intended devices.
- Pending, failed and final states understood by support.
- Repeated or delayed callbacks tested without double credit.
- Escalation references and reconciliation owner agreed.
For operator background, see the Easypaisa business onboarding portal and JazzCash payment gateway information. Their products do not establish your approved PAYJN coverage or a direct partnership.
Get a merchant-specific integration review
Share your website, target market, required methods and expected volume. Our team will review merchant fit and the proposed payment flow. Do not send API secrets or customer banking data in a first enquiry.
Discuss Pakistan integrationMethod availability, transaction limits, fees and production access depend on the approved merchant setup. Operator references describe the payment ecosystem and do not imply a direct partnership.