Integrate with ET Checker

Why this is worth doing

How integration works

The verification flow, end to end:

1. 1
   Employer submits a candidate

   Full name, national ID, and the specific checks needed (criminal record, education, etc.).
2. 2
   Candidate authorizes screening

   Consent is recorded before anything is checked — required for every check, every time.
3. 3
   ET Checker requests verification

   Today: a verification officer confirms each data point with the relevant institution. With a partnership: a structured, logged request through the shared channel.
4. 4
   Result recorded and reported

   Each check gets a result and a finding; once every check is in, the report generates and is delivered to the employer.

The highest-volume check on the platform, and our priority partnership.

For roles requiring a verified academic credential.

Fayda identity verification runs on VeriFayda 2.0's eSignet — the same OpenID Connect (OIDC) system every relying party integrates with. The phone number is the anchor: HR starts a request with the candidate's phone number, Fayda confirms it belongs to a real FAN (Fayda ID Number) by sending a one-time code straight to that number, and the candidate authenticates directly with Fayda — ET Checker never sees or handles the OTP, a password, or biometric data.

GET https://esignet.fayda.et/authorize
  ?client_id=<et_checker_client_id>
  &response_type=code
  &redirect_uri=https://www.etcheckers.com/api/fayda/callback
  &scope=openid%20profile
  &acr_values=mosip:idp:acr:generated-code
  &code_challenge=<sha256_of_code_verifier>
  &code_challenge_method=S256
  &state=<request_code>
  &claims=%7B%22userinfo%22%3A%7B%22name%22%3A%7B%22essential%22%3Atrue%7D%2C%22phone_number%22%3A%7B%22essential%22%3Atrue%7D%2C%22birthdate%22%3A%7B%22essential%22%3Atrue%7D%2C%22gender%22%3A%7B%22essential%22%3Atrue%7D%7D%7D

import { SignJWT, importJWK } from "jose";
 
async function faydaClientAssertion() {
  const jwk = JSON.parse(
    Buffer.from(process.env.FAYDA_PRIVATE_KEY_BASE64!, "base64").toString("utf8"),
  );
  const privateKey = await importJWK(jwk, "RS256");
 
  return new SignJWT({
    iss: process.env.FAYDA_CLIENT_ID,
    sub: process.env.FAYDA_CLIENT_ID,
    aud: process.env.FAYDA_TOKEN_ENDPOINT,
  })
    .setProtectedHeader({ alg: "RS256", typ: "JWT" })
    .setIssuedAt()
    .setExpirationTime("2h")
    .sign(privateKey);
}

{
  "sub": "6140798523917519",
  "name": "Tesfaye Alemu",
  "phone_number": "+251911223344",
  "birthdate": "1994-03-12",
  "gender": "male",
  "verifiedAt": "2026-09-21T09:14:02.000Z"
}

The OTP, and any password or biometric step, happens entirely on Fayda's own hosted page — it never passes through ET Checker's servers, browser, or logs.

The screening catalog isn't fixed to ride-hailing or general employment — the same request/response shape extends to any sector with its own verification need.

A new sector doesn't need a new platform — it needs a new check type and a partner on the other end of it. Reach out (see Getting Started) and we'll scope the fields together.

Authentication

Every completed report gets a short, unguessable public link. Anyone holding it can look up who the report is for; seeing the actual result requires signing in as ET Checker staff or that employer's own HR account.

The snippets below use placeholders. Want a sandbox login and a real report link to run them against? Get a demo account from the assistant.

curl https://www.etcheckers.com/api/r/$TOKEN

{
  "locked": true,
  "preview": {
    "requestCode": "EC-2026-00006",
    "candidateFullName": "Tesfaye Alemu",
    "companyName": "Feres Transport"
  }
}

curl -X POST https://www.etcheckers.com/api/r/$TOKEN/unlock \
  -H "Content-Type: application/json" \
  -d '{"email":"you@company.com","password":"YOUR_PASSWORD"}'

{
  "report": {
    "requestCode": "EC-2026-00006",
    "candidate": { "fullName": "Tesfaye Alemu", "nationalIdMasked": "████—9012" },
    "job": { "positionTitle": "Driver", "department": "Ride-Hailing Operations" },
    "company": { "name": "Feres Transport" },
    "services": [
      { "code": "S-01", "result": "clear", "findings": "No criminal record found." }
    ],
    "overallResult": "clear",
    "validUntil": "2027-03-21T19:01:24.680Z",
    "expired": false
  }
}

Status codes

Data protection

• Purpose-bound — every request names the employer, the candidate, and which check it's for. No open-ended lookups.
• Consent-gated — nothing is checked until the candidate has authorized screening, recorded with a timestamp and method.
• Minimum necessary — we ask for the fields that answer one question, not the full underlying record.
• Results, not raw records — a partnership returns a verification result (match / no match / not found), never a copy of the source document.
• Auditable — every request and result is logged against the request code that created it.

Getting started

If you represent an institution that holds records ET Checker verifies against — or a new sector that needs its own check type — start with a conversation, not a contract:

1. Email us with who you represent and which check(s) you'd cover.
2. We scope the exact fields together — request shape, response shape, expected volume.
3. A partner API key is issued once a data-sharing agreement is signed.
4. We integrate, test against real requests, then go live.