Payment Gateway and Automated Settlement: A Practical Guide
It's easy to assume that once a customer's payment goes through, the money is yours and the job is done. It isn't. Accepting a payment and confirming you actually received it — the right amount, net of fees, in your account — are two genuinely different problems, and the gap between them is where a surprising amount of revenue quietly leaks.
Getting this right comes down to two pieces working together: the payment gateway and the settlement reconciliation behind it.
Gateway versus settlement
The payment gateway is the part customers touch: it authorises and captures the payment at the point of sale or checkout. Settlement is what happens afterwards — the money moving from the processor into your bank account, on the processor's timeline, minus its fees. A transaction can be successfully captured today and not settle for a day or more, and the amount that lands is rarely the amount the customer paid, because fees come out in between.
Confusing the two is how businesses think they've been paid when they've only been promised payment. Knowing the difference is the start of controlling it.
The multi-rail reality
Customers in Malaysia pay across many rails — cards, FPX, DuitNow QR, e-wallets — and each one settles on its own schedule, with its own fees, reported through its own portal. The naive approach is to log into each portal, export a file, and stitch them together in a spreadsheet to work out what really arrived. It's slow, it's manual, and it's precisely the kind of reconstruction where a missing settlement or an unexplained fee slips past unnoticed.
The more rails you accept, the worse this gets — and the more it matters that something other than a tired human is checking the maths.
Automating reconciliation — and what good looks like
Automated settlement reconciliation closes the loop. It takes what the gateway captured and matches it against what actually settled in the bank, account by account, net of fees, flagging anything that doesn't reconcile — a transaction that captured but never settled, a fee that doesn't match the agreed rate, a payout that's short. Every rail lands in one record, and the exceptions surface themselves instead of hiding in a spreadsheet.
What good looks like is simple to state: at any moment, you can answer "did we receive what we sold," by rail, with confidence, and finance is reviewing exceptions rather than rebuilding the picture from exports. That's how we integrate payments at Appcellen — gateway and settlement wired into the finance system so reconciliation is continuous and trustworthy, not a month-end act of faith.
