PKR payment coverage

Show only the route the project can use

Approved projects may use JazzCash, Easypaisa, Raast, Bank Alfalah, or NayaPay. Availability, limits, and commercial terms are confirmed per merchant before launch.

Apply for merchant access

Method catalogue

Match the checkout to approved coverage

Do not display a method until it is enabled for the merchant project and tested with the correct PKR flow.

  1. 01

    JazzCash

    Confirm the wallet flow, project availability, limits, customer handoff, and refund path.

  2. 02

    Easypaisa

    Enable only after the merchant project and customer journey have been approved and tested.

  3. 03

    Raast

    Keep the instant-transfer reference connected to the order and server-verified result.

  4. 04

    Bank Alfalah

    Confirm the approved account-based route, status model, settlement record, and limits.

  5. 05

    NayaPay

    Validate current wallet availability for the project before offering it to customers.

Project controls

What must be confirmed before launch

Coverage is project-specific. The merchant should test the approved route and preserve the gateway reference through every state.

Project approval

Complete the merchant and KYC/AML review before relying on any method.

Test access

Use a test project or sandbox path to validate approved, pending, failed, and duplicate-event cases.

Server verification

Use the API key and project ID on the backend and verify the authoritative status.

Signed postbacks

Validate incoming signatures and process duplicate notifications idempotently.

Confirm payment coverage before integration

Bring the target methods, customer journey, expected PKR volume, and technical route to the merchant review.

Confirm payment coverage