PTI and Digital Public Infrastructure
Digital Public Infrastructure (DPI) refers to shared, interoperable public rails — digital identity, instant payments, open data registries, and consent managers — that enable inclusive service delivery at national scale. PTI is a trust layer that composes DPI components into governed, portable trust intelligence for private and public sector decisions.
1. What digital public infrastructure is
DPI stacks typically include:
- Digital identity — national ID, authentication, attribute sharing
- Payment rails — real-time retail payments (UPI, Pix, FedNow-style systems)
- Open data and registries — business registration, land records, tax identifiers
- Consent managers — citizen-controlled data sharing (Account Aggregator, CM frameworks)
- Open protocols — Beckn, MOSIP, and interoperable API standards
DPI answers: How do we build inclusive digital services on shared public foundations rather than proprietary silos?
2. What problem DPI solves
| Problem | DPI response |
|---|---|
| Fragmented citizen services | Shared identity and data rails |
| Cash-heavy informal economy | Instant payment ubiquity |
| Private gatekeeping of public data | Open registries and APIs |
| Cross-ministry duplication | Reusable infrastructure components |
DPI solves access and interoperability at population scale. It does not automatically define how private institutions evaluate trust across lending, rental, employment, and commerce — nor how behavioral signals from diverse partners compose under consent and audit.
3. What PTI adds
Digital public infrastructure
- Identity, payments, registries, consent
- Public-good interoperability rails
- Citizen-to-government service delivery
PTI adds
- Trust as DPI layer — programmable trust lookup alongside ID and payments
- Private-sector signal exchange — governed producer/consumer model
- Context-scoped outcomes — same citizen, multiple life-area evaluations
- Inclusion thesis — thin-file populations access credit via portable proof
Policy thinkers describe India Stack (identity + payments + data consent) as foundational DPI. PTI extends that model with Trust Stack semantics — not replacing UPI or Aadhaar, but enabling MFIs, landlords, and employers to consume portable trust built on top of those rails.
4. How they compose together
National inclusion pattern:
- Citizen authenticates via national digital ID (DPI identity layer).
- Payment and account activity flows through consent manager to authorized trust producers.
- PTI ingests derived trust events — repayment, income regularity, business registration confirmation.
- Regulated institutions and government programs run trust lookups for SME lending, social housing, or farmer finance — with sovereign auditability.
Governments MAY operate PTI-compatible trust exchange as public infrastructure; private implementations MUST interoperate via RFC-006 — Trust Exchange profiles.
5. When to use each
| Scenario | DPI component | PTI |
|---|---|---|
| Citizen receives pension payment | Payment rail Required | Not involved |
| National farmer subsidy eligibility (identity-only) | ID + registry | Optional |
| Inclusive MFI lending at scale | ID + payments DPI | PTI Recommended |
| Cross-ministry data sharing | Consent manager | PTI for trust outcomes |
| Private landlord screening | ID verification via DPI | PTI rental lookup |
PTI extends DPI; it does not compete with sovereign identity or payment authority.
6. Related PTI spec/RFC links
- RFC-001 — Architecture
- RFC-006 — Trust Exchange
- Interoperability specification
- Governance specification
- Why PTI Exists — inclusion thesis