The Saint Lucia Broker Banking Playbook: Build a File Banks Actually Approve

Opening banking for a Saint Lucia forex brokerage isn’t usually blocked by one “missing document.” It’s blocked by a file that doesn’t tell a coherent story: who you are, how money moves, why the activity is legitimate, and how you control risk.

Banks and EMIs (electronic money institutions) typically run the same playbook: verify the company and UBOs, understand the product, map the payment flows, and test whether your AML controls match your risk profile. Below is what they commonly ask for—and how to package it into an approval-ready onboarding file that reduces back-and-forth.

1) Start with the story: business model, jurisdictions, and why Saint Lucia

Most rejections happen before “compliance review” because the relationship manager can’t summarize your business in two sentences. Your first page should make that easy.

Include a short overview that answers:

• Entity: Saint Lucia company name, registration number, incorporation date, registered address.
• What you do: forex/CFD brokerage (or introducing broker model), whether you are principal/agent, and whether you handle client money.
• Where clients are: target countries and explicit exclusions (e.g., “no U.S. persons,” “no sanctioned jurisdictions”).
• How you acquire clients: direct, affiliates/IBs, paid media, partnerships.
• Why Saint Lucia: operational rationale (group structure, cost, regional presence). Avoid framing it as “privacy/tax only.”

Practical tip: add a one-paragraph “risk positioning” statement. Example: “Retail FX/CFD, no crypto deposits, no third-party payments, strict country restrictions, enhanced due diligence for high-risk geographies, automated screening and transaction monitoring.”

2) Corporate pack: prove control, ownership, and substance

Banks/EMIs are onboarding your corporate identity first. If your corporate pack is inconsistent, everything else will be treated as higher risk.

Prepare a single PDF folder (indexed) with:

• Certificate of Incorporation and Company Registry extract (or equivalent).
• Memorandum & Articles (or constitutional documents).
• Register of Directors and Register of Shareholders.
• Incumbency / Certificate of Good Standing (where applicable).
• Board resolution authorizing account opening and naming signatories.
• Organizational chart (especially if there’s a holding company or multiple operating entities).
• Proof of operating address (lease/utility) and a short “substance note” (office, staff, outsourced functions).

If you have a group structure, add a one-page “who does what” table:

• Entity A: marketing/lead gen
• Entity B: brokerage operations
• Entity C: tech/IP
• Entity D: payments/merchant contracting

The goal is to eliminate ambiguity about which entity is contracting with clients and which entity receives funds.

3) UBO + management KYC: make it audit-grade, not “good enough”

Expect full KYC on UBOs, directors, and often senior management (CEO/COO/MLRO/Compliance Officer). The friction usually comes from incomplete personal files and unclear wealth narratives.

Build a standardized “person pack” for each relevant individual:

• Government ID (not expired) + selfie/liveness if requested
• Proof of address (recent and matching)
• CV/LinkedIn (role history relevant to financial services)
• Source of wealth (SoW) narrative and supporting evidence
• Source of funds (SoF) for initial capitalization (bank statements, sale agreements, dividends, audited accounts)
• PEP/sanctions declaration (and explanation if applicable)

What reviewers look for:

• Consistency across documents (names, addresses, transliterations)
• A plausible wealth-building timeline (not just “trading profits”)
• Clear beneficial ownership down to natural persons (including trusts/nominees, if any)

If your UBO is also funding the business, separate the story into two parts:

1. how the UBO earned the wealth (SoW), and
2. how that wealth is being transferred into the brokerage (SoF).

4) Compliance pack: policies, controls, and the MLRO’s operating model

For a forex brokerage, banks/EMIs want to see that AML isn’t a template—it’s operational. Your file should show controls mapped to your actual onboarding and payment flows.

Minimum policy set (tailor to your setup and check local regulations):

• AML/CTF Policy (risk-based approach, EDD triggers, ongoing monitoring)
• Sanctions & screening procedure (screening points: onboarding, payouts, periodic rescreen)
• KYC/Customer Due Diligence procedure (retail vs corporate clients)
• Transaction monitoring & suspicious activity reporting procedure
• Risk assessment (product, geography, delivery channels, customer types)
• Record retention & data protection (including vendor access)
• Complaints handling and chargeback/dispute procedure

Operational artifacts that increase approval odds:

