Canonical infrastructure terms are defined in the PTI Glossary. This glossary covers TumiTrust-specific product terminology.
TumiTrust Product Glossary
Living dictionary
Every Portable Trust Infrastructure term in one place — platform, hub, partner ingest, and API — built to scan, not slog.
Portable Trust Infrastructure (PTI)
The trust network on TumiTrust: partners generate signals from activity; the platform derives context-scoped outcomes; institutions and members consume trust reports under platform rules. Generation is separated from consumption.
Overview: Portable Trust Infrastructure.
Trust layer
Product stance: credibility surfaced whenever an important decision is on the line — hire, house, lend, partner, admit — not a curiosity score checked once a month.
Portable trust
Proof you can carry across organizations on the network — via Trust CV, context indicators, and authorized reports — within visibility settings and product rules.
Trust Bridge (Portable Trust Bridge)
Trust Bridge shows how you know someone through people you both know — for example a friend who can introduce you, or a longer path through a few connections. In the app you see that path as a map and a simple step-by-step journey. The formal name is Portable Trust Bridge; the short label PTB may appear in tight spaces.
Not the same as portable trust (proof you share with organisations) or a Trust Chain (a trail of formal checks back to trusted organisations).
PTB
Short name for Trust Bridge (Portable Trust Bridge).
PTI-ID
Portable Trust ID — subject key shaped pti_{CODE} (e.g. pti_9A72X8K2). Links partner entity ids (merchant id, subscriber id) to one trust subject. Immutable once issued. Used in webhooks, widgets, and partner payloads.
Say Portable Trust ID in speech and UI tips — not “Portable Trust Infrastructure ID.” PTI (the platform) still expands to Portable Trust Infrastructure; PTI-ID is the portable subject identifier on that network. Native members also use numeric user ids for directory and trust-reports flows.
Trust producer
Organization that feeds PTI: webhooks, API, CSV, connector. Console: Pulse, Partner Operations, TCU billing. For partners
Trust consumer
Organization that reads outcomes: Lookup Studio, trust report API, report credits — not ingest or TCU. For institutions
Hybrid tenant
One institution tenant that both produces and consumes trust — e.g. bank plus data affiliate. Glossary: hub mode
Hub mode
How the institution hub adapts navigation and widgets:
| Mode | Console emphasis |
|---|---|
| Institution consumer | Lookups, credits, team, billing |
| Partner producer | Pulse, ingest funnel, TCU, connector |
| Hybrid | Both arcs visible |
Trust context
Life-area scope for signals and scores — e.g. lending, rental, merchant. 20+ documented contexts (10 primary + 10 lens). Scores stay isolated by context.
Full table: Documented trust contexts.
Primary context
Core life-area scope partners emit and consumers request on reports — e.g. lending, rental, employment, merchant, informal_sector.
Lens context
Cross-cutting view derived from primary activity — e.g. education, health, family, digital_platform. Consumers may request on reports; producers enable direct lens emission only when contract covers it.
Headline indicator
Member-facing overall trust indicator where the product shows one. Not a naive average of every context — it reflects platform rules for your account. Exact scales and field names are in the API reference.
PTS (Portable Trust Score)
PTS means Portable Trust Score — your overall trust number in the app (typically 0–1000). Different from PTI (the platform) and PTI-ID (your subject id). Numbers for one life area (work, rent, and so on) are context scores.
Context indicator
Indicator for one trust context (employment, rental, lending, and so on). Used in reports, Pulse filters, and API context fields. Prefer reading the explain summary with the number — not the number alone.
TumiTrust score (legacy: Ubuntu score)
Cover term for overall + context trust numbers. In the product you will usually see PTS, TumiTrust score, or trust score. Avoid “ubuntu-score” and “PTI score” in everyday copy (PTI is the platform; the score is the trust signal). APIs may still use older field names.
Grade bands
Colour or label tiers the app prints for quick reading (e.g. strong / building / early). Bands are illustrative in UI — always read numeric indicators and explain text for decisions.
Explain summary
Plain-language why behind context indicators in a trust report or intelligence payload — part of trust_intelligence.v1.
trust_intelligence (trust_intelligence.v1)
Structured JSON envelope on completed reports: explain_summary, context_scores, partner_attestation, lookup_scope.contexts_included, etc. Schema version trust_intelligence.v1.
Report tier
Depth of a generated trust report — commonly basic, detailed, predictive. Set on POST …/trust-reports/reports/generate/.
Score contract & trust assurance
Public promise that API and PDF fields match documented ranges and semantics — institutions rely on stable JSON for automation. Machine-readable detail: OpenAPI at tumitrust.com/api/docs/.
Trust lookup
Structured check producing a trust report on a subject — scores, explainability, time-limited access, often PDF. Run from platform (member) or hub/API (organization). Credits debit from the runner.
Not the same as Trust CV or profile search.
Trust CV (shareable trust profile)
Free portable profile share — link, QR, Open in TumiTrust — within visibility settings. For voluntary proof before a formal lookup.
Profile search (browse)
Discover profiles within visibility rules — no structured report, no lookup credit charge.
Trust report
Output of a trust lookup — JSON + optional PDF. Includes Report ID for verification. Integrators: Trust platform API.
Portable Trust Profile
The PDF (or printable) trust briefing an organisation gets after a trust lookup. Cover and authenticity pages say Portable Trust Profile. It includes your PTS, trust band, context detail, and a QR code tied to the Report ID so others can check it is real. How deep it goes depends on the report tier (basic, detailed, predictive). Different from a member Trust CV (your ongoing profile) and from the raw API JSON.
PTP
Short name for Portable Trust Profile.
Affiliation confidence
Trust metric on a member↔organisation edge (work-history confirm, roster link, or team seat). Raises when the organisation confirms the claim, when evidence is present, and when platform chronology is known — e.g. the member was on TumiTrust before the organisation onboarded, or the organisation existed first. Chronology adds confidence; it does not invent a social network. Feeds the PTP work-history / relationship lane. See PTI: Affiliation Confidence.
Report ID
Unique identifier on a lookup report (e.g. for verification URLs and audit). Third parties can confirm authenticity without seeing full private detail.
Community validation
Endorsements, connections, and peer-visible activity strengthening your profile — alongside verified activity from partners and institutions.
Endorsement (vouch)
Context-specific vouch from someone in your network — strength, message, and context tag optional. Core community validation signal.
Badge
Institution-backed verification — employment, tenancy, insurance, education, merchant, etc. May decay or revoke when relationships change.
Verifier
Institution role: issues badges and runs verification queues — in addition to or instead of passive lookups. For institutions
Tribe
Your intentional trust network on the platform — connections you curate for endorsements and visibility (label may vary by build).
Circles
Group contexts on the platform — savings groups, cooperatives, or community units where your plan supports shared standing (label may vary).
Introductions
Signal interest in an organization or opportunity with the trust fields you allow to travel — distinct from a full trust lookup.
Cooperatives & savings groups
Community finance groups whose standing may appear as signals where Circles or group products are available in your region.
Roster (organization roster)
Institution-maintained list of subjects without smartphones — onboarding path for organizations serving members who cannot use the app directly. For institutions
Thin file
Little or no traditional bureau history — common in emerging markets; under-documented, not untrustworthy. TumiTrust surfaces community validation, badges, and optional connectors.
Trust requests
In-app flows asking someone to endorse, verify, or connect — surfaced in inbox / notifications where enabled.
Platform languages
Locales shipped in web/mobile builds. Switch in Settings where supported.
Deep link & Open in TumiTrust
Web URL opening the platform with context — profile, Trust CV intent, verification. Also called Open in TumiTrust.
Trust passport (informal)
Playful shorthand for Trust CV or portable trust — not a separate product or government ID.
Home, inbox & device lock
- Home: shortcuts to scores, shares, alerts
- Inbox / notifications: trust requests, intros, badge updates
- Device lock: PIN / biometrics in Settings → Security where supported
Institution hub
Web console for organizations on tumitrust.com — team, billing, Lookup Studio, and (for producers) Pulse / Partner Operations.
Lookup Studio
Consumer console to search subjects, generate reports, track status, download PDFs. Same /api/v1/trust-reports/ contract as API automation.
Screening services
TumiTrust product for sanctions, PEP, and UN list checks — hub Screening Intelligence, partner embeds, and Compliance Center audit. Hosted by TumiTrust; not part of the open PTI specification. See Screening services.
List pack
A focused set of lists for one screening run (for example Sanctions + PEP, or UN Security Council lists). Out-of-pack checks are marked skipped, not silently clear.
Compliance Center
Institution hub surface for screening history, coverage, and CSV audit export. Complements Screening Intelligence (where you run checks).
Pulse
Producer command center — ingest volume, TCU timelines, context filters, link to Insight Studio.
Insight Studio
Event-level audit inside Pulse (producers) or intelligence views on completed reports (consumers).
Partner Operations
Producer console for connector health, ingest funnel, CSV batches, usage dashboard, and event feed. Open from your institution hub under Partner operations.
Directory (people search)
GET /api/v1/directory/people/search/ — resolve subjects by name, phone, email, or id before generate. Complements GET /api/v1/trust-reports/search/.
Subject
Person or entity being looked up — numeric user id and/or PTI-ID depending on onboarding path.
Credits (report credits)
Wallet balance for trust lookups and premium institution flows. Distinct from partner TCU. Trust CV and profile building typically free for members.
TCU (Trust Compute Units)
Postpaid meter for partner compute — ingest, recompute, signal processing. MTD TCU = month-to-date in open billing period. Partner billing
MTD TCU (tcu_mtd)
Month-to-date TCU for an open billing period, often per context in hub APIs.
Usage period
Calendar window (monthly, quarterly, annual) accumulating partner TCU before invoicing.
Rate card
Published TCU cost per operation type (event ingest, recompute, etc.) applied when recording usage.
Invoice forecast
Projected end-of-period TCU total and USD estimate from current run-rate in Partner Operations.
Trust update batching
Groups rapid partner activity so scores refresh once per window instead of on every single event — protects subjects and compute.
TrustEvent
Normalized ingest atom after webhook/API/CSV acceptance — carries context_id, channel, idempotency key — before downstream signals exist.
Partner activity record
Single business event from a partner (order completed, repayment, verification) mapped through the event catalog.
Event catalog
Partner-specific list of event_type values, trigger rules, and context mappings configured in the hub.
Ingest channel
How an event arrived: webhook, api, csv, or connector. Used in Pulse funnels and TCU attribution.
Connector & data connection
Single integration profile per partner: webhook URL, credentials, delivery policy, per-context channels. Data connection = sync adapter to your platform.
CSV batch & batch_id
Bulk ingest via Data upload studio — one context per batch, batch_id for Pulse audit. CSV upload guide
Webhook
HTTPS callback from TumiTrust to your server — e.g. trust_report.generated for consumers, partner delivery receipts for producers. Verify HMAC signatures in production.
Trust signal
Product term for derived inputs to scoring after ingest — distinct from raw partner payloads. Used in API naming (/api/v1/trust-signals/… for webhook registration).
Organization API key
Secret prefixed e.g. tt_live_… / sandbox variant — sent as X-API-Key on trust-reports automation. Created under API & trust signals in the hub.
Bearer token
Session JWT for hub users — used to register webhooks, manage workspace settings — not for high-volume report polling (use API keys).
Sandbox and live API keys
Sandbox keys for integration and testing; live keys after account verification and deliberate go-live. Sandbox report generate calls share a daily budget per account (UTC). Trust platform API
Base URL (API)
Product JSON lives under https://tumitrust.com/api/v1/ unless your contract specifies a dedicated API endpoint.
Roles on the network
| Role | Guide |
|---|---|
| Individual / member | For individuals |
| Trust producer | For partners |
| Trust consumer | For institutions |
| Verifier | For institutions |
| Hybrid | Producer + consumer guides |
Busy-time reliability
Platform should stay legible under load — flows complete on slower networks and during peaks, not only in quiet demos. FAQ: reliability
Ubuntu (philosophy)
“I am because we are” — community-shaped trust: credibility from relationships and validation, not only solitary transactions. Ubuntu Intelligence is the product label for broader cross-context tools in hub and reports.
OpenAPI
Machine-readable API contract at tumitrust.com/api/docs/ — authoritative for integrators when field names differ from prose.
See also
- FAQ — questions by audience
- Trust platform API
- Documented trust contexts
- Get started