Skip to main content

Overview

In B2B, an agent may act for a business through a particular person. A supplier portal or procurement system needs to know both: which business the agent represents and which person is acting for it. Verifying that the business exists doesn’t prove that the person may act on its behalf. For example, an agent for Harbor Concrete reorders parts from Acme Supply’s portal. Acme needs to know that the agent represents Harbor Concrete, which verified person is behind it, and that the person is verified to act for Harbor Concrete. Acme still decides whether to allow the reorder. Key challenges:
  • Identifying the business an agent represents
  • Identifying the person behind the agent
  • Confirming that the person is verified to act for the business
  • Evaluating the business and person separately when a rule applies to both
With KYA, the agent presents a business credential and the acting person’s credential.
  • Baselayer mints the two together and binds them to the same agent key.
  • It mints a business credential only when the operator link between the person and the business is VERIFIED.
  • The credentials establish identity and the relationship between the two.

How it works

1

Verify the person and the business together

Do one of these:Include the business’s tax ID (tin) so the link can verify on its own.The response includes an individual_ref, a business_ref and the link’s status. See Verifying an Identity.
2

Check the operator link

The link is VERIFIED when:
  • A tax ID was provided.
  • The IRS matched it to the business name.
  • The business was verified against its state registry.
If a check fell short, the link is UNDER_REVIEW and its shortfalls say which.
3

Review links that need a decision

  1. List links with status=UNDER_REVIEW.
  2. Look at the evidence.
  3. Approve or reject each one.
Decisions apply only to your organization. See Who Can Act for a Business.
4

Mint the business credential

Ask Baselayer to mint for the person and the business with level: L3, the only level a business credential takes. level: L2 is refused with error code 6320.The mint returns two credentials minted together: the business’s and the person’s.Each carries only the fields allowed by the site’s published scope.A mint for a link that isn’t VERIFIED is refused with error code 6300. See Minting Credentials.
5

The agent presents the pair

The agent signs both credentials with the same key and the same nonce. In the token exchange:
  • The business credential goes as subject_token.
  • The person’s goes as actor_token.
6

Verify the pair as one

The site checks the business credential (subject_token) and the person’s (actor_token) together, as one unit.If either credential fails, the whole presentation is refused. A business credential sent without its person is refused with actor_mismatch. See Business Agents.
7

Check both the business and the person

Each credential carries its own checks.
  • verification.active_keys lists the business’s checks only.
  • act.verification.active_keys lists the person’s checks only.
For any rule that should cover both, such as a clear watchlist result, require both. A check that passed for the business may not have passed for the person.

What each party sees

The site sees:
  • A site-specific ID for the business (sub).
  • The acting person’s site-specific ID (act.sub).
  • Separate verification results for each (verification.active_keys and act.verification.active_keys).
  • Their expiry.
  • Any shared fields.

Next steps