Evoke Wallet Parameters
This page describes the URL shapes used when the Pakistan cashier launches the Easypaisa / Jazzcash wallet apps, and how to handle them in three contexts: system browser H5, in-app native code, and in-app WebView (iOS and Android).
Nigeria Pay With Wallet uses schemes such as
pay://to open PalmPay. See Android in-app cashier launch and iOS in-app cashier launch. Pakistan Pay with MoMo follows the same WebView rules below.
Scenarios overview
Pakistan — URL shapes by platform
H5 / general: URLs the cashier may trigger
iOS (system browser and any URL ultimately handed to the OS)
- Easypaisa:
easypaisa:// - Jazzcash:
jazzcash://
Android (Chrome and similar often use intent://; the OS resolves it to the app)
- Easypaisa:
intent://easypaisa.onelink.me/miniapp#Intent;scheme=https;package=pk.com.telenor.phoenix;end - Jazzcash:
intent://deeplink#Intent;scheme=jazzcash;package=com.techlogix.mobilinkcustomer;end
In some environments the cashier may fall back to plain schemes (
easypaisa:///jazzcash://); treat them like any other custom scheme on Android as below.
iOS: in-app (WebView and native)
- Let the OS handle non-http(s) links
InwebView(_:decidePolicyFor:navigationAction:)(or equivalent), detectnavigationAction.request.urlschemes such aseasypaisa,jazzcash(andpaywhere applicable):return .cancelfor that navigation so the WebView does not show an error page, then callUIApplication.shared.open(url)with the full URL so the wallet app can open. - Optional:
canOpenURLand declared queries
Addeasypaisa,jazzcash(and any others you need) toLSApplicationQueriesSchemesin Info.plist if you callcanOpenURL; otherwise iOS may restrict the result. - Native-only launch
Buildeasypaisa:///jazzcash://asURLand open withUIApplication.shared.open—same as after a WebView intercept.
Android: in-app (WebView and native)
- Intercept WebView navigations
InshouldOverrideUrlLoading(or theWebResourceRequestcallback):intent://:Intent.parseUri(url, Intent.URI_INTENT_SCHEME)thenstartActivity; add fallback handling if required (e.g. package / browser).easypaisa://,jazzcash://, etc.:Intent(Intent.ACTION_VIEW, Uri.parse(url))thenstartActivity.
Returntrue(or consume the load) so the WebView does not load the URL internally.
- Native-only launch
intent://: sameIntent.parseUri+startActivity.- Custom schemes:
ACTION_VIEW+Uri.parse.
- Reference
PalmpayDemoAndroid - WebViewActivity.kt - Platform notes
From Android 11, package visibility affectsresolveActivityand explicit launches; configurequeries/intent-filterper official docs if you detect “not installed” incorrectly.
In-app demo code
Minimal patterns below: native from any screen; WebView on the WKWebView / WebView that loads cashier H5. Add error UI, analytics, and other schemes (e.g. Nigeria pay://) in production.
iOS (Swift)
1) Native: open the deep link URL directly
2) WebView: WKNavigationDelegate — cancel and hand off to the system
Declare easypaisa, jazzcash, etc. under LSApplicationQueriesSchemes in Info.plist if you use canOpenURL.
Android (Kotlin)
1) Native: single entry for intent:// and custom schemes
2) WebView: WebViewClient — intercept non-http(s) URLs
For more branches, see PalmpayDemoAndroid - WebViewActivity.kt.
System browser H5 (reference)
In Safari / Chrome, navigations to the URLs above are usually handled by the OS without extra wrapping on the merchant web page, as long as the cashier domain, HTTPS, and product configuration are correct.
Summary
- H5 browser: iOS schemes and Android
intent://(or fallback schemes) as listed. - App WebView: do not let the WebView load launch URLs alone; intercept and open with the OS (iOS
UIApplication.open; AndroidIntent.parseUri/ACTION_VIEW). - App native: same URLs and APIs as after a successful WebView intercept.