Download websites that use WooCommerce PayPal Checkout Payment Gateway

About WooCommerce PayPal Checkout Payment Gateway

A payment plugin is the closest thing on the public web to a statement of intent. A site can install a cart, a theme and a contact form and still sell nothing, but a configured payment gateway means somebody expects money to arrive. WooCommerce PayPal Checkout Payment Gateway is a WordPress plugins extension for WooCommerce, written in PHP and published by Automattic under GPL v3.

Geography is worth reading closely on a plugin of this type. A concentration like that is less about the software than about the brand it connects to, since small merchants tend to adopt whichever gateway their own customers already recognise. Anyone using this data commercially should read the country column closely, because it changes what the rest of the row means: the same plugin implies a different merchant profile in a market where PayPal competes with entrenched local schemes than in one where it is the assumed option at checkout.

Version spread tells the other half of the story. We record 24 distinct versions, and the build we encounter most often is 2.1.3. WooCommerce's own PayPal integration has since moved to a newer official extension, so a shop still running this gateway is running something that is no longer the recommended path, whether because checkout is stable and nobody wants to touch it, or because nobody is watching the shop at all. Either way the store is identifiable, and the difference between a maintained store on a recent build and a dormant one on an old build is visible in the data rather than guessed at.

As of October 2026 the gateway is present on 5,241 sites. Looking up a single domain confirms one merchant. The export answers the questions that only exist across a whole population: how many WooCommerce stores accept PayPal through this particular route, how the count splits across countries and domain suffixes, what else sits in each checkout, and how quickly the installed base is drifting away from a superseded plugin. Competing payment providers build switching campaigns from exactly that shape of list. Agencies use it to find checkout migration work with a clear technical trigger. Risk and fraud teams use it to understand which processing paths a merchant population actually relies on.

The limits deserve stating plainly. A payment plugin is detected from traces it leaves in a public page, so a store whose checkout sits behind a login, or which loads gateway assets only at the final step, can be missed entirely. Presence also does not prove the gateway is switched on, because a deactivated or half-configured plugin still leaves files where a scanner will find them. Version strings come only from installs that expose them, which means the version distribution covers a subset of the sites in the total. None of that undermines the list for market sizing or outreach, but the count is better read as a floor than as a complete tally.