bKash & Nagad API Integration in Bangladesh

Confirm the route before designing the wallet checkout

Describe your company, website, product and customers to the provider. Ask for the approved payment journey for bKash or Nagad and how the payer authorizes payment. A direct merchant checkout and another collection arrangement should not be treated as identical merely because both mention the same wallet.

Do not describe a route as native, official or directly partnered unless that status has been confirmed. PAYJN’s public coverage describes available methods for eligible merchants; it does not mean PAYJN is the wallet operator.

Handle changing transaction limits explicitly

A collection limit does not determine the payout limit. Limits may also differ by route. Obtain the current merchant notice before launch and show the applicable range in checkout. This guide intentionally does not publish a combined maximum that every route must support.

Build BDT order matching and verification

Agree the amount format, order references, expiry and final status process. Store enough transaction context for reconciliation, but keep wallet PINs, one-time passwords and unrelated personal information out of your application and first enquiry.

Test what happens when a customer reports payment before your callback arrives. Use the provider’s documented verification process and a clear pending message. Crediting an order based on a screenshot creates an avoidable reconciliation gap.

Test payout exceptions separately

For payouts, validate the required destination fields before sending a request. Confirm how rejected, timed-out and pending instructions are resolved. If a payout request times out, check the existing transaction through the documented process before attempting another transfer.

Agree how finance reconciles collection receipts, payout debits and fees. Keep a record of provider references and escalation outcomes so the same exception is not paid twice or repeatedly investigated by different support staff.

What to include in your Bangladesh enquiry

Provide the company website, jurisdiction, business model, expected BDT volume, typical ticket size and required payment directions. PAYJN lists bKash, Nagad and Upay for approved Bangladesh merchant setups. Ask the team to confirm each method and current route-specific terms.

For wallet background, consult bKash’s business services information. The operator’s published offerings are distinct from your approved PAYJN integration. Use the payment API checklist to prepare the technical discussion.