Quick answer: verify the money flow before comparing fees
A forex broker should choose a payment service provider by checking the contracting entity and permissions, written acceptance of its business, client-fund arrangements, settlement and reserves, refunds and disputes, reconciliation, and exit arrangements. A lower processing fee cannot remedy an incompatible service. A balance displayed in a dashboard is not necessarily settled cash available for client withdrawals. Make the decision using documented commitments and tested evidence, not a sales assurance.
Last verified: 13 October 2026. This is general information and an operational review framework, not legal advice or a promise of payment acceptance. UK and European examples apply within their respective regimes. The comparison tools, cash-flow illustration and test plan below are planning recommendations, not universal regulatory requirements.
Distinguish the bank, payment institution, EMI and gateway
PSP is an umbrella description, not a single worldwide licence. One brand may combine a gateway, acquiring, an electronic wallet and payouts in the same interface while different entities contract for, execute or hold funds for each service. Assess the product-level arrangements rather than checking only the group’s parent company.
| Role | What to establish | Unsafe assumption |
|---|---|---|
| Bank | Account provider, legal account holder, permitted use and currencies | A PSP’s partner bank is also the broker’s direct account provider |
| Payment institution | Specific payment permissions, territory and holding arrangements | A payment permission covers any banking or investment service |
| Electronic money institution | Issuance, redemption, payment services and protection terms | Electronic money has the same legal character as a bank deposit |
| Acquirer or payment aggregator | Merchant identity, upstream acquirer, settlement and dispute responsibilities | The front-end brand has the same role in every country |
| Technical gateway | Data transmission, integration and the actual funds-handling provider | A checkout interface demonstrates permission to hold funds or acquire payments |
Record who supplies the software separately from who takes responsibility for payments and money. A supplier may perform several roles or only one part of the chain. Verify each role against the contract, applicable permissions and actual money flow rather than inferring it from a product name.
Gate one: verify the entity, permissions and contact details
Obtain the proposed contracting entity’s full legal name, company number, regulatory reference, address, official website and service schedule. Independently access the regulator’s register to check current status, relevant permissions and restrictions. Confirm the relationship through independently verified contact details rather than relying on a screenshot or link supplied by a salesperson.
For a UK provider, use the FCA Financial Services Register. For EU and EEA payment and e-money institutions, the EBA central register helps identify the institution, but EBA states that this register itself confers no legal rights. Check the relevant national authority’s record as well. A parent’s authorisation does not establish the subsidiary’s permission.
Record each review as passed, evidence outstanding, not applicable or incompatible, with an owner and verification date. Trace agents, branches and outsourced functions to the responsible institution. Do not turn the exercise into a weighted score in which cheap pricing cancels out a failed permission check.
Gate two: obtain written acceptance of the actual brokerage
“We support financial services” is not acceptance of your particular business. Give each candidate the same description of the broker’s licence and conditions, instruments, customer types, target markets, marketing channels, expected monthly volume, average transaction and deposit-to-withdrawal mix. Ask which entities, domains, countries, currencies and payment methods are accepted and which still require approval.
- Separate operating expenditure, client deposits, client withdrawals, refunds and payments to liquidity providers.
- Match the checkout merchant name and statement descriptor to the broker’s customer-facing contractual identity.
- Explain introducing brokers, white labels, affiliates and intermediate payment providers in the chain.
- Identify changes in volume, markets or products that require renewed acceptance before implementation.
Do not conceal forex or CFD activity or route it through an unrelated merchant identity. A PSP’s willingness to process transactions does not determine whether the broker may solicit the underlying customers. Review the market and licence selection framework separately.
Gate three: distinguish payment safeguarding from client-money compliance
The FCA warns that using a non-bank payment provider does not give the customer bank-deposit-style FSCS protection when that provider fails; safeguarding also does not guarantee immediate, full recovery. Its consumer explanation is a useful corrective to treating regulation as an absence of loss risk.
Under PS25/12, the UK’s Supplementary Regime for relevant payment and e-money institutions took effect on 7 May 2026. That payment framework does not replace another jurisdiction’s brokerage client-money rules. Obtain both the provider’s explanation of the relevant balances and a separate applicability review of the broker’s permitted institutions, account structure and reconciliation obligations.
Map proprietary money and client money independently. At each step identify the payer, legal account holder, intermediary, currency, nature of the funds, protection boundaries and availability. Ask specifically about reserves, fees and unsettled balances rather than assuming every amount receives identical treatment. “Dedicated” or “segregated” in an account name is not a substitute for this analysis.
Compare pricing and reserves through available cash
Request quotations against the same volume, currencies, average payment and refund assumptions. Distinguish expenses from restricted liquidity: a reserve may be temporarily withheld money rather than an immediate fee, but it can still create a cash shortfall. The following is a procurement checklist, not a statement of standard commercial terms.
| Item | Definition to obtain | Evidence |
|---|---|---|
| Processing and fixed charges | Setup, monthly and minimum fees; successful and failed payment charges | Complete tariff and change-notice provisions |
| Currency conversion | Reference rate, markup, conversion time and settlement currency | Sample transaction and settlement report |
| Settlement cycle | Starting event for T; business days, cutoffs and holidays | Contract definition and tested arrival record |
| Reserves and collateral | Calculation base, increases, caps, release cohorts and set-off | Reserve ledger and post-termination provisions |
| Refunds and chargebacks | Original fee treatment, dispute charges, evidence deadlines and losses | Dispute workflow and worked fee examples |
| Suspension and exit | Notice, escalation, unsettled amounts, retained funds and exports | Service agreement and exit checklist |
An illustrative cash-flow calculation, not a market quote
Assume a batch contains USD 100,000 of processed transactions. Under purely illustrative terms, deduct USD 2,000 in fees, USD 10,000 in new reserves and USD 3,000 in refunds. If all figures use the same settlement basis and there are no other adjustments, the net amount for that batch is USD 85,000. These are not industry prices or recommended reserve terms. Nor does the calculation establish that the USD 85,000 belongs to the broker as proprietary money.
Model settlement delays, reserve increases and concentrated refunds separately. Include money in a payment plan only when it is actually available, reconciled and usable for that purpose under the applicable rules. Do not fund operating expenses from client money or count pending settlements as cash already received. Ask the provider to walk through the example using its own report format before signing.
Prepare onboarding evidence and allocate responsibilities
Create one consistent application pack: incorporation and ownership records, directors and beneficial owners, licence conditions, business description, customer contracts and websites, money-flow diagram, expected payment profile, AML/KYC and sanctions controls, and refund and complaint policies. Track every additional request, response version, submission date and outstanding condition. More documents do not solve contradictions between the contract, website and business model.
Assign an owner, data input and escalation channel for customer checks, payer matching, unusual transactions, sanctions alerts, refund approval, dispute evidence and incident notification. Operational work can be shared, but the broker should not assume its own duties have been completed merely because the PSP screened a payment. Do not split transactions or change merchant identities to conceal unaccepted activity.
If entity and fund boundaries are unclear, review the broker’s corporate structure first. For supplier controls, use the outsourcing risk framework. Manage onboarding through evidence review, contracting, integration and acceptance testing. A quick API activation is not an operational launch date.
What should pass before going live?
Use a sandbox first. Conduct controlled live-money tests only with provider permission and after the relevant compliance conditions are met; do not create fictitious customers or real suspicious transactions for testing. Acceptance should involve operations, finance, compliance and technology, not just the integration developer.
| Scenario | Suggested acceptance criterion | Retained evidence |
|---|---|---|
| Payment through settlement | Customer ledger, PSP transaction, batch and bank statement connect | Unique references, reports and reconciliation |
| Duplicate notification or timeout | No duplicate credit; unknown status queried before retry | Logs, idempotency rules and exception queue |
| Failure and refund | Clear state; controlled destination, amount and approval | Simulated case and refund evidence |
| Chargeback and reserve | Deadlines, deductions, reversals and release cohorts traceable | Dispute ticket and balance movements |
| Settlement difference or delay | Fees, FX, funds in transit and unexplained gaps separated | Aged exceptions, owners and escalation |
| Outage or exit | Unavailable route stopped; transactions and open items exportable | Exercise report, contacts and recovery steps |
For card payments, PCI SSC explains that outsourcing does not eliminate the merchant’s responsibility for protecting account data. Obtain evidence covering the actual services and document shared duties; confirm your own validation requirements with the acquirer or other relevant compliance-accepting entity. A successful sandbox transaction does not prove production access, upstream approval or settlement readiness.
For every test, record expected and actual results and the person authorised to accept residual issues. A screenshot showing “success” is insufficient if the resulting ledger, refund state or settlement balance is wrong. Resolve material discrepancies before taking customer money through that route.
Monitor the service and define stop conditions
As a practical governance model, finance tracks unsettled funds and aged reserves, operations tracks failures and refunds, compliance monitors market and customer changes, and technology monitors access and integration health. Reassess evidence when a material change affects the upstream bank, contracting entity, settlement account, service scope or charges. Set review frequency by risk while meeting applicable local requirements.
Unexplained beneficiary changes, requests to hide the business, an inability to export complete records, prolonged unexplained withholding, or the loss of a critical permission call for escalation and a pause in new exposure—not increased throughput. Preserve records and use the contract’s escalation process while assessing the appropriate legal and regulatory response. A second PSP is useful only if its own acceptance, disclosures, reconciliation and withdrawal arrangements have been tested.
An exit plan should stop new transactions, complete open settlements, handle historic refunds and chargebacks, reconcile reserves, recover lawfully returnable balances, export records and revoke access. Closing a dashboard is not completion of an exit. Do not promise customers an instant migration when past disputes and retained funds remain unresolved. If the proposed money flow cannot yet be shown to be lawful and workable, resolve those gaps before launching acquisition campaigns.
Frequently asked questions
Does a licensed PSP necessarily accept forex brokers?
No. Check the particular entity and permissions, then obtain written acceptance of the broker, products, customer countries and payment purposes. Marketing statements do not replace that review.
Can an electronic money account replace every bank account?
Not by assumption. Assess operating payments, client-money placement, acquiring settlement and withdrawals separately against legal eligibility, contractual use and counterparty acceptance.
How can a broker tell whether a quote is genuinely cheaper?
Compare total charges, FX, refunds and disputes using identical transaction assumptions, then assess cash tied up by reserves and settlement delays. The advertised processing rate is only one component.
Is a reserve money the broker has already lost?
Not necessarily. Its treatment depends on the contract, reason for withholding and ownership arrangements. Track withholding, set-off and release separately, and do not treat unreleased balances as available cash.
What if a customer requests a refund to someone else’s account?
Do not act solely on an email instruction. Apply the relevant rules and established policy to verify identity, the payment relationship, the reason and receiving account. Complete the necessary review rather than bypassing unresolved concerns.
Will two PSPs eliminate payment interruptions?
No. They may depend on the same upstream institution, while extra routes increase reconciliation and data complexity. Validate the backup beforehand instead of assuming it will work during an incident.
How long does PSP onboarding take?
There is no single deadline for all brokers. Evidence completeness, business acceptance, upstream approvals, contracting and testing all affect timing. Obtain staged conditions rather than relying on a guaranteed activation date.
Discuss Your Licensing and Business Needs
Tell us what you need and our team will contact you shortly.