The module manifest

The app does not decide for itself which of its screens a customer may use. It asks your server once, right after sign-in, and draws the Futures tab, the Trading Tools tiles, the Help Centre row and the spot order ticket from the answer. That answer is the module manifest: one entry per module, each with a yes or no and, for a no, the reason.

Everything on this page happens on your server. The app has no setting that shows a module the server refuses, and none that hides one it allows — apart from the build flag for Merchant, AI Investment and Affiliate, which decides whether their screens exist at all (see Merchant, AI Investment and Affiliate).

The request

It needs a signed-in session and answers 401 without one. It answers for the customer who is asking, so two customers on the same install can get different answers. Nothing in it depends on whether the caller is the app or a browser.

A shortened answer:

{
  "user": {
    "roleName": "User",
    "isSuperAdmin": false,
    "kycLevel": 1,
    "kycEnforced": true,
    "residence": "GB",
    "attestationEnforced": false
  },
  "modules": [
    {
      "id": "futures",
      "title": "Futures",
      "extension": "futures",
      "installed": true,
      "enabled": true,
      "licensed": true,
      "kycRequired": true,
      "kycSatisfied": false,
      "attestationRequired": true,
      "attested": true,
      "visible": false,
      "reason": "KYC_REQUIRED"
    }
  ]
}

The list always carries the same 21 modules, including four the app has no screens for (nft, copy-trading, ai-support, ecosystem), because the server answers for the website's addons as well. Binary options, the core Investment plans and forex are not in it and cannot be added, so no answer can ever tell the app to show them.

How each module is decided

The server runs these checks in order and stops at the first one that fails. The reason names the check that failed.

Core modules (wallet, markets, trade, account, support, blog, news) have no addon, so they always count as installed and licensed. Only checks 2, 4 and 5 can stop them, and only two core modules have anything for those checks to look at: trade (its switch, attestation and KYC) and wallet (KYC).

Attestation is checked before KYC on purpose. If you are not licensed to serve a customer's country, telling them to complete identity verification would cost them their documents and still show them nothing.

1. Installed

An addon is installed when it has a row in your extension list, whether or not it is switched on. Two modules also need a second addon:

• Futures needs the Exchange Engine addon (ecosystem). Without it, Futures reports NOT_INSTALLED however healthy the Futures addon is.
• Staking in on-chain mode needs Exchange Engine and Web3 Wallet & On-Chain Trading (dex). Fixed-rate staking — the default — needs only the Staking addon.

2. Switched on

The addon's own on/off state in System → Extension Manager (/admin/system/extension) is the first half. The second half is a switch of yours, for four modules:

An addon that another module depends on counts here too: Futures with Exchange Engine installed but switched off reports DISABLED, and so does on-chain staking when Exchange Engine or Web3 Wallet & On-Chain Trading is switched off or unlicensed.

3. Licensed

The addon's licence must be valid. When the licence check throws — an unreachable licence file, say — that one module reports UNLICENSED rather than the whole request failing, and the backend log records Licence check failed for "<addon>". Hiding a module whose licence cannot be confirmed is the safe direction: a tab that then refuses every request is worse than no tab. See Licences and the extension manager.

4. Licence attestation

Only when Enforce Licence Attestations (Mobile App) is on — Admin → System → Platform Settings, tab Features, group Verification, off by default — and only for nine modules: trade, p2p, staking, ico, futures, ecosystem, copy-trading, gateway and ai-investment.

The server works out where the customer lives from their approved KYC applications, oldest first, and falls back to the country on their profile. It never uses the IP address or the phone's settings. Then:

• a known country with a live (unexpired) licence row for the module passes;
• a known country without one gets NOT_ATTESTED;
• no known country gets RESIDENCE_UNKNOWN.

With enforcement on and no rows recorded, all nine modules are closed to every app user: their tiles, the Futures tab and the spot ticket stay on screen, locked, and say why (see the warning under Finding out why a screen is missing). The rows live under System → Compliance → Licence Attestations (/admin/system/attestation) — see Licence attestations. The website is never gated by any of this.

