Pakistan Payments Guide

Payments in Pakistan: Mobile Accounts, Bank Transfers, and Emerging Digital Demand A customer finds an online course through a social-media post. She opens the merchant’s checkout on her phone, sees the price, and decides to buy. She has enough money in a mobile account and regularly transfers funds through her banking app. But the checkout offers only an internationally enabled payment card. Her local debit card cannot complete the transaction. The merchant records an abandoned checkout. It looks like a customer-level payment failure. It is actually the last visible result of several earlier decisions: which payment methods the merchant integrated, which customers the provider could serve, whether the transaction could be processed in Pakistani rupees, how the merchant would receive the funds, and whether the selected operating model complied with local payment and foreign-exchange requirements. That sequence captures Pakistan’s central payment tension. Pakistan generated approximately $407.3 billion in nominal GDP in 2025, placing it in the mid-40s among world economies by that measure. Its population was estimated at approximately 255.2 million, while GDP per capita was about $1,596. The country therefore offers considerable potential transaction volume, but uneven purchasing power and payment access make product pricing and payment-method selection critical. (World Bank Open Data)

At the same time, Pakistan’s formal payment infrastructure is becoming heavily digital. By March 2026, more than 132 million mobile-app and wallet registrations were connected to banks, branchless-banking providers and electronic money institutions. Digital channels accounted for approximately 92% of formally recorded retail-payment volume during the January–March 2026 quarter—but only about 40% of the value. These figures cover transactions within formal banking and payment channels; they do not measure cash activity outside the regulated system. This is not a conventional transition from cash to cards. Pakistan is developing through a more complicated combination of: * Mobile and branchless-banking accounts * Banking applications * Electronic money wallets * Raast instant payments * Bank transfers * QR acceptance * Domestic and international cards * Cash-in and cash-out agents * Cash on delivery * Regulated foreign-exchange channels For merchants, the central planning question is therefore not simply: Can customers reach the checkout? It is: Can the intended customer access an appropriate payment method, complete it on the available device, receive a reliable confirmation, obtain a workable refund, and generate funds that the merchant can legally and economically settle? Payment access and settlement feasibility should lead Pakistan market planning—not be added after demand generation has begun.

Pakistan payment snapshot Category Pakistan market profile Region South Asia Population Approximately 255.2 million in the World Bank’s 2025 estimate. Pakistan’s official 2023 census counted approximately 241.5 million people; the two figures use different years and methodologies. (World Bank Open Data) Currency Pakistani rupee, code PKR, commonly displayed as Rs Nominal GDP Approximately $407.3 billion in 2025. (World Bank Open Data) Global economic position Approximately mid-40s by 2025 nominal GDP. The brief’s 42nd-place figure should be recalculated against the final publication dataset. GDP per capita Approximately $1,596 in 2025. (World Bank Open Data) Economic structure Services represented approximately 58.4% of FY2026 output, with agriculture and industry remaining material contributors. (National Account Dashboard) Digital-payment profile Digital channels represented approximately 92% of formal retail-payment volume in Q3 FY2026 but around 40% of recorded value. App and wallet access More than 132 million mobile-app and wallet registrations by March 2026; registrations are not unique customers. Branchless-banking infrastructure Approximately 157.9 million accounts and 819,397 agents in January–March 2026. Account totals do not equal unique or active people. Payment cards Approximately 68.3 million cards, including 57.2 million debit cards and 3.1 million credit cards, at the end of March 2026. Important local infrastructure

Raast, branchless-banking accounts, bank and EMI wallets, QR payments, interbank transfers, PayPak and agent-assisted cash services Raast usage Approximately 742 million transactions worth PKR 23.27 trillion during January–March 2026 across reported Raast services. QR acceptance Approximately 2.5 million QR-enabled merchants were reported in March 2026. Mobile relevance High among reachable digital customers, although subscriptions, devices, accounts and cards should not be interpreted as unique or universally active users Recurring-payment readiness Most practical through appropriately enabled cards; wallet, account-to-account and request-to-pay capabilities require provider-specific validation Local-acquiring relevance Potentially important for PKR processing, domestic cards, local methods and settlement, but contracting and entity requirements vary Regulatory complexity Material because payment licensing, merchant acquiring, customer due diligence, ecommerce taxation and foreign-exchange rules interact Strong merchant opportunities Education, freelance and professional tools, SaaS, marketplaces, gaming, digital media, on-demand platforms and B2B services Primary merchant takeaway Design the market around payment access and the complete settlement chain, not around card acceptance alone

Pakistan’s access-to-settlement failure chain A merchant can generate demand in Pakistan and still fail commercially at one of seven handoffs. Handoff Customer or merchant question Typical failure 1. Discovery to checkout Can the customer reach and use the checkout on the available device? Slow page, broken mobile layout, lost basket or inaccessible language 2. Checkout to payment access Does the customer possess one of the payment methods displayed? Card-only checkout excludes customers with mobile or bank accounts 3. Access to initiation Can the method open and authenticate correctly? Redirect, QR, OTP, app-switching or bank-login failure 4. Initiation to confirmation Can the merchant distinguish success, failure, expiration and pending status? Customer debit without matched order, duplicate order or false screenshot 5. Confirmation to fulfilment Is the payment final enough to release the product or service? Digital goods released against an unverified or reversible event 6. Fulfilment to refund or dispute Can the merchant return funds and prove fulfilment? Unsupported partial refund, manual refund or mismatched records 7. Settlement to usable funds Can the merchant receive, convert, reconcile and use the proceeds? FX restrictions, unsuitable payout currency, reserves or manual reconciliation

A provider may solve only one or two links. “Pakistan coverage” could mean international card acceptance without local wallets, local collection without international payout, a gateway without merchant acquiring, or access to Raast without a complete refund and settlement operation. Market readiness must be evaluated across the entire chain.

Economic scale and merchant reality Pakistan’s economic scale makes it difficult to dismiss as a niche market. Its estimated population exceeds 255 million, and annual output exceeds $400 billion. But low average income means a merchant cannot translate population directly into addressable revenue. Product affordability, transaction cost and local demand matter more than national scale alone. (World Bank Open Data) A merchant selling low-cost education, productivity tools, gaming content or professional services may reach a large number of relevant customers. A merchant dependent on high-value discretionary spending or internationally enabled credit cards may reach a much narrower segment. The economy is service-led, while agriculture, manufacturing, trade and remittance activity remain commercially significant. This supports both consumer-payment use cases and business-payment opportunities, including education, professional services, software, supplier platforms, logistics and digital exports. (National Account Dashboard) Pakistan should therefore be assessed as: * A large total market with relatively low average purchasing power * A digitally active market whose payment access remains uneven * A country with extensive formal account and agent infrastructure * An export-oriented digital-services opportunity * A market where local collection and international settlement may require different providers or contracts

* A country in which transaction value, product category and customer segment can lead to very different payment strategies

