bKash Bangladesh Mobile Financial Service API
bKash Bangladesh mobile financial service REST API for merchants and businesses in Bangladesh to accept mobile wallet payments, process disbursements, and manage B2B payments through Bangladesh's largest MFS network with 60+ million registered accounts. Enables AI agents to manage payment request creation for Bangladesh e-commerce automation, handle customer wallet charge for Bangladesh mobile payment automation, access agreement-based recurring payment for subscription billing automation, retrieve payment status and verification for transaction confirmation automation, manage refund processing for order management automation, handle B2B payment for merchant-to-merchant Bangladesh automation, access disbursement and payout for Bangladesh salary and incentive automation, retrieve transaction reporting for financial reconciliation automation, manage sandbox testing for Bangladesh payment integration testing, and integrate bKash with Bangladeshi e-commerce, banking, and fintech platforms for end-to-end Bangladesh payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Bangladesh MFS. PCI-DSS. Token auth. BD. Mobile payment data.
⚡ Reliability
Best When
A Bangladesh merchant or fintech wanting AI agents to automate bKash mobile wallet payment acceptance, disbursements, and recurring billing through Bangladesh's dominant MFS provider with 60+ million accounts.
Avoid When
BANGLADESH BANK REGULATORY COMPLIANCE: bKash MFS operations are regulated by Bangladesh Bank; automated payment operations must comply with Bangladesh Bank MFS guidelines (transaction limits, KYC tiers); automated payment exceeding tier limits creates declined transaction. AGREEMENT-BASED PAYMENT REQUIRES PRE-AUTHORIZATION: bKash recurring payments require customer agreement creation before charge; automated recurring billing must first create and confirm agreement with customer; automated charge without agreement creates unauthorized charge error. OTP VERIFICATION FLOW FOR CUSTOMER AUTHORIZATION: bKash payment requires customer OTP verification on their mobile phone; automated payment flow must present OTP prompt to customer and wait for verification; automated payment execution without customer OTP creates incomplete payment session. TAKA CURRENCY AND TRANSACTION LIMITS: bKash transactions are in BDT (Bangladeshi Taka); daily and monthly transaction limits apply per wallet tier; automated high-value disbursements must be split per regulatory limits.
Use Cases
- • Accepting bKash wallet payments from Bangladesh e-commerce agents
- • Processing bulk disbursements from Bangladesh salary payment agents
- • Managing recurring bKash charges from subscription billing agents
- • Verifying payment status from Bangladesh order fulfillment agents
Not For
- • Cross-border or international payments (bKash is Bangladesh-only)
- • Card payment acceptance (use SSLCommerz or SSLCZ for card payments in Bangladesh)
- • Large enterprise payments outside MFS (use bank APIs for corporate Bangladesh payments)
Interface
Authentication
bKash uses App Key, App Secret, and token-based OAuth for API authentication. Token refresh required. REST API with JSON. Dhaka, Bangladesh HQ. Founded 2011 as BRAC Bank subsidiary (now 51% BRAC Bank, 20% Ant Financial/Alipay, 20% Money in Minutes, 9% IFC). Bangladesh's largest MFS with 60M+ accounts. Products: Checkout, Payment Agreement, B2B, Disbursement. PCI DSS. Competes with Nagad and Rocket for Bangladesh MFS.
Pricing
Dhaka BD. BRAC Bank / Ant Financial backed. Per-transaction fees in BDT. Merchant agreement required.
Agent Metadata
Known Gotchas
- ⚠ TOKEN EXPIRY AND REFRESH REQUIREMENT: bKash API tokens expire after a short period (typically 1 hour); automated payment systems must implement token refresh before expiry; automated API calls with expired token create authentication failure requiring manual re-login
- ⚠ PAYMENT EXECUTION TWO-STEP FLOW: bKash checkout requires Create Payment then Execute Payment two-step flow; automated checkout must complete both steps with paymentID; automated single-step payment attempt creates incomplete payment with no charge
- ⚠ SANDBOX vs LIVE URL SEPARATION: bKash sandbox and production use completely different base URLs and credentials; automated environment switching must update both URL and credentials; automated production URL use with sandbox credentials creates certificate or credential rejection
- ⚠ AGREEMENT STATUS VERIFICATION BEFORE CHARGE: bKash agreement-based payments require checking agreement status before charging; automated recurring billing must verify agreement is ACTIVE before each charge attempt; automated charge on INACTIVE or CANCELLED agreement creates agreement not found error
- ⚠ IPN (INSTANT PAYMENT NOTIFICATION) SECURITY VALIDATION: bKash IPN webhook must be validated with HMAC signature and IP whitelist; automated IPN processing without validation creates spoofed payment acceptance vulnerability; bKash provides IP ranges for whitelist configuration
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for bKash Bangladesh Mobile Financial Service API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.