Payment Rails

In the AI Story

The payment gap is a specific instance of a general problem de Soto identified throughout his career: the institutional infrastructure that the developed world treats as default requires specific preconditions that the majority of the world's population does not meet. A Stripe account requires a bank account. A bank account requires identity verification. Identity verification requires government documentation of a type not universally available. Each requirement is individually reasonable. Collectively, they constitute a filter.

Mobile money systems have partially addressed this gap in specific regions. M-Pesa in Kenya, OPay and Kuda in Nigeria, bKash in Bangladesh — these platforms have provided financial services to hundreds of millions of previously unbanked individuals. The success of mobile money demonstrates that financial infrastructure can reach populations that traditional banking cannot, when the infrastructure is designed for the population it serves rather than adapted from systems designed for someone else.

The limitation of mobile money for AI builders is its domestic character. Mobile money serves local transactions effectively but connects to international payment systems only with significant friction. A Nigerian developer who wants to charge users in the United States or Europe cannot typically receive that payment through mobile money directly. The payment must flow through intermediaries — banks, payment processors, or remittance services — each of which imposes fees, delays, and compliance requirements that can consume much of the margin on a small-scale software business.

The AI economy's payment infrastructure gap has specific consequences. A developer who builds a product that users want cannot capture revenue if the payment mechanism cannot accept the users' money and deliver it to the developer's account. The product exists. The business does not. The builder produces an artifact that generates value for users and no capital for herself — dead intelligence in its most literal financial form.

Closing the payment gap requires either extending existing payment rails to currently-excluded jurisdictions (which payment platforms have been doing incrementally) or constructing alternative rails designed for the excluded population (which mobile money has done domestically and which blockchain-based payment systems aim to do globally). Both approaches face genuine obstacles: regulatory complexity, fraud prevention, and the legitimate compliance requirements that make international payment systems operate at all.

Origin

The payment gap became visible as software-as-a-service business models became dominant in the 2010s, making payment infrastructure a more central component of the software economy. As subscription and micropayment models proliferated, the gap between payment-enabled and payment-excluded jurisdictions translated directly into a gap between builders who could monetize their work and builders who could not.

The AI era has intensified the gap because AI-powered products often rely on subscription or usage-based pricing — models that depend fundamentally on functioning payment rails. A developer whose product requires infrastructure costs that must be recouped through user payments cannot sustain the product if the payment mechanism does not reach her users and her bank account.

Key Ideas

Payment platforms concentrate geographically. Stripe's forty-seven countries represent only a minority of the world's nations, and other dominant platforms show similar concentration.

Identity verification is the filter. The documentation requirements of KYC compliance exclude those without government-issued documentation of specific types.

Mobile money addresses the gap partially. Domestic success demonstrates feasibility; international integration remains the remaining challenge.

The gap converts working products into failing businesses. The artifact functions; the revenue cannot flow; the developer receives nothing.

Closure requires institutional construction. Either extending existing rails or building alternatives — both require sustained work that technology alone cannot accomplish.

Debates & Critiques

Whether payment platforms have the capacity to extend to currently-excluded jurisdictions and choose not to, or whether the excluded jurisdictions have regulatory environments that genuinely prevent extension, is contested. Critics argue that platform extension has been slower than capacity allows. Defenders note that genuine regulatory obstacles, fraud risks, and compliance costs constrain extension. The question of what institutions should do about the gap depends partly on answering the question of why the gap persists.