New to UAE KYC? Start with the Overview page to understand the platform and journeys, then use this guide as your practical onboarding checklist.
Submit Required Forms
Contact
business@uaekyc.ae to begin the onboarding process. The following forms and documents are typically required:| Form | Description | Download |
|---|---|---|
| Information Security Questionnaire | Detailed security questionnaire covering your organization’s controls and posture | Download PDF |
| Service Provisioning Form | Defines requested UAE KYC services and required network connectivity | Download PDF |
| Client Onboarding Form | General organization details and primary points of contact | Download DOCX |
Additional documents may be required based on your industry or ICP requirements. Contact
business@uaekyc.ae to request any forms not listed above.Network Connectivity Setup
UAE KYC operates within a secure environment. Choose the appropriate connectivity option based on your organization’s size and infrastructure:
Many clients expose UAE KYC through an internal FQDN (for example,
| Option | Description |
|---|---|
| ADnet | Abu Dhabi Government network — for entities already connected to the AD government backbone |
| FedNet | UAE Federal Government network — for federal entities with existing FedNet access |
| MPLS Line | Dedicated private line — for large enterprises requiring a direct, high-bandwidth connection |
| Site-to-site VPN | Encrypted tunnel between your network and the UAE KYC environment |
| IP Whitelisting | Public IP-based access — typically used for smaller clients or initial sandbox/PoC testing |
Your connectivity option will be agreed upon during the onboarding process. Contact
business@uaekyc.ae if you are unsure which option is right for you.stg-icp-dash.<your-domain>.ae) that is only reachable over the chosen secure network (ADnet, FedNet, MPLS, VPN, or whitelisted IPs).Configure Network Routing
All API calls from your servers must be routed through the whitelisted or approved network channel configured in Step 2.
- Ensure your backend services route outbound traffic to stg-api.
uaekyc. icp. gov.ae via the agreed connectivity method - Verify that DNS resolution and firewall rules are correctly configured
- Test connectivity before proceeding to SDK integration
- Implement routing and access policies on your gateway or WAF (for example, iRules or equivalent) so that all UAE KYC traffic is forced through the approved path
Create API Keys & Sandbox Users
Generate your API keys from the Dashboard:
- Log into the Dashboard
- Navigate to the API key management section
- Create a new key pair for your integration
Receive Platform Access
Once your forms are approved and network connectivity is established, UAE KYC will share the following:
You will receive credentials to log into the Dashboard.Once you have these endpoints and credentials, review the end‑to‑end Communication Flow to see how your backend will initiate journeys and handle callbacks.Many institutions configure an internal subdomain (for example,
| Resource | URL / FQDN / IP | Description |
|---|---|---|
| Nexus (SDK Registry) | repo. | Repository for downloading SDK packages |
| Dashboard | stg-dash. | Web portal for managing journeys, sandbox users, and analytics |
| API Domain | stg-api. | Base domain for all API calls (staging) |
| API IP (staging) | 83.111.28.12 | Public IP address to whitelist for API access (staging) |
stg-icp-dash.<bank>.ae) on their WAF or proxy that forwards to the official UAE KYC FQDNs above, and restrict access to that subdomain to office and VPN networks.Integrate SDK
Choose the SDK that matches your platform and follow the integration guide:After integration, your application invokes the SDK using the journey token, SDK and API traffic flows through your approved network path, and your backend pulls verification results via the Journey Details and Customer Details APIs.
Web SDK
Browser-based integration
Android SDK
Android & Huawei devices
iOS SDK
iPhone & iPad integration