Digital maturity: connectivity can outpace payment access No single current, official percentage was identified that adequately measures “Pakistan’s digital economy as a share of GDP.” ICT exports, online payments, telecommunications revenue, ecommerce activity and digitally enabled conventional businesses are different measures. Combining them into a single percentage would create false precision. Pakistan’s digital maturity is better evaluated through several related indicators. Connectivity By March 2026, Pakistan had approximately 207.2 million telecommunications subscriptions and 160.9 million broadband subscriptions. Approximately 71.6% of devices identified on mobile networks were smartphones. These are subscriptions and network-observed devices, not unique people or a measure of universal ecommerce readiness. These figures nevertheless explain why mobile checkout should be treated as the standard journey rather than a reduced version of a desktop experience. Digital accounts and applications As of March 2026, reported access included: * 95.8 million branchless-banking mobile-app users * 28.9 million mobile-banking users * 16.2 million internet-banking users * 7.3 million EMI wallet users The categories can overlap because a person may use more than one account, application or institution.

Pakistan also had approximately 267.9 million bank accounts by December 2025, of which about 49% were linked to a mobile application or wallet. Account totals are not unique-user totals, but they show how quickly formal payment access is becoming connected to mobile interfaces. Branchless banking Branchless banking connects formal accounts with an extensive physical agent network. In the January–March 2026 quarter, the State Bank of Pakistan reported approximately: * 157.9 million branchless-banking accounts * 819,397 agents * 2.99 billion transactions * PKR 13.02 trillion in transaction value Mobile shops and grocery stores represented large portions of the agent network. This makes the agent a bridge between cash and digital value rather than merely a service counter. Access is not uniform. Approximately 30.4% of reported branchless-banking accounts were held by women, indicating that national account totals can conceal meaningful participation gaps. Digital services and freelancing During July 2025–March 2026, Pakistan reported: * Approximately $3.39 billion in ICT export proceeds * An ICT and IT-enabled-services trade surplus of approximately $2.91 billion * Approximately $856.3 million in freelancer remittances * More than 34,000 registered IT and IT-enabled-services companies

Freelancer remittances increased by approximately 51% compared with the equivalent previous period. These are export and remittance measures, not total domestic digital-economy output, but they provide strong evidence of demand for professional software, creator tools, education, productivity services and compliant cross-border payment infrastructure.

How customers access payments 1. Cash and the agent network Pakistan’s digital-payment growth has not eliminated cash. The State Bank’s payment-system figures cover formal banking and payment channels and explicitly exclude transactions outside that system. (State Bank of Pakistan) The agent network allows customers to: * Deposit cash into an account * Withdraw received funds * Transfer money * Pay bills * Access services without a conventional branch * Convert physical cash into value usable through a mobile application For merchants, agent-assisted funding can expand the number of customers capable of making a digital payment. It can also delay checkout when the customer does not have sufficient balance. A mobile checkout should therefore: * Display the final payable amount before authentication * Preserve the basket if the customer leaves to add funds * Keep the payment session open for a reasonable period * Explain whether an expired payment can be retried * Prevent duplicate orders when the customer returns * Provide a clear pending state * Avoid adding fees only after method selection 2. Mobile accounts and wallets Pakistan’s mobile-payment category includes several operating models: * Bank mobile applications * Microfinance and branchless-banking accounts * Electronic money institution wallets * Mobile applications linked to conventional accounts * Wallets or applications capable of initiating Raast transactions

The licensing, custody and settlement model matters. An electronic money institution is not the same as a bank, while a licensed payment-system operator or payment-service provider may facilitate transactions without holding customer funds. (State Bank of Pakistan) A merchant should not treat “wallet payment” as a complete capability statement. For each integration, confirm: * Customer eligibility * Merchant-category eligibility * Account or wallet funding rules * Redirect, QR, app-link or embedded experience * OTP, PIN or in-app approval * Confirmation timing * Expiration * Partial and full refunds * Reusable authorization * Recurring-payment support * Settlement currency * Payout timing * Reconciliation identifiers * Dispute escalation * Whether an international merchant can contract directly 3. Raast instant payments Raast is Pakistan’s national instant-payment system. It was designed to support interoperable, real-time retail transactions across participating financial institutions. (State Bank of Pakistan) During January–March 2026, Raast processed approximately 742 million transactions worth PKR 23.27 trillion. Person-to-person payments represented about 664 million transactions and PKR 18.88 trillion of that total. More than 2.6 million merchants were reported as enabled for Raast person-to-merchant payments. Raast P2M can support payment initiation using: * QR codes * A Raast alias * An IBAN * Request to Pay * Ecommerce or merchant-application integration

The scheme provides for immediate customer confirmation and includes a customer-initiated refund-request process. The merchant can accept or reject that request, after which the relevant participant processes the resulting fund movement. Operational behavior still depends on the merchant’s bank, provider and integration. (State Bank of Pakistan) Merchant implications Raast can be valuable for: * Education payments * Marketplaces * On-demand services * Local digital goods * B2B invoices * Professional services * Physical merchants * Account-to-account ecommerce It does not automatically solve: * Recurring debits * International merchant contracting * Foreign-currency settlement * Refund automation * Reconciliation * Customer support * Merchant-category approval A merchant should ask whether its provider offers a real ecommerce integration or only a QR and manual bank-notification workflow. 4. Conventional bank transfers Bank transfers remain useful for: * Higher-value purchases * B2B invoices * Tuition * Seller funding and payouts * Professional services * Institutional collections * Customers unwilling to enter card information The merchant should prefer structured transfers that include: * A unique reference * Virtual or dedicated account information * An invoice identifier * Reliable status reporting * An automated match to the order * An expiration period where applicable A customer screenshot is not proof of final payment. Merchant fulfilment should depend on a verified provider or bank status.

5. Payment cards At the end of March 2026, Pakistan had approximately: * 57.2 million debit cards * 3.1 million credit cards * 204,800 prepaid cards * 7.7 million social-welfare cards The total was approximately 68.3 million cards. These are issued cards, not unique cardholders, active ecommerce cards or internationally enabled cards. The difference between debit- and credit-card issuance is commercially important. Credit-card access remains narrow relative to population and mobile-account access. A cardholder may have: * A card intended primarily for ATM use * A domestically enabled debit card * An online-enabled card * A card usable with Pakistani merchants * An internationally enabled card * An international card with a limited foreign-exchange allowance * A card that works for one-time purchases but not recurring payments Merchants should not treat these as the same customer capability. 6. PayPak PayPak is Pakistan’s domestic card scheme and is relevant to domestic acceptance and processing. In July 2026, the State Bank of Pakistan announced a co-badged PayPak solution intended to combine domestic payment infrastructure with international acceptance. Actual availability will depend on issuing banks, acquirers, card products and merchant integrations. (State Bank of Pakistan) A merchant should confirm: * Ecommerce enablement * Gateway and acquirer support * Domestic-only versus co-badged acceptance * Authentication * Tokenization * Recurring-payment capability * Refund and dispute procedures

7. Cash on delivery Cash on delivery may remain commercially relevant for physical-goods merchants, especially when customer trust or digital-payment access is limited. It creates a second, less visible transaction funnel: 1. Customer places order. 2. Merchant confirms order. 3. Merchant allocates inventory. 4. Courier attempts delivery. 5. Customer accepts or refuses. 6. Courier collects cash. 7. Courier reconciles the collection. 8. Merchant receives the payout. 9. Returns or disputes are processed. A checkout order is therefore not equivalent to collected revenue. For digital goods, SaaS, gaming, streaming and immediately delivered education, cash on delivery is generally unsuitable.

