> For the complete documentation index, see [llms.txt](https://central-bank-of-libya.gitbook.io/devportal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://central-bank-of-libya.gitbook.io/devportal/national-alias-directory-nad.md).

# National Alias Directory (NAD)

Overview and integration guidance for the Central Bank of Libya National Alias Directory (NAD), including access to the official NAD API documentation.

### Standardized alias services for interoperable financial payments

The **National Alias Directory (NAD)** is a Central Bank of Libya service that supports standardized alias-based account identification across participating financial institutions. NAD helps institutions resolve a registered alias to the appropriate financial account information required for supported payment and financial-service flows.

{% hint style="success" %}

## Available now

Participating institutions can use the NAD integration documentation and official API reference for supported directory operations.
{% endhint %}

## Core capabilities

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><h3><i class="fa-user-plus" style="color:$primary;">:user-plus:</i></h3></td><td><strong>Alias Registration</strong></td><td>Associate an approved alias with the relevant customer or account relationship.</td></tr><tr><td><h3><i class="fa-magnifying-glass" style="color:$primary;">:magnifying-glass:</i></h3></td><td><strong>Alias Lookup</strong></td><td>Resolve an alias during a supported transaction or service flow.</td></tr><tr><td><h3><i class="fa-circle-check" style="color:$primary;">:circle-check:</i></h3></td><td><strong>Alias Verification</strong></td><td>Validate directory information before continuing with an applicable financial transaction.</td></tr><tr><td><h3><i class="fa-building-columns" style="color:$primary;">:building-columns:</i></h3></td><td><strong>Institution Interoperability</strong></td><td>Provide a standardized directory mechanism across participating financial institutions.</td></tr></tbody></table>

## NAD in the payment ecosystem

```mermaid
flowchart LR
    A[Customer / Business] --> B[Bank or Financial Institution]
    B --> C[National Alias Directory]
    C --> D[Alias Resolution / Verification]
    D --> E[Payment or Financial-Service Flow]
```

For an LYPay transaction using an alias, the participating institution can use NAD to resolve or verify the alias information required before progressing through the applicable LYPay payment flow.

## Integration journey

{% stepper %}
{% step %}

### Review NAD requirements

Identify the directory functions required by your institution and review the official API documentation.
{% endstep %}

{% step %}

### Prepare connectivity and authentication

Use the approved credentials, connectivity, and development environment provided for your integration.
{% endstep %}

{% step %}

### Implement alias operations

Integrate the applicable registration, lookup, and verification functions defined in the official API reference.
{% endstep %}

{% step %}

### Validate and integrate

Validate returned directory data, then continue into the applicable payment or financial-service process.
{% endstep %}

{% step %}

### Add operational controls

Implement monitoring, secure logging, error handling, audit trails, and support procedures.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}

## Authoritative technical reference

The exact endpoint paths, request fields, response fields, validation rules, and error responses are defined in the official NAD API documentation.
{% endhint %}

## Official NAD API documentation

[Open NAD API Documentation on Postman →](https://documenter.getpostman.com/view/30951400/2sAXqqej3L)

## Security & data handling

* Use only approved secure connectivity and authentication mechanisms.
* Protect customer and account information in transit and at rest.
* Do not expose credentials, tokens, secrets, or sensitive directory data in client-side code or logs.
* Validate returned directory information before continuing with a payment.
* Maintain appropriate audit trails for directory requests and operational investigation.
* Apply relevant **KYC, AML/CFT, privacy, and information-security** requirements.

## Related documentation

* [LYPay Instant Payment System](/devportal/lypay/lypay-instant-payment-system.md)
* [LYPay Technical Overview](/devportal/lypay/lypay-instant-payment-system-technical-overview.md)
* [LYPay API Documentation](/devportal/lypay/api-documentation.md)
* [NUMO QR Code Standards](/devportal/lypay/numo-qr-code-standards.md)
* [Contact & Support](/devportal/contact-and-support.md)