---
title: "Zero-Sum by Design: 10 Years of Uber’s Payments Platform"
description: "Uber’s Payments Platform, internally called Gulfstream, grew from a small 2016 microservices effort into infrastructure supporting $217 billion in annualized gross bookings, nearly twice that amount in total money movement, and ledger balances for more than 1.2 billion entities. It is built around immutable Money Orders, zero-sum double-entry accounting, strongly consistent ledger balances, and three core models: money orders, ledgers, and entity changelogs. Independent stateless services communicate primarily through Apache Kafka, while generic abstractions for lines of business and payment instruments let new products and methods plug into the platform; synchronous in-session flows use Cadence. As scale and audit requirements increased, Uber introduced Entity Fares, addressed hot ledger entities, and built LedgerStore for auditability and tamper-evident record-keeping, while also extending the ledger as a multi-tenant service."
---

# Zero-Sum by Design: 10 Years of Uber’s Payments Platform

[Uber](https://yomu.fyi/company/uber) · Aug 10, 2026

**Type:** Explainer

## Summary

Uber’s Payments Platform, internally called Gulfstream, grew from a small 2016 microservices effort into infrastructure supporting $217 billion in annualized gross bookings, nearly twice that amount in total money movement, and ledger balances for more than 1.2 billion entities. It is built around immutable Money Orders, zero-sum double-entry accounting, strongly consistent ledger balances, and three core models: money orders, ledgers, and entity changelogs. Independent stateless services communicate primarily through Apache Kafka, while generic abstractions for lines of business and payment instruments let new products and methods plug into the platform; synchronous in-session flows use Cadence. As scale and audit requirements increased, Uber introduced Entity Fares, addressed hot ledger entities, and built LedgerStore for auditability and tamper-evident record-keeping, while also extending the ledger as a multi-tenant service.

## Context

Uber needed a payments foundation that could support rapid growth in gross bookings and money movement, maintain balances for more than 1.2 billion entities, serve multiple lines of business and payment instruments, and satisfy increasingly demanding audit and compliance requirements.

## Approach / What changed

The platform uses immutable Money Orders validated through zero-sum and double-entry rules, strongly consistent ledger balances, independent stateless microservices, Apache Kafka, and generic abstractions for commerce transactions and payment integrations. Later changes included Entity Fares, measures for hot ledger entities, custom LedgerStore infrastructure, and a multi-tenant Ledger-as-a-Service model.

## Takeaways

- Immutable Money Orders preserve an auditable record; adjustments are represented by additional money orders rather than modifying an existing order.
- The ledger stores each entity’s sub-ledger accounts together in a DynamoDB row, prunes zero-balance accounts to control row size, and records balance updates in an entity changelog.
- Generic line-of-business and payment-instrument abstractions allowed products such as Uber Freight and payment methods including PayPal, UPI, and Apple Pay to use the core platform with little to no core changes.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [DynamoDB](https://yomu.fyi/topic/dynamodb), [Kafka](https://yomu.fyi/topic/kafka), [Payments](https://yomu.fyi/topic/payments)

- Source: [Uber](https://www.uber.com/us/en/blog/ubers-payments-platform)
- Source URL: https://www.uber.com/us/en/blog/ubers-payments-platform
- Ingested by Yomu: 2026-09-10T04:01:44.437Z

[Read original post](https://www.uber.com/us/en/blog/ubers-payments-platform)