Registry coverage and source policy

Pilot coverage. This table describes the latest version in the separate test installation, not the older production app. Confirm your shop’s version and licence class before a pilot.

Professional licence checks depend on the issuing authority and exact licence class. The classes below have configured lookups; other professional applications require staff to check the official source. A result never approves a buyer automatically.

Registry catalog audited 4 September 2026. It contains 23 source resources and 132 jurisdiction-and-credential rows. 5 resources are withheld by policy or freshness gates. Pilot coverage JSON · Source catalog JSON.

The broader Registry service has 15 enabled US resources across 6 states and manual links for 37 US jurisdictions. Those totals include legacy lookups without licence-class scope and are not a claim that every professional licence in those states is supported. It also has 29 configured European VAT jurisdictions; the app does not accept VAT numbers. Catalog configuration is not a live availability guarantee.

Professional classes with configured lookups

Enter the licence type and issuing authority as printed. Automatic lookup still depends on source availability and freshness at the time of the check. Texas TDLR and Illinois beauty licences are not enabled.

How a lookup runs

The application sends only the credential type, two-letter jurisdiction and number to the separate BuyerClear Registry Worker. The request never contains a buyer name, email, document, shop identifier or application identifier. The Registry Worker selects every applicable enabled source and queries them in parallel.

Identifier comparison belongs to each source connector. Leading zeroes are preserved, and a name never selects a record. If one applicable source is unreachable, stale or ambiguous, the result stays with a person instead of turning another source’s silence into “not found”.

US application coverage

These are the two credential types accepted by the pilot application. Automatic means a source is configured for the listed scope; each lookup still depends on availability and freshness. An official-search link remains available as a staff fallback where the issuing authority publishes one.

Source catalog by zone

The catalog includes sources that run, sources held back by a policy or freshness gate, and integrations that need production credentials. “Manual fallback” means BuyerClear does not call that API; staff receive the authority’s public search instead.

European Registry capability

VIES validates VAT numbers across its EU VAT jurisdictions and Northern Ireland. Norway uses the live Brønnøysund entity endpoint. The UK HMRC connector remains a manual link until production OAuth credentials are approved and configured. These connectors belong to Registry, but the BuyerClear application’s current form and domain model remain US-only.

Storage, refresh and policy

Lookup storage

The Registry Worker has no database or object-store binding. It does not persist request bodies or upstream responses, sends Cache-Control: no-store on lookup results and disables invocation logs that could retain credential numbers.

Response limits

Requests are capped at 2 KiB. A Socrata response is capped at 256 KiB; VIES, Brønnøysund and HMRC responses are capped at 64 KiB. Each upstream request has an eight-second timeout.

Source freshness

Each roster owns a maximum accepted age. A roster older than that limit becomes unavailable. Live VAT services do not publish a common per-record refresh timestamp, so their answer is evidence for the time of the request.

Public metadata

Coverage and source metadata may be cached for five minutes. The source catalog records the exact endpoint, selected fields, request trigger, timeout, response limit, publisher cadence, observed refresh, freshness limit and policy documents.

Application evidence

The calling BuyerClear application stores the returned evidence encrypted with the case record. Customer and shop erasure remove it. A time-based retention schedule for non-document evidence still has to be fixed before paid production use; the 90-day document setting does not define this separately.

Adding or enabling a source

A source moves to automatic use only after its identifier rules, response schema, freshness, reuse terms, attribution, privacy and deletion duties are recorded and tested. The live catalog is the source of truth for that decision, including sources that remain disabled.

Tell us which jurisdictions your buyers need.