The card-versus-account payment gap During January–March 2026, approximately 434.5 million online purchases worth about PKR 470 billion were initiated through reported accounts or wallets. Card-based ecommerce generated approximately 16.4 million transactions worth about PKR 80.1 billion during the same quarter. The reporting categories are not perfectly interchangeable, but the scale difference demonstrates why card-only ecommerce data do not describe Pakistan’s complete digital-payment environment. The merchant implication is not that cards are unimportant. Cards remain valuable for: * International customers * Higher-income domestic segments * Cross-border services * Automatic subscriptions * Travel * Returning customers using tokenized credentials * Customers without a suitable local account-to-account option The implication is that cards should usually form one layer of the Pakistan payment portfolio rather than the whole portfolio.

Payment-method priority matrix The appropriate priority changes by vertical and transaction model. Method Education Freelance and professional tools SaaS Marketplaces Gaming and digital media Merchant classification Raast or structured account-to-account payment Launch essential High-value addition Useful for customer-initiated renewals Launch essential High-value addition Essential for broad local account access Bank and branchless-banking mobile accounts Launch essential Launch essential High-value addition Launch essential Launch essential for one-time purchases Essential consumer-payment layer Domestic and international cards High-value addition Important for international products Launch essential for automatic subscriptions High-value addition Important for international and recurring use Necessary, but insufficient alone Structured bank transfer Essential for high-value tuition Essential for professional and B2B payments High-value addition for annual contracts Important for seller and business flows Segment-specific Strong for higher-value transactions QR payment High-value addition Useful for local service providers Segment-specific Important for local sellers Useful for events and physical distribution Useful for merchant-present and selected online journeys Cash on delivery Usually unnecessary Unnecessary Unnecessary Important for physical-goods sellers Usually unsuitable Segment-specific and operationally expensive PayPak Useful as issuer and ecommerce coverage expands Segment-specific Segment-specific

High-value addition High-value addition Monitor production support Credit cards Useful for higher-income and international segments Important for global tools Essential for many subscriptions Segment-specific Important for recurring and international spending Narrow reach but high strategic value Request to Pay Useful for fee reminders Useful for invoice collection Potential customer-initiated renewal mechanism Useful for collections Useful for one-time purchases High-value addition where provider-supported Direct debit or automated account mandate Potential long-term use Potential B2B use Attractive if commercially supported Optional Optional Do not assume availability or adoption Carrier billing Usually unnecessary Unnecessary Unnecessary Unnecessary Segment-specific Consider only after proven demand and viable economics Buy now, pay later Limited relevance Usually unnecessary Usually unnecessary Segment-specific for retail Usually unnecessary Provider- and vertical-specific “Launch essential” refers to commercial importance for the indicated merchant model. It does not mean that every international merchant is automatically eligible to accept the method.

Growth prospects that matter for payment strategy A current authoritative national ecommerce-revenue forecast with a consistent definition was not identified for this guide. Instead of presenting a potentially incompatible commercial forecast, the opportunity should be evaluated through current payment and digital-service activity. Education Pakistan’s population, mobile connectivity and digital-account infrastructure create potential for: * Online courses * Test preparation * Professional certification * Tutoring * Language learning * University and application services * Skills training * Educational software The payment profile can include small one-time course purchases, larger tuition payments, term-based collections and manually renewed access. Recommended methods: * Mobile account or wallet payments * Raast or structured account-to-account collection * Cards for international and automatic recurring payments * Bank transfer for high-value tuition Main operating issues: * Matching a parent or payer to the correct student * Refunds after course access * Partial refunds * Installment schedules * Payment deadlines * Proof of enrolment * Renewal communication Freelance and professional tools Pakistan’s freelancer remittances reached approximately $856.3 million during July 2025–March 2026, while ICT export proceeds exceeded $3.3 billion. This supports demand for professional software, education, invoicing, creator tools, communications services and productivity platforms.

The merchant must separate two use cases: * Collecting PKR from a customer in Pakistan * Receiving or paying cross-border earnings through an authorized banking arrangement A provider capable of domestic collection may not solve international payouts, and an international card provider may not reach customers whose money is held in a local account. SaaS SaaS opportunity is strongest among: * Freelancers * Agencies * Software companies * Exporters * Educational institutions * Professional-services firms * Small and medium-sized businesses The primary payment problem is recurring coverage. A practical portfolio may include: * Cards for automatic subscriptions * Account-to-account payment for annual plans * Request-to-pay or invoice-based renewal * Bank transfer for business contracts * PKR pricing for domestic customers * Foreign-currency pricing only where legally and commercially appropriate Marketplaces Marketplaces can benefit from mobile accounts, Raast, cards, bank transfers, QR acceptance and cash on delivery. They also introduce the most complicated operating model. The platform must define: * Who is the merchant of record * Who onboards sellers * Who receives customer funds * Whether funds are held before delivery * When sellers are paid * Who handles refunds * Who records withholding and tax information * Who bears fraud and non-delivery losses * Whether local licensing or partnering requirements apply

Marketplace opportunity should be evaluated together with seller payouts and regulated fund flow—not solely with customer checkout conversion. Gaming Pakistan’s mobile connectivity and account-based payment infrastructure support potential demand for: * Virtual currency * Downloadable content * Passes * One-time upgrades * Subscriptions * Esports or event payments * Creator and community purchases Wallets and account-to-account methods can be valuable for one-time, low-value payments. Cards may be needed for automatic renewal and some international products. Gaming merchants should validate: * Minimum economically viable transaction value * Method fees * Account takeover * Minor and family-member spending * Digital-delivery evidence * Refund abuse * Merchant-category eligibility * Recurring support * Foreign-exchange treatment Digital media Streaming, news, music, creator content and other digital-media products can use: * One-time access passes * Customer-initiated monthly renewal * Annual account-to-account payment * Automatic card subscription * Sponsored or ad-supported tiers Merchants should not assume every wallet or Raast payment can be converted into a reusable recurring mandate. B2B commerce B2B opportunity includes: * Procurement software * Supplier platforms * Logistics * Professional services * Invoicing * Business education * Software licensing * Marketplace seller tools Structured bank transfer and Raast may be more important than consumer-wallet branding. Finance teams will expect:

* Invoice references * Tax fields * Gross and net reporting * Multi-user approval * Refund and credit-note handling * Settlement reconciliation

Currency and pricing Pakistan’s official currency is the Pakistani rupee, code PKR. Consumer prices are commonly displayed using Rs. Why PKR pricing matters Local-currency presentment can: * Make affordability clearer * Align with account and wallet balances * Reduce uncertainty * Improve recognition * Simplify customer-support conversations * Make refund amounts easier to explain Displaying PKR does not prove that a provider can process, settle or pay out PKR to the merchant. Separate the currency layers Merchants should document: 1. Presentment currency: what the customer sees. 2. Processing currency: what enters the payment network. 3. Customer funding currency: the currency in the card, wallet or account. 4. Settlement currency: the currency in which the provider calculates the merchant balance. 5. Payout currency: what reaches the merchant’s bank. 6. Reporting currency: what appears in financial systems. 7. Conversion currency: any intermediary conversion. An international merchant may display PKR while receiving another currency after provider or bank conversion. This can create: * FX spread * Conversion fees * Timing differences * Refund-value differences * Treasury exposure * Reconciliation exceptions Foreign-exchange constraints

