Checkout as Identity Middleware

The real opening is not another payment button, it is a neutral layer that turns a messy pile of buttons into one merchant controlled checkout. Once checkout offers many wallets, BNPL plans, and express pay options, the scarce thing is no longer payment acceptance, it is shopper recognition, saved credentials, and one integration that lets merchants switch providers on and off without rebuilding the flow.

• The closest analogy is identity software. Gigya won an early point problem, social login, but broader platforms like Auth0 lasted longer because developers wanted one system that handled many login methods plus future needs. Checkout is following the same path from single button tools to full middleware platforms.
  2 sacra
• Fast struggled because it added one more express payment button and therefore touched only a small slice of each merchant's checkout volume. Bolt and Rally instead try to own the whole checkout flow, so every guest purchase can become a saved identity that works across merchants later.
  1 sacra 3 sacra 4 sacra
• Owning checkout creates a data and workflow advantage beyond payments. Bolt uses the flow for passwordless login and shopper recognition across sites, while Rally uses it to run post purchase offers and campaign specific checkout pages. That makes checkout middleware look more like an operating layer than a single feature.
  1 sacra 3 sacra 4 sacra

The category is heading toward fewer visible buttons and more hidden orchestration. The winners will look less like branded wallets and more like infrastructure that lets merchants recognize shoppers early, route them into the best payment method, and keep control of the brand experience across web, mobile, and in store surfaces.