17 June 2026

What belongs in a Malaysian merchant’s gateway application file

Rows of labelled archive files on metal shelves

Most of the packs that reach our desk in Kuching are overstuffed and still incomplete. They contain a pitch deck, a brand guide, and a screenshot of a storefront. They omit the twelve months of current-account statements that a gateway underwriter will open first.

If you are a Malaysian merchant applying to a payment gateway platform, the file is a financial document. The platform is deciding whether it can settle card, e-wallet, or alternative-method volume into your account without taking on a dispute book it cannot see. That decision is made from papers, not from a conversation with sales.

Start with the bank. Current-account statements for the trading entity, in full, for the period the form requests — often twelve months, sometimes six for a younger company. Cropped PDFs and “summary” exports are not statements. If the entity changed banks, include both, and write one sentence that says so.

Then the processing history. If you already take cards or e-wallets through another gateway, an acquirer, or a marketplace, those payout reports belong next to the bank credits. A reviewer will try to match them. If you have never processed, say so, and do not paste a projection where a history is asked for.

Ownership and authority papers sit behind the money. SSM extracts, director lists, and the resolution that authorises the person who will sign the gateway contract. Beneficial-ownership charts that stop at a holding company in Labuan or overseas will be sent back. Name the natural persons.

Leave out what does not help the reading: mood-board photography, unrelated group accounts, and draft contracts with other vendors. Extra paper is not diligence. It is noise that hides the month where refunds exceeded sales.

Send a file inventory