Download websites that use Amazon Pay

About Amazon Pay

A payment button is one of the few things on a web page that reveals a commercial decision rather than a technical one. Amazon Pay is a Payment processors integration from Amazon, offered to merchants since 2007, that lets a shopper check out with the card and shipping address already held in an Amazon account. Adding it means a store has judged that some share of its buyers will abandon a form before they will abandon a purchase, and has accepted a large third party sitting in the middle of its own checkout.

As of October 2026 the button is detectable on 68,959 sites in our crawl. The population is not a sample of online stores in general. Wallet buttons cluster in particular merchant tiers, because they usually arrive with a cart platform, a plugin or an agency template rather than through an independent evaluation by each merchant.

Country attribution makes the clustering visible. Canada carries 58,239 of the detections, a share heavy enough that it should be read as the footprint of a few build stacks rather than as a national payment preference. Our country field describes where a site resolves and is registered, not where its shoppers hold their accounts, so a store selling into one market from infrastructure in another lands under the infrastructure. Anyone sizing a market by nation needs to treat the field as a first filter and confirm it against the currency, language and address data on the store itself.

The domain side of the same picture points elsewhere. The suffix that recurs across these sites is .com, which is what generic commercial hosting produces and which says little about a merchant's home market. Two signals that disagree are more useful than one that agrees with itself, because the gap between registration country and domain suffix is often exactly where cross border sellers sit.

Detection has a boundary worth naming. The button and its script appear on pages where the merchant chooses to show them, usually a cart or a product page, and sometimes only once a shopper has begun to check out. Pages behind a login, a region gate or a later cart step are outside what a crawler sees, so the count understates real deployment. Our record also cannot separate a live, configured account from a leftover snippet on a store that has since moved to another processor.

For a researcher the question is rarely whether one domain uses it. A per domain lookup answers that in a second and answers nothing else. The list answers the questions a lookup cannot: how large the addressable base of merchants is for a competing wallet or processor, which stores run several alternative payment methods side by side, how the base moves between quarters, and which cohorts of stores share a builder and can therefore be reached through the builder instead of one at a time. The Proprietary model matters here too, because nothing about the service is self hosted. Every detection corresponds to a merchant account with Amazon, which makes the file a list of commercial relationships rather than a list of installed software.