Payment Processing for Forex Merchants: Entity, Market and Funds-Flow Checks
A forex broker’s customer deposits, an introducer’s referral fees and a software company’s subscriptions need different payment arrangements. Start with the entity, the product and the money flow.
Inside this guide
Forex is not one merchant business model
What does the customer’s payment buy? For a forex broker, it may fund a trading account. For an introducer, the income may be a referral fee. For a software company, it may pay for analytics or a platform subscription. Calling all three forex merchants leaves the payment provider with very little to assess.
Start with the legal entity and the product it supplies. Then follow the payment: who pays, who receives it and whether the money belongs to the business or relates to a customer account. A familiar checkout does not turn a trading deposit into an ordinary software sale.
These distinctions affect the application, provider selection and reconciliation. They also help reveal questions that need regulatory or legal review before commercial terms are discussed. A broad statement that a provider accepts forex should be the beginning of that conversation, not the end.
Match regulatory evidence to the contracting entity
Record the legal entity that contracts with the customer, the products it offers, relevant regulator and permissions, and the markets it intends to serve. Match the website’s terms and disclosures to that entity. Group ownership or a shared brand does not make every associated company the same regulated counterparty.
The FCA’s CFD guidance covers retail products including rolling spot foreign exchange. It advises checking the actual contracting entity and warns about risks when customers are directed to similarly named overseas businesses. That is UK guidance for the stated products, not a conclusion about all forex activities or every jurisdiction. [1]
A September 2026 FCA release describes action against firms using UK-authorized status to make linked overseas operations appear more trustworthy. It reinforces the need to establish which entity actually supplies the customer’s service. [2] For other markets or an uncertain permission boundary, obtain appropriate specialist review. Neither a provider’s commercial indication nor a related company’s licence resolves the question automatically.
Trace deposits, withdrawals, revenue and settlement separately
Map the customer deposit from the payment method through the provider to its destination. Then map customer withdrawals as a separate flow, including who authorizes them, where the money comes from and what beneficiary checks apply. Identify the accounts used at each stage and the parties responsible for reconciliation.
Do not equate deposits with earned revenue. A broker’s processing throughput can be large while its fee or spread revenue is a much smaller amount. Nor is an outbound transfer automatically a refund of the original card payment. Ask the provider what mechanisms and conditions apply instead of assuming any incoming method supports all forms of outgoing payment.
Where an introducer, technology supplier or related company collects money, explain the contractual role and beneficiary. Unexplained third-party collection creates an additional question for the route. Avoid settling customer deposits to an unrelated operating company merely because that company already has a merchant account. The entire flow should be assessed by the appropriate provider and specialists before implementation.
Use a model-specific readiness matrix
Use the table below to describe each activity you actually carry out. A broker needs to explain the trading-account relationship and deposit and withdrawal flows. An introducer needs to show whether it only earns referral fees or also handles customer money.
For software, education and signals businesses, make the product and any connection to trading explicit. If customers pay for a course, what is promised? If they pay for software, does the business also operate or manage trading accounts? Currency conversion and transfer services need their own explanation of the money movement.
Check the customer journey against the application. A website selling education while the application describes only software creates a question to resolve. So does an introducer collecting deposits under an agreement that only permits referrals. Give reviewers the agreements and facts they need to establish the applicable permissions and processing scope.
| Model | Flow to explain | Question for review |
|---|---|---|
| Broker / CFD provider | Customer deposits and withdrawals around the trading account | Which entity, product and customer-market permissions apply? |
| Introducing business | Referral fees and any customer-money collection | Does the actual activity stay within the stated role? |
| Software / analytics supplier | Payment for tools and any linked services | Is it only software, or also trading/managed-account activity? |
| Education / signals business | Subscription, course or advice-related receipts | What exactly is promised, and what review does that require? |
| Currency conversion / transfer | Money sent, exchanged and delivered to beneficiaries | Which payment and financial-service structure is actually proposed? |
Check provider policies without extrapolating acceptance
Stripe lists investment and brokerage services among restricted financial activities requiring further review. Adyen’s restrictions differentiate merchant and platform/partner models and list financial-service activities with model-specific treatment. These are examples of provider-specific conditions; they do not establish that either provider accepts a particular forex merchant or deposit route. [3][4]
Ask for a response covering the exact entity, products, customer countries, payment methods and payout structure. Confirm whether the proposed service covers deposits, ordinary fee collections, withdrawals or only a technology component. A gateway integration does not itself establish an acquiring relationship for every flow.
Record the source and date for each capability and condition. Treat a statement such as financial services supported as a research lead, not a verified approval. If a country or model remains unconfirmed, keep the route conditional. Request clarification through the provider’s authorized process rather than trying to route around a restriction or remove material facts from the application.
Reconcile throughput before calculating cost or exposure
Take a business that receives $500,000 in customer deposits during a month, pays out $350,000 in withdrawals and earns $20,000 in service revenue. These are three different figures. The $150,000 difference between deposits and withdrawals is not automatically profit or cash available to run the business.
For illustration, a 3% processing charge on the incoming deposits would cost $15,000. A reserve of 10% of those gross deposits would retain another $50,000. Neither calculation establishes the customer liability, client-money position or amount available to fund withdrawals. Those need to be reconciled separately.
When comparing quotes, state the basis of each charge. Does it apply to deposits, outgoing transfers or earned fees? Add FX and other relevant charges to the correct flow. A proposal based on the wrong turnover figure can appear attractive while failing to price the service the business actually needs.
Make customer controls and reconciliation operational
Explain how the business establishes the customer relationship, detects inconsistent payer or beneficiary information, handles funding from third parties and investigates unusual activity. The exact requirements depend on the activity, market and service; this guide does not prescribe a universal KYC or AML programme.
For the proposed route, ask what information accompanies the transaction, what is screened by each party and which exceptions require review. Identify responsibility for customer complaints, refunds and disputes. A customer claiming a trading loss and one alleging an unauthorized card charge present different issues; maintain records that let the responsible team establish what actually happened.
Reconcile provider transactions to customer-account entries and bank movements using stable references. Handle pending, failed, reversed and duplicated events explicitly. A successful gateway response should not cause multiple credits if a notification is received twice. Keep the payment ledger distinct from the trading ledger while ensuring the two can be linked and reconciled. These are operational recommendations, not a determination of the firm’s regulatory obligations.
Test the route and plan for material changes
Agree an approved test covering deposit, decline, relevant authentication, reversal or refund, reconciliation and the permitted withdrawal process. Do not assume a successful inbound test proves that the outbound route is available. Confirm settlement account details and the treatment of currency conversion separately.
Plan for a change in customer market, entity, product or collection model. Those changes may invalidate an earlier scope confirmation even if the brand and software stay the same. Maintain the application version, provider response, relevant agreements and dates so the next reviewer can understand what was assessed.
Compare cash requirements under normal operation and a period of elevated withdrawals or reduced new deposits. Ask what happens if processing is paused while customers still need support. A backup provider can be useful only where it has separately assessed the actual business and flow; an unapproved connection does not provide credible continuity. Keep incident owners and escalation contacts available before moving material volume.
What it means to merchants
Prepare three things before requesting terms: an entity-and-market map, a clear product description and a diagram of deposits, withdrawals and settlement. Keep customer deposits separate from earned revenue in the financial information you provide.
Ask the provider to confirm the exact service it is considering. A rate for collecting software fees tells you little about the terms for accepting trading-account deposits. Likewise, a successful incoming payment does not establish that customer withdrawals are supported.
Use Core IQ to organize the private application and outstanding questions. Market permissions still need the appropriate review, and the provider must assess its own processing scope. The clearer those boundaries are, the more useful the commercial discussion becomes.
Sources
Sources checked on 31 October 2026.
Payment Guide helps you research the structure, understand the questions and prepare your next conversation.