Skip to main content

Configuration Options

ParameterTypeRequiredDescriptionDefault
journeyTokenstringYesToken from Create Journey API
languagestringNoUI language: en, ar, ru, fr, zh, it, tr, uk"en"
themestringNoUI theme: light, dark, system"system"
apiDomainstringNoAPI domain for the journeyWindow origin
privacyPolicyUrlstringNoURL to your privacy policynull
logoUrlstringNoURL to your logoUAE KYC logo
accentColorstringNoHex color code for UI accent
docCaptureCamFacingModestringNoCamera mode: user, environmentundefined

Status Codes

StatusValueDescription
Cancelled0User cancelled the journey
DocumentVerificationFailed1Document verification failed
FaceVerificationFailed2Face verification failed
Expired3Journey token or session expired
Error4An error occurred
Success5Journey completed successfully
Unknown6Unknown status
Blocked7Journey blocked due to multiple failed attempts — see Journey Blocking

Error Codes

Error CodeValueDescription
LoggerInit1Logger initialization failed
Init2SDK initialization error
Consent3Error during consent step
DocumentSelection4Error during document selection
EidFrontSideUpload5Emirates ID front upload failed
EidBackSideUpload6Emirates ID back upload failed
GccIdFrontSideUpload7GCC ID front upload failed
GccIdBackSideUpload8GCC ID back upload failed
PassportUpload9Passport upload failed
DocumentVerification10Document verification error
FaceUpload11Face image upload failed
Finalize12Journey finalization error
Unknown13Unknown error
Internal14Internal SDK error
FormSubmission15Form submission error
EmiratesIdSubmission16Emirates ID submission error
Panic17SDK internal error — message contains panic details
LivenessInit18Face capture / liveness service initialization failed — message contains error details

Troubleshooting

  • Journey token invalid or expired: Generate a new token from the Create Journey API
  • Container not found: Ensure <div id="uae-kyc-container"></div> exists in the DOM before calling startJourney
  • SDK fails to load: Confirm the script URL is correct and the file is served over HTTPS
  • CORS errors: Ensure proper CORS headers are configured on your CDN or server
  • Self-hosting: Mirror all files in the SDK version directory — not just the main JS file — with correct relative paths
  • Camera not working: The SDK requires HTTPS in production for camera access