Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Available now

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

Core capabilities

Alias Registration

Associate an approved alias with the relevant customer or account relationship.

Alias Lookup

Resolve an alias during a supported transaction or service flow.

Alias Verification

Validate directory information before continuing with an applicable financial transaction.

Institution Interoperability

Provide a standardized directory mechanism across participating financial institutions.

NAD in the payment ecosystem

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

1

Review NAD requirements

Identify the directory functions required by your institution and review the official API documentation.

2

Prepare connectivity and authentication

Use the approved credentials, connectivity, and development environment provided for your integration.

3

Implement alias operations

Integrate the applicable registration, lookup, and verification functions defined in the official API reference.

4

Validate and integrate

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

5

Add operational controls

Implement monitoring, secure logging, error handling, audit trails, and support procedures.

Authoritative technical reference

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

Official NAD API documentation

Open NAD API Documentation on Postman →

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

PreviousNUMO QR Code Standards
NextContact & Support