This guidance defines minimum publication standards for the NLA public register. It covers required fields, naming conventions, status states, publication timing, update rules, and correction requests. The aim is consistent, verifiable, and non-misleading records.
The public register is a transparency tool. Its purpose is to allow third parties—clients, banks, PSPs, counterparties, and reviewers—to confirm whether a license claim is valid and what activity headers are approved. Register content must be consistent, attributable, and non-misleading.
Each register entry must contain the minimum dataset below. Additional fields may be published by license family, but the fields here are required for baseline verification.
| Field | Minimum requirement | Notes |
|---|---|---|
| License number | Unique identifier in a consistent format (no reuse). | Must match verification interface output. |
| Legal entity name | Full legal name (as recorded), not just a trading name. | Trading name may be included as secondary. |
| Jurisdiction / seat | Location metadata applicable to the license record. | Use consistent naming (e.g., “Nevis”). |
| License family | License category or framework family (e.g., NFSA / NGA). | Must align to published categories. |
| Approved activity headers | Clear list of permitted activities. | No broad “licensed for everything” phrasing. |
| Status state | One of the defined status states (see next section). | No custom states without publication. |
| Issue date | Date the license was issued/recorded. | ISO date format recommended. |
| Verification link / endpoint | Direct verification path for third parties. | Prefer a stable URL structure. |
Status states must be consistent across the register and verification outputs. If status is not “Active”, the record must communicate limitations clearly.
| Status | Meaning | Public claim rule |
|---|---|---|
| Active | License is valid and not under restriction beyond standard conditions. | May claim “Licensed under NLA framework” (with verify link). |
| Suspended | License temporarily inactive pending resolution of a matter. | Must not claim “active license”; must disclose suspension. |
| Revoked | License withdrawn; no longer valid. | Must not claim license; record remains for history. |
| Expired | License lapsed or not renewed where renewal applies. | Must not claim current license; may reference historical record only. |
| Under review | Status requires additional checks; outcome not final. | May not claim full license validity; disclose “under review”. |
“Under review” prevents false certainty. It allows a record to exist while checks are being completed and avoids a situation where marketing claims imply full validity before a third party can confirm final status.
Register data must be updated in a controlled way. Silent edits create credibility problems. This section sets minimum timing expectations and update controls.
| Event | Minimum expectation | Typical failure pattern |
|---|---|---|
| New license issued | Entry published once the decision is recorded and verification output is available. | Publishing before verification output exists. |
| Material change | Change recorded and reflected in register within a defined window. | Old scope wording remains while marketing updates immediately. |
| Status change | Status updated promptly with clear public meaning. | Using vague wording (“restricted”) without clarity. |
| Correction request | Handled through a documented correction workflow (see next section). | Ad-hoc edits without trace or acknowledgement. |
Licensees may request corrections where the public record contains an error. Correction requests must be evidence-based and must not be used to expand scope or rewrite status history.
Neves Licensing Authority – Disciplina • Unitas • Labor