bKash
Nagad
Rocket
Upay
TAP
SureCashLocal wallets, banks and more
Each method is a modular connector with explicit capability flags — we never assume a provider supports every operation.
Capabilities shown are planned connector scopes. A method goes live only after provider authorization and end-to-end testing.
Automatic collection
- 1Create an invoice through the API
- 2Customer picks a method in hosted checkout
- 3Provider confirms the payment to PayBangla
- 4Amount, currency and reference are verified
- 5Your server receives a signed webhook
A payment is never marked paid from a customer-entered transaction ID, SMS or screenshot.
Controlled payouts
- 1Request a payout against settled balance
- 2Beneficiary verification and limit checks
- 3Risk review and approval thresholds
- 4Idempotent execution via provider API
- 5Automatic reconciliation and audit trail
Payouts run only where the provider has authorized that capability for your account.
Versioned, predictable, developer-first
- Invoices and payment status
- Payout requests and status
- Balances and transaction history
- Idempotency keys on every write
- HMAC-signed, replay-resistant webhooks
POST /v1/invoices
Authorization: Bearer sk_test_••••
Idempotency-Key: 7f3c-order-1042
{
"amount": 1500.00,
"currency": "BDT",
"reference": "order_1042",
"return_url": "https://shop.example/thanks"
}Security by design
The principles every PayBangla component is built on.
Payment state changes only from authenticated provider confirmations.
Provider credentials are never exposed to browsers.
Timestamped HMAC signatures protect against replay.
Owner and merchant consoles require strong authentication.
Every balance is derived from balanced ledger entries.
We never ask for or store wallet PINs or payment OTPs.
Ready to start collecting?
Apply for a merchant account. Pricing is set per merchant agreement — see the pricing page for details.