Malaysian payment gateways and how they actually differ

Choosing a payment gateway in Malaysia is usually presented as a rate comparison, and the market has consolidated enough to make that comparison look simple.

Rates matter least of the things that will affect you. Two gateways charging near-identical percentages can differ enormously in how much finance work they create, and nobody discovers that until after integration.

Who is actually in the market

The landscape has shifted. iPay88 and eGHL — for years two separate names — now sit together under ADAPTIS, the payment suite from NTT DATA Payment Services. Fiuu, previously Razer Merchant Services, positions around bridging online and in-person sales. Billplz is known for depth on Malaysian bank rails, particularly FPX. Alongside them are senangPay, Curlec, and Stripe, which operates in Malaysia and brings a developer experience many teams already know.

For choosing between them on commercial terms, see choosing a payment gateway for your Malaysian store. What follows is what changes on the finance side.

The four differences that decide your workload

1. Settlement timing, and whether it is predictable

Some gateways settle daily, some on a working-day cycle, some weekly. What matters more than speed is consistency: a predictable cycle can be forecast and reconciled on a schedule, while an irregular one forces someone to check.

Ask specifically what happens over a weekend, over a public holiday, and during a sale period when volume spikes. Those are the three moments the answer usually changes.

2. Whether the payout is decomposable

The single most important question, and the one least often asked.

When money lands, can you get a record showing exactly which transactions made up that deposit, with fees itemised per transaction? Or do you get a total and a date?

With decomposition, reconciliation is mechanical and can be automated. Without it, somebody rebuilds the payout by hand from transaction records, every time.

Two gateways with identical rates differ by hours of monthly work on this alone.

3. Fee granularity per payment method

FPX, cards, e-wallets and buy-now-pay-later cost different amounts. Sometimes very different amounts.

The question is whether the settlement data tells you which method each transaction used and what it cost, or whether it reports one blended figure. Blended reporting makes per-order and per-product margin impossible to calculate properly, because your product mix and your customers' payment preferences are not evenly distributed.

4. What the API returns, and when

Some gateways expose a modern API with settlement endpoints. Some provide a scheduled file. Some offer a portal you download from by hand.

A well-structured file processed automatically beats a shallow API returning totals — see why integration depth beats feature count. What matters is whether the reconciliation completes without a person, not the transport.

Also ask when settlement data becomes available relative to the money. A payout arriving before the report explaining it is a normal and irritating gap.

The Malaysian specifics that catch people out

FPX is a bank transfer, not a card. Behaviour differs — different failure modes, different timing, a different fee structure, and no chargeback in the card sense. If FPX is a large share of your volume, and for many Malaysian stores it is, the card-shaped assumptions in most guidance do not apply.

E-wallets each behave differently. Touch 'n Go, GrabPay, Boost and ShopeePay may reach you through the gateway or directly, and settlement timing can differ from cards on the same gateway.

Buy-now-pay-later is a different arrangement. The provider pays you and takes the credit risk, for a higher fee. The customer's instalments are between them and the provider. Your accounting concerns the settlement you receive, not the instalment plan.

Shopify adds its own fee. Independent of the gateway and invisible in gateway data — see the Shopify third-party gateway fee explained.

The questions worth asking before signing

• Can I get a settlement report where every payout decomposes to individual transactions with fees itemised?
• Is the fee shown per payment method or blended?
• What is the settlement cycle, and what happens on weekends, holidays and during peak volume?
• Is settlement data available by API, scheduled file, or manual download only?
• How are refunds represented — is the original processing fee returned?
• How do chargebacks appear, and with what notice?
• What holds or reserves apply, and under what conditions?
• Can I get historical settlement data for migration, and how far back?

Ask for a sample settlement file during evaluation and open it. An hour spent on a real file tells you more than any specification.

Why this matters more when you run several

Most growing Malaysian stores end up with two or three gateways, because customers reach for FPX, cards and e-wallets in different proportions and coverage differs.

Every difference above then multiplies. Two settlement cycles, two report formats, two fee structures, two reference schemes, all landing in one bank account. See running more than one payment gateway.

This is not an argument for one gateway — restricting payment methods costs conversion, which costs more than the reconciliation. It is an argument for choosing the second one with the reconciliation question asked upfront rather than discovered later.

Common questions

What matters most when comparing Malaysian payment gateways?

Not the rate, which tends to be broadly similar across providers, but whether each payout can be decomposed into the individual transactions that made it up with fees itemised per transaction. That single capability determines whether reconciliation can be automated or has to be rebuilt by hand every settlement cycle.

Who are the main payment gateway providers in Malaysia?

iPay88 and eGHL now sit together under ADAPTIS, the payment suite from NTT DATA Payment Services. Fiuu, formerly Razer Merchant Services, positions around bridging online and in-person sales, Billplz is known for depth on Malaysian bank rails including FPX, and senangPay, Curlec and Stripe also operate in the market.

How is FPX different from card payments for accounting?

FPX is a bank transfer rather than a card payment, so it has different failure modes, different settlement timing, a different fee structure and no chargeback in the card sense. Since FPX is a large share of volume for many Malaysian stores, guidance written around card behaviour frequently does not apply.

Why does running several gateways multiply the work?

Because every difference between them compounds. Two or three gateways mean several settlement cycles, report formats, fee structures and reference schemes, all paying into the same bank account where only the narration distinguishes them. Restricting payment methods is usually the wrong fix, since lost conversion costs more than the reconciliation does.

Related: choosing a payment gateway for your Malaysian store · running more than one payment gateway · how to read a payment gateway settlement report