Agent-Credentials

Purpose

The “companyAgent” credential ensures that the user has access to an official communication channel of a company. Therefor you can request company credential along with it. But it doesn’t provide any information about the person.

A Minimal Order

If you don’t care about the company the user is an agent of, you can simply define your order like this:

{
  "verifierId": "[VERIFIER_ID]",
  "webhook": "[WEBHOOK_ADDRESS]",
  "redirects": {
    "success": "[SUCCESS_REDIRECT]",
    "failure": "[FAILURE_REDIRECT]"
  },
  "requiredCredentials": [
    "companyAgent": true
  ],
  "acceptedIdMethods": ["itm_videoident", "nect_autoident", "pinletter_ident"],
  "offeredIdMethods": ["itm_videoident", "nect_autoident", "pinletter_ident"],
}

Here we added the offered and accepted ID methods straight away to allow the user to actually use the method with the least friction.

Pitfalls

Requesting person credentials along with the “companyAgent” credential and allowing only the “pinletter_ident” method will result in an error response.