METHOD PROVIDER
↗
Connect Directly to bKash
Your business works with the bKash provider under its merchant and technical requirements.
Primary focus
Implementing bKash under the provider's own integration arrangement.
bKash Payment Gateway Integration for Businesses in Bangladesh
Accept bKash payments from customers in Bangladesh through A-Pay. Connect the local payment method to your platform using an agreed integration configuration, with transaction results delivered to your backend.
Explore bKash integration options, payment processing requirements, and the additional local methods available for your business.
Bangladesh / Local payment acceptance
What Is bKash and How Can Businesses Accept It Through A-Pay?
bKash is a mobile financial service in Bangladesh. A-Pay provides a payment gateway integration through which eligible businesses can accept payments using supported bKash configurations.
Your customer uses bKash as the local payment method. Your platform connects to A-Pay for payment processing and transaction results. The exact customer experience depends on the configuration enabled for your project.
Use bKash to serve customers in Bangladesh, and discuss related local methods if your payment setup needs wider coverage.
bKash
PAYMENT METHOD PROFILE
Market
BangladeshPayment type
Mobile financial serviceDeposit currency in API
BDTIntegration
Via A-Pay gatewayMETHOD → GATEWAY → MERCHANT
A-Pay / Technical reference
bKash Configurations in A-Pay Documentation
The deposit API lists four bKash payment-system identifiers under BDT. Use the specific configuration agreed for your merchant project; each may have different request requirements.
DEPOSIT CURRENCYBDT
payment_system / Bangladesh
API REFERENCE
01
bkash_aDocumented deposit configuration02
bkash_bDocumented deposit configuration03
bkash_api_vDocumented deposit configuration04
bkash_p2pDocumented deposit configurationProject-specific configuration and payment instructions
DOCUMENTED ≠ UNIVERSALLY ENABLED
The deposit activation documentation references additional activation handling for selected variants. Do not assume the four variants share identical customer steps. Read A-Pay deposit documentation.
Payment lifecycle / Illustrated
How a bKash Payment Works Through A-Pay
Follow a payment request from your platform to the enabled local method and the transaction result back to your backend. Exact customer instructions depend on the selected bKash configuration.
Merchant platformInitiates payment
A-Pay gatewayProcesses request
bKash methodCustomer follows instructions
PAYMENT REQUEST →← STATUS TO MERCHANT
01. Create request
Your backend starts a deposit using the agreed payment configuration.
02. Complete payment
The customer follows the instructions associated with that configuration.
03. Handle result
A-Pay sends transaction information to your backend. Your platform records and displays the outcome.
Illustrative lifecycle, not a live transaction or a promise of a particular authorization screen, speed, or outcome.
Choose your integration model
Direct bKash Integration or A-Pay Gateway?
Both approaches can serve a merchant's payment acceptance needs, but they differ in whom you integrate with and how you manage additional local methods.
PAYMENT GATEWAY
↔
Connect Through A-Pay
Your developers connect to A-Pay and implement the bKash configuration enabled for your merchant project.
Primary focus
Accepting bKash with the option to add other supported local methods through the gateway.
Actual onboarding, technical requirements and processing terms depend on your merchant project. This comparison does not imply that either approach is universally cheaper or faster.
Developer readiness / A-Pay API
Integrating bKash into Your Platform
Connect with the integration approach and payment-system configuration agreed for your project. Your backend remains responsible for payment requests and transaction results.
01 / API
Host-to-Host
Your backend exchanges requests with A-Pay. The merchant platform builds the customer-facing interface according to the enabled payment flow.
02 / HOSTED
Hosted Payment Page
A-Pay hosts the payment interface. Your platform still implements the required integration and handles transaction statuses.
The availability of each option for the selected bKash configuration is confirmed during integration planning.
IMPLEMENTATION CHECKLIST BDT / bKash
01
Confirm configuration
Agree on the enabled payment system and required transaction flow.
02
Create deposit requests
Implement authenticated server requests using the documented parameters.
03
Handle activation if needed
Follow additional steps only when required by that configuration.
04
Implement status handling
Configure backend postbacks and verify payment outcomes.
For technical fields and examples, see the A-Pay deposit API documentation and deposit activation documentation.
Payment operations / Backend
How Your Platform Handles bKash Payment Results
A-Pay sends payment information to your backend through its postback mechanism. Your system matches the transaction to its record, verifies the result and displays the outcome to the customer.
BACKEND VERIFICATION → CUSTOMER-FACING STATUS
1
Receive the result
Your backend receives the configured transaction status event.
2
Match and verify
Validate the information using the applicable documentation and reconcile it to the relevant order.
3
Update your platform
Record the outcome and present the correct status to your customer.
The field labels shown are illustrative descriptions, not a sample live payload. A-Pay provides status data to your project; it does not operate a separate customer notification service.
Merchant operations
bKash Processing Terms and Merchant Settlements
Payment acceptance, customer payouts and merchant settlements are separate operations. Confirm the applicable availability, processing fees, transaction limits and settlement details for your merchant setup before launch.
↓
Pay-in
Customers make payments using the bKash configuration enabled for your project. Your platform receives the transaction result through A-Pay.
↑
Customer payout
A-Pay supports payout operations. bKash-specific payout availability, terms and the supported flow must be confirmed separately.
MERCHANT SETTLEMENT
T+0
Same-day sending
A-Pay sends merchant settlements on the same day. The time funds reach a recipient account is not guaranteed by the T+0 designation.
Processing and settlement currencies are agreed separately. Merchant settlement is not a payout to an end user.
Frequently Asked Questions
Share your business and payment requirements with A-Pay. Our team will help you confirm the bKash configuration available for your project, the integration requirements, and the applicable processing terms before launch.
When connecting bKash through A-Pay, your developers use A-Pay's integration documentation and the payment configuration agreed for your project. Any additional requirements related to bKash credentials or authorization are confirmed during integration planning.
A-Pay's deposit documentation lists bkash_a, bkash_b, bkash_api_v, and bkash_p2p under BDT. The available configuration and its technical requirements depend on your merchant setup.
A-Pay provides transaction-status information to your backend through its postback mechanism. Your system processes the result, matches it to the relevant transaction, and displays the appropriate status to your customer.
A-Pay supports payout operations. However, customer payout availability, configuration requirements, and processing terms for bKash must be confirmed separately from payment acceptance.
A-Pay sends merchant settlements on the same day (T+0). Merchant settlement is separate from a customer payout, and T+0 does not guarantee instant receipt of funds in the recipient account.
Yes. Existing A-Pay merchants can request additional supported payment methods in Bangladesh at no extra connection cost. The number of connected methods does not change the connection price. Processing terms and available payment operations are agreed separately.
