Vishwasa-Antarkriyashilata: Trust and Interoperability

The Philosophy Behind Open Architecture

When a Google Pay user pays a PhonePe merchant, two competitors' apps work seamlessly together. This isn't an accident, it's the result of deliberate design choices rooted in ancient principles of trust and openness. This lesson explores how *vishwasa* (trust) and *antarkriyashilata* (interoperability) became the philosophical foundations of UPI, why NPCI chose openness over control, and what temples that served as trusted third parties can teach us about designing systems where rivals cooperate.

Two Rivals, One Transaction

March 2024, 8:47 AM. Priya opens Google Pay on her iPhone to pay for her morning coffee at a small café in Indiranagar, Bangalore. The café owner, Ramesh, has a PhonePe QR code displayed at his counter, not Google Pay.

Priya doesn't hesitate. She scans the PhonePe QR code with her Google Pay app. Within two seconds, ₹180 moves from her HDFC account to Ramesh's ICICI account. She receives a confirmation; Ramesh hears a 'PhonePe!' notification. Transaction complete.

Neither Priya nor Ramesh thinks this is remarkable. But pause and consider what just happened:

• Two competing apps (Google Pay and PhonePe) worked together seamlessly
• Two competing banks (HDFC and ICICI) transferred money instantly
• Zero friction, zero fees, zero thought about compatibility

In America, this transaction would be impossible. You cannot pay from Venmo to Cash App. You cannot pay from Apple Pay to Google Pay. American payment apps are walled gardens, deliberately incompatible to lock in users.

India chose differently. And that choice, encoded in UPI's architecture, reflects a philosophy older than fintech, older than banking itself: the principle that trust enables openness, and openness creates value for all.

The Temple as Trusted Third Party

To understand UPI's trust architecture, we must visit an unlikely source: ancient Indian temples.

In medieval India, temples were not just religious centers, they were commercial infrastructure. The great temples of Tirupati, Thanjavur, and Srirangam served as neutral spaces where merchants from rival communities could transact safely. The temple's sanctity provided something precious: trusted third-party verification.

A merchant from Gujarat and a merchant from Tamil Nadu might not trust each other. But both trusted the temple. So they would deposit goods or money with temple authorities, who would verify, hold, and release based on agreed terms. The temple was the original escrow service.

देवालये विश्वासः सर्वेषां, तत्र वाणिज्यं निर्भयम्

Devālaye viśvāsaḥ sarveṣāṃ, tatra vāṇijyaṃ nirbhayam

"In the temple, all have trust; there, commerce is without fear."

This principle, that a trusted neutral party enables transactions between parties who don't trust each other, is exactly what NPCI provides for UPI. Google doesn't trust PhonePe. PhonePe doesn't trust Google. But both trust NPCI, and that shared trust enables interoperability.

The temple model had another crucial feature: non-extraction. Temples facilitated commerce but didn't seek to dominate it. They earned through donations and offerings, not by taxing every transaction. NPCI operates similarly, a non-profit that facilitates without extracting.

The Architecture of Trust: How UPI Works

UPI's interoperability isn't magic, it's careful architecture. Understanding the technical design reveals the trust philosophy embedded within.

Layer 1: The Rails (NPCI)

At the foundation, NPCI operates the payment rails, the infrastructure through which all UPI transactions flow. When Priya pays Ramesh:

