Download websites that use Bolt Payments

About Bolt Payments

Checkout is the step where a retailer loses shoppers it has already paid to attract, and Bolt Payments was built to attack that step alone rather than to replace the store around it. The pitch is a shared shopper identity across participating merchants, so that a buyer who has completed a purchase inside the network is recognised at the next storefront and does not retype card and address details. Everything else about the store, the catalogue, the theme, the hosting, stays where it was.

A name like Bolt is worth pinning down before anyone buys a list, because several unrelated products ship under it. The fingerprint here belongs to the checkout and payments product from Bolt Financial Inc., published at bolt.com, and not to the ride hailing app or the content management project that share the word. Our record has the product as Proprietary software with a first release year of 2014 and a client side implementation in JavaScript, which is also why it is visible to us at all. A checkout has to load in the shopper's browser, so it leaves a trace in the page.

As of October 2026 we detect the product on 43 sites. The figure is modest, and the modesty is informative. Nothing here is switched on by a hosting company across every account, so each domain represents a merchant who decided that conversion at the final step justified an integration and a payments relationship. A domain on the list is a store with real order volume, or at least a store whose operator believes it has real order volume and is spending accordingly.

A per domain lookup tells you whether one shop you already care about runs the checkout. The downloadable set answers the reverse question, and the reverse question is the one that drives commercial work. Give me every store that has made this decision. That population is the addressable market for anyone selling adjacent tooling, fraud scoring, subscription billing, post purchase logistics or returns, and it is the sample frame for anyone researching how shared checkout networks actually spread between merchants rather than how the vendors say they spread.

The limits are worth stating. Detection is client side, so a store that loads the checkout only deep in a funnel, behind a cart with items already in it, may never expose the fingerprint on the pages a crawler can reach without a session. Our record carries no country breakdown, no top level domain concentration and no version data for Bolt Payments, so questions about where these merchants trade have to be answered from the domain list itself rather than read off a summary field. The count should be treated as a floor for public facing storefronts and not as a customer roster.