Stripe made a crypto currency? (Founders, pay attention)

Stripe is rolling out a cluster of payment infrastructure upgrades that aim to remove the hardest parts of running global commerce—tax compliance, fraud, disputes, and even customer support—while also giving developers new ways to control billing logic inside Stripe itself. The most startup-relevant change is “managed payments,” Stripe’s merchant-of-record offering in private preview, which shifts legal and operational responsibility for transactions from the business to Stripe. That means fewer headaches around where customers live, how taxes apply, how chargebacks are handled, and how disputes get resolved.

The core idea behind managed payments is easiest to understand by analogy to “employer of record” services. Instead of a company acting as the merchant (and therefore owning the compliance burden), Stripe acts as the merchant through an entity already set up across countries and states. Customers still buy subscriptions through Stripe Checkout, but the card statement and transaction details reflect Stripe rather than the business. The business keeps the product relationship, yet Stripe absorbs the compliance and liability work—global tax management, fraud prevention, dispute handling, fulfillment support, and a direct support path for transaction issues like stolen-card fraud. Stripe also plans a migration path for customers using Lemon Squeezy, which Stripe acquired; the managed payments effort is positioned as a way to stabilize and replace a product that some users feel has been deteriorating over time.

Alongside managed payments, Stripe is introducing “Stripe Scripts,” a new programming language for embedding business logic directly into Stripe. Built as a TypeScript subset (with a custom runtime implied by restrictions on allowed operations), Scripts let teams define logic tied to Stripe objects—such as coupon rules—without pushing all the logic into their own servers. A concrete example: a coupon can be configured to apply a 50% discount only up to a maximum dollar amount, enforced by logic that runs within Stripe. That reduces the risk of coupon misuse (like applying a code to the wrong invoice) because the constraints live with the payment system rather than in application-side code.

Stripe’s crypto angle ties into the same “money movement” problem: multicurrency management. Through Bridge, Stripe is introducing a stablecoin called USDB (a USD bridge stable coin) backed one-to-one by cash and short-duration money market funds held with BlackRock. The pitch is practical rather than speculative: stablecoins can reduce friction and fees when moving value across borders, and stablecoin balances can act as an internal settlement layer for Stripe’s multicurrency features.

Stripe is also adding a credit card product that can spend from USDB balances, reducing the need to constantly transfer funds from Stripe to a bank and back again. The transcript frames this as a major operational win for businesses that keep money in Stripe—especially international founders who struggle with withdrawals and bank account setup in certain countries. The stablecoin and card features are presented as complementary to managed payments: both are meant to make global billing and payouts less chaotic.

Finally, Stripe is expanding payment method support by adding CLA to Stripe Link, a European payment processing group frequently requested for regional customer preferences. Taken together, these changes signal a shift toward handling more of the “messy middle” of global payments inside Stripe—so startups can ship and iterate without rebuilding compliance, fraud, and dispute workflows from scratch.