1. Google Pay sends a payment request to NPCI
2. NPCI routes it to HDFC Bank (Priya's bank)
3. HDFC debits Priya's account and confirms to NPCI
4. NPCI routes the credit instruction to ICICI Bank (Ramesh's bank)
5. ICICI credits Ramesh's account and confirms to NPCI
6. NPCI notifies PhonePe, which notifies Ramesh

NPCI is the trusted intermediary that both apps and both banks trust. Without this neutral layer, Google Pay and PhonePe would need to negotiate direct trust relationships, which they would never do, being competitors.

Layer 2: The Apps (Third-Party Applications)

Above the rails, apps like Google Pay, PhonePe, and Paytm provide the user interface. They compete fiercely on design, features, and customer experience. But they all speak the same language, UPI's open protocol, which NPCI defines and enforces.

This is controlled openness: anyone can build on UPI (open), but they must follow NPCI's rules (controlled). The rules ensure interoperability, security, and fair play.

Layer 3: The Banks (Trust Anchors)

At the deepest level, banks hold actual money and provide the trust anchor. When Priya pays, it's ultimately her bank (HDFC) guaranteeing the payment. The app is just an interface; the bank is the institution backing the transaction.

This layered architecture distributes trust:

• Users trust their apps (convenient interface)
• Apps trust NPCI (neutral infrastructure)
• NPCI trusts banks (regulated institutions)
• Banks trust RBI (sovereign authority)

Each layer can focus on its role because it trusts the layer below.

Global Perspectives: Why Open Systems Are Rare

If interoperability creates so much value, why don't more countries build open payment systems?

Paul Graham, Y Combinator founder, observed: "The best way to predict the future is to understand incentives." In most markets, payment providers have no incentive to interoperate. Venmo's value comes from network effects, the more friends you have on Venmo, the more locked in you are. If Venmo interoperated with Cash App, users could leave easily. Closed systems create moats; open systems destroy them.

India's UPI worked because NPCI mandated interoperability. Apps couldn't opt out. Google Pay couldn't refuse to accept PhonePe QR codes. The regulatory mandate overrode commercial incentives for closure.

Tim Wu, Columbia law professor and author of "The Master Switch," argues that communications networks naturally tend toward monopoly unless regulators intervene. UPI is a case study in such intervention, RBI and NPCI actively preventing the winner-take-all dynamics that plague American payments.

China provides a contrasting model. Alipay and WeChat Pay dominate Chinese payments, but they are not interoperable. A merchant must have separate QR codes for each. The duopoly competes, but users are still locked in. India explicitly rejected this model, mandating that all UPI QR codes work with all UPI apps.

The WhatsApp Lesson: Even Giants Must Play by the Rules

The power of UPI's trust architecture was tested when the world's largest messaging app tried to enter Indian payments.

In 2018, WhatsApp (owned by Facebook/Meta) announced WhatsApp Pay for India. With 400+ million Indian users, WhatsApp seemed unstoppable. They could leverage their existing user base to dominate payments overnight.

But NPCI and RBI had other ideas. WhatsApp faced unprecedented regulatory scrutiny:

Data Localization: WhatsApp was required to store all payment data in India, not on Facebook's global servers. This took years to implement.

Interoperability Compliance: WhatsApp Pay had to be fully interoperable, a WhatsApp user must be able to pay any UPI merchant, and WhatsApp merchants must accept any UPI app. No walled garden allowed.

Gradual Rollout: Instead of launching to 400 million users, WhatsApp was limited to 20 million, then 40 million, with permission to expand only after demonstrating compliance.

Market Share Caps: In 2021, NPCI announced that no single app could process more than 30% of UPI transactions, a rule that would prevent WhatsApp (or anyone) from monopolizing the market.

WhatsApp finally launched widely in 2022, four years after their initial announcement. By then, PhonePe and Google Pay had cemented their positions. The world's most powerful messaging platform was forced to compete on a level playing field, following the same rules as everyone else.

विश्वासः नियमैः रक्षितः, बलवान् अपि नियमं मानयेत्

Viśvāsaḥ niyamaiḥ rakṣitaḥ, balavān api niyamaṃ mānayet

"Trust is protected by rules; even the powerful must honor the rules."

This principle, that institutional trust requires rule enforcement, even against powerful players, echoes ancient guild governance where even wealthy merchants were bound by guild rules.

The Dharmic Foundation: Vishwasa as System Design

UPI's architecture embodies a dharmic principle: vishwasa (trust) isn't just a feeling, it's infrastructure. Trust can be designed, built, and maintained through institutions.

The Arthashastra recognizes three types of trust:

1. Svabhava-vishwasa (natural trust): Trust based on personal relationship, I trust my family
2. Karana-vishwasa (instrumental trust): Trust based on incentives, I trust because betrayal is costly
3. Vyavastha-vishwasa (institutional trust): Trust based on systems, I trust because institutions guarantee it

UPI operates primarily on vyavastha-vishwasa. Priya doesn't personally know Ramesh. She doesn't trust Google or PhonePe as companies. But she trusts the system, NPCI, RBI, the banking infrastructure, to ensure her payment reaches the right person.

व्यवस्था-विश्वासः वाणिज्यस्य मूलम्

Vyavasthā-viśvāsaḥ vāṇijyasya mūlam

"Institutional trust is the foundation of commerce."

This is precisely what medieval temples provided, and what UPI provides today. Personal trust doesn't scale; institutional trust does.

Modern Resonance: The 30% Rule and Market Balance

In late 2020, NPCI introduced a rule that would shape UPI's future: no single third-party app could process more than 30% of UPI transactions. At the time, PhonePe and Google Pay together handled over 80% of transactions.

The rule was controversial. PhonePe and Google Pay had earned their market share through better products and marketing. Why should they be penalized for success?

NPCI's reasoning reflected the trust architecture philosophy: concentration threatens interoperability. If one app dominates, it gains leverage to demand special treatment, resist rules, or eventually undermine openness. The temple model worked because no single merchant could dominate the temple; the 30% rule ensures no single app dominates UPI.

The rule also creates space for competition. New entrants like WhatsApp Pay, Amazon Pay, and bank-specific apps can compete knowing that incumbents can't lock up the entire market.

As of 2024, the rule is being implemented gradually, with PhonePe and Google Pay required to reduce their market share over time. Whether this succeeds, balancing innovation incentives with market diversity, remains an ongoing experiment.

Your Turn: Trust Architecture in Your Life

UPI's trust architecture offers principles applicable far beyond payments:

1. Trusted Neutrals Enable Cooperation: When rivals need to cooperate, a neutral party (like the temple, like NPCI) can enable transactions that bilateral trust cannot.

2. Rules Protect Trust: Open systems require rules that everyone, including the powerful, must follow. Without enforcement, openness degrades into winner-take-all.

3. Institutional Trust Scales: Personal trust is limited to people you know; institutional trust extends to strangers through shared systems.

Consider your own contexts: What "temples" enable cooperation between rivals in your field? What rules protect openness and prevent monopolization? Where could institutional trust enable transactions that personal trust cannot?

The chaiwala accepting payment from a stranger via UPI participates in a trust architecture that medieval temple administrators would recognize. The technology is new; the principle is ancient.

In our next lesson, we'll explore India Stack, the broader ecosystem of digital public infrastructure that includes Aadhaar, UPI, and more. You'll see how India is building not just payment rails but an entire digital layer for the economy.

Economists like Oliver Williamson analyzed how 'asset specificity' creates hold-up problems, once you invest in a relationship, you're vulnerable to exploitation. Neutral intermediaries reduce this risk by providing credible enforcement. Western solutions typically involve legal contracts; Indian tradition added institutional intermediaries like temples.

India's tradition of institutional intermediaries, temples, guilds, panchayats, provided cultural templates for NPCI's role. The idea that a neutral body could enable transactions between rivals wasn't foreign; it was traditional. This cultural foundation made UPI's design feel natural rather than imposed.

UPI processes transactions between 300+ banks and 40+ apps, all of whom are competitors. This would be impossible without NPCI as neutral intermediary. The volume of cross-app, cross-bank transactions (the majority of all UPI transactions) demonstrates the power of trusted third-party architecture.

Game theory emphasizes that cooperation requires 'credible commitment', the assurance that defection will be punished. In most Western payment markets, powerful players (Visa, Google, Apple) effectively capture regulators, preventing rules that constrain them. India's relatively stronger regulatory stance against powerful players (see WhatsApp case) is unusual globally.

India's regulatory willingness to constrain powerful foreign companies, requiring data localization, mandating interoperability, imposing market share caps, created the conditions for genuine openness. This isn't anti-business; it's pro-competition. The rules that constrain WhatsApp also constrain PhonePe, creating a level playing field.

WhatsApp Pay's delay from 2018 to 2022 demonstrates rule enforcement against the world's largest messaging platform (owned by one of the world's most valuable companies). This sent a signal: the rules apply to everyone. That credibility is essential for trust architecture.