How wallet top-ups work: bKash, Nagad and card

Every order is paid from a balance rather than a checkout. There is a practical reason, and it is not to hold on to your money.

Why a wallet rather than per-order payment

SMM orders are frequently tiny — a few taka each, several a day. Routing each one through a payment gateway would cost more in transaction fees than the order is worth, and would put you through a payment page every single time. You top up once and order in one click after that.

It also makes the API usable. A reseller placing four hundred orders a day cannot be redirected to a payment page for each one; the balance is what makes automated ordering possible at all.

What we never see

Card numbers, CVVs, PINs and bKash passwords never touch our servers. The gateway collects them on its own page, under its own certificate, and tells us only whether the payment succeeded and for how much.

That is also why we cannot look up your card when something goes wrong — we do not have it, and a panel that offers to is a panel to leave. See the privacy policy for what we do hold.

Every top-up is verified server to server

A browser arriving back with "success" in the URL proves nothing; anyone can type that address. Each payment is confirmed directly with the gateway before a balance moves, and the amount that was actually paid is checked against the amount that was requested.

The deposit row is also locked while it is being credited, so a success redirect and a gateway notification arriving at the same moment cannot credit you twice. That protects both sides, and it is the sort of thing you only notice when a panel does not have it.

The three methods

• bKash — tokenized checkout. Clears in seconds; the balance is there before you switch back to the tab.
• Nagad — the same experience through Nagad's own payment page.
• Card and net banking — through SSLCommerz, which covers Visa, Mastercard, Amex and the local banks. Slightly slower to confirm, and useful when you want to top up a larger amount at once.

A method only appears on the Add Funds page once its credentials are configured, so what you see is what actually works.

If the money left but the balance did not arrive

Do not pay again. Open a support ticket with the transaction ID and the exact amount.

The usual cause is a callback that never landed: the payment succeeded on the gateway's side and the notification did not reach us. The transaction ID lets us match it and credit the deposit manually. Duplicate payments are traceable and do get credited, but paying twice makes the whole thing slower to resolve, not faster.

Currency, and why you see two numbers

Prices are held in US dollars because that is what the supplier bills in. Holding the catalogue in one currency and converting for display means an exchange-rate move can never quietly eat the margin on a service, and your balance is never re-valued behind your back.

You enter a top-up in dollars and see the local equivalent before you confirm. The gateway charges that local amount, and the exact rate used is recorded on the deposit — so what you paid and why is never in doubt afterwards.

The wallet is credit, not a bank account

Balance is spendable on services here. It is not withdrawable as cash and it cannot be transferred to another account or sent back to your bKash. Top up what you intend to spend rather than parking money in it. The refund policy states this plainly, and it is worth knowing before your first large deposit rather than after.

Why the balance is in one currency and the charge in another

Your wallet is denominated in the currency the catalogue is priced in, and your bank is charged in yours. Both numbers are shown before you confirm, and both are stored on the deposit afterwards.

This trips people up when the rate moves between two top-ups: the same $5 costs slightly different local amounts a fortnight apart. That is the exchange rate doing what exchange rates do, not a fee appearing. The rate applied to your deposit is recorded on the deposit row, so any two top-ups can be compared directly rather than argued about.

Nothing in your balance is ever re-valued afterwards. Money credited stays credited at the amount credited, whatever the rate does later.

Minimum deposits, and why they exist

Every panel sets a minimum top-up, and it is not greed. Gateway fees have a fixed component, so a very small deposit can cost more to process than it is worth. A sensible minimum sits low enough that a new customer can try the panel without committing, and high enough that the transaction is not a loss.

If a minimum looks absurdly high for the prices on the list — a few taka per thousand units, but a four-figure minimum deposit — that is usually a configuration mistake rather than a policy, and it is worth asking about rather than assuming.

Reading your transaction history

Every movement is a row: deposits in, order charges out, refunds back in, and any manual adjustment. Each carries a source and a description, and the balance after it. Two habits make this useful rather than decorative:

• Check the balance-after column when something looks wrong. It tells you the order things actually happened in, which is not always the order you remember.
• Match refunds to orders. A refund row names the order it came from, so a partial delivery and its credit can be read as one event.

Failed payments and what they cost

A payment that fails at the gateway costs you nothing — no balance moves and no deposit is created. What does happen occasionally is a payment that succeeds on the gateway and fails to notify us, which looks identical from your side. The difference is your bKash or bank statement: if the money left, it was the second case, and the transaction ID is all we need to fix it.

Take the habit of screenshotting the confirmation on any large top-up. It takes a second and it turns a ten-message conversation into a one-message one.

Refunds land back in the wallet

When an order is cancelled or partly delivered, the refund goes to your balance, not back to your card. That is how it can be instant and automatic — there is no gateway reversal to wait on, and no three-to-five working days. Every movement, in or out, appears in your transaction history with the reason attached.

No comments yet — be the first.