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
Scope of Activities | Forex License Permissions
Scope of Activities — Scope-First Reference | NevesForexLicense.org
Core concept

Scope of Activities

“License” is a framework label. “Scope” is the operational permission set. Most counterparty failures happen when scope, business model, and funds flow don’t match.

Informational reference only. Scope is assessed on facts, documentation, and controls—not on descriptions.
Quick path: Scope mapping · Boundaries · Bank lens.
Method

How scope is mapped (practically)

  • ActivitiesWhat you actually do: execution, routing, market interface, support, promotions.
  • Custody postureDo you touch funds? Where do they sit? Who controls the keys or accounts?
  • Funds flowWho pays whom, for what, and under what contractual responsibility?
  • ControlsPolicies, monitoring, complaints, incident response, recordkeeping.
Output

What a “scope statement” should do

  • Be falsifiableSpecific enough that a bank can verify consistency.
  • Avoid implied permissionsNo “we are licensed therefore we can…” language.
  • Match the moneyClaims must match flows, counterparties, and contracts.
  • Protect boundariesExplicitly state what you do not do.
Activity taxonomy

Activities banks ask about first

These buckets are used to clarify scope. They are descriptive categories for analysis—not “sub-licenses”.

Core Bank-sensitive

Execution & order handling

Order intake, routing, execution, dealing model boundaries, disclosures, complaint handling.

  • Execution-only vs discretionary
  • Best execution / fairness claims (careful)
  • Client comms and risk warnings

Back to Capital Markets

Boundary High risk

Custody & client funds

Where client funds sit, who controls accounts, segregation, withdrawal policy, safeguarding.

  • Touching funds triggers deeper review
  • Segregation model must be clear
  • Consistency with contracts & UX

Read boundary explainer

Non-negotiable

Boundaries prevent scope creep

A clean scope statement includes what you do, what you do not do, and what you outsource—so counterparties don’t assume hidden activity.

Do → Do not → Outsourced → Evidence
Counterparty lens

What counterparties try to prove

They’re not trying to “understand your story”. They’re trying to prove you are consistent and low-risk.

Truth
Verify public status and entity details.
Scope
Confirm activities match declarations.
Money
Locate funds, control points, settlement.
Controls
Policies, monitoring, escalation, audits.
Records
Evidence trail over narratives.

Banking expectations (detail)

How “licensed” claims are interpreted in onboarding.

Open banking expectations

Common scope mistakes

The fastest ways to trigger “more docs please” loops.

Open mistakes guide

Contact

Contact us

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

Reference enquiries

Replace placeholders with your final channels.

Include: entity name, license reference (if any), activity summary, and what exactly you want clarified.
Reference desk

Contact details

Emailinfo@nevesfinancialauthority.org
Phone+2399087684
LocationCapital Markets Desk, Neves Financial Services Authority Division, Neves Licensing Authority, R.3 de Feveirero, Almeirim, São Tomé , São Tomé & Príncipe
If you need application intake, use the commercial domain (.com). This .org is a reference site.