• A one-page CDD/EDD decision tree (what triggers EDD, what evidence you collect)
• Sample KYC checklist your ops team uses
• A short MLRO/Compliance Officer bio with responsibilities and escalation lines
• Evidence of training (training log or plan)

Where Brokeret typically fits: a broker-grade CRM and onboarding workflow can help you demonstrate consistent KYC collection, screening checkpoints, audit logs, and case management—exactly what reviewers need to see in practice.

5) Payment flows and funds handling: diagrams beat paragraphs

If a reviewer cannot visualize your money movement in 60 seconds, you’ll get long questionnaires—or a “not a fit.” Provide flow diagrams and match them to your written answers.

Include 2–3 simple diagrams (one page each):

• Deposit flow: client → payment method → EMI/bank account → wallet/ledger → trading platform crediting
• Withdrawal flow: trading balance → withdrawal request → checks (KYC status, sanctions, velocity, name match) → payout rail → client
• Chargeback/dispute flow (if cards are involved): dispute intake → evidence → representment → outcome handling

Then add a “funds handling” table:

• Accepted payment methods (cards, bank transfer, local APMs) and what you exclude (e.g., cash, third-party deposits)
• Third-party payments policy (usually “not allowed”)
• Name matching rules (payer name must match verified client)
• Payout rules (same method, same beneficiary, cooling-off/settlement periods)
• Refund logic (when you refund vs withdraw)

Also prepare projected volumes (3–6 months) that are realistic:

• expected monthly deposits/withdrawals
• average ticket size
• top 5 client countries by volume
• expected chargeback ratio (if cards)

Overstated projections are a common red flag.

6) Trading and technology stack: show you can control abuse and reconcile

Banks/EMIs increasingly ask how you run the brokerage operationally—because fraud, manipulation, and poor reconciliation become their risk.

Provide a concise “stack & controls” overview:

• Trading platform (MT4/MT5/cTrader/MatchTrader) and who hosts it
• Liquidity/bridge (PrimeXM/Centroid, LP model, A/B book approach at a high level)
• Client ledger and how you separate balances (wallets, accounts, bonus balances)
• Reconciliation process (daily/weekly): platform vs CRM ledger vs bank/EMI statements
• Access controls: role-based access, 2FA, audit logs, maker-checker for payouts
• Incident handling: how you respond to account takeover, suspicious withdrawals, and data breaches

Approval-ready evidence you can attach:

• screenshots of your onboarding steps and KYC statuses
• a sample reconciliation report (redacted)
• payout approval workflow (who approves, what checks run)

If you run IB/affiliate programs, add controls:

• how you vet IBs
• how you prevent incentive abuse
• how commissions are calculated and paid (and to whom)

7) Assemble the “approval-ready file”: a checklist and packaging format

Treat onboarding like a deal room. Your goal is to reduce reviewer effort and eliminate unanswered questions.

Recommended folder structure (single ZIP or shared drive with PDFs):

1. 00_Executive_Summary
   • 1-page business overview + risk positioning
   • jurisdictions served/excluded
   • volume projections
2. 01_Corporate_Documents
   • incorporation, registers, resolutions, org chart
3. 02_UBO_and_Management_KYC
   • one subfolder per person (ID, POA, CV, SoW/SoF)
4. 03_Compliance_Policies_and_Risk_Assessment
   • AML/CTF, sanctions, monitoring, training plan
5. 04_Payment_Flows_and_Funds_Handling
   • diagrams, third-party payment policy, payout rules
6. 05_Technology_and_Operations
   • stack overview, reconciliation, access controls
7. 06_Commercials_and_Contacts
   • key contacts (CEO/COO/MLRO), support email, escalation path

Packaging rules that matter:

• Name files clearly (e.g., “UBO1_Source_of_Wealth.pdf”) and keep dates visible.
• Use a master index (one page) listing every document.
• Keep narratives short but specific; attach evidence behind them.
• Ensure your answers are consistent across forms, pitch decks, and policies.

The Bottom Line

Banks/EMIs don’t just want documents—they want a coherent, testable picture of your Saint Lucia brokerage’s ownership, controls, and money movement.

If you deliver a structured corporate pack, audit-grade UBO/SoW evidence, tailored AML procedures, and clear payment-flow diagrams, you reduce onboarding cycles and avoid “not a fit” outcomes.

If you want help aligning your onboarding workflow, KYC/AML ops, and payment flows into an approval-ready file, talk to Brokeret at /get-started.