Pakistan’s foreign-exchange framework is administered through the State Bank of Pakistan and Authorized Dealer banks. Regulations and the Foreign Exchange Manual govern how permitted payments, receipts, card transactions and cross-border transfers are handled. Cases not covered by delegated authority may require additional bank or regulatory review. (State Bank of Pakistan) This means that international payment capability is not determined solely by possession of a card or account. Merchants and providers should confirm: * Permitted transaction purpose * Customer documentation * Card or account capability * Merchant category * Currency * Transaction limits * Settlement route * Payout route * Repatriation * Reporting * Refund treatment Avoid displaying a live exchange rate in an evergreen guide. FX rates, spreads and controls should be checked at the time of pricing and contracting.

Local acquiring and cross-border processing These terms should not be treated as synonyms: * Local acquiring * Domestic card processing * Local PSP * Raast connectivity * Wallet support * PKR settlement * Local bank payout * Cross-border acquiring * International merchant contracting A provider can offer one without offering the others. Potential advantages of local acquiring Local acquiring may: * Enable domestic card routing * Support PayPak * Improve issuer familiarity * Reduce selected cross-border costs * Support PKR settlement * Expand local-method access * Improve domestic reporting Any improvement depends on issuer, acquirer, merchant category, fraud profile, transaction value, product and customer mix. It should be tested rather than promised. Potential operating requirements Depending on the provider and merchant model, local acquiring may involve: * A Pakistani entity * A domestic bank account * Local tax registration * Merchant due diligence * Product approvals * Beneficial-ownership documentation * Local settlement * Reserves * Minimum volume * Local contracts * Data and reporting obligations These requirements must be confirmed with the selected acquirer and legal advisers. Cross-border alternatives A global PSP or Merchant of Record may allow a merchant to test demand without building a complete local operation. Potential trade-offs include: * Higher processing cost * Lower domestic-method coverage * Restricted merchant categories * Foreign-currency pricing * Limited PKR settlement

* Lower control over refunds * Dependence on the provider’s eligibility model A common scaling architecture is: * International provider for cards and reusable global integration * Local bank, acquirer or regulated provider for Raast, domestic cards and account-based methods * Orchestration or an internal payment layer to normalize statuses and reporting

Payment regulation and merchant eligibility Pakistan’s payment framework is led by the State Bank of Pakistan. The Payment Systems and Electronic Fund Transfers Act 2007 establishes the statutory foundation for payment systems, electronic transfers and related rights and responsibilities. Additional regulations and circulars govern banks, branchless banking, electronic money institutions, payment-system operators, payment-service providers, merchant acquiring and digital acceptance. (State Bank of Pakistan) Responsibilities differ by participant Merchant Usually responsible for: * Accurate product description * Lawful goods or services * Customer terms * Fulfilment * Refund policy * Customer support * Fraud controls * Tax and invoice obligations * Evidence retention Acquirer or merchant-acquiring institution Typically responsible for: * Merchant onboarding * Due diligence * Payment acceptance * Scheme compliance * Settlement arrangements * Monitoring * Dispute administration Bank, microfinance bank or EMI May be responsible for: * Customer account or stored value * Authentication * Transaction execution * Account limits * Customer due diligence * Regulated safeguarding or custody requirements PSO or PSP May provide: * Switching * Gateway services * Processing * Routing * Technical connectivity An SBP-authorized PSO or PSP should not automatically be assumed to hold customer funds; its licensed role and contractual function must be examined. (State Bank of Pakistan) Marketplace or Merchant of Record

May additionally take responsibility for: * Seller onboarding * Customer contracting * Tax collection * Payment collection * Seller payout * Refunds * Prohibited-product controls * Complaints The responsibilities depend on the legal and contractual model. Merchant acquiring and digital acceptance State Bank requirements direct relevant institutions to offer digital merchant-acceptance facilities such as QR, POS, softPOS, ecommerce gateways and Raast P2M APIs. Merchant onboarding remains subject to KYC, due diligence, categorization, limits and monitoring. (State Bank of Pakistan) Provider coverage should not be treated as proof that a merchant can enter production. Eligibility may depend on: * Product * Merchant category * Local licensing * Customer age * Transaction value * Digital-delivery model * Cross-border activity * Foreign-exchange purpose * Ownership * Expected volume * Fraud exposure * Refund policy * Marketplace structure Legal, regulatory and tax disclaimer: This article provides general information and does not constitute legal, regulatory, tax or accounting advice. Merchants should confirm applicable obligations and operating requirements with qualified advisers and relevant payment partners.

Tax and invoicing context Pakistan’s tax environment cannot be summarized by one national ecommerce tax rate. Federal authorities generally administer sales tax on goods and income-tax requirements, while services can be subject to provincial or territorial sales-tax regimes. Product classification, seller location, customer location and operating model can change the result. Finance Act changes introduced and expanded concepts relevant to ecommerce, including: * Ecommerce * Digitally delivered services * Online marketplaces * Payment intermediaries * Courier services * Withholding and reporting * Cash-on-delivery collection Payment intermediaries and couriers can have withholding or reporting responsibilities when settling digitally ordered goods, depending on the transaction and current rules. (FBR) The Finance Act 2026 and the current consolidated tax legislation should be checked before publication and before launch. (Federal Board of Revenue) Merchants should obtain advice on: * Registration * Goods versus services classification * Provincial jurisdiction * Digitally delivered services * Marketplace liability * Withholding * Courier and cash-on-delivery treatment * Tax-inclusive pricing * Invoice timing * Customer tax identifiers * Refund adjustments * Merchant of Record implications * Cross-border services Tax analysis should follow the actual payment and fulfilment flow. The entity receiving funds may differ from the entity delivering the service, issuing the invoice or paying the seller.

Checkout localization Localization should remove payment-completion barriers, not merely translate marketing copy. Language English may be suitable for selected professional and internationally oriented customers. Urdu can improve accessibility for a broader domestic audience. The most important content to localize includes: * Pay button * Method instructions * OTP guidance * QR instructions * Pending-payment message * Failure reason * Retry path * Refund policy * Support contact * Confirmation Payment-method ordering A practical starting order for a domestic mobile customer is: 1. Relevant mobile account, wallet or Raast option 2. Domestic and international cards 3. Structured bank transfer 4. Cash on delivery for eligible physical goods 5. Additional segment-specific methods The final order should be based on eligibility and measured completion—not on a universal global template. Mobile performance The checkout should tolerate: * Small screens * Lower-cost devices * Variable bandwidth * Older operating systems * App switching * OTP delay * QR scanning * Return from a banking application * Session interruption while adding funds The merchant should preserve both basket and payment state during every handoff. Phone and identity fields * Support Pakistani phone-number formats. * Normalize the number after entry rather than forcing unfamiliar formatting. * Explain why the number is needed. * Avoid requesting the same number repeatedly.

* Do not request a CNIC or other national identifier unless a legitimate provider, regulatory or risk requirement applies. * Protect and minimize identity data. Trust signals Display: * Merchant identity * PKR amount * Recognizable method branding * Product or course name * Delivery or access timing * Refund terms * Support path * Confirmation that the merchant will not request the customer’s PIN, password or OTP

