Tribal VerifyIdentity verified by the Nation.
Developer integration

One verification interface. Nation-controlled answers.

Tribal Verify provides one verification contract across participating Nations while each Nation controls its own matching profile, source of truth, review rules, and approved response.

Request flow

  1. An approved relying organization requests tribal_citizenship.
  2. Tribal Verify validates the organization, purpose, consent, and requested Nation.
  3. The Nation connector receives the minimum lookup fields configured by that Nation.
  4. The Nation's authoritative system returns match / exception / no-match to its gateway.
  5. Routine matches resolve automatically; exceptions enter the Nation staff queue.
  6. The relying organization receives only the approved assertion and audit reference.
Example minimum request
{
  "nation": "cherokee-nation",
  "member": {
    "legal_first_name": "Avery",
    "legal_middle_name": "T",
    "legal_last_name": "River",
    "date_of_birth": "1988-03-14",
    "tribal_member_number": "TV-CN-1001",
    "card_type": "Cherokee Nation Photo ID",
    "card_issue_date": "2025-01-15"
  },
  "attribute": "tribal_citizenship",
  "consent": true
}
Lookup contract

Common core, Nation-specific profile.

Core identity

Legal name and date of birth provide the human identity context needed to distinguish records.

Nation identifier

Citizenship, membership, enrollment, roll, census, or other Nation-issued number configured per Nation.

Optional credential data

Card type, issue date, expiration date, or other card fields can be enabled only when the Nation wants them used.

Excluded by default

SSN, blood quantum, genealogy, address, and card images are not part of the standard verification request.

Nation connector strategy

Nation connectors run with read-only, least-privilege access and return a narrow matching decision rather than exporting a Tribal roll into Tribal Verify.

REST / API

Preferred for modern Nation-owned or vendor enrollment systems with supported service APIs.

Microsoft Dataverse

For Power Platform-based enrollment environments under Nation-controlled credentials.

SQL gateway

Read-only, allow-listed queries through a Nation-side gateway for custom or legacy systems.

Vendor adapters

Purpose-built mappings for major Tribal enrollment vendors without changing the public Tribal Verify contract.

Example approved assertion
{
  "verified": true,
  "nation": "Cherokee Nation",
  "attribute": "tribal_citizenship",
  "verification_id": "TV-VER-A82F93...",
  "issuer": "Cherokee Nation"
}

Data boundary

Payment processors receive only opaque billing references. Relying parties receive only the approved verification result. Nation staff can see the lookup fields needed to resolve an exception. The authoritative citizenship record remains with the Nation.