Getting paid as a freelancer in Bangladesh (bKash, Nagad, Rocket)

If you freelance from Bangladesh, you already know the daily friction: your client wants to pay from bKash, your invoicing tool only understands cards, and you end up texting a wallet number and screenshotting confirmations like it's 2014. The good news is that mobile money in Bangladesh is now first-class — bKash, Nagad, and Rocket can sit on a proper invoice, settle into your own account, and reconcile themselves. This guide walks through how that actually works, what to set up once, and how to stop chasing screenshots for good.

Why one gateway beats three wallet numbers

The biggest mistake Bangladeshi freelancers make is treating bKash, Nagad, and Rocket as three separate things a client has to navigate. From your side, they aren't. The local payment gateway SSLCommerz aggregates all of them — plus local cards — behind a single checkout. You connect SSLCommerz once; your client lands on a page, taps the wallet they already use, and pays. You don't maintain three integrations, and you don't ask the client which apps you 'accept'.

In Kliently, SSLCommerz is one of six payment rails (alongside Stripe, Razorpay, PayPal, Wise, and manual bank transfer). Enable it, and a Pay button for bKash/Nagad/Rocket appears on every invoice and in your client portal. The client picks their wallet at checkout — you never have to.

Set it up once: connecting SSLCommerz

1. Register as an SSLCommerz merchant (a sole-proprietor freelancer can do this; you'll provide ID, a bank account, and basic business details).

2. Get your store credentials from the SSLCommerz dashboard.

3. Add them to your Kliently payment settings and enable SSLCommerz as a rail.

4. Send yourself a test invoice and pay it with your own bKash to confirm the flow end-to-end before you bill a real client.

The one-time admin is the price of never doing manual reconciliation again. Once it's connected, every new invoice can take wallet payments with zero extra steps.

The money goes to your account, not ours

This matters, so it's worth being blunt: Kliently is not in the middle of your money. SSLCommerz settles funds into the bank account tied to your own merchant profile, on SSLCommerz's normal settlement schedule. Kliently records that the invoice was paid and reconciles your books — but the cash never routes through us. That's the same philosophy across every rail: your Stripe, your PayPal, your SSLCommerz. You own the money path.

Where you live shouldn't decide whether your tools take your money seriously. A Dhaka designer billing a Dhaka client should get the same clean experience as anyone in San Francisco.

Send a pay link, not wallet digits

When you build an invoice in Kliently, the client receives a link — not a string of numbers to copy. They open it, see the line items in BDT, tap Pay, choose bKash (or Nagad, or Rocket), and confirm in the app they already trust. The difference is more than convenience:

• Auto-reconciliation — the moment the payment clears, the invoice flips to paid. No manual marking, no 'did that BDT 8,000 come in?' at month-end.

• Smart reminders stop on payment — before-due and after-due nudges go out automatically and shut off the instant the client pays.

• A clean record — every payment is tied to its invoice, so your books and your client's books agree.

Billing local and overseas clients from one workspace

Plenty of Bangladeshi freelancers serve both a local market and clients abroad. You don't need two systems. The same invoice can offer SSLCommerz for a Dhaka client and Stripe or PayPal for a client in London — each pays the way that's natural for them, and you watch one dashboard. Kliently syncs 18 currencies daily, so you can bill a local client in BDT and an overseas client in USD without doing exchange math by hand.

If most of your income is cross-border, it's worth reading our companion guide on cross-border payments to decide which rail keeps the most money in your pocket.

A few practical habits

• Set clear terms up front — put your payment methods and due date into the proposal so there are no surprises at invoice time. A proposal that's accepted with the terms attached saves an awkward conversation later.

• Keep your JSON export — your data is yours; a one-click export means your payment history is portable, never locked in.

• Test before a big invoice — currencies, fees, and settlement timing are easiest to verify on a small test payment to yourself.

Mobile money is the default way Bangladesh moves cash — your invoicing should treat it that way. Wire SSLCommerz in once, send links instead of digits, and let the wallet your client already opens every day become the way they pay you. See how all six rails fit together on the payments overview, or start free on the pricing page.