Forex Merchant Account vs Payment Gateway: What Brokers Actually Need

Brokers frequently ask for "a forex merchant account" when what they need is a working combination of an account that can hold and settle funds and a gateway that can process transactions. The two are related but distinct, and confusing them leads to procurement decisions that only reveal their gaps after go-live.

This article explains both, how underwriting typically works for trading-related businesses, and how to structure the relationship sensibly. It is educational rather than legal or financial advice; requirements differ by jurisdiction and by provider.

The distinction in one paragraph

A merchant account (or settlement account) is where funds land and from which they are paid out. It exists in the regulated financial system and carries the commercial relationship, the settlement cycle and any reserve arrangement. A payment gateway is software: it routes and processes individual transactions and reports their outcome. You can have a gateway without an account of your own, and you can have an account with no gateway attached — neither situation is useful on its own.

For a fuller description of the gateway side, see what is a forex payment gateway.

What a merchant account provides

• A place for settled funds in one or more currencies.
• A settlement cycle — daily, T+1, weekly, or on negotiated terms.
• A fee arrangement, which may include per-transaction pricing, monthly minimums, chargeback fees and FX spread.
• A risk arrangement, which for higher-risk categories often includes a rolling reserve: a percentage of processed volume held for a defined period.
• A contractual counterparty responsible for compliance with scheme and regulatory rules.

Why underwriting is stricter for trading businesses

Providers underwrite the business, not just the transaction volume. For a trading-related applicant they typically examine:

• Corporate structure — entity, ownership, ultimate beneficial owners, group relationships.
• Licensing and regulatory position in each market where clients are accepted.
• Client geography and whether any of those markets restrict the product.
• Flow of funds — where client money is held, how it moves, and how segregation works if required.
• Historical processing data — volumes, average ticket size, refund and chargeback history.
• Website and client-facing terms — risk warnings, refund policy, withdrawal terms, contact details.
• AML and KYC programme — policies, screening tools, escalation and record-keeping.

Applications rarely fail because the business is unacceptable. They usually stall because documentation is incomplete or inconsistent between documents. Preparing a clean pack in advance is the single highest-leverage thing an applicant can do.

A practical document checklist

• Certificate of incorporation and current corporate register extract
• Ownership chart and UBO identification documents
• Any licences held, with the issuing authority and scope
• Recent bank statements and, where available, processing statements
• AML/KYC policy and named compliance contact
• Description of the client onboarding flow, including verification steps
• Terms of service, privacy policy and risk disclosure as published

Reserves, limits and settlement terms

Higher-risk categories commonly attract three commercial mechanisms:

• Rolling reserve — a percentage of volume retained for a fixed period, released on a rolling basis, to cover future disputes or reversals.
• Volume caps — monthly or daily ceilings, often raised gradually as history builds.
• Extended settlement — a longer delay between processing and payout.

These are negotiable over time and usually improve with a clean processing record. What matters operationally is modelling them in your treasury plan from day one: a reserve plus extended settlement can lock up a meaningful share of working capital.

How the pieces fit together

A typical structure looks like this:

1. The client portal presents payment methods.
2. The gateway routes each transaction to a provider that supports the method.
3. The provider processes the payment and accumulates funds.
4. Settlement moves net funds into the merchant or settlement account.
5. Payouts to clients are executed from an account funded for that purpose.
6. The broker's internal ledger records everything and drives reconciliation.

Note step 5. Collection and payout are often funded and reported separately, and a common operational failure is treating them as one pool. Payout float needs to be planned explicitly, particularly where settlement is delayed.

Local acquiring and local settlement

In markets where domestic payment methods dominate, funds may settle locally in local currency before being repatriated. That introduces additional questions:

• Which entity is the recipient of local settlement?
• What documentation supports repatriation, and what timelines apply?
• Where does currency conversion occur and at what rate?
• What reporting obligations attach to the local flow?

Our overview of cross-border payment solutions describes how local collection and consolidated settlement are usually structured.

Common mistakes

• Treating the account and gateway as one purchase and discovering later that payouts, currencies or reporting are missing.
• Underestimating reserve impact on cash flow.
• Presenting inconsistent documentation — a website description of the business that does not match the application form is a frequent cause of delay.
• Single-account dependency, which leaves no continuity if terms change.
• Not reading the termination clause, including how in-flight funds and reserves are handled on exit.
• Ignoring reporting formats until the finance team tries to reconcile the first month.

Questions worth asking a provider

• Which entity holds settled funds, and in which jurisdiction?
• What is the settlement cycle and currency, and can it be changed later?
• Is a reserve applied, at what rate, and for how long?
• Are payouts supported, and are they funded from the same balance?
• What is the full fee schedule, including FX, chargeback and payout fees?
• What reporting is available, in which formats, and via API?
• What are the notice periods and conditions for termination or repricing?
• Which markets and methods are in scope, and what is the process for adding more?

Where PayEurasia fits

PayEurasia focuses on collection and payout rails in Bangladesh, India, Pakistan and Nepal, combining local methods with consolidated settlement and reconciliation reporting. The merchant onboarding page sets out what is required at application stage, and payment infrastructure describes the ledger, routing and reporting layers behind the API.

Frequently asked questions

What is a forex merchant account?

It is an account arrangement that allows a trading business to receive settled funds from payment processing and, in many cases, fund client payouts. It carries the commercial terms — settlement cycle, fees and any reserve — and the compliance relationship with the provider.

Do I need both a merchant account and a payment gateway?

You need both functions. Whether they come from one supplier or several depends on the markets you operate in and the coverage each supplier offers.

Why do providers ask for so much documentation?

Because they carry regulatory and scheme obligations for the businesses they onboard. Corporate, licensing, flow-of-funds and AML documentation allows them to assess and evidence that the relationship is within their risk appetite.

What is a rolling reserve?

A portion of processed volume held back by the provider for a defined period before being released, used to cover potential future disputes, refunds or reversals. It is common in higher-risk categories and is usually expressed as a percentage held for a number of days.

Can a broker use more than one provider?

Yes, and many do. Multiple providers offer redundancy against outages, volume caps and policy changes, and allow traffic to be routed to whichever route performs best for a given market and method.

How long does approval usually take?

It varies widely by provider, market and completeness of documentation. A well-prepared application pack shortens the cycle materially; incomplete or inconsistent documentation is the most common reason for delay.

Sources and further reading

• Financial Action Task Force — international AML/CFT standards
• Bank for International Settlements, CPMI — payment system publications
• Wolfsberg Group — financial crime principles and guidance

Author: PayEurasia Payments Team — payment operations and infrastructure specialists working on collection and payout rails in South Asia. Last reviewed: 9 August 2026.