I came across a piece by Stripe's Mason Reeves called Cloud Clearing. In short, it analyzes how money leaks through fragmented cross-border payment settlement and proposes an architecture that unifies everything into a single optimization engine.

The problem with today's payment infrastructure is that each rail is an isolated system optimizing only one cost dimension:

• Visa nets card transactions but ignores FX.

• ACH reduces time costs but doesn't consider exchange rates.

• CLS eliminates FX settlement risk only.

• Fedwire maximizes certainty but also maximizes cost.

Take a Korean SaaS company that receives $500K via cards in the US and €300K via SEPA in Germany, while paying $120K to AWS and €80K to a German contractor. Four separate pipelines run independently, and card fees, FX spreads, correspondent bank fees, and SWIFT fees all stack up redundantly.

Reeves' explanation for why this hasn't been unified is straightforward. In financial markets, your counterparty might know something you don't, so FX needs FX specialists, rates need rates specialists, and credit needs credit specialists, each managed separately. But commercial payments are different. The $50K owed to a supplier is a fixed obligation set at invoice time. There's no hidden information. And without hidden information, there's no reason for separate specialists. A single system can optimize all costs simultaneously.

First, we need to define what's being optimized. Every payment has five cost dimensions attached to it at once.

• Credit: risk tied to the form of money. Depending on what form of money is used for settlement, the counterparty's perceived risk changes, and that difference shows up as cost. Currently, card networks bundle this risk into interchange fees.

• Time (interest): the opportunity cost of funds tied up while settlement is delayed. With T+2 card settlement, a merchant can't use two days' worth of funds. Merchants don't see this cost explicitly. It gets absorbed by processors earning interest on pending funds, or baked into processing fees.

• Currency (FX): conversion costs. The spread that correspondent banks or FX brokers add on cross-border transactions. In the Korean SaaS example above, four separate conversions each carry a 0.4–0.5% spread.

• Liquidity: how much the actual transfer amount can be reduced through netting. The more offsetting flows there are, the higher the compression ratio. CLS achieves 99% compression on FX alone. Currently, each rail only nets within its own network, missing all cross-rail offset opportunities.

• Operational costs: fixed per-rail fees. Moving the same amount can cost orders of magnitude more depending on which rail you use.

Previously, five separate systems priced each of these independently. Cloud Clearing optimizes all of them simultaneously within a single objective function.

Here are the four tools for optimizing these variables.

1. Netting: offset opposing obligations against each other. When A owes B $100K and B owes A $70K, only the $30K difference moves. Cost is near zero, so this runs first.

2. Gross settlement: send the remaining balance after netting through an actual rail. Fedwire, SWIFT, stablecoin transfers fall here. Because rail fees apply, this is used last and minimally.

3. Bridge financing: when outflows are due before inflows arrive, borrow briefly to cover the timing gap. Bank overdrafts and correspondent bank credit lines are the current version.

4. Novation: a third party assumes the obligation. In trade finance, a bank purchasing an exporter's receivables (factoring) is the classic example.

Let's walk through how this engine actually works using the Korean SaaS example. Suppose the same system also includes BerlinApp (receiving €400K from Germany, paying $200K to the US) and TexasSaaS (receiving $600K from the US, paying €250K to Germany).

• Netting: first, offset each company's same-currency inflows and outflows. KoreaTech's $500K inflow minus $120K outflow leaves a net $380K; €300K inflow minus €80K outflow leaves a net €220K. Then match across participants. BerlinApp needs dollars and KoreaTech has dollars to spare, so they offset. TexasSaaS needs euros and BerlinApp has euros to spare, so they offset again. Finally, triangulate the remaining dollar-euro cross-flows. Cost to this point is near zero.

• Bridge financing: even after netting, timing can mismatch. If KoreaTech's dollar inflow arrives tomorrow but the AWS payment is due today, a bank lends against the receivable for one day and gets repaid when the inflow lands. Since it's a fixed obligation, the risk is low for the bank and the rate is cheap.

• Gross settlement: only the net balance that netting and bridging can't resolve actually hits a rail. The engine picks the cheapest path among options like SWIFT ($25–50/tx) and stablecoin transfer ($0.01/tx).

The result: four FX conversions drop to one or two, and the actual amount moving through rails shrinks from over $1M to roughly $520K. That's with just three participants. As more join, more offset paths emerge and efficiency improves further.

The core argument in Bradley Freeman's Nobody Cares About Yield is that once stablecoins and DeFi enable every app to become a bank, the axis of competition shifts from yield to loyalty rewards. And that USDC-backed loyalty points can let any brand build the kind of reward network that was previously only possible for major credit card companies and airlines.

Once every consumer app can offer competitive yield, yield becomes table stakes, not a differentiator. The question shifts from "what rate do you offer" to "why should I put my money here."

Starbucks is the decisive case. Its rewards program holds $1.8B in customer deposits and earns roughly $100M in annual interest, but the yield passed back to its 32 million members is exactly 0%. Customers don't deposit for yield. They deposit for free drinks, status badges, and emotional loyalty.

But most loyalty programs fail. The reason is structural: they fund all rewards from their own margins, a zero-sum setup. Too generous and you lose money. Too stingy and customers don't engage. The average American consumer is enrolled in 17 programs and actively uses fewer than half. $10B in rewards go unredeemed annually. Starbucks works because coffee is a daily habit driving five store visits per week. Few businesses have that frequency advantage.

Amex took a different approach.

Amex's structure is fundamentally a three-way value exchange. Members earn points through card usage. Partner merchants (airlines, hotels, retailers) offer discounts in exchange for direct access to Amex's premium customer base. Amex sits in the middle, delivering rewards that cost roughly $200 to produce as $500 in perceived value to members. The result: a $17B reward network running on $10B in annual fees. The key is that rewards come from partner wholesale discounts, not from Amex's own margins.

The problem is that most companies can't become Amex, for two main reasons:

1. Technical complexity: every partner integration is a bespoke engineering project. Each partner has different databases, catalogs, inventory systems, and settlement rails. Points are effectively money, so bugs translate directly into financial losses or exploitation.

2. Capital intensity: every issued point sits on the balance sheet as a future obligation. Predicting when and how much members will redeem requires modeling, plus capital reserves against redemption risk. Without an enterprise-scale balance sheet and decades of accumulated partnerships, the model doesn't work. That's why only major credit card companies and airlines have achieved this scale.

This is where stablecoins come in. Freeman's proposal is to back all points internally with USDC instead of inventing custom point currencies. To users, it still looks like branded points. What changes is the infrastructure.

The advantages of switching points to a USDC base:

1. Points are backed 1:1 by dollars, keeping their value stable.

2. USDC is already widely circulated, so partner integration shifts from bespoke engineering to shared standard connections.

3. When every point is backed by real dollars at issuance, there's no floating liability to hedge. Reserves earn USDC yield (~3.5%), turning points from a balance sheet liability into a self-funding asset.

The framing matters. Stablecoin loyalty isn't "using crypto to make points better." It's "structurally lowering the barriers to building an Amex-scale reward network." The technical barrier (standardized settlement rails) and the capital barrier (self-funding reserves) are addressed simultaneously, which makes this different from simple point tokenization.