The Scope Creep Automated reviews of new AI-related working group submissions

Update review · November 10, 2026

Identity Verification Methods Values Update (-03)

draft-skyfire-oauth-id-verification -03View on Datatracker →

Revision -03 adds five new ivm values for verifying organizations. Nothing else changed. None of the feedback from the previous review of -02 was addressed.

What Changed

The registry grows from eight values to thirteen. The new ones cover business verification (KYB):

  • brv: the organization's legal name, registration number, and status matched against an official company register, such as Delaware's Division of Corporations or Companies House in the UK
  • tin: legal name and tax identification number matched with the tax authority, such as the US IRS TIN Matching program
  • bdoc: business documents, such as a certificate of incorporation, certificate of good standing, or shareholder register
  • bov: the beneficial owners were identified and each one's identity was verified
  • rep: the identity of the person acting for the organization was verified, along with their authority to act for it

The draft also adds an informative reference to the FATF Glossary for the definition of "beneficial owner."

Nothing was removed. The authors are the same.

Why Add Organization Values?

The KYAPay token is the reason. KYAPay token -03 now carries ivm in two places. Inside hid it describes how the human principal was verified. Inside apd it describes how the agent platform was verified. An agent platform is a company, and the eight person-oriented values had nothing to say about a company.

The previous review noted that KYAPay didn't use ivm at all. That's fixed now, on the KYAPay side.

Was the Previous Feedback Addressed?

No. Every item is still open.

  • No mapping to OpenID IDA. The draft still says IDA can be used "with the ivm claim, or separately" and never relates the two vocabularies.
  • dbv, dbv1, and dbvm are still three values for one method.
  • No combination rules. A passport checked at a counter is still inp, phy, or both.
  • No biometric binding value. There's still nothing for a selfie or liveness match against the document photo.
  • No context. The claim still doesn't say when, by whom, or which attributes were verified.
  • US-centric definitions. "Consumer reporting data sources" is unchanged. The new tin example is the IRS.
  • Template errors. The registration template still describes "the authentication method or family of closely related authentication methods." inp and vid still use "Identity Verification Method Reference Name." RFC 5226 is still cited instead of RFC 8126. The ivm claim's change controller is still Mike Jones personally.
  • Security and privacy considerations. Each is still one sentence pointing at JWT.

New Problems in -03

"Whose identity?" got worse. The previous review asked which party ivm describes when the subject is an agent. KYAPay answered this for itself by nesting ivm under hid and apd and banning it at the top level. This draft didn't follow. The abstract and introduction still say the claim declares "how the person's identity was verified," while five of the thirteen values now describe an organization. In any JWT other than a KYAPay token, a top-level ["phy", "brv", "rep"] doesn't say whose passport was scanned. The fix KYAPay applied belongs in this draft: say that ivm describes exactly one subject, and say how a token identifies that subject.

bov and rep are verification of other people, compressed into one string. bov says each beneficial owner's identity was verified. rep says the representative's identity was verified. Neither says how. The draft already has eight values for how a person was verified, and they can't be used here because the array is flat. A relying party that requires document verification for the representative can't tell rep backed by a passport scan from rep backed by an email to the company's domain.

rep mixes identity and authority. It covers both who the representative is and whether they can act for the organization. Those are separate checks with separate failure modes. Authority to act is an authorization fact, and it's the more important one in an agent payments context. One issuer will emit rep after checking a board resolution. Another will emit it after checking a LinkedIn title.

bov has no threshold. FATF's definition leaves the ownership threshold to each jurisdiction. Most use 25%, some use 10%. Two issuers emitting bov may have verified different sets of people. The definition also depends on an informative reference to a web page with no date or version.

tin is defined only for organizations. The definition says "the organization's legal name and tax identification number." A US SSN is also a TIN, and dbv already lists ssn as a matched attribute. A sole proprietor verified by SSN could be tin, dbv, or both.

brv and bdoc repeat the combination problem. A certificate of good standing is issued by the same registry that brv checks. An issuer that downloads one from the Delaware site has done brv, bdoc, or both.

The IDA gap is wider. The eKYC & IDA working group also has work on legal entities and on natural persons acting for them. The draft now overlaps with that as well, still with no mapping.

Writing Quality

The new sections match the existing style: one line of definition per value, no guidance on when to emit it. The new definitions are better written than the old ones. They spell out what was matched and give non-US examples for brv.

The title, abstract, and introduction weren't updated for the new scope. A reader of the first page will think this draft is only about people.

The privacy considerations matter more now. bov discloses that the issuer has identified the natural persons who own the company. rep discloses that a specific person's identity was checked. The section is still one sentence.

Bottom Line

This revision expands scope without fixing anything. The organization values are driven by a real need in KYAPay, and KYAPay -03 handles the subject ambiguity well on its own side. This draft needs the same treatment. Feedback should repeat the three asks from the last review: align with OpenID IDA, collapse the dbv variants and define combination rules, and write real privacy considerations. Add two new asks. State that an ivm array describes exactly one subject, either a person or an organization. Split rep into identity and authority, or drop the authority half and leave it to a claim designed for delegation.