About NaklaPay

We built the tool we kept rebuilding for clients.

NaklaPay is payment automation software made in Dhaka. We turn bKash, Nagad, Rocket and bank confirmations into verified orders — automatically, audibly and without ever touching your money.

4.2s

Median verification

৳0

Held by NaklaPay

99.98%

Match accuracy

2,400+

Workspaces

Why we exist

The last manual step in an online business.

Almost everything in a Bangladeshi online store is automated except the payment confirmation. The order arrives, the customer taps “send money”, and then a human being opens a phone, reads a message and marks the order paid. Do that forty times a day and mistakes are not a risk — they are a schedule.

We started as a small agency in Dhanmondi fixing exactly this for clients. The first version was a phone taped to a wall and a script that forwarded SMS to a spreadsheet. It worked, which told us the problem was not technical — it was that nobody had packaged the loop properly.

NaklaPay is that package: the SMS ingestion, the parser, the balance check, the pending queue, the checkout, the dashboard and the API. It runs as a hosted service or on your own server. The money never leaves your account, and the audit trail is yours to keep.

Built in Dhaka. Used across Bangladesh and by diaspora sellers abroad.

Principles

Four constraints we do not trade away.

These are the rules that decide what we build and what we refuse to build, regardless of what is easier.

Non-custodial, permanently

We will never hold customer funds. Money lands in your own bKash, Nagad, Rocket or bank account from the first day of the trial to your ten-thousandth order. That is a product constraint, not a policy we can change later.

The message is the source of truth

Every confirmation is traceable to a raw SMS or bank alert, the device that received it and the moment it arrived. Nothing is inferred into existence.

Local first, not local only

Bangladesh-first means Bangla QR, MFS balance checks and a checkout that works on a 3G connection. It does not mean accepting a worse developer experience, so the API is as careful as the UI.

Boring on purpose

Payments software should be the least exciting part of your day. We would rather ship a well-tested verification loop than a clever feature nobody can debug at 11pm.

Timeline

From a spreadsheet to 2,400 workspaces.

No funding round, no growth hacks. Just merchants telling other merchants that the confirmation queue finally disappeared.

  1. 2021

    An agency problem

    Our client work kept ending in the same screen: someone scrolling a bKash statement, matching TrxIDs to orders in a spreadsheet.

  2. 2022

    An internal tool

    We built SMS forwarding and a matcher for three clients. It removed an entire evening shift from their week.

  3. 2023

    A product

    Other merchants asked for it. We rebuilt it multi-tenant with balance verification and a pending-payment fallback.

  4. 2024

    A platform

    Hosted checkout, invoices, payment links and a public API. The first self-hosted licence shipped to a hosting company in Chattogram.

  5. 2026

    Now

    2,400+ workspaces run on NaklaPay. Some sell on a hosted checkout, the rest wire the API into their own storefront with our language guides.

See whether it fits your business.

Create a workspace with sample data, or talk to us about the way you collect today.