Authentication and customer verification Depending on the method, a customer may encounter: * Wallet or account PIN * OTP * Mobile-app approval * QR confirmation * Bank-login authentication * Card 3-D Secure * Device registration * Additional KYC or transaction review The issuing bank, account provider, wallet or payment network usually controls the authentication decision. The merchant controls the quality of the handoff. What merchants can improve * Send complete transaction data. * Use reliable redirect and return URLs. * Preserve state during app switching. * Make OTP instructions concise. * Avoid automatic retries that create duplicate challenges. * Use server-side status notifications. * Distinguish canceled, failed, pending, expired and successful events. * Offer a safe recovery path. * Test both same-device and cross-device QR journeys. * Avoid releasing digital goods based only on the browser return page. What merchants cannot guarantee * OTP delivery * Issuer approval * Account balance * International card enablement * Provider uptime * Customer device condition * Additional bank verification * Foreign-exchange permission Error messages should identify the next safe action without making unsupported claims about why a bank or provider declined the transaction.

Recurring payments and subscriptions Pakistan can support subscriptions, but the automatic recurring audience is likely to be smaller than the audience capable of making a one-time account payment. Cards Cards may support: * Tokenization * Card-on-file * Initial authentication * Subsequent recurring charges * Merchant-initiated transactions * Automatic renewal * Failed-payment retries Actual capability depends on issuer, acquirer, scheme, customer enablement, merchant category and foreign-exchange treatment. Raast and account-to-account payments Raast Request to Pay can help a merchant request a customer-initiated payment. It should not be described as an automatic recurring debit unless the selected provider offers a compliant mandate or reusable authorization product. (State Bank of Pakistan) For customers without an automatic payment method, a merchant can offer: * Monthly payment request * Renewal link * Annual account-to-account plan * Invoice reminder * Manual wallet payment * Grace period The product must clearly state that renewal requires customer action. Vertical implications * SaaS: Use cards for supported automatic renewal and bank or Raast payments for annual contracts. * Education: Term-based or monthly customer-initiated payments may be sufficient. * Gaming: Wallets and accounts suit one-time content; memberships require separate recurring validation. * Digital media: Combine card subscriptions with manually renewed passes.

* Professional tools: Annual invoice and bank-transfer plans can reduce dependence on automatic card billing. * Marketplaces: Seller subscriptions and buyer payments may require different payment arrangements. Subscription operating requirements Validate: * Initial authentication * Token or mandate * Amount and frequency limits * Renewal notifications * Failed-payment status * Retry rules * Account updater * Grace period * Cancellation * Refund * Customer support * FX treatment

Refunds, reversals and disputes A payment method should not be considered launch-ready until its refund operation has been tested. Raast refunds Raast P2M includes a process through which a customer can initiate a refund request and the merchant can accept or reject it. The practical experience, timing and reconciliation depend on the participating institutions and merchant integration. (State Bank of Pakistan) Wallet and account refunds For each method, confirm: * Full refunds * Partial refunds * Multiple partial refunds * Refund deadline * Refund funding * Destination account * Customer notification * Provider fee * Failed-refund behavior * Status webhook * Reconciliation reference * Manual exception process Do not assume that returning funds to a bank account manually is equivalent to a linked payment refund. Cards Card payments can involve: * Authorization reversal * Full or partial refund * Chargeback * Retrieval or information request * Fraud claim * Service dispute Merchants need: * Authentication evidence * Order records * Customer communication * Delivery or access evidence * Cancellation history * Refund record * Provider reference Cash on delivery Cash refunds may require: * Bank transfer * Wallet transfer * Courier return * Store credit * Manual customer verification The refund method and expected timing should be disclosed before purchase. Customer communication Every refund confirmation should include: * Refund amount * Original payment method * Initiation date * Expected processing period * Merchant reference

* Support contact “Refund issued” should not appear until the payment provider has accepted the instruction.

Settlement and treasury A successful checkout is not the same as usable merchant funds. The finance chain is: 1. Customer initiates payment. 2. Bank, wallet or provider authenticates it. 3. Merchant receives payment status. 4. Transaction enters settlement. 5. Fees, refunds, withholding, reserves or adjustments are applied. 6. Provider calculates the merchant balance. 7. Funds are paid to the designated account. 8. FX conversion or cross-border transfer occurs. 9. Merchant bank receives the payout. 10. Finance reconciles the payout to transactions. A merchant can achieve high checkout completion and still have an unattractive market if this chain is slow, expensive or manually intensive. Provider questions Confirm: * Customer payment currency * Processing currency * Settlement currency * Payout currency * Settlement schedule * Payout schedule * Domestic-account requirement * Local-entity requirement * Minimum payout * Reserve * Fee deduction * Withholding * FX conversion method * Exchange-rate basis * Refund prefunding * Negative-balance handling * Chargeback deduction * Reconciliation report * Gross and net amounts * Transaction-level settlement reference Foreign-exchange and repatriation Cross-border movement of funds can require an Authorized Dealer bank and documentary compliance under Pakistan’s foreign-exchange framework. A provider’s ability to collect PKR does not automatically establish its ability to pay the merchant internationally. (State Bank of Pakistan) The merchant should map: * Customer

* Payment institution * Acquirer * Settlement account * Tax or withholding deduction * Authorized Dealer bank * FX conversion * International payout * Merchant bank * Refund route before signing the provider contract.

Fraud and risk characteristics Pakistan should not be described as uniformly high risk. Controls should respond to the method, behavior and vertical. Social engineering Customers may be targeted through: * Requests for OTP or PIN * Fake merchant-support calls * False refund messages * Payment links impersonating a trusted business * Compromised accounts * False payment screenshots The merchant should clearly state that employees will not ask for a PIN, password or OTP. Account takeover Gaming, digital media, marketplaces and stored customer balances can face: * Credential reuse * SIM-related attacks * Device compromise * Social engineering * Session theft Useful controls include: * Device and account history * Step-up verification for sensitive changes * Velocity checks * Secure recovery * Notification of new devices * Payout holds after account changes False payment confirmation For bank and account transfers, fulfilment should be triggered by: * Provider API * Bank status * Server notification * Reconciled settlement event not by: * Screenshot * Customer email * Browser message alone * Unverified transaction ID Marketplace fraud Marketplaces should address: * Fake sellers * Non-delivery * Counterfeit or prohibited products * Buyer–seller collusion * Multiple accounts * Account takeover * Refund manipulation * Fraudulent beneficiary accounts * Cash-on-delivery refusal * Payout before complaint risk Seller due diligence, delayed payout and evidence management may be as important as checkout fraud screening.

Digital-goods and gaming risk The speed of delivery increases the importance of: * Authentication * Device history * Account age * Consumption evidence * Velocity * Purchase limits * Refund rules * Customer-support records

