Deprecated: Return type of Ai1wm_Recursive_Directory_Iterator::hasChildren($allow_links = true) should either be compatible with RecursiveDirectoryIterator::hasChildren(bool $allowLinks = false): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/8fb4216b-599f-4753-bef4-b07428b53796/nevesforexlicense.org/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/iterator/class-ai1wm-recursive-directory-iterator.php on line 57

Deprecated: Return type of Ai1wm_Recursive_Directory_Iterator::rewind() should either be compatible with FilesystemIterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/8fb4216b-599f-4753-bef4-b07428b53796/nevesforexlicense.org/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/iterator/class-ai1wm-recursive-directory-iterator.php on line 35

Deprecated: Return type of Ai1wm_Recursive_Directory_Iterator::next() should either be compatible with DirectoryIterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/8fb4216b-599f-4753-bef4-b07428b53796/nevesforexlicense.org/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/iterator/class-ai1wm-recursive-directory-iterator.php on line 42

Deprecated: Return type of Ai1wm_Recursive_Extension_Filter::getChildren() should either be compatible with RecursiveFilterIterator::getChildren(): ?RecursiveFilterIterator, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/8fb4216b-599f-4753-bef4-b07428b53796/nevesforexlicense.org/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-extension-filter.php on line 47

Deprecated: Return type of Ai1wm_Recursive_Extension_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/8fb4216b-599f-4753-bef4-b07428b53796/nevesforexlicense.org/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-extension-filter.php on line 37

Deprecated: Return type of Ai1wm_Recursive_Exclude_Filter::getChildren() should either be compatible with RecursiveFilterIterator::getChildren(): ?RecursiveFilterIterator, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/8fb4216b-599f-4753-bef4-b07428b53796/nevesforexlicense.org/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-exclude-filter.php on line 41

Deprecated: Return type of Ai1wm_Recursive_Exclude_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/8fb4216b-599f-4753-bef4-b07428b53796/nevesforexlicense.org/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-exclude-filter.php on line 37

Deprecated: Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/8fb4216b-599f-4753-bef4-b07428b53796/nevesforexlicense.org/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-newline-filter.php on line 28
Client Money vs Proprietary Capital | Forex Compliance
Client Money vs Proprietary Capital — Boundary Explainer | NevesForexLicense.org
Boundary explainer

Client Money vs Proprietary Capital

This distinction drives how banks assess risk. If your model touches client money, you are evaluated as a safeguarding / custody risk. If you only trade your own capital, you are evaluated as a business-risk and controls-risk—very different outcomes.

Informational reference only. Do not market “safeguarding” or “custody” claims unless your scope and controls support it.
Comparison

The difference in one page

Banks care less about what you call yourself, and more about where money sits and who controls it.

Client money Higher scrutiny

Client money model

Meaning Funds belonging to clients are received, held, or controlled (directly or indirectly).
Bank focus Segregation, withdrawals, chargebacks, dispute handling, custody posture, and audit trail.
Evidence Policies, account structure, reconciliations, incident response, complaint workflows.
Risk Safeguarding/custody risk, fraud/AML exposure, operational loss risk.
Proprietary capital Different lens

Proprietary capital model

Meaning Trading is conducted using the firm’s own capital; clients are not depositing tradeable funds.
Bank focus Source of funds, treasury controls, revenue model, counterparties, operational controls.
Evidence Corporate bank accounts, capital provenance, governance, risk controls, reporting discipline.
Risk Market/strategy risk + compliance controls risk (not custody-by-default).

Capital Markets context

Where client-facing execution and routing can trigger client-funds questions.

Open Capital Markets License

Prop model context

If you operate evaluation / funded trader structures, keep the boundary clean.

Open NevesPropLicense.org

Key concept

Custody posture (what triggers deep review)

  • Direct custodyYou hold or control client funds/accounts directly.
  • Indirect custodyYou can initiate transfers, approve withdrawals, or control access—even if funds sit elsewhere.
  • Operational controlYou manage the operational steps that effectively move money.
  • Evidence requirementIf any custody posture exists, banks want policies + proof of execution discipline.
How to stay clean

How to state the boundary (safely)

  • Say what is trueState where money sits, who controls it, and why.
  • Say what you do not doNo deposits, no holding, no withdrawal discretion (if true).
  • Align contracts + UXWebsite, T&Cs, UI flows must match the claim.
  • Keep “payment” language outDo not imply payment services on this domain.
“We do not hold client funds” is meaningless unless you explain where funds sit and who controls movement.
Avoidable failures

Common misclassifications

These issues create endless “more docs please” loops and sometimes outright rejections.

Risk Bank trigger

Using payment language

Words like “wallet”, “deposit”, “withdrawals processed by us” imply custody/payment activity.

  • Use neutral language: “funds flow” / “settlement”
  • State control points clearly
Risk Evidence gap

Claims without proof

“Segregated”, “safeguarded”, “audited” claims get interrogated immediately.

  • Only claim what your scope + controls support
  • Keep it factual and bounded

Banking expectations

What banks actually ask for, and why.

Open banking expectations

License verification

How to verify claims cleanly and read register fields.

Open verification guide

Contact

Contact us

For reference enquiries, verification questions, or corrections. This site does not accept applications.

Reference enquiries

Replace placeholders with your final channels.

Include: business model summary, whether you touch client funds, and where settlement occurs.
Reference desk

Contact details

Emailinfo@nevesfinancialauthority.org
Phone+2399087684
LocationNeves (reference) — update as applicable
If you need application intake, use the commercial domain (.com). This .org is a reference site.