5. KYC feature

Only when KYC Verification (kycStatus) and Enforce KYC Feature Access (kycFeatureEnforcement) are both on — same tab and group as above. A module that names a KYC feature then needs the customer's level to include it:

The features are set per level in the KYC level builder — see KYC. That page also lists the individual actions your server refuses for a missing feature, which go further than this list: a module can be shown while an action inside it is refused.

Every module at a glance

Which screen each module opens is on What is in the app.

What the app shows for each reason

The app splits the reasons in two. KYC_REQUIRED, NOT_ATTESTED and RESIDENCE_UNKNOWN mean the product exists on your platform but this customer may not start anything in it — they may still hold a futures position or a P2P escrow there, so the way in stays on screen. NOT_INSTALLED, DISABLED and UNLICENSED mean the product is not on your platform at all, so nobody can hold anything in it and the way in disappears.

The locked Futures order form adds a second line under the message: "Positions you already hold can still be closed." The spot ticket on the full-screen chart shows the same messages without the buttons.

The Help Centre row in Profile appears only when faq is OK. When it is not, the help-centre shortcut in the support chat answers "This platform has not published a help centre."

The messages

The app writes these itself, with the module's title from the answer in place of title:

So a customer without the trade feature reads "Complete identity verification to use Spot trading." When trade is missing from the answer altogether, the spot ticket says "Trading is not available right now."

Only the first two tell the customer to do something, because only those two are theirs to fix. NOT_ATTESTED deliberately does not suggest the website or another device.

When the answer cannot be read

The app fails closed: until it has an answer, every module counts as hidden.

• While the first request is in flight, the Trading Tools row and the Futures tab are simply not there yet, and the spot ticket shows a spinner.
• If no answer has ever arrived, Trading Tools shows "We couldn't check which tools are available on your account." with Retry, and the spot ticket shows "Couldn't check what's available on your account." with Retry.
• If an earlier answer arrived and a later request fails, the app keeps the earlier answer. A dropped connection does not empty somebody's dashboard.
• A 401 or other refusal from your server counts as no answer, not as an empty list, so an expired session never looks like an unlicensed install.

Hiding is the deliberate direction. Showing a module by default would put something you may not be licensed for in front of a store reviewer, under your developer account.

When the app asks again

The app reads the manifest:

• at every sign-in — password, Google, and after the two-factor code;
• every time the app starts with a saved sign-in;
• when the app comes back to the foreground, only if no answer has loaded yet;
• on pull-to-refresh on Home, only if no answer has loaded yet;
• from the Retry buttons above;
• when the customer comes back from Add your country or Verify identity on the locked spot ticket.

It throws the answer away at sign-out, so the next person to sign in on the phone never sees the previous account's modules.

It does not ask on a timer, and your server does not tell it when something changes. A change you make — an addon switched on, a licence row recorded, a customer's KYC approved — reaches a customer who is already signed in the next time they sign in or fully close and reopen the app.

Taking something away works the other way round. A licence row withdrawn or a KYC feature removed from a level is enforced by your server on the next request, so the order or offer is refused even while an app that read an older answer still shows the screen.

Finding out why a screen is missing

What it deliberately does not do

• It does not read your website's navigation settings. The app's public settings request (/api/settings) lists which addons are switched on, but carries nothing about licences, KYC or countries, so the app does not use it to decide what to show.
• It does not hide the core tabs. Nothing in the app reads the wallet, markets, account or support entries: the Wallet and Market tabs, Profile and support tickets are always there. A KYC level without view_wallets hides no tab. What your server refuses inside the Wallet tab — a deposit, a withdrawal, a transfer — follows the other features on the customer's level, action by action.
• It does not refresh itself. See When the app asks again.
• It does not show what the server does not list. A module this build knows but the server's answer does not contain is hidden — which is also how an app build newer than your server behaves.

Related

• Server settings that shape the app
• Licence attestations
• What is in the app
• Merchant, AI Investment and Affiliate