Provider and operating-model options Global PSP Best suited to: * International cards * Reusable multi-country integration * Centralized reporting * Global subscriptions Potential limitations: * Local account coverage * Raast * PKR settlement * Domestic acquiring * Merchant eligibility Local gateway, PSO or PSP Best suited to: * Local connectivity * Ecommerce integration * Domestic institutions * QR or Raast access * Local support Potential limitations: * A gateway or PSO/PSP may not itself hold funds or provide acquiring. * International merchant contracting may be restricted. * Settlement may require another licensed institution. Bank or acquirer Best suited to: * Domestic cards * PayPak * Merchant acquiring * Bank settlement * Raast P2M * Local treasury Potential limitations: * Local contracting * Due diligence * Technical integration * Merchant-category restrictions * Minimum scale Branchless-banking provider or EMI Best suited to: * Mobile accounts * Wallet access * QR payment * Broad domestic reach * Lower-value transactions Potential limitations: * Direct international merchant eligibility * Recurring payment * Cross-border payout * Separate reconciliation * Method-specific refund processes Merchant of Record Best suited to: * Merchants seeking a provider to contract with customers and assume selected payment, tax or compliance responsibilities Potential limitations: * Higher commercial cost * Reduced control * Restricted products * Provider-dependent settlement * Provider refund and customer-service policies

Payment orchestration Best suited to: * Multiple providers * Method routing * Standardized payment statuses * Failover * Central reporting * Regional expansion Orchestration cannot create regulatory eligibility or settlement rights that the underlying providers do not possess.

Payment strategy by merchant vertical Vertical Typical transaction Priority payment capability Main operating risk Launch recommendation Education Course, exam, application and tuition payments Mobile account, Raast, cards and bank transfer Incorrect student matching, access-before-payment and partial refund Use unique payer or student references Freelance and professional tools Monthly or annual software, training and services Cards, Raast, bank transfer Cross-border eligibility and renewal Offer PKR annual payment and card subscription SaaS Recurring individual or business payment Cards plus invoice or account-to-account alternative Narrow recurring-card coverage and FX Validate tokenized recurring payments before acquisition Marketplaces Buyer collection and seller payout Raast, mobile accounts, cards, bank transfer and selected COD Seller fraud, fund custody, withholding and refunds Resolve regulated fund flow before scaling sellers Gaming Frequent low- and medium-value digital purchases Mobile account, Raast and cards Account takeover, instant fulfilment and refund abuse Begin with one-time payments and add recurring separately Digital media Passes and subscriptions Cards, account payment and request-to-pay Renewal friction and customer churn Offer both automatic and customer-initiated plans B2B commerce Invoice and higher-value payment Structured bank transfer and Raast Reconciliation, tax and approval workflows Prioritize references and finance-system integration On-demand services

Frequent lower-value transactions Mobile account, QR, Raast and cards Cancellation, duplicate payment and service dispute Optimize mobile return and rapid refund status

Payment-performance measurement Do not use one blended Pakistan payment-success figure. Metric Recommended denominator Payment-method visibility rate Eligible checkouts where the method appeared ÷ eligible checkout sessions Selection rate Method selections ÷ checkouts where the method appeared Initiation rate Initiated payment attempts ÷ method selections Authentication success Successful authentications ÷ authentication attempts Payment completion rate Confirmed payments ÷ initiated attempts Card authorization rate Approved card authorizations ÷ submitted card authorizations Pending-payment rate Attempts remaining pending beyond the expected period ÷ initiated attempts Technical-error rate Technical failures ÷ initiated attempts Completed-order rate Paid and accepted orders ÷ checkout sessions Delivered-order rate Delivered orders ÷ dispatched physical-goods orders Refund rate Refunded transactions ÷ successful transactions Chargeback rate Chargebacks ÷ settled card transactions Fraud-loss rate Confirmed fraud loss ÷ settled payment value Cost per successful payment Total payment cost ÷ successful payments Cost per completed order Payment, fraud, support and fulfilment cost ÷ completed orders Settlement delay Time from payment confirmation to usable merchant funds Reconciliation-exception rate Unmatched transactions or adjustments ÷ reportable transactions Support-contact rate Payment-related support cases ÷ payment attempts Retained revenue

Collected revenue minus refunds, chargebacks, fraud, tax deductions and unrecovered costs Segment results by: * Payment method * Provider * Issuer * Bank or wallet * Domestic versus international card * Device * Operating system * New versus returning customer * Customer location * Currency * Order value * Authentication result * Product * Vertical * Checkout version For cash on delivery, measure order submission, confirmation, dispatch, delivery attempt, successful collection, return and final retained revenue separately.

Launch recommendations by merchant stage Merchant testing demand Start with: * PKR pricing * One well-integrated account, wallet or Raast route * Cards * Structured bank transfer where order value justifies it * Cash on delivery only for appropriate physical goods * Limited product range * Defined customer segment * Manual but controlled reconciliation * Clear completion and retained-revenue targets The test must establish whether customers can pay—not merely whether they click an advertisement. Merchant launching nationally Add: * Broader local account coverage * Automated payment-status notifications * Reliable pending-payment handling * Full and partial refund testing * Localized support * Documented settlement and FX routes * Tax review * Device and bandwidth testing * Fraud controls * Formal reconciliation Merchant scaling volume Investigate: * Domestic acquiring * PayPak * Additional Raast or QR coverage * Provider routing * Provider failover * Cost per completed order * Reserve negotiation * Treasury optimization * Automated finance reporting * Local operations support Merchant optimizing performance Focus on: * Method ordering * Account- and wallet-specific abandonment * QR completion * Bank and issuer segmentation * OTP failure * App-switch loss * Pending-payment recovery * Duplicate prevention * Returning customers * Refund contact rate * Settlement exceptions Merchant introducing subscriptions Validate: * International and domestic card eligibility * Tokenization * Merchant-initiated charging * Initial authentication

* Request-to-pay * Manual renewal * Failed-payment recovery * Grace period * Notifications * Cancellation * Refund * FX compliance Merchant expanding regionally Separate reusable components from Pakistan-specific components. Reusable: * Payment-state model * Provider abstraction * Tokenization * Fraud data * Reconciliation engine * Reporting * Support workflow Pakistan-specific: * Raast * PKR * Branchless-banking access * PayPak * Local merchant acquiring * Foreign-exchange rules * Ecommerce tax and withholding * Provider eligibility * Local refund processes

Pakistan launch checklist Commercial opportunity * Confirm demand among customers who can realistically access the product. * Estimate pricing and retained margin in PKR. * Separate mobile-account, banked, card-capable and cash-dependent segments. * Confirm product and merchant-category eligibility. * Identify whether the opportunity is one-time, recurring, B2C or B2B. Payment access * Offer a commercially relevant account, wallet or Raast payment route. * Add cards for appropriate domestic and international customers. * Add structured bank transfer for high-value or business payments. * Validate PayPak support where relevant. * Use cash on delivery only when fulfilment economics support it. * Confirm which methods work for recurring payment. Provider and contracting * Confirm that provider coverage includes the merchant’s exact category. * Identify the licensed institution holding or settling funds. * Determine whether a local entity is required. * Determine whether a local bank account is required. * Confirm merchant onboarding and KYC requirements. * Confirm production—not merely test—access. * Review service levels, reserves and termination rights. Currency and settlement * Present PKR where appropriate. * Document processing, settlement and payout currencies. * Confirm the Authorized Dealer and FX route. * Confirm payout timing and minimums. * Confirm fees, withholding and reserves. * Validate repatriation and usable-funds access. * Test transaction-to-payout reconciliation. Regulation and tax

