Payments in Bangladesh: Mobile Financial Services and a Large Emerging Digital Market Bangladesh is a large economy, but its commercially reachable payment market cannot be measured by card ownership alone. Using the IMF’s April 2026 World Economic Outlook estimates, Bangladesh generated approximately $458 billion in nominal GDP in 2025, placing it around 37th among the world’s economies by nominal output. Its population was approximately 175.7 million. Together, those figures create substantial potential transaction volume, even though average purchasing power remains considerably lower than in mature ecommerce markets. (IMF Data) The more revealing statistic is found in the country’s mobile financial-service infrastructure. By December 2025, Bangladesh had approximately 250.2 million registered mobile financial-service accounts, but only 76.9 million were classified as active. Registered accounts are not equivalent to unique customers: people may hold multiple accounts, and many registrations are inactive. Cash-in, cash-out, and person-to-person transfers still represented more than 85% of mobile financial-service activity.
That combination explains Bangladesh’s payment environment. Digital value frequently begins or ends as cash. A customer may deposit money through an agent, store it in a mobile account, use a wallet to pay a merchant, receive a remittance, scan an interoperable QR code, or withdraw the remaining balance. Cards, bank transfers, mobile wallets, agents, cash networks, and licensed providers therefore operate as parts of one connected system rather than as separate customer segments. For international merchants, the central question is not simply whether online payments are growing. It is whether the merchant can connect with customers at the appropriate point on this customer-access ladder, while also managing merchant eligibility, settlement, refunds, foreign exchange, reconciliation, and customer support. The practical conclusion is clear: Merchants entering Bangladesh should prioritize access to mobile financial services and operationally viable local payment flows before assuming that an imported card-led checkout will reach the full addressable market.
Bangladesh payment snapshot Category Bangladesh market profile Region South Asia Population Approximately 175.7 million in 2025. (World Bank Open Data) Currency Bangladeshi taka, code BDT, commonly displayed with the symbol ৳ Nominal GDP Approximately $457.9 billion in 2025 using the IMF April 2026 estimate Global economic rank Approximately 37th by 2025 nominal GDP when the IMF country estimates are ranked globally. (IMF Data) GDP per capita Approximately $2,636 in the IMF’s 2025 estimate Economic structure Services generate slightly more than half of output, with industry accounting for roughly another third. (World Bank Open Data) Digital-maturity position Large mobile footprint and extensive mobile financial-service infrastructure, but material gaps remain in account ownership, internet use, ecommerce adoption, and active wallet use Mobile financial services Approximately 250.2 million registered accounts and 76.9 million active accounts in December 2025. Cards Approximately 44.1 million debit cards, 3.0 million credit cards, and 9.8 million prepaid cards had been issued by July 2025. These are cards issued, not unique cardholders. Dominant payment categories Cash and cash on delivery, mobile financial services, bank transfers, and cards Important local methods Mobile financial-service wallets such as bKash, Nagad, Rocket, and Upay; Bangla QR; domestic bank-transfer rails; and the developing TakaPay card scheme Mobile-commerce relevance
Very high for addressable digital customers, although mobile use should not be confused with universal internet or wallet access Recurring-payment readiness Moderate for cards; provider- and integration-specific for wallets and local methods Local-acquiring relevance Potentially useful for cards and essential to many local-method arrangements, but entity, account, merchant-category, and contract requirements vary Regulatory complexity Material because payment licensing, merchant acquiring, escrow, foreign exchange, cross-border processing, tax, and settlement rules interact Strong merchant opportunities Education, marketplaces, digital services, gaming, fashion and retail, freelance or creator services, on-demand platforms, and B2B commerce Primary takeaway Build for a customer journey that can move from cash to a mobile account and then into digital commerce—not for a card-only customer model
Why Bangladesh matters to international merchants Bangladesh combines a large population, a sizeable manufacturing and services economy, and an expanding digital-payment infrastructure. Services represented approximately 52% of GDP in 2025, while the country also retains a substantial industrial and export base. This creates opportunities in both consumer commerce and business payments. (World Bank) Its scale, however, should not be confused with high average transaction value. GDP per capita remains relatively low, price sensitivity is material, and the near-term economy has faced elevated inflation, banking-sector pressure, and foreign-exchange constraints. Merchants should therefore evaluate expected order values, payment costs, refund economics, and customer-acquisition expenses rather than treating the population figure as a direct measure of commercial demand. (World Bank Open Data) The opportunity is strongest for businesses that can serve a large number of mobile-connected customers with appropriately priced products or services. It is less straightforward for merchants whose business model depends on high credit-card penetration, seamless international recurring billing, or unrestricted cross-border settlement. Bangladesh should consequently be assessed as a large, layered-access market: 1. Some customers remain primarily dependent on cash. 2. Some use agents to move cash into and out of mobile accounts.
3. Some use mobile financial services for transfers but not yet for frequent merchant payments. 4. Some are comfortable paying merchants with wallets, QR codes, bank transfers, or cards. 5. A narrower segment can make international card payments or maintain recurring digital subscriptions. 6. Businesses may use bank-based rails even when their customers rely on wallets or cash. The merchant’s addressable market grows as the checkout supports more of this ladder—but every additional payment layer also adds contracting, reconciliation, refund, support, and settlement requirements.
Bangladesh’s digital-economy maturity No single percentage adequately describes the digital economy A current, official, methodologically comparable estimate for “the digital economy as a percentage of Bangladesh’s GDP” was not identified in the sources reviewed for this guide. That omission matters because several measurements are commonly—and incorrectly—treated as interchangeable: * ICT-sector output * Internet use * Ecommerce revenue * Mobile-broadband subscriptions * Account ownership * Mobile-wallet registrations * Digital-payment transaction value * Digitally enabled activity in otherwise traditional industries These indicators describe different parts of the economy. A more reliable assessment of Bangladesh therefore uses a digital-maturity profile rather than an invented single percentage. Connectivity and account access World Bank Global Findex 2024 country data indicate that approximately 43.3% of Bangladeshi adults had an account at a financial institution or mobile-money provider. Approximately 32.9% had a financial-institution account, while about 20.8% had a mobile-money account. The same dataset indicates that approximately 82.4% of adults owned a mobile phone and around 40.4% had used the internet within the relevant survey period. These figures apply to adults and should not be compared directly with total population, SIM-registration, or wallet-registration figures. (World Bank)
The International Telecommunication Union reported approximately 56.5 active mobile-broadband subscriptions per 100 people in 2024. A subscription is not the same as a unique internet user: customers can hold multiple subscriptions, share devices, or maintain a connection without using ecommerce. (ITU Data Hub) Official household research also suggests that online purchasing remains far from universal. Reporting based on the Bangladesh Bureau of Statistics’ 2024–25 ICT survey indicated that approximately 14.4% of individuals had used the internet to purchase goods or services online, with substantially higher participation in Dhaka than in some other divisions. (BSS) These measures describe a country with meaningful digital demand but considerable room for further adoption. They also show why mobile access, financial inclusion, and ecommerce readiness must be treated separately. Mobile financial services are infrastructure, not merely a checkout option Bangladesh Bank reported approximately 250 million registered mobile financial-service accounts, approximately two million agents, and a 71.5% annual increase in remittance inflows through mobile financial-service channels during 2025. The agent network allows customers to convert between cash and stored digital value, making mobile financial services part of the country’s broader access infrastructure.
That infrastructure does not mean that every wallet user is ready to make online merchant payments. Cash-in, cash-out, and person-to-person transfers continue to dominate transaction flows. Merchants should therefore distinguish among: * Registered accounts * Active accounts * Customers who use a wallet for transfers * Customers who use it for merchant payments * Customers willing to pay an unfamiliar online merchant * Customers who can complete a recurring or cross-border transaction The distinction changes market sizing, payment-method ordering, and conversion expectations.
The customer-access ladder: from cash to mobile commerce The most useful way to understand Bangladesh is to follow how customers gain access to digital value. Level 1: Cash and cash on delivery Cash remains embedded in ecommerce. The current International Trade Administration guide to Bangladesh characterizes cash on delivery as a dominant ecommerce payment behavior, even as cards and mobile financial services gain ground. (Trade.gov) For physical-goods merchants, cash on delivery can increase the number of customers who are able or willing to place an order. It also introduces substantial operating costs: * Failed delivery attempts * Customers refusing orders * Inventory held during delivery * Cash-handling and courier reconciliation * Longer access to funds * Fraudulent or unserious orders * Difficult partial refunds * Inconsistent proof of delivery * Additional customer-service contacts Cash on delivery can be commercially important without being economically attractive. Merchants should measure completed, paid, non-returned orders, not only checkout orders. For digital goods, gaming, SaaS, and most education services delivered immediately, cash on delivery is generally unsuitable. These merchants need a bridge from the cash economy into an instant digital payment method—most commonly a mobile financial-service account funded through an agent. Level 2: Agent-assisted mobile financial services
Mobile financial services allow a customer to deposit cash with an agent, receive value into a mobile account, and then transfer or spend it digitally. Bangladesh Bank’s licensed-provider list includes services such as bKash, Nagad, Rocket, Upay, MYCash, mCash, TAP, First Pay, OK Banking, Rupali Cash, TeleCash, Islamic Wallet, and others. Merchant access, supported transaction types, commercial terms, refund functions, and eligibility differ by provider and integration model. A typical merchant-payment journey may involve: 1. The customer selects a mobile financial-service method. 2. The checkout requests a mobile number, opens a provider page, displays a QR code, or deep-links into an app. 3. The customer authenticates with a PIN, OTP, or in-app approval. 4. The payment provider confirms the transaction. 5. The merchant receives a payment notification. 6. The provider later settles or pays out funds according to the merchant agreement. Merchants must test each of these steps. A successful customer debit does not automatically prove that the merchant has received final confirmation, that the order-management system has recorded the correct payment, or that funds will appear in the next merchant payout. Level 3: Merchant payments and interoperable QR Mobile financial-service merchant payments are now substantial. Bangladesh Bank’s 2025 data show monthly merchant-payment volumes regularly exceeding 40 million transactions, with monthly transaction values often above BDT 60 billion.
Bangla QR adds an interoperable layer. As of December 31, 2025, Bangladesh Bank reported participation by 46 banks, seven mobile financial-service providers, and four payment-service providers, with approximately 963,000 merchants. Interoperability through the National Payment Switch allows participating customers to scan one standardized merchant QR using supported bank, MFS, or PSP applications. Bangladesh Bank also introduced instant settlement for Bangla QR transactions in December 2025. Merchants should still distinguish network-level settlement from the payout, reserve, deduction, and reporting terms applied by their particular provider. Bangla QR is especially relevant to: * Omnichannel retailers * Educational institutions * Restaurants and on-demand services * Marketplaces with physical sellers * Events and ticketing * Small local merchants * Businesses collecting in-person or payment-on-delivery amounts It is not automatically a replacement for an online-wallet integration. A web merchant must confirm how a desktop or mobile customer receives the QR, changes devices if necessary, returns to checkout, and receives payment confirmation. Level 4: Bank transfers and formal account-to-account payments Bangladesh’s payment infrastructure includes the National Payment Switch, electronic funds-transfer systems, and real-time gross settlement.
Bangladesh Bank’s 2025 report states that electronic funds transfers accounted for approximately 55% of transaction volume across the reported banking rails, while RTGS represented approximately 66% of transaction value. This reflects the different purposes of the systems: bulk and retail transfers can generate high volume, while RTGS is designed for higher-value payments. Bank-based payments can be particularly useful for: * B2B invoices * Tuition and education payments * High-value purchases * Marketplace seller funding or payouts * Professional services * Government or institutional collections * Customers uncomfortable entering card details The primary operational problem is reconciliation. Merchants need a reliable reference number, virtual account, payment request, or provider-generated identifier. Asking customers to make an unstructured transfer and send a screenshot creates manual work and weakens payment verification. Level 5: Cards Cards remain important but should not be treated as universally available. By July 2025, Bangladesh Bank reported approximately: * 44.1 million issued debit cards * 3.0 million issued credit cards * 9.8 million issued prepaid cards Prepaid-card issuance had expanded particularly quickly. These figures measure cards issued, not unique people, active cards, online-enabled cards, or cards capable of international ecommerce transactions. Merchants must distinguish among: * Ownership of a domestic debit card * Use of that card at an ATM
* Use at a local point of sale * Domestic online-payment capability * International online-payment capability * Availability of sufficient foreign-exchange allowance * Support for recurring or card-on-file transactions International card schemes are present, and the Bangladesh Bank card report identified Visa as the leading network across several July 2025 usage categories. Bangladesh is also developing the domestic TakaPay scheme, which Bangladesh Bank reported as available through 17 banks in 2025. (BB.org.bd) Cards are especially valuable for: * Internationally experienced customers * Higher-income urban consumers * Travel and cross-border services * SaaS and subscriptions * Digital goods * Customers purchasing without a wallet balance * Returning customers using tokenized credentials However, a card-only launch is likely to exclude customers who have access to mobile financial services but not an appropriate online card.
Payment-method priority matrix The correct priority depends on the merchant’s vertical and transaction model. Payment method Retail and fashion Education Digital services and gaming Marketplaces B2B platforms Merchant classification Major mobile financial-service wallets Launch essential Launch essential Launch essential for one-time payments Launch essential Useful for lower-value collections Essential for broad consumer reach Domestic and international cards High-value addition High-value addition Essential for international customers and many subscriptions High-value addition Segment-specific Important, but insufficient alone Structured bank transfer Useful for higher-value orders Essential for larger tuition payments Segment-specific Important for sellers and larger transactions Launch essential Essential in selected verticals Cash on delivery Often essential while testing physical-goods demand Usually unnecessary Usually unsuitable Important for physical-goods marketplaces Usually unnecessary Segment-specific and operationally costly Bangla QR High-value omnichannel addition High-value addition Segment-specific Useful for local sellers Useful for local collections Strong for merchant-present payments TakaPay and prepaid cards Useful as coverage matures Segment-specific Potentially useful for younger or budget-controlled customers Useful later Segment-specific Monitor provider and issuer coverage Carrier billing Usually unnecessary Usually unnecessary Potential gaming or digital-content niche Usually unnecessary Unnecessary
Only after proven demand and commercial viability Direct debit or automated bank debit Optional Potential use for scheduled fees Potential subscription use if supported Optional Potentially useful Do not assume availability or customer familiarity Buy now, pay later Segment-specific Limited current priority Usually unnecessary Segment-specific Not generally relevant Add only with evidence of demand and viable provider support The matrix should be recalibrated using the merchant’s actual customers. “Launch essential” means essential for the relevant vertical—not that every provider can offer the method to every international merchant.
Ecommerce and future growth prospects A commercial market forecast estimated Bangladesh’s business-to-consumer ecommerce market at approximately $7.4 billion in 2025 and projected growth to approximately $9.7 billion by 2029, representing a forecast compound annual growth rate of about 6.8%. This is a third-party market estimate rather than an official national statistic, and results will depend on definitions, inflation, exchange rates, logistics, consumer confidence, and the treatment of social commerce. (Research and Markets) The more dependable growth thesis is not a single market-size number. It is the interaction of: * A population approaching 176 million * Expanding access to mobile financial services * Increasing wallet merchant-payment activity * QR interoperability * Digital remittance flows * Rising online purchasing from a relatively low base * Growth in services and export-oriented digital work * Increasing formalization of local payment infrastructure Bangladesh Bank reported that mobile financial-service remittance inflows rose 71.5% during 2025. Separately, World Bank data put personal remittances at approximately 6.1% of GDP in 2024. Remittances do not automatically translate into ecommerce spending, but they can place digital value into accounts that customers can subsequently use for transfers, bills, savings, and merchant payments. Merchant verticals with the strongest alignment 1. Education: strong immediate fit
Education is well aligned with Bangladesh’s payment environment because it can combine: * One-time course purchases * Recurring or term-based tuition * Exam and application fees * Digital content * Mobile-first student audiences * Parent-funded payments * Higher-value bank transfers * Lower-value wallet payments Bangladesh Bank specifically identifies tuition and educational collections among the uses of digital-payment channels. An education merchant should offer mobile financial services for accessible one-time payment, cards for international and subscription use, and structured bank transfer for larger amounts. Refund policies and course-access timing must be explicit. 2. Marketplaces: high-growth but operationally complex Marketplaces can benefit from mobile financial services, cash on delivery, bank transfers, and QR payments, but they also inherit seller-onboarding, escrow, delivery, payout, refund, fraud, and tax responsibilities. Bangladesh’s merchant-acquiring and escrow rules are particularly relevant to ecommerce and marketplace models. The rules establish due-diligence and settlement expectations for merchants operating through banks, payment-system operators, payment-service providers, and MFS providers. Marketplaces should not launch until they understand whether the platform, seller, payment provider, or Merchant of Record is responsible for customer funds, refunds, seller verification, and payout reporting.
3. Digital services and freelance platforms: strong strategic opportunity Bangladesh has a substantial base of freelancers, software providers, and export-oriented individual service providers. In July 2026, Bangladesh Bank issued updated rules consolidating foreign-exchange arrangements for freelancers and individual service exporters. This creates opportunities for: * Professional-service platforms * Creator tools * Freelance marketplaces * Software and productivity products * Education and certification services * Business tools for individual exporters The key payment issue is two-sided: collecting from Bangladeshi customers may require local methods, while paying or receiving international service revenue requires compliant foreign-exchange and banking arrangements. 4. Gaming and digital goods: attractive but method-sensitive Gaming is well matched to: * Mobile usage * Low- and medium-value transactions * Prepaid spending behavior * Mobile financial services * One-time virtual-item purchases * Younger digital customers The main limitations are recurring-payment support, age and identity considerations, merchant-category eligibility, fraud, refund policy, and foreign-exchange treatment. Gaming merchants should test wallet completion rates, low-value transaction economics, account-takeover controls, and customer-support volumes before investing heavily in broad acquisition. 5. Fashion and retail ecommerce: large potential, difficult fulfillment
Fashion and other retail categories can benefit from a large population, mobile discovery, social commerce, wallets, and cash on delivery. The difficulty lies beyond checkout: * Address accuracy * Delivery coverage * Return rates * Cash handling * Size-related returns * Failed delivery * Reverse logistics * Refund timing For these merchants, the most useful conversion metric is not the order-submission rate. It is the percentage of checkout sessions that become paid, delivered, non-returned orders. 6. B2B commerce: attractive for formal payment flows Bangladesh’s industrial, trading, and services sectors create demand for: * Supplier platforms * Procurement tools * Software * Logistics * Business services * Invoice collection * Seller and contractor payments Bank transfers, structured payment references, local settlement, invoicing, and reconciliation matter more than consumer-wallet breadth for many B2B businesses. RTGS and electronic funds-transfer infrastructure can support higher-value and institutional transactions, subject to provider access and bank procedures.
Card-market characteristics Debit is much larger than credit Bangladesh Bank’s issued-card data show that debit cards substantially outnumber credit cards. This reinforces the need to distinguish access to a bank account from access to consumer credit. It also means that merchants should not build pricing, subscriptions, or retry logic around assumptions imported from credit-heavy markets. International capability is a separate question A domestic card may not be enabled for every international transaction. Foreign-exchange controls, issuer policies, customer documentation, transaction purpose, available limits, and merchant category can affect whether a cross-border payment can be completed. Merchants should segment card performance by: * Domestic versus foreign issuer * Domestic versus cross-border processing * Debit, credit, and prepaid * Card scheme * Issuer * Transaction currency * Merchant category * One-time versus recurring * New versus returning customer * 3-D Secure outcome * Device and checkout version A blended authorization rate can hide a strong domestic portfolio and a weak cross-border one—or the reverse. Domestic processing may help, but it is not a guarantee Local acquiring may: * Improve domestic routing * Allow BDT settlement * Reduce some cross-border fees * Improve issuer recognition * Provide access to domestic schemes * Support local-method contracting
The commercial result depends on issuer behavior, acquirer performance, merchant category, transaction mix, fraud profile, technical configuration, and contract terms. Merchants should test local and cross-border processing rather than promising a predetermined authorization increase. TakaPay is an infrastructure development to monitor TakaPay is Bangladesh’s domestic card scheme. Its expansion could reduce dependence on international card networks for selected domestic transactions and support local processing. Its relevance to a particular online merchant depends on issuer adoption, acquirer support, ecommerce enablement, gateway integration, and merchant eligibility. Merchants should ask providers for production evidence rather than assuming that scheme availability at the banking level guarantees ecommerce acceptance.
Priority local payment methods Mobile financial-service wallets Mobile financial-service wallets are the defining local payment category. They should be prioritized for: * Mobile-first customers * Low- and medium-value purchases * Education * Gaming * Digital goods * Marketplaces * On-demand services * Domestic ecommerce * Customers without suitable online cards Merchant operating questions Before enabling a wallet, confirm: * Whether the merchant category is eligible * Whether an international merchant can contract directly * Whether a local entity is required * Whether the integration uses redirect, app, QR, hosted page, or API * Whether payment confirmation is synchronous * How pending and failed payments are represented * Whether full and partial refunds are available * Whether the method supports reusable authorization or recurring charges * Whether refunds require prefunding * Settlement and payout currencies * Payout timing * Reconciliation fields * Chargeback or complaint procedures * Customer-support escalation * Expiration and retry behavior A provider’s support for “wallet payments” does not establish that all these capabilities are available. Bangla QR Bangla QR is most valuable when the payment journey includes a merchant-present interaction. Its interoperability can reduce the need for separate QR displays for every participating institution. As of the end of 2025, the network connected banks, MFS providers, PSPs, and nearly one million merchants. For online use, merchants must test:
* Whether the QR is displayed on the same phone being used for payment * Whether the customer can open the relevant app without losing checkout state * Whether desktop-to-mobile scanning is clearer * How payment status is refreshed * What happens when the customer pays after checkout expiration * Whether duplicate scanning can create duplicate orders * How refunds are initiated * Whether the merchant receives usable reconciliation references Bank transfers Bank transfer can serve higher-value, education, B2B, and institutional payments. A merchant should prefer a provider flow that creates a unique reference, payment request, or virtual identifier. Important distinctions include: * Immediate versus batch processing * Customer payment confirmation versus bank settlement * Reversible versus final transactions * Individual versus corporate accounts * Same-bank versus interbank flows * Structured versus unstructured remittance information * Domestic collection versus cross-border receipt Manual bank transfers should not be marked paid based solely on a customer-uploaded screenshot. Cash-assisted methods Bangladesh’s extensive MFS agent network effectively functions as a cash-assisted digital-payment layer. A customer can fund a mobile account with cash and then complete an online transaction.
This can provide many of the access advantages of a cash voucher without requiring the merchant to build a separate voucher product. The customer still bears the cash-in step, however, and may abandon checkout if the wallet balance is insufficient. Merchants can improve the journey by: * Displaying the final payable amount before authentication * Avoiding late-added fees * Keeping the checkout session active long enough for funding * Explaining whether the customer can return after adding money * Preserving the basket during app switching * Showing a clear pending-payment state * Avoiding automatic duplicate retries
Currency and pricing Bangladesh’s official currency is the Bangladeshi taka, code BDT. The symbol ৳ is commonly recognized locally. Bangladesh Bank states that the taka’s exchange rate is determined through the interbank foreign-exchange market. Local-currency presentment Most consumer merchants should display prices in BDT because local-currency pricing: * Makes the payable amount understandable * Reduces customer uncertainty * Aligns with mobile-wallet balances * Supports local card and bank payment * Makes refunds easier to explain * Reduces surprise conversion at the point of payment Presentment in BDT does not prove that the merchant will process, settle, or receive funds in BDT. Distinguish every currency layer Merchants should document: 1. Presentment currency: what the customer sees. 2. Processing currency: the currency submitted into the payment system. 3. Settlement currency: the currency in which the provider calculates the merchant’s settlement. 4. Payout currency: the currency transferred to the merchant’s bank account. 5. Reporting currency: the currency used in merchant finance systems. 6. Conversion currency: any intermediary conversion performed by the provider or bank. A checkout can show BDT while the merchant ultimately receives another currency after conversion. That arrangement can introduce FX spreads, payout deductions, conversion timing risk, and reconciliation differences. Pricing recommendations * Show the full amount before the customer leaves checkout.
* Avoid unnecessary decimal precision for consumer-facing prices. * Explain delivery charges and platform fees before payment. * Preserve the quoted amount through wallet authentication. * Refund the amount promised in the customer-facing policy. * Reconcile exchange-rate differences separately from payment failure. * Test how large BDT amounts appear on smaller screens. * Do not rely on dynamic currency conversion as a substitute for local pricing.
Local acquiring and cross-border processing Bangladesh’s acquiring environment should be viewed as several distinct layers: * A locally licensed payment provider * A local card acquirer * Domestic card processing * Access to a mobile financial-service provider * Local BDT settlement * A domestic merchant bank account * Cross-border merchant payout * An international PSP with Bangladesh coverage These capabilities may be provided together, but they are not interchangeable. The July 2026 cross-border framework On July 29, 2026, Bangladesh Bank issued a framework allowing Authorized Dealer banks to establish arrangements with qualifying foreign payment-service providers, online platforms, online payment gateways, and related cross-border digital-payment providers. The framework remains subject to foreign-exchange, AML/CFT, tax, reporting, and banking requirements. This is commercially important because it can create more formal pathways between international digital platforms and Bangladesh’s banking system. It should not yet be interpreted as universal access. Merchants must validate: * Which banks have implemented the framework * Which foreign providers have approved arrangements * Eligible merchant and transaction categories * Permitted currencies * Required customer information * Documentation and reporting * Whether inbound, outbound, or both transaction directions are supported * Settlement and repatriation procedures * Practical production timelines When local acquiring deserves investigation
Local card acquiring should be considered when: * Domestic card volume becomes material * Cross-border card approval is weak * BDT settlement is commercially important * The merchant has sufficient scale to support local contracting * The merchant’s category is accepted by local acquirers * Local scheme support would add meaningful coverage * Domestic pricing can reduce payment costs * Local reporting and treasury can be managed A merchant testing demand may be better served by a provider that combines local methods and cross-border contracting. A merchant scaling substantial volume may benefit from separating acquiring, local methods, and orchestration.
Payment regulation and licensing Bangladesh’s payment system is regulated by Bangladesh Bank. The Payment and Settlement Systems Act 2024 provides the primary statutory framework for payment and settlement activity. Bangladesh Bank also maintains regulations, guidelines, circulars, and licensing requirements covering mobile financial services, payment-system operators, payment-service providers, merchant acquiring, escrow, electronic funds transfers, QR payments, and cross-border foreign-exchange arrangements. Mobile financial services follow a regulated institutional model Bangladesh Bank’s Mobile Financial Services Regulations 2022 emphasize financial inclusion, safe payment services, and AML/CFT controls. The framework uses a bank-, financial-institution-, or government-entity-led model, with the qualifying institutional sponsor retaining majority ownership of an MFS provider. An international merchant should therefore expect to access MFS through an approved provider, acquirer, gateway, PSP, or other authorized arrangement rather than treating the service as an unregulated wallet API. Merchant acquiring and escrow Bangladesh Bank’s merchant-acquiring and escrow guidelines apply to relevant ecommerce and online merchant-payment arrangements involving banks, PSOs, PSPs, and MFS providers. The framework addresses merchant due diligence, authentication, settlement, escrow, refunds, and the handling of customer funds. The parties must determine which responsibilities belong to:
* The merchant * The platform * The payment provider * The acquirer * The seller * The Merchant of Record * The bank * The customer A platform that collects money for third-party sellers may have materially different obligations from a merchant selling its own products. Merchant eligibility Merchant approval may depend on: * Merchant category * Product or service * Local licensing * Customer age * Digital-content classification * Refund policy * Delivery model * Seller relationships * Cross-border nature * Expected transaction value * Source and destination of funds * KYC and beneficial-ownership documentation * Foreign-exchange treatment * Risk history A provider’s country-coverage page should not be treated as proof that a specific merchant can enter production. 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 Bangladesh’s standard VAT rate is generally stated as 15%, while exports can qualify for zero-rating under applicable conditions. Actual treatment can vary by product, service, business model, merchant location, customer location, exemption, supplementary duty, withholding requirement, and current National Board of Revenue rules. (National Board of Revenue) International merchants should obtain advice on: * Whether registration is required * Treatment of electronically supplied services * VAT on digital products * Marketplace responsibilities * Withholding taxes * Tax-inclusive or tax-exclusive display * Business Identification Number requirements * Invoice and receipt content * Foreign-currency invoices * Refund-related tax adjustments * Seller versus platform liability * Merchant of Record treatment Tax should be reviewed alongside the payment flow. The entity receiving the payment, issuing the invoice, recognizing revenue, paying the seller, and handling the refund may not always be the same party.
Checkout localization Translation alone is not sufficient localization. Language A bilingual approach can be effective: * Bangla for broad domestic accessibility * English for internationally experienced customers and selected urban segments * Consistent language through checkout, authentication instructions, confirmation, refunds, and support The customer should not move from Bangla product content into an unexplained English-only payment error. Method ordering For a consumer-facing mobile checkout, a reasonable initial order is: 1. Major mobile financial-service methods 2. Cards 3. Bank transfer where relevant 4. Cash on delivery for eligible physical goods 5. Additional segment-specific methods The final order should be determined by the customer’s eligibility and measured completion rate, not a global checkout template. Mobile design A Bangladesh checkout should be designed for: * Smaller screens * Limited bandwidth * Android devices with varying performance * App switching * OTP entry * Wallet deep links * QR scanning * Sessions interrupted while the customer adds funds * Customers returning from another application The checkout must preserve the order and prevent duplicate payment when the customer returns. Phone-number handling * Accept the local number format customers recognize. * Normalize country code and local formatting in the backend. * Explain why the number is required. * Do not request the same phone number repeatedly.
* Avoid treating spacing or leading-zero differences as different customers. * Mask the number on confirmation screens. Trust and instruction Customers should see: * Recognizable payment-method branding * BDT amount * Merchant identity * Refund policy * Delivery or access timing * A clear description of the next step * A local support path * Confirmation that the merchant will not request the wallet PIN directly Trust messaging is particularly important when customers are moving from a familiar wallet into an unfamiliar merchant checkout.
Authentication and customer verification Authentication varies by provider and method. A customer may encounter: * Wallet PIN * OTP * App approval * QR confirmation * Bank-login flow * Card 3-D Secure challenge * National ID-based verification during account onboarding * Additional review for higher-risk transactions Bangladesh Bank’s payment-system reporting notes the use of electronic KYC linked to national identity infrastructure and continued regulatory attention to customer identification, merchant due diligence, and authentication. What merchants can improve * Pass complete, accurate customer and transaction data. * Keep redirect and return URLs reliable. * Preserve checkout state. * Make OTP instructions clear. * Avoid repeated authentication caused by technical retries. * Use provider status APIs or webhooks rather than browser return alone. * Distinguish pending, failed, canceled, and timed-out payments. * Offer a safe recovery path. * Explain device switching. What merchants cannot guarantee * Whether an issuer challenges a card transaction * Whether the customer receives an OTP * Whether a wallet account has sufficient funds * Whether an issuer approves a cross-border payment * Whether a customer’s card has international capability * Whether a provider requires additional verification * Whether a bank or wallet app is temporarily unavailable Customer messaging should reflect this division of responsibility.
Recurring payments and subscriptions Bangladesh can support subscription businesses, but the addressable recurring-payment audience may be narrower than the one-time-payment audience. Cards Cards are likely to be the most practical starting point for recurring international payments when the provider supports: * Tokenization * Initial customer authentication * Card-on-file storage * Merchant-initiated transactions * Recurring-payment indicators * Failed-payment recovery * Expiry updates or account updater * Cancellation and refund functions Issuer capability and international-card restrictions may still reduce coverage. Mobile financial services Do not assume that a wallet’s one-time merchant-payment capability includes automated recurring debits. For each wallet or PSP, verify: * Customer mandate * Reusable token or authorization * Maximum frequency * Maximum amount * Renewal notification * Customer cancellation * Failed-debit handling * Refund support * Merchant eligibility * Whether the arrangement is available to international merchants Where recurring wallet support is unavailable, merchants can use a customer-initiated renewal flow with reminders, while clearly describing the product as manually renewable rather than automatically recurring. Vertical implications * SaaS: Cards may be necessary for automatic renewal; offer wallet-paid monthly or annual plans where recurring support is limited. * Streaming: Payment continuity and low-friction renewal are critical.
* Gaming: Wallets work well for one-time currency or item purchases; memberships require separate validation. * Education: Term payments can be customer-initiated rather than automatically recurring. * Marketplaces: Seller subscriptions and customer payments may require different methods. * Memberships: Renewal notices and easy cancellation are commercially important.
Refunds, reversals, and disputes A popular method is not necessarily an operationally simple method. Questions to answer before launch For every method, document: * Full-refund support * Partial-refund support * Multiple partial refunds * Refund time limit * Customer notification * Refund destination * Refund funding * Provider fees * Status notifications * Failed-refund handling * Reconciliation identifier * Whether the customer can dispute separately * Whether a reversal is different from a refund Bangladesh’s merchant-acquiring and escrow framework makes refund, settlement, delivery, and customer-fund handling part of the provider and merchant operating model rather than a purely technical API function. Dispute environment Bangladesh Bank recorded approximately 699,600 MFS disputes during 2025, with a reported value of approximately BDT 1.54 billion. It also reported approximately 419,400 card disputes, with substantial variation during the year. These figures are recorded disputes, not proof that every case involved fraud or merchant wrongdoing. Merchants should maintain: * Order evidence * Authentication evidence * Delivery or access logs * Customer communications * Refund records * Device and IP information where lawful * Seller records for marketplaces * Proof of digital-goods consumption * Consistent cancellation policies Customer communication When a refund is not immediate, show: * The refund amount * The original payment method * The date initiated * Expected provider processing time
* A merchant reference * A support contact * What the customer should do if funds do not arrive “Refund issued” should not be displayed until the provider has accepted the refund instruction.
Settlement and treasury Payment completion is only the beginning of the merchant’s financial process. The merchant must distinguish: 1. Customer account debited 2. Provider confirms payment 3. Transaction becomes final 4. Funds enter settlement calculation 5. Fees, taxes, reserves, and refunds are deducted 6. Provider initiates payout 7. Merchant bank receives funds 8. Funds become usable or are converted 9. Finance reconciles the payout to orders Questions for providers * What is the settlement currency? * What is the payout currency? * Is a domestic account required? * Is a local entity required? * What is the settlement schedule? * Are weekends and holidays excluded? * Is there a minimum payout? * Is there a rolling reserve? * When are fees deducted? * Who performs FX conversion? * Which exchange-rate basis is used? * Can refunds exceed the current balance? * How are chargebacks deducted? * What files and APIs support reconciliation? * Can settlements be split by payment method? * Can the merchant retrieve gross and net amounts? Repatriation and cross-border access Foreign-exchange and Authorized Dealer bank requirements can affect the movement of funds between Bangladesh and an international merchant. The July 2026 cross-border framework may create additional provider arrangements, but the merchant must confirm implementation and permitted flows with the relevant provider and bank.
Settlement economics can change whether a market is attractive. A method with strong customer conversion may be commercially weak if payout is slow, conversion is expensive, refunds require prefunding, or reconciliation is highly manual.
Fraud and risk characteristics Bangladesh should not be labeled broadly as a high-risk country. Risk should be analyzed by behavior, method, device, vertical, and transaction. Relevant patterns Social engineering and account takeover Mobile financial-service customers may be targeted through: * False support calls * Requests for PIN or OTP * Compromised mobile accounts * SIM-related attacks * Fake merchant pages * Misleading payment requests * Fraudulent refund messages The merchant should repeatedly state that employees will not request a customer’s wallet PIN or OTP. Card-not-present fraud Digital goods, gaming, travel, and immediately delivered services can be attractive targets because a fraudster can receive value before a chargeback or dispute begins. Controls should include: * 3-D Secure where appropriate * Velocity rules * Device analysis * Account-age signals * Customer history * Transaction-value thresholds * Behavioral monitoring * Post-payment review for selected high-risk orders Marketplace risk Marketplaces must manage both buyer and seller risk: * Fake sellers * Non-delivery * Collusion * Refund manipulation * Multiple seller accounts * Account takeover * Cash-on-delivery fraud * Payout to fraudulent beneficiaries * Prohibited products Seller onboarding, delayed payout, delivery evidence, complaint management, and reserve policies may be as important as payment authentication. Refund abuse
A customer may claim non-receipt after consuming a digital product, request multiple refunds through different channels, or exploit differences between merchant and provider records. Merchants should create one case record linking: * Order * Payment * Customer * Delivery * Refund * Dispute * Provider reference * Support history
Provider landscape and operating models Bangladesh Bank licenses and supervises banks, mobile financial-service providers, payment-service providers, and payment-system operators. Its current provider listings include multiple MFS services, payment gateways, payment-service providers, and infrastructure operators. Merchants can consider several operating models. Global PSP Best for: * Faster international contracting * Cards and cross-border customers * Reusable integration * Multi-country reporting Potential limitation: * Incomplete access to local mobile financial services, domestic settlement, or local acquiring Local PSP or gateway Best for: * Local wallets * Domestic cards * BDT payment * Local bank relationships * Country-specific support Potential limitation: * Local entity, bank account, merchant eligibility, and additional integration requirements Direct MFS integration Best for: * Large merchants with material local volume * Greater control over wallet experience * Direct operational relationship Potential limitation: * Separate contracts, technical integrations, reporting formats, settlement processes, and support escalation for each method Local card acquirer Best for: * Meaningful domestic-card volume * Domestic routing * Local scheme support * Potential BDT settlement Potential limitation: * Contracting, entity, risk, and technical obligations Merchant of Record Best for: * Merchants seeking support with local selling, customer payment, tax, or compliance responsibilities Potential limitation:
* Higher cost * Less control * Product and merchant-category restrictions * Dependence on the Merchant of Record’s refund, settlement, and customer policies Payment orchestration Best for: * Merchants operating several providers * Routing * Failover * Consolidated monitoring * Multi-market expansion Potential limitation: * Orchestration cannot create regulatory eligibility or payment-method access that the underlying providers do not possess The best architecture may combine a global provider for cards and international coverage with a locally authorized partner for MFS and domestic payment methods.
How payment strategy changes by merchant vertical Vertical Transaction pattern Priority methods Main operating concern Recommended launch approach Education Course, application, exam, and term payments MFS, cards, bank transfer Matching payer to student, partial refunds, access timing Launch wallets and structured bank transfer together Gaming Frequent low- and medium-value digital purchases MFS, cards, selected prepaid methods Account takeover, minor access, instant delivery, refund abuse Begin with one-time payments and validate recurring separately Digital services One-time and recurring Cards, MFS, bank transfer Cross-border eligibility, renewal, tax and FX Offer wallet-paid one-time plans and card subscriptions Fashion ecommerce Physical orders with high return sensitivity MFS, cards, COD Failed delivery, returns, cash reconciliation Measure delivered and retained revenue, not orders Marketplaces Buyer collections and seller payouts MFS, cards, COD, bank transfer Escrow, seller KYC, complaints, payouts Resolve regulated fund flow before seller acquisition B2B platforms Higher-value invoices and recurring commercial payments Bank transfer, cards, selected MFS Reconciliation, invoicing, treasury Prioritize structured transfer and finance integration Creator and freelance platforms Cross-border service income and platform fees Cards, bank channels, approved cross-border arrangements FX, payout compliance, beneficiary verification Confirm Authorized Dealer and provider model first On-demand services
High-frequency, lower-value payments MFS, cards, Bangla QR Cancellation, duplicate payment, service disputes Optimize mobile wallet recovery and fast refunds
Payment-performance measurement Do not rely on one blended “Bangladesh conversion rate.” Core metrics and denominators Metric Recommended calculation Payment-method visibility rate Checkouts where the method was displayed ÷ eligible checkout sessions Selection rate Customers selecting the method ÷ sessions where it was displayed Initiation rate Payment attempts initiated ÷ selections Authentication success Successful authentications ÷ authentication attempts Payment completion rate Confirmed successful payments ÷ initiated payment attempts Card authorization rate Approved authorizations ÷ submitted authorization attempts Completed-order rate Paid, accepted orders ÷ checkout sessions Delivered-order rate Successfully delivered orders ÷ accepted physical-goods orders Refund rate Refunded transactions ÷ successful transactions Chargeback rate Card chargebacks ÷ settled card transactions Technical-error rate Payment attempts failing for technical reasons ÷ initiated attempts Cost per successful payment Total payment cost ÷ successful payments Cost per completed order Payment, fraud, delivery, support, and refund costs ÷ completed orders Settlement delay Time from payment confirmation to usable merchant funds Reconciliation-exception rate Unmatched transactions or adjustments ÷ total reportable transactions Support-contact rate Payment-related support cases ÷ successful and failed payment attempts Retained revenue Collected revenue minus refunds, chargebacks, fraud, delivery loss, and unrecovered fees
Segment every relevant metric by: * Payment method * Provider * Issuer * Domestic versus cross-border card * Device * Operating system * New versus returning customer * Customer region * Currency * Order value * Authentication result * Merchant vertical * Checkout version * Delivery method For cash on delivery, measure checkout, confirmation, dispatch, delivery, payment collection, return, and final retained revenue as separate stages.
Launch recommendations by merchant stage Merchant testing demand Start with: * BDT pricing * One well-supported MFS integration * Cards * Bank transfer only where transaction value justifies it * Cash on delivery only for relevant physical products * Manual daily reconciliation * Clear demand and completion targets * A limited product range * A controlled acquisition budget The test should establish whether customers can and will pay—not merely whether they visit the site. Merchant launching nationally Add: * Additional high-contribution MFS coverage * Reliable payment-status webhooks * Automated reconciliation * Full and partial refund testing * Localized support procedures * Documented settlement and FX flows * Authentication recovery * Device testing * Marketplace or escrow compliance where applicable * Delivery and return measurement for physical goods Merchant scaling volume Investigate: * Local card acquiring * Domestic scheme support * Provider routing * Wallet-by-wallet performance * Cost per completed order * Treasury optimization * Reserve reduction * Automated fraud controls * Provider uptime and failover * Formal operational service levels Merchant optimizing performance Focus on: * Method visibility and ordering * Wallet-specific abandonment * Issuer-level card results * Domestic versus cross-border routing * OTP and redirect failures * App-switching loss * Technical timeouts * Duplicate-payment prevention * Returning-customer flows * Refund and support contact rates Merchant introducing subscriptions Validate:
* Which customers have recurring-capable cards * Wallet mandate support * Initial authentication * Subsequent merchant-initiated charging * Failed-payment recovery * Renewal notice * Cancellation * Refund procedures * Cross-border and FX rules Provide a customer-initiated renewal option for users without an automated recurring method. Merchant expanding regionally Separate reusable infrastructure from Bangladesh-specific requirements. Reusable components may include: * Tokenization * Provider abstraction * Payment-state model * Reconciliation engine * Fraud data * Reporting * Customer-support workflow Bangladesh-specific components may include: * MFS integrations * BDT presentation * Bangla QR * Local acquiring * Escrow rules * Authorized Dealer bank arrangements * Local refund procedures * Country-specific merchant eligibility
Bangladesh launch checklist Market and customer * Confirm demand among customers who can realistically access the product. * Estimate order value and retained margin in BDT. * Separate urban, regional, mobile-wallet, banked, and card-capable segments. * Confirm that the merchant category and product are permitted. Payment access * Launch at least one commercially important MFS option. * Confirm whether the chosen integration reaches the intended wallet users. * Add cards for appropriate domestic and international customers. * Add structured bank transfer for education, B2B, or higher-value transactions. * Decide whether cash on delivery is economically viable. * Evaluate Bangla QR for merchant-present or omnichannel use. Contracting and regulation * Confirm merchant eligibility with each provider. * Determine whether a local entity or bank account is required. * Confirm which licensed party acquires and holds customer funds. * Review merchant-acquiring and escrow requirements. * Review foreign-exchange and cross-border arrangements. * Obtain Bangladesh-specific legal and tax advice. * Document marketplace and seller responsibilities where applicable. Checkout * Present prices in BDT. * Prioritize mobile financial services in method ordering. * Localize key checkout and error messages in Bangla and English. * Test low-bandwidth and lower-performance devices. * Test redirects, app switching, OTP, QR, and customer return. * Preserve the order during wallet funding.
* Prevent duplicate payments and duplicate orders. Operations * Test successful, failed, canceled, expired, pending, and late payments. * Test full and partial refunds. * Confirm customer refund timing and messaging. * Validate settlement currency and payout currency. * Validate payout timing, fees, reserves, and FX conversion. * Reconcile orders, transactions, refunds, fees, and payouts. * Establish provider and customer-support escalation. * Prepare controls for account takeover, social engineering, refund abuse, and marketplace fraud. Measurement * Define the denominator for every metric. * Segment by method, provider, issuer, device, and customer cohort. * Measure delivered and retained revenue for physical goods. * Establish a formal post-launch review date. * Assign owners for payments, fraud, finance, compliance, tax, support, and product.
Final merchant recommendation Bangladesh should be prioritized by merchants whose products fit a large, price-conscious, increasingly connected population and can be sold through mobile-first, locally accessible payment journeys. The strongest immediate candidates include: * Education and online learning * Marketplaces with strong operating controls * Digital services * Gaming and digital goods * Fashion and value-oriented ecommerce * Freelance and creator platforms * On-demand services * B2B commerce A merchant’s first payment release should generally include: 1. BDT pricing 2. One or more commercially important mobile financial-service methods 3. Cards for customers who can use them 4. Structured bank transfer where transaction value or vertical justifies it 5. Cash on delivery only where the economics of physical fulfillment support it 6. Bangla QR where the journey includes local, in-person, or omnichannel collection Before committing significant resources, the merchant must validate: * Merchant-category eligibility * Provider production access * Local-entity and bank-account requirements * Cross-border and foreign-exchange arrangements * Refund functionality * Recurring-payment suitability * Settlement and payout economics * Tax treatment * Escrow or marketplace obligations * Reconciliation * Customer support * Actual completion by method and device
Bangladesh’s opportunity does not come from mobile payments eliminating cash. It comes from an infrastructure that increasingly connects cash, agents, mobile accounts, banks, QR networks, cards, merchants, and international platforms. The merchants most likely to succeed will be those that design for that connected system rather than for only its most digitally advanced customers.
Prepared from the Bangladesh country-specific editorial brief and its required merchant, research, structure, and differentiation standards.
Editorial recommendations package SEO recommendations Title options 1. Payments in Bangladesh: Mobile Financial Services, Cards and Merchant Strategy 2. Payment Methods in Bangladesh: A Guide for International Merchants 3. Bangladesh Payments Guide: MFS, Cards, Bank Transfers and Cash 4. Accepting Payments in Bangladesh: A Merchant Market-Entry Guide 5. Bangladesh Ecommerce Payments: Wallets, Cards, Settlement and Regulation Recommended SEO title Payment Methods in Bangladesh: Merchant Guide 2026 This is direct, keyword-aligned, and short enough to leave room for a brand suffix in search results. Recommended H1 Payments in Bangladesh: Mobile Financial Services and a Large Emerging Digital Market Meta description Understand payment methods in Bangladesh, including mobile financial services, cards, bank transfers, QR payments, cash, settlement and regulation. URL slug /payments-in-bangladesh/ Primary keyword payment methods in Bangladesh Secondary keywords * Payments in Bangladesh * Bangladesh payment gateway * Mobile payments in Bangladesh * Bangladesh mobile financial services * Accept payments in Bangladesh * Ecommerce payments Bangladesh * Bangladesh digital payments * bKash payments for merchants * Bangladesh card payments * Bangla QR * Bangladesh payment regulations * Bangladesh local acquiring Related entities * Bangladesh Bank * Bangladeshi taka * BDT * Mobile financial services * bKash * Nagad * Rocket * Upay * Bangla QR * National Payment Switch Bangladesh * TakaPay * Payment and Settlement Systems Act 2024
* Authorized Dealer banks * National Board of Revenue * Electronic KYC * RTGS * Electronic funds transfer Search intent The dominant intent is commercial investigation supported by informational research. The reader is likely evaluating: * Which payment methods to offer * Whether Bangladesh is commercially attractive * How MFS differs from cards * Whether local acquiring is needed * How to collect and settle BDT * Which provider or operating model can support entry * What regulatory and operational barriers must be addressed Article excerpt Bangladesh combines a population of more than 175 million with one of the world’s largest mobile financial-service ecosystems. For merchants, however, registered wallet accounts, active customers, card ownership and ecommerce readiness are different measures. This guide explains how cash, agents, wallets, bank transfers, QR payments, cards, regulation and settlement shape the real payment opportunity. Social description Bangladesh is not simply a cash market becoming a card market. Its customers move through a connected system of cash agents, mobile accounts, wallets, QR payments, bank transfers and cards. Here is what merchants must support—and validate—before launching.
Internal-link recommendations
* How to expand into new international markets * Local payment methods * How mobile wallets work * Payment authorization versus conversion * How to improve payment authorization rates * Why customer payments are declined * Cross-border payment processing * Local acquiring versus cross-border acquiring * Payment gateway integration * Payment orchestration * Merchant of Record services * Payments for gaming * Payments for education platforms * Marketplace payments * Subscription-payment recovery * Refunds, reversals and chargebacks * Payment reconciliation * Fraud prevention in emerging markets * Global Payments Atlas * South Asia regional payment guide Anchor text should describe the destination naturally rather than repeating “Bangladesh payments” throughout the article.
Authoritative external-source recommendations Use and periodically recheck: * Bangladesh Bank’s annual Payment Systems Report for MFS, QR, bank-rail, dispute, and provider data. * Bangladesh Bank’s card report for issued-card and network developments. * Bangladesh Bank circulars for cross-border payment and foreign-exchange changes. * IMF World Economic Outlook for internationally comparable GDP and rank calculations. (IMF Data) * World Bank country data and Global Findex for population, economic, account-access, and financial-inclusion indicators. (World Bank Open Data) * Bangladesh Bureau of Statistics for household internet and ecommerce-use research. * International Telecommunication Union for comparable connectivity indicators. (ITU Data Hub) * National Board of Revenue for current VAT, tax, and invoicing requirements. (National Board of Revenue) Competitor PSP articles should not be used as primary factual evidence.
Structured-data recommendation Use: * Article or BlogPosting * BreadcrumbList * FAQPage, provided the visible FAQ content exactly matches the structured data * ImageObject for the original hero and diagrams Recommended Article fields include: * Headline * Description * Date published * Date modified * Author and reviewer * Publisher * MainEntityOfPage * Citation * About * Mentions * Image Do not add numerical claims to structured data that are not visible and sourced in the article.
Original asset recommendations Asset 1: Bangladesh customer-access ladder Purpose: Show why payment access progresses from cash to agent-funded mobile accounts, merchant wallets, QR, bank transfers and cards. Intended reader: Ecommerce leaders, product teams and market-entry decision-makers. Data required: * MFS registered and active accounts * Agent count * Main MFS transaction categories * Card counts * QR merchant participation * Online-purchase indicator Recommended format: Horizontal or ascending-step infographic with a customer journey running through each level. Recommended placement: Immediately after the country payment snapshot. Suggested caption: “Bangladesh’s digital customer journey often begins with cash entering a mobile account rather than with a conventional payment card.”
Asset 2: Payment-method portfolio scorecard by vertical Purpose: Help merchants compare how MFS, cards, bank transfer, cash on delivery, Bangla QR and other methods perform for education, gaming, fashion, marketplaces and B2B commerce. Intended reader: Payments, product, finance and commercial teams. Data required: * Customer reach * Recurring support * Refund support * Typical transaction value * Mobile suitability * Settlement complexity * Merchant eligibility * Integration burden Recommended format: Color-coded matrix with ratings such as essential, high-value, segment-specific and optional. Recommended placement: Beside or immediately after the article’s payment-method priority matrix. Suggested caption: “No payment method has the same value for every merchant: wallet access may be essential for gaming, while structured bank transfer may matter more for B2B or tuition.”
Asset 3: Bangladesh merchant flow-of-funds diagram Purpose: Explain the difference between customer payment, provider confirmation, settlement, payout, FX conversion and usable merchant funds. Intended reader: Finance, treasury, legal, operations and executive stakeholders. Data required: * Customer payment currency * Payment provider * Licensed local participant * Escrow or settlement account * Fees and deductions * Authorized Dealer bank * FX conversion * Merchant payout currency * Refund flow Recommended format: Two-direction flow diagram showing both the original payment and refund path. Recommended placement: In the settlement and treasury section. Suggested caption: “A successful BDT payment and an international merchant payout are separate events, potentially involving different institutions, currencies and timing.”
Visual recommendations Hero image concept Create an editorial illustration showing a Bangladeshi customer journey moving through connected payment layers: * Cash passed to an agent * Value appearing in a mobile account * A wallet checkout on a phone * A Bangla QR transaction * A bank-transfer rail * A card as one option rather than the central object * A merchant dashboard receiving the completed payment Avoid a generic skyline, flag background, currency pile, or oversized credit card. Suggested hero caption: “Reaching Bangladesh’s digital customers requires connecting cash access, mobile financial services, bank infrastructure and merchant operations.” Hero alt text: “Illustration of a Bangladesh payment journey connecting cash agents, mobile financial-service wallets, QR payments, bank transfers, cards and an online merchant.” Diagram concept Title: From Customer Funds to Merchant Payout in Bangladesh Show: Customer → cash agent or bank → MFS/card/bank rail → licensed provider → settlement or escrow → Authorized Dealer or payout bank → merchant. Add a separate refund arrow traveling back toward the original method. Alt text: “Flowchart showing how a Bangladesh customer payment moves through local payment providers, settlement and foreign exchange before reaching an international merchant.” Chart concept Title: Registered Access Is Not the Same as Active Payment Use Compare, while preserving different definitions: * Total population * Registered MFS accounts * Active MFS accounts * Debit cards issued
* Credit cards issued * Prepaid cards issued * Bangla QR merchants The chart must explicitly state that accounts and cards are not unique users. Alt text: “Comparison of Bangladesh population, registered and active mobile financial-service accounts, issued cards and Bangla QR merchants.” Map concept A national map should be used only when credible regional data can illustrate: * Internet purchasing * Agent access * Merchant density * Urban versus regional ecommerce participation * Delivery or logistics coverage Do not shade the country using unsupported market-opportunity scores. Suggested caption: “Digital-commerce participation varies across Bangladesh; national wallet-registration totals should not be interpreted as uniform regional demand.”
Human review and first-hand contribution recommendations Required before publication Bangladesh regional payments specialist Review: * Current wallet importance * Merchant access * Method terminology * Customer journey * Local-provider arrangements * Bangla QR use cases * Accuracy of the launch hierarchy Compliance or payments-law reviewer Review: * Payment and Settlement Systems Act interpretation * MFS regulations * Merchant-acquiring and escrow requirements * Marketplace responsibilities * Cross-border provider framework * Merchant eligibility language Bangladesh tax adviser Review: * VAT statements * Digital-service treatment * Nonresident registration * Withholding * Invoicing * Marketplace or Merchant of Record implications Strongly recommended Treasury or banking specialist Review: * BDT settlement * Payout currency * Authorized Dealer arrangements * FX conversion * Repatriation * Reserves * Bank-account requirements Payment operations and reconciliation specialist Review: * Wallet statuses * Refund capability * Late payment * Duplicate payment * Settlement files * Provider reporting * QR reconciliation Fraud specialist Review: * MFS social-engineering language * Card-not-present controls * Marketplace risk * Gaming and digital-goods risk * Refund abuse * Evidence-retention recommendations Payment product expert Review: * Integration feasibility * Recurring-payment support * Local acquiring * Webhook and API behavior * Provider capability claims Optional enhancement Local ecommerce merchant or marketplace operator
Contribute an approved first-hand observation about: * Cash-on-delivery completion * Wallet preference * Regional differences * Refund expectations * Delivery and payment reconciliation Education or gaming merchant Contribute an implementation lesson on: * Wallet checkout * Low-value payment economics * Customer support * Renewal behavior Local MFS or acquiring specialist Contribute an explanation of: * Merchant onboarding * Wallet refunds * Settlement * Bangla QR * Recurring-payment limitations The article should not imply that any of these reviews or contributions have already occurred.
Final fact-check list The following claims require verification immediately before publication: 1. Bangladesh’s global nominal GDP rank using the latest IMF dataset. 2. Nominal GDP and GDP-per-capita values, including whether 2025 figures remain estimates. 3. Population estimate and reference year. 4. Services, industry and agriculture shares of GDP. 5. Registered and active MFS accounts, including the precise active-account definition. 6. MFS agent count. 7. Share of MFS flows represented by cash-in, cash-out and P2P. 8. MFS merchant-payment volumes and values. 9. MFS-linked remittance growth. 10. Bangla QR merchant count and participating institutions. 11. Bangla QR interoperability and instant-settlement implementation. 12. TakaPay bank and acquirer coverage. 13. Issued debit, credit and prepaid card totals. 14. Visa or other network usage claims. 15. Adult account, mobile-money, phone-ownership and internet-use percentages from Global Findex. 16. ITU mobile-broadband subscription figure. 17. BBS online-purchasing percentage and regional breakdown. 18. Ecommerce-market forecast, forecast period and methodology. 19. Claim that cash on delivery remains dominant. 20. Licensed MFS, PSP and PSO list. 21. Merchant-acquiring and escrow requirements. 22. Practical implementation of the July 2026 cross-border digital-payment framework. 23. Local-entity and domestic-bank-account requirements by operating model. 24. Wallet refund, partial-refund and recurring-payment capabilities.
25. Card tokenization and merchant-initiated transaction support. 26. Foreign-exchange and payout requirements. 27. VAT rate, exemptions, digital-service treatment and invoicing requirements. 28. Settlement frequency, reserves and payout currencies offered by each selected provider. 29. Vertical-growth claims for education, gaming, marketplaces, fashion and B2B commerce.
Not sure which payment solution fits?
Use the merchant matching prototype to understand the types of providers to evaluate.
Explore matching ↗