MétaCan
Menu
Back to cohort
Record W4385289483 · doi:10.17645/si.v11i3.6687

Transformation of the Digital Payment Ecosystem in India: A Case Study of Paytm

2023· article· en· W4385289483 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueSocial Inclusion · 2023
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicDigital Platforms and Economics
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsPaymentDigital economyDatabase transactionDigital ecosystemBusinessAuditEconomicsAccountingFinancePolitical science

Abstract

fetched live from OpenAlex

Paytm is a payment app in India providing e‐wallet services; it is also the most prominent mobile e‐commerce app in the world’s third‐largest economy. This article uses Paytm as a case study to better understand the global platform economy and its implications for social and economic inequities. We contextualize the emergence of Paytm by drawing attention to its relationship with India’s developing digital infrastructure and marginalized populations—many of whom are part of the platform’s user base. We use a political economy lens to investigate Paytm’s market structure, stakeholders, innovations, and beneficiaries. Our research is guided by the question: What resources, infrastructures, and policies have given rise to India’s digital payment ecosystem, and how have these contributed to economic and social inequities? Accordingly, we audited the international and Indian business press and Paytm’s corporate communications from 2016 to 2020. Our analysis points to the tensions between private and public interests in the larger platform ecosystem, dispelling notions of platforms as neutral arbiters of market transactions. We argue that Paytm is socially beneficial to the extent that it reduces transaction costs and makes digital payments more accessible for marginalized populations; it is detrimental to the time that it jeopardizes user data and privacy while suppressing competition in the platform economy.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.464
Threshold uncertainty score0.180

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.018
GPT teacher head0.230
Teacher spread0.211 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it