Gateway onboarding and what they ask for

Merchants tend to treat gateway onboarding as paperwork. It is closer to a credit application, and understanding what the provider is actually trying to establish makes the process both faster and cheaper.

The provider is not verifying that you exist. It is estimating how likely it is to lose money on you.

The documents to have ready

For a Malaysian company, the standard set is predictable.

Company registration documents confirming the legal entity, its registration number and its directors.

Identification for directors and shareholders, and often proof of address.

A company bank account in the same legal name as the applicant. A mismatch here is one of the most common causes of delay, and it is not negotiable — settlement goes to an account matching the merchant entity.

Business licence or permits where your category requires one.

A live website with your product range, prices, terms of service, refund and return policy, privacy policy and contact details visible. Providers check this, and an incomplete site is a routine rejection reason rather than a formality.

Recent financials or bank statements, particularly if you are asking for higher volume limits or a lower reserve.

Having all of it ready before you start is the single largest determinant of how quickly this goes, because each round of missing documents adds days.

What underwriting is actually assessing

Four risks, and every question maps to one of them.

Chargeback risk. How likely are your customers to dispute? Driven by your category, your delivery times and your return policy. See chargebacks on your own store.

Delivery risk. How long between payment and the customer receiving the goods? A long gap, a pre-order model or made-to-order goods all raise the amount the provider could be exposed to if you stopped trading tomorrow.

Volume and volatility. How much, how variable, and how large is your biggest single transaction. A store with occasional very large orders is a different risk from one with steady small ones.

Category. Some categories carry higher dispute rates or additional rules, and are priced and reserved accordingly.

None of this is about your integrity. It is about the shape of your business, and it is worth answering accurately rather than optimistically.

Why the answers you give shape your reserve

This is the part with lasting financial consequences.

The rolling reserve a provider applies, and the fee rate it quotes, both come out of that risk assessment. Understating your delivery times or your expected dispute rate to get approved faster tends to produce a worse outcome, because the provider adjusts once it sees your actual pattern — and adjusting upward mid-relationship is far more disruptive than starting at the right level.

The reserve matters more than merchants expect, because it is a permanent claim on working capital that grows with revenue. A percentage withheld on a rolling basis means a growing business always has a growing amount of its own money held — see payment gateway holds and reserves and settlement timing and your cash forecast.

So the negotiation worth having at onboarding is not only about the headline rate. Ask about the reserve percentage, the release schedule and the conditions under which either changes. Those terms affect your cash more than a small difference in fee.

The technical setup that follows approval

Approval is not the finish line. Three things still have to happen properly.

Credentials and environments. Test keys and live keys, kept separate, with the live ones held somewhere your team does not paste them into a chat message.

Notification endpoints, configured and verified, with signature checking enabled so you can prove a notification came from the provider. Then designed on the assumption that some notifications will be missed, arrive out of order or arrive twice — see gateway API or settlement file.

Settlement data access. Establish now, not later, how you will receive transaction-level settlement data and whether it contains a reference that joins to your orders. This is the thing that decides whether reconciliation can be automated at all, and it is much easier to ask during onboarding than after go-live — see the gateway reference that joins everything.

The timeline to plan around

Expect it to take longer than the provider's marketing suggests, and plan the sequence rather than the duration.

Document collection is the part you control, and it is where most delay actually happens. Underwriting is the part you do not control, and it stretches when documents are inconsistent or the website is incomplete. Technical integration and testing can happen in parallel with underwriting if you have test credentials, and asking for those early is worth doing.

The practical advice is to apply before you need it. A gateway application started because your current provider has become unworkable is an application made under time pressure, which is how merchants end up accepting terms they would otherwise question.

Common questions

What documents does a Malaysian payment gateway require?

Company registration documents, identification for directors and shareholders, a company bank account in the same legal name as the applicant, any licences your category requires, a live website showing products, prices, terms, refund policy and contact details, and recent financials or bank statements where higher limits are sought. Having the full set ready before applying is the main thing that shortens the process.

Why do payment gateways ask about delivery times?

Because the gap between payment and delivery is the window in which the provider carries exposure. Long lead times, pre-orders or made-to-order goods mean more customer money has been taken for goods not yet received, which raises the amount the provider could lose if the merchant stopped trading, and that assessment feeds directly into the reserve and the fee.

Can the reserve and fee rate be negotiated at onboarding?

They are both outputs of the risk assessment, so they respond to evidence rather than to argument. Accurate information about volumes, delivery times and dispute history, plus financials supporting the request, is what moves them. The reserve percentage, its release schedule and the conditions for changing either are worth discussing explicitly, because they affect cash more than a small fee difference.

What should be settled technically before going live?

Separate test and live credentials, verified notification endpoints with signature checking, and confirmed access to transaction-level settlement data containing a reference that joins to your own orders. The last is the one most often left until after launch, and it determines whether reconciliation can be automated at all.

Related: Malaysian payment gateways and how they actually differ · payment gateway holds and reserves · gateway API or settlement file