* Review payment-system and merchant-acquiring requirements. * Review foreign-exchange rules. * Review federal and provincial tax treatment. * Review payment-intermediary and courier withholding. * Define marketplace and seller responsibilities. * Obtain legal and tax review before production. Checkout and authentication * Prioritize mobile performance. * Localize essential instructions in English and Urdu where appropriate. * Test OTP, redirects, app switching and QR. * Preserve the basket during account funding. * Handle pending, late and expired payments. * Prevent duplicate orders. * Use server-side confirmation before fulfilment. Refunds, fraud and support * Test full and partial refunds. * Test failed and delayed refunds. * Document card dispute procedures. * Prepare for false payment screenshots. * Protect customers from PIN and OTP phishing. * Prepare account-takeover controls. * Prepare marketplace seller controls where relevant. * Establish local-method support escalation. Measurement * Define the denominator for every metric. * Segment results by method, provider, issuer, device and cohort. * Measure retained revenue rather than checkout orders alone. * Assign owners across product, payments, finance, tax, fraud and support. * Establish a formal post-launch review date.

Final merchant recommendation Pakistan should be prioritized by merchants whose products match its expanding mobile, account-based and digital-services economy and whose operating model can support local payment access without losing control of settlement. The strongest fits include: * Education and skills platforms * Freelance and professional tools * SaaS * Marketplaces with mature seller and fund-flow operations * Gaming * Digital media * On-demand services * B2B platforms A first Pakistan payment release should generally include: 1. PKR pricing 2. A well-integrated mobile-account, wallet or Raast payment route 3. Cards for customers able to use them 4. Structured bank transfer for higher-value, education or B2B transactions 5. Cash on delivery only where physical-goods economics justify it 6. A verified refund, reconciliation and settlement operation Before committing significant acquisition, product or engineering resources, the merchant must validate: * Exact merchant eligibility * Local-method production access * Card and recurring-payment coverage * Local entity and bank-account requirements * Foreign-exchange treatment * Settlement and international payout * Tax and withholding * Refund capability * Reconciliation * Fraud controls * Customer support

Pakistan’s digital demand is not limited by a lack of connected customers. It is limited by the number of customers whose available accounts, devices and payment methods can be connected to a merchant’s checkout—and by whether the resulting funds can complete the journey from customer payment to usable merchant settlement. The merchants most likely to succeed will design that complete journey before they begin paying to generate demand. The publication and optimization package follows.

The supplied brief lists Pakistan as the world’s 42nd-largest economy. Current 2025 nominal-GDP datasets place it closer to the mid-40s, depending on the countries and territories included, so the draft uses a verified value and flags the exact rank for publication-day recalculation. The article follows the brief’s access-to-settlement structure and merchant-first editorial position.

Editorial recommendations package SEO recommendations Title options 1. Payments in Pakistan: Mobile Accounts, Raast and Merchant Strategy 2. Payment Methods in Pakistan: A Guide for International Merchants 3. Accepting Payments in Pakistan: Raast, Cards, Wallets and Bank Transfers 4. Pakistan Payments Guide: Local Methods, Settlement and Regulation 5. Ecommerce Payments in Pakistan: Access, FX and Merchant Readiness Recommended SEO title Payment Methods in Pakistan: Merchant Guide 2026 Recommended H1 Payments in Pakistan: Mobile Accounts, Bank Transfers, and Emerging Digital Demand Meta description Understand payment methods in Pakistan, including Raast, mobile accounts, bank transfers, cards, PKR settlement, refunds, tax and foreign exchange. URL slug /payments-in-pakistan/ Primary keyword payment methods in Pakistan Secondary keywords * Payments in Pakistan * Pakistan payment gateway * Accept payments in Pakistan * Raast payments * Pakistan mobile wallets * Bank transfers in Pakistan * Pakistan ecommerce payments * PayPak payments * Pakistan local acquiring * Pakistan digital payments * PKR payment processing * Pakistan payment regulations Related entities * State Bank of Pakistan * Pakistani rupee * PKR * Raast * Raast P2M * PayPak * Branchless banking * Electronic money institutions * Payment-system operators * Payment-service providers * Authorized Dealer banks * Foreign Exchange Manual * Federal Board of Revenue * Payment Systems and Electronic Fund Transfers Act 2007 * QR payments * Request to Pay Search intent

The primary intent is commercial investigation supported by operational research. The reader is likely evaluating: * Whether Pakistan is commercially attractive * Which local payment methods matter * How Raast can be used * Whether card acceptance is sufficient * How to process in PKR * Whether local acquiring is required * How settlement and foreign exchange work * Which provider model can support entry * What tax and regulatory constraints apply Article excerpt Pakistan has more than 130 million mobile-app and wallet registrations, an expanding Raast network and growing digital-services activity. But mobile connectivity does not guarantee access to an internationally enabled card—or a workable merchant settlement route. This guide explains the complete payment chain from customer access through refunds, FX and usable merchant funds. Social description A Pakistani customer may have a smartphone, money in a mobile account and strong intent to buy—but still be excluded by a card-only checkout. Here is how Raast, mobile accounts, bank transfers, cards, FX and settlement shape the real merchant opportunity.

Internal-link recommendations

* Global market expansion * Local payment methods * Account-to-account payments * Mobile wallets * How payment gateways work * Local acquiring versus cross-border acquiring * Payment authorization versus conversion * Improving payment authorization rates * Why payments are declined * Payment orchestration * Merchant of Record services * Payments for gaming * Payments for education platforms * Marketplace payment operations * SaaS and recurring payments * Subscription-payment recovery * Refunds and reversals * Payment reconciliation * Cross-border settlement * Global Payments Atlas * South Asia payment markets The article should also link to any future dedicated pages explaining Raast, PayPak and account-to-account payments.

Authoritative external-source recommendations Maintain citations to: * State Bank of Pakistan quarterly Payment Systems Reviews for current transaction, card, QR, Raast and merchant-acceptance data. (State Bank of Pakistan) * State Bank branchless-banking statistics for account, transaction and agent-network data. (State Bank of Pakistan) * State Bank Raast documentation for scheme functionality, Request to Pay, refunds and participant obligations. (State Bank of Pakistan) * Pakistan Economic Survey for ICT exports, freelancer receipts, telecommunications and device indicators. * World Bank data for internationally comparable GDP, population and per-capita indicators. (World Bank Open Data) * State Bank laws, regulations and foreign-exchange material for licensing, settlement and cross-border requirements. (State Bank of Pakistan) * Federal Board of Revenue legislation and circulars for current ecommerce, withholding and sales-tax treatment. (Federal Board of Revenue) Provider marketing pages should not be used as the sole evidence for regulatory eligibility, production access, refund functionality or settlement.

Structured-data recommendation Use: * Article or BlogPosting * BreadcrumbList * FAQPage after adding a visible FAQ section * ImageObject for the hero and diagrams * DefinedTerm or clearly marked explanatory content for Raast, PayPak and branchless banking where useful Recommended Article properties include: * Headline * Description * Author * ReviewedBy * DatePublished * DateModified * Publisher * MainEntityOfPage * About * Mentions * Citation * Image Do not put figures in structured data that do not appear visibly in the article.

Original asset recommendations Asset 1: Pakistan’s access-to-settlement failure chain Purpose: Demonstrate that a payment can fail before checkout access, during authentication, during confirmation, during refund or after settlement. Intended reader: Executives, payment teams, product leaders and market-entry teams. Data required: * Customer payment-access categories * Method-initiation options * Authentication steps * Merchant confirmation states * Settlement participants * FX and payout process * Refund route Recommended format: Horizontal seven-stage flow with a customer on the left and usable merchant funds on the right. Recommended placement: Directly after the country payment snapshot. Suggested caption: “A Pakistan payment launch can fail at seven separate handoffs—even when the customer has sufficient funds and clear purchase intent.”

