Skip to main content
JazzCash is a mobile wallet in Pakistan. Customers pay from their JazzCash wallet balance and confirm each payment with their mobile number and a one-time password. Payrails processes JazzCash through three payment service providers (PSPs). The flow is the same with each one, but the required request fields and the supported workflows differ. Pick a PSP below for its setup steps and request examples.

​
How a JazzCash payment works

JazzCash is a redirect payment method:
  1. The customer selects JazzCash at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to the PSP’s payment page.
  3. The customer enters their JazzCash mobile number and confirms the payment with a one-time password.
  4. The PSP sends the customer back to your returnInfo URL.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer confirms every payment on its own. Payrails captures JazzCash payments immediately, so a successful payment is final. To return funds, refund the payment. Refunds work with Boku and dLocal, but not with Thunes.

​
Supported currencies and countries

JazzCash supports PKR (Pakistani rupee) as its only presentment currency.

​
Integrate JazzCash

Choose the PSP that processes JazzCash for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

Boku

JazzCash via Boku

dLocal

JazzCash via dLocal

Thunes

JazzCash via Thunes

​
Compare PSPs

JazzCash is a one-off payment method: no PSP saves a JazzCash instrument for later merchant-initiated transactions (MIT).

​
Ways to integrate JazzCash

  • Payrails SDK: the Web SDK shows JazzCash when your workflow returns it as a payment option, and redirects the customer to the PSP’s payment page. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with jazzCash as the paymentMethodCode. Each PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 2, 2026