Choosing a payment gateway for your Malaysian store

Most Malaysian merchants pick a payment gateway on two criteria: will my customers use it, and what does it cost per transaction.

Both are reasonable. Neither is the one that will occupy your finance team for the next three years.

The gateway you choose also determines the shape of the money coming back to you — whether it arrives per order or in batches, how long it holds before releasing, what it deducts before you see it, and how legible the report explaining all that turns out to be. That is the part nobody evaluates, and it is the part you live with.

What Malaysian customers actually reach for

The market has settled into four broad habits, and most stores end up serving more than one.

Online banking. FPX is the default for a great many Malaysian buyers, particularly for larger baskets, and Billplz is how a lot of businesses accept it. Customers trust it because it is their own bank's screen.

Wallets. GrabPay and its peers are everyday money — small amounts, high frequency, and the same wallet the customer used for lunch. Wallet payments tend to settle in batches, which matters more than it sounds.

Cards. Stripe and equivalents cover card payments and anything international. Cards bring the widest reach and the most familiar dispute mechanics.

Instalments and cashback. Atome lets a customer spread payment while you record the sale in full. ShopBack brings the customer to you at a cost that behaves like a marketing spend but arrives as a deduction on a settlement.

You do not choose one of these so much as decide which combination is worth supporting, because each one you add is another checkout option and another settlement stream.

The four questions that actually matter

Conversion and per-transaction cost are the obvious ones. These four are the ones that surface later.

Does it settle per order or in batches? Per-order settlement is rare and easy. Batched settlement means one deposit covers many orders, and no line in your bank statement will ever correspond to a sale again.

How long does it hold? Settlement delay is working capital. A gateway that releases in two days and one that releases in seven are different products for a business buying stock on credit terms.

What comes out before you see it? Transaction fees, obviously. Also refunds, chargebacks, reversals and occasionally a rolling reserve. Each is legitimate. Each also has to be attributed to the order it came from, or your margin is fiction.

What does the report look like? This is the question nobody asks and everyone regrets. Some gateways produce a settlement file where each line ties cleanly to an order reference. Others produce a total and a date. The difference is measured in days per month for whoever does your reconciliation.

Why "just use one" stops being advice

The tidy recommendation is to run a single gateway and keep everything simple. It is good advice for about a year.

Then you notice the basket-abandonment on card-only checkout among customers who wanted FPX. Or a supplier of yours starts offering instalments and your conversion drops. Or you open a physical counter and the wallet everyone already has becomes the fastest way to take money.

So you add a second. Then a third. And now you have three settlement streams on three schedules with three fee structures and three report formats, and the person reconciling them has become a specialist in something you never intended to hire for.

This is normal. It is not a mistake. What is a mistake is letting the reporting burden decide which payment methods your customers are allowed to use, because that is a commercial decision being made by an operational constraint.

The reconciliation question, asked early

The useful reframe is this: a gateway is not just a way to take money, it is a source of financial data you will be reconciling for as long as you use it.

Which means the question to ask before signing up is not only "what does this cost per transaction" but "what will it cost me per month to explain what this paid me".

If the answer is that somebody downloads a report and matches it by hand, that cost scales with your order volume, and it scales badly. If the settlement data comes in automatically and matches itself against the orders it belongs to, the cost stays roughly flat as you grow. That is the whole argument for connecting gateways rather than exporting from them, and it is why SmartB reconciles orders against whichever gateways you run rather than requiring a particular one.

Your gateway mix should be decided by what your customers want to use. Nothing else.

Two things are worth settling before you sign rather than afterwards: what the settlement data actually contains, since that decides whether reconciliation can be automated at all — see gateway API or settlement file — and what the arrangement costs in total once fees, settlement delay and reserve are included — see the true cost of accepting a payment.

What to actually do

Start with your customers, not your accountant. Support the payment methods your buyers reach for. Everything else is downstream of revenue.

Then ask each provider for a sample settlement file. Before you sign. A provider that cannot show you one is telling you something.

Check the settlement timing against your cash cycle. If you pay suppliers on 30 days and your gateway releases on seven, fine. If it holds for fourteen and you are buying stock weekly, that is a working capital decision, not a payments one.

Assume you will end up with more than one. Design the reconciliation for two or three from the start, and adding the third stops being an event.

Common questions

Is it bad to run several payment gateways at once?

No, and most growing Malaysian stores end up doing it, because customers split across online banking, wallets, cards and instalments. The cost is not the gateways themselves. It is having several settlement streams that nothing joins back to your orders.

Which gateway is cheapest?

Rates change and depend on your volume and mix, so ask providers directly rather than trusting a figure in an article. The more useful comparison is total cost including the reconciliation effort, because a slightly cheaper rate on a settlement report nobody can read is not cheaper.

Why does my gateway deposit never match a day's sales?

Because it is a batch, usually covering a period that does not align with your trading day, net of fees and any refunds or chargebacks that landed in the same window. It is not an error. It just means the deposit has to be decomposed rather than matched.

Do I need to reconcile gateway settlements if my accountant handles it?

Somebody has to, and the question is when. Reconciled monthly by an accountant from exported files, problems surface weeks later. Reconciled continuously, a missing settlement or an unexpected deduction is visible while it can still be queried.

The decision behind the decision

Choosing a gateway looks like a checkout question. It is really a decision about what your finance function will be doing every month for the next several years.

Pick for your customers. Then make sure the money each one sends can be traced back to the orders it came from, whichever combination you end up running.