Asset 2: Pakistan payment-method portfolio scorecard Purpose: Compare Raast, mobile accounts, bank transfer, cards, PayPak, QR and cash on delivery by merchant vertical. Intended reader: Product, payments, finance and commercial teams. Data required: * Customer reach * One-time suitability * Recurring support * Refund support * Typical value * Mobile experience * Merchant eligibility * Settlement complexity * Operating burden Recommended format: Color-coded matrix with categories such as launch essential, high-value addition, segment-specific and optional. Recommended placement: Adjacent to the payment-method priority matrix. Suggested caption: “Raast may be essential for education and marketplaces, while cards remain more important for internationally oriented SaaS and automatic subscriptions.”

Asset 3: PKR collection-to-international-payout map Purpose: Clarify that customer payment, merchant settlement, FX conversion and international payout can involve different institutions. Intended reader: Finance, treasury, compliance, legal and executive stakeholders. Data required: * Customer account * Raast, card or wallet rail * Acquirer or provider * Settlement account * Tax or withholding * Authorized Dealer bank * FX conversion * Merchant payout account * Refund direction Recommended format: Two-direction flow-of-funds diagram, with the refund path shown separately. Recommended placement: In the settlement and treasury section. Suggested caption: “A successful PKR payment and a usable international merchant payout are separate operating events.”

Visual recommendations Hero image concept Show a mobile customer facing a card-only checkout. Behind the blocked card path, reveal several accessible routes: * Mobile account * Raast transfer * QR payment * Bank transfer * Agent-assisted funding On the merchant side, show payment confirmation continuing through settlement, foreign exchange and payout. Avoid: * Generic flag graphics * Islamabad or Karachi skyline imagery * Oversized credit cards * Currency piles * An image implying that every mobile user has a digital wallet Hero caption: “In Pakistan, digital demand can reach the checkout before the customer gains access to the payment method the merchant expects.” Hero alt text: “Illustration of a Pakistani mobile customer moving from a card-only checkout to Raast, mobile-account, QR and bank-transfer payment options connected to merchant settlement.” Diagram concept Title: Where a Pakistan Payment Can Fail Show: Customer intent → device → payment access → authentication → confirmation → fulfilment → refund → PKR settlement → FX → merchant payout. Each arrow should include the party responsible for the handoff. Alt text: “Flowchart showing customer, provider, bank, merchant and settlement handoffs in a Pakistan online payment.” Chart concept Title: Digital Access Is Broader Than Credit-Card Access Compare: * Branchless-banking accounts * App and wallet registrations * Branchless-banking mobile-app users * Total payment cards * Debit cards * Credit cards * QR-enabled merchants

The chart must state that accounts, registrations and cards are not unique individuals. Alt text: “Comparison of Pakistan mobile accounts, app registrations, debit cards, credit cards and QR-enabled merchants.” Map concept A map is useful only if supported by credible regional data showing: * Broadband access * Account participation * merchant density * ecommerce activity * agent coverage * delivery reach Do not use an unsupported province-level market-attractiveness score. Suggested caption: “National account and connectivity totals can conceal significant differences in customer access, merchant acceptance and logistics across Pakistan.”

Human review and contribution recommendations Required before publication Pakistan payments specialist Review: * Raast terminology and use cases * Branchless-banking interpretation * Local method priority * Merchant-acquiring practices * Provider accessibility * Customer behavior Pakistan payments-law or regulatory reviewer Review: * Payment Systems and Electronic Fund Transfers Act * EMI, PSO and PSP descriptions * Merchant-acquiring requirements * Raast participant obligations * Marketplace fund flow * Local entity requirements Pakistan tax adviser Review: * Federal and provincial jurisdiction * Goods versus services * Digitally delivered services * Ecommerce withholding * Courier and cash-on-delivery treatment * Invoicing * Marketplace and Merchant of Record responsibilities Treasury and foreign-exchange specialist Review: * Authorized Dealer role * PKR settlement * Payout currency * Conversion * Repatriation * Reserves * Documentation * Refund treatment Strongly recommended Payment product specialist Review: * Raast ecommerce availability * Request-to-pay behavior * Card and PayPak support * Tokenization * Recurring payments * Provider APIs * Refund capability Operations and reconciliation specialist Review: * Pending payments * Late payments * Duplicate prevention * Provider reporting * Settlement files * Refund matching * Manual exceptions Fraud specialist Review: * Account takeover * Social engineering * OTP theft * False payment screenshots * Marketplace risk * Gaming and digital-goods controls * Refund abuse Optional enhancement

Local education, SaaS or gaming merchant Contribute a first-hand implementation observation about: * Method selection * Customer-initiated renewal * OTP or app-switching friction * Refund expectations * Customer support * Transaction-value economics Marketplace operator Contribute an approved lesson concerning: * Seller onboarding * Cash on delivery * Payout timing * Tax withholding * Dispute management * Raast reconciliation Local bank or payment-method specialist Contribute a technical explanation of: * Raast P2M onboarding * Request to Pay * Refund processing * Settlement references * Merchant QR use The article must not imply that any proposed reviewer or contributor has already participated.

Final fact-check recommendations Verify immediately before publication: 1. Pakistan’s nominal GDP year and value. 2. The exact global nominal-GDP rank generated from the selected dataset. 3. Whether the brief’s 42nd-place ranking should be replaced. 4. Population estimate and official-census distinction. 5. GDP-per-capita value. 6. Sector shares of GDP. 7. Total formal retail-payment volume and value. 8. Digital-channel share by volume and value. 9. App and wallet registration totals. 10. Bank-account total and mobile-linkage percentage. 11. Branchless-banking account and agent totals. 12. Active branchless-banking accounts, if added. 13. Branchless-banking gender distribution. 14. Raast quarterly volume and value. 15. Raast P2P and P2M figures. 16. QR-enabled merchant count. 17. Raast refund and Request-to-Pay functionality. 18. Debit-, credit-, prepaid- and welfare-card totals. 19. Domestic and foreign-card ecommerce figures. 20. Account- and wallet-based online-purchase figures. 21. PayPak ecommerce and co-badged international availability. 22. Telecommunications and broadband subscriptions. 23. Smartphone share and its precise device-based definition. 24. ICT export value and reporting period. 25. Freelancer-remittance value and growth. 26. Number of registered IT and IT-enabled-services companies. 27. Current list and status of licensed banks, EMIs, PSOs and PSPs. 28. Merchant-acquiring and KYC requirements. 29. Local-entity and bank-account requirements by provider.

30. Provider support for Raast, PayPak and local accounts. 31. Provider support for full and partial refunds. 32. Recurring-payment and tokenization capability. 33. Foreign-exchange limits and Authorized Dealer procedures. 34. PKR settlement and international payout availability. 35. Federal and provincial tax treatment. 36. Ecommerce withholding and courier obligations. 37. Marketplace and Merchant of Record responsibilities. 38. Settlement timing, reserves and payout deductions. 39. Education, SaaS, gaming and marketplace opportunity claims.