Rally building neutral checkout layer
Jordan Gal, CEO of Rally, on building the Switzerland of checkout
Rally is trying to win checkout the same way Stripe won payments APIs, by becoming the neutral layer every merchant and every app can plug into. In composable commerce, merchants may use Next.js on the front end, Salesforce Commerce Cloud or another system on the back end, and separate tools for payments, fulfillment, SMS, and fraud. Checkout becomes the hardest piece to rebuild, so the vendor that already works with everything can become the default choice.
-
Rally’s bet is that a full hosted checkout beats a thin button. Instead of adding one more payment button, it provides the actual checkout page, confirmation page, shopper vault, and post purchase offers, which removes PCI and payment plumbing work from merchants modernizing off legacy stacks.
-
The core moat is shopper recognition plus integration breadth. Like Bolt, Rally wants each guest checkout to turn into a saved identity that works across merchants later. The more merchants it serves, the more often shoppers are recognized, and the harder it is for a merchant to justify building checkout in house.
-
This position only works if Rally stays cooperative. Bolt has explored a broader merchant software and shopper network story, while Rally is explicitly framing checkout as shared infrastructure, keeping payment methods and surrounding tools open so partners do not see it as a future competitor.
If composable commerce keeps spreading, checkout should consolidate into a small number of neutral layers with the broadest integrations and the largest shopper vaults. The company that becomes the easiest way to launch a reliable checkout, without forcing merchants into a full platform, can turn checkout from a feature into core infrastructure.