Payment Gateways: How Onboarding Works

A payment gateway is the bridge between your checkout and the banks that actually move money. Onboarding looks like a form, but it is really a risk assessment: the provider is deciding whether it wants to stand behind your orders before it lets you take payments. Understanding what that decision needs is the fastest way through it, and it saves the frustration of an application that stalls on a missing document.

The process is not designed to be difficult. It is designed to be careful, because the provider carries part of the loss when a buyer disputes a payment. A store that arrives with clean paperwork, a working website and a clear product description moves quickly, while a vague application moves slowly and may be declined for reasons the seller never sees.

What a Gateway Actually Does

A gateway moves payment information between your store, the buyer's bank and your bank, and it returns a yes or a no within seconds. Depending on how it is set up, it may also hold funds briefly, handle refunds and pass disputes back to you. It helps to keep three roles apart: the gateway, which takes the payment, the merchant account, which receives and settles the money, and the provider that bundles both. You will meet all three names during onboarding.

The Documents Usually Requested

Most providers ask for a similar core set. Expect to supply proof of your business, such as a registration or incorporation document, a tax identifier, and the bank account details for settlement. They will usually want identity and address proof for the owner or a director, a working website or app link, a plain description of what you sell, and a visible refund and contact policy. The exact list varies by provider and by market, so confirm it before you start uploading, because a partly complete application is the slowest kind.

Why Advertised Pricing Needs Reading Twice

Pricing models differ, and the headline figure rarely tells the whole story. Some providers charge per transaction, some add a monthly or platform fee, and some price by payment method, by card type or by currency. Settlement timing, holds and reserves can also sit outside the headline rate. There is no safe way to compare from memory, so read the current terms, work out what a typical order would actually cost, and ask what is excluded from the quoted price.

Settlement: Where the Money Goes

After a payment is authorised, the provider captures it and batches the day's transactions for settlement. The funds are paid into your nominated account on the provider's schedule, less the agreed fees and any reserve the provider is holding. A rolling reserve means a slice is held back for a period against future disputes. The mechanics are standard, but the schedule, the reserve and the thresholds are set by the provider, so check the provider's current terms rather than assuming a fixed cycle.

Risk Reviews, Holds and Reserves

An account can be reviewed after launch as well as before. A sudden jump in order volume, a spike in disputes or a mismatch between what you said you sell and what buyers receive can all trigger a hold. This is normal risk management rather than an accusation, and it is easier to handle if your descriptions, delivery times and policies match the application. Keep the provider informed when your business changes materially, because a surprise is what turns a routine review into a freeze.

• Have business registration, tax and bank details ready before applying.
• Publish a clear product description, contact page and refund policy first.
• Make sure the website or app actually shows prices and completes a test order.
• Check settlement timing, reserves and dispute fees in the current terms.
• Keep your stated business activity and your real activity aligned.

How Chargebacks Touch Onboarding

The dispute process is part of the same relationship. When a buyer asks their bank to reverse a payment, the provider passes the case to you and asks for evidence within a deadline. The paperwork you gathered at onboarding, plus your order records and delivery proof, becomes the material you use to answer. A store that keeps good records from day one finds disputes manageable, while one that cannot show what was sent and when will lose them by default.

Questions to Ask Before You Commit

Write a short list and get answers in writing. Ask which payment methods are supported and whether they can be switched on later, how and when funds settle, what reserves or holds may apply, how disputes and refunds are handled, what each costs, and how support is reached when something breaks. Compare the answers against a normal month of your own orders rather than against a comparison site, and re-read the terms whenever the provider changes them.

Authentication and Fraud Checks

Most providers add an authentication step for card payments, where the buyer confirms the payment with their bank. It shifts some fraud liability and reduces unauthorised transactions, at the cost of an extra step in checkout. Work out where that step sits in your flow, test it on a phone, and make sure a failed authentication gives the buyer a clear way to try a different method rather than a dead end.

Onboarding is best treated as part of running the store rather than a hurdle before it. Gather the documents, publish honest pages, understand how and when money settles, and keep records that answer a dispute. Do that, and the gateway becomes what it should be: plumbing that you set up once and then stop thinking about.