license Confirmation & Attestation Requests | Neves Licensing Authority
Written confirmation

License Confirmation & Attestation Requests

Where a bank, service provider, institutional counterparty, or professional advisor requires written confirmation, the Authority may issue a license confirmation or attestation through controlled channels. This page explains eligibility, required information, and expected handling.

Controlled channel Status-only confirmation No APIs / no third-party feeds
Verify a license → Submit a request →
Written confirmation is typically limited to status and high-level particulars. It is not an endorsement and does not validate products, services, performance, or suitability.

Overview

Public confirmation is available via the Verify License interface. In some institutional workflows, a written confirmation is required. The Authority may issue a written confirmation or attestation upon request, subject to identity checks, authority-to-request, scope limitations, and confidentiality safeguards.

Institutional workflows Controlled disclosure Point-in-time outcome

1) When to request written confirmation

Written confirmation may be appropriate where:

  • A bank or payment/service provider requires a formal confirmation document for onboarding or periodic review.
  • An institutional counterparty requires written confirmation for contractual, risk, or compliance purposes.
  • A professional advisor requires confirmation for due diligence files.
  • Public verification output is insufficient for the requesting party’s internal controls.
First step: Use Verify License to confirm the current status. If a written document is still required, submit a request below.

2) What the Authority may confirm

Confirmation/attestation is generally limited to high-level particulars such as:

  • License number / reference
  • Legal name of the license holder (where available)
  • High-level category / license type (where applicable)
  • Current status outcome as at the date of issuance
  • Effective date and/or expiry date (where applicable)
Not included: Personal data, internal application papers, review notes, or sensitive operational information are not disclosed through confirmations. See Confidentiality & License Data Protection.

3) Request process

The standard workflow is:

Step 1 — Submit

Required

Submit the request with license details, requester identity, and purpose. Incomplete requests may be returned for clarification.

Step 2 — Validate

Internal checks

The Authority reviews the request for authority-to-request, legitimacy, and scope. Additional verification may be required.

Step 3 — Issue

Point-in-time

If approved, the Authority issues a written confirmation/attestation reflecting status at the time of issuance.

Handling: Requests are processed through official channels only. The Authority does not provide confirmations via third-party websites or intermediaries.

4) Required information (minimum)

Please include the following to avoid delays:

License details

License number/reference (preferred) and legal name of the License holder.

Requester identity

Name, organisation, role/title, and official contact details.

Purpose

Why the confirmation is required (e.g., onboarding, periodic review, due diligence file).

Recipient details

Who should receive the confirmation (requester email or specific named recipient).

Scope requested

Specify whether you need status-only confirmation or also dates/type (where applicable).

Supporting references

Optional: screenshot of Verify License output or the applicant’s provided documents.

5) Timelines & administrative fees

  • Standard handling: Typically within 2–5 business days, depending on completeness and verification needs.
  • Complex requests: May require additional time where identity, authority-to-request, or scope requires clarification.
  • Administrative fees: If an administrative fee applies, it will be communicated during processing. The Authority does not accept payment requests from third parties.
Important: If anyone asks you to pay for an “official confirmation” outside the Authority’s official channels, treat it as suspicious and contact the Authority.

6) Submit a confirmation request

Submit your request through the Authority’s official contact pathway.

Note: Do not include sensitive personal data unless specifically requested through official follow-up. The Authority may request additional details if required to validate the request.

7) Disclaimer

Written confirmations and attestations confirm license status and limited particulars only, as recorded in the internal database at the time of issuance. They do not guarantee performance, validate products or services, or confirm suitability of any arrangement, and they do not constitute an endorsement by the Authority.