What this module is for

NX / Currencies is the reference area for currencies known to the NX layer. Operators use it to confirm that a currency exists, check its display code/symbol/decimal precision, and inspect whether games or providers are available for that currency.

This module is not a marketing currency setup form. In the current CRM, the list and detail pages are mostly navigation and visibility surfaces. They help an operator answer "is this currency present?" and "which games/providers are mapped to it?" without changing the mapping from this workspace.

Included units

• List: currency grid with code, symbol, decimal precision, display name, search, and row navigation.
• Detail: record-level hub for one currency. It shows the currency title and opens the mapping relation pages.
• Relations / Games: read-only game availability view for one currency. It separates selected, unselected, and all games.
• Relations / Providers: read-only provider availability view for one currency. It separates selected, unselected, and all providers.

How to choose the right page

Use the list when you only need to find a currency or verify its basic attributes. Open detail when you need the mapping links for that currency. Open the relation pages when a support, operations, or product question depends on availability, for example why a provider or game is not visible for a specific currency.

Common confusion

• Currency detail is not an edit form in the current UI. It mainly opens mapping links.
• The current currency relation pages are read-only: there is no Save button and row selection is disabled.
• A selected game can be available through game-level or provider-level currency mapping. Treat the relation pages as visibility into effective availability, not as the place where operators change availability.
• If a currency is missing entirely, the fix is outside this CRM module. Do not expect the list page to create currencies.

Current coverage

The detailed pages under this module document visible fields, filters, row actions, read-only mapping behavior, and the Core read paths used by the current CRM. Screenshots are intentionally not included in this documentation wave.