Developer resources

RD Service test console

Check that the ACPL RD Service is running on this computer, read service and device information, and run test captures for authentication and eKYC. The raw response from the service is shown on this page.

Fingerprint (FM220) and iris (Iritech) RD services Device requests go straight from your browser to this computer HTTPS on localhost

Connect to the RD service

The page scans for ACPL RD services as soon as it opens and lists each one it finds.

Service status
Scanning active RD Service...
Scanned on page load
https://localhost, ports 11100–11104 and 11200
Each entry shows the port, the service provider and the device model. Choosing an entry switches the capture settings between fingerprint and iris.
Request host Requests in step 3 use localhost by default. A message confirms the new host. Switching does not run the scan again.

Status stays on “Scanning active RD Service...”?

  • Check that the ACPL RD Service is installed and running, and that the device is connected.
  • If your browser blocks the local HTTPS connection to the RD service, allow it and then reload this page.
  • The RD Service integration and error-code manuals are on the developer resources page.

Set PID options

These values build the PidOptions XML sent with each capture. The capture settings, OTP, demographic data and validation key unlock once an RD service is detected. The WADH field is always editable.

Testing eKYC? Run the WADH calculator (beside these steps, or after step 3 on smaller screens) before you fill in this step. Calculating reloads the page, restarts the service scan and resets the request host.

Capture settings

Request data

Sent inside <Demo>…</Demo>. A complete <Demo> element is sent as entered.
Sent as the ValidationKey custom option.
Paste a WADH or fill it with the WADH calculator. Capture for Auth always sends an empty WADH.

Send a request

Each action calls the selected RD service and shows its raw response below. The buttons unlock once a service is detected.

Service information

Capture

Capture for eKYC needs a value in the WADH field (step 2). Capture for Auth sends an empty WADH.

Raw XML returned by the RD service. It is cleared each time you send a new request.