Skip to main content
Audact
See the offer

Integration · IDnow

Verify who is on the line, mid-call.

Planned · no date set

IDnow is widely used for identity verification in regulated onboarding across DACH. The planned integration lets an agent trigger a verification the moment a caller agrees to a product, and links the result into the receipt for that call, so the identity check and the conversation that required it are one record.

What the agent produces per call

{
  "event": "call.completed",
  "outcome": "identity_verification_started",
  "receipt_id": "rcpt_01HX7K9M3P4Q5R6S7T8U9V",
  "article_50": { "disclosed": true, "clause": "1", "at_turn": 1 },
  "consent": { "captured_at_turn": 11, "scope": "identity_verification" },
  "write_back": {
    "system": "idnow",
    "method": "video_ident",
    "case_ref": "idn_2026_0841",
    "linked_receipt": "rcpt_01HX7M2N3P..."
  }
}

Worked example. Acme GmbH and Nova Industries are fictional; no customer data appears here.

Where a verification method involves biometric processing, the consent for it carries its own scope. It is not folded into the consent for the call.

What applies around the verification

Processing biometric data for the purpose of uniquely identifying a person is prohibited unless one of the narrow grounds applies, explicit consent among them.
Regulation (EU) 2016/679 (GDPR), Art. 9(1) and 9(2)(a)
The person must be told they are speaking to an AI system, before anything is agreed.
Regulation (EU) 2024/1689, Art. 50(1) and 50(5)
Consent must be demonstrable by the controller, and as easy to withdraw as to give.
Regulation (EU) 2016/679 (GDPR), Art. 7(1) and 7(3)

What Audact governs in the call

Article 50 disclosure at the top of the call, recorded.
In controlled testing
Outbound eligibility before every dial in a regulated campaign.
In controlled testing · Germany: national policy layer active. Netherlands: in development. Belgium and Austria: planned.
The gate reads a recorded consent state for biometric processing with its own scope.
In controlled testing
Triggering an IDnow verification and linking the result back.
Planned

Sector

Regulated outbound needs the identity at the moment of the yes.

Banking, insurance, telco activation and gambling all reach a point where the customer agrees and an identity check has to follow. Doing it later means a second contact and a drop-off; doing it in the call means the verification and the agreement share a moment — and, if it is recorded properly, a record.

Biometric verification is the part that deserves care rather than enthusiasm. Consent for it is captured on its own terms, with its own scope, and can be withdrawn on its own terms too. That is not a feature bolted on; it is the condition under which the rest of it is lawful.

Setup

Four steps, once the integration ships.

  1. Connect IDnow with your own subscription.
  2. Choose which flows may trigger a verification, and which method each uses.
  3. Configure the consent wording, separately from the consent for the call.
  4. Run in shadow mode, read the linked receipts, then switch to active.

Questions

Does Audact process biometric data?
No. IDnow performs the verification and holds what that requires. Audact records that consent was given, with what scope, and links the outcome reference into the chain.
Can the caller withdraw consent afterwards?
Yes, and it is recorded as its own event. Art. 7(3) GDPR requires withdrawal to be as easy as giving it, which is why the biometric consent is not bundled with the consent for the conversation.

Do not wait for the integration

Every integration will be built on the same six endpoints. They run inside the managed platform; no public API is served on api.audact.ai yet, apart from the published Merkle roots. Where a sector system exposes an API, the shorter route is to call it from your side and let Audact govern the conversation.

See the API

Related