Skip to content
← All posts
Straight Answers

Do You Need an Online Store to Take Payments?

Do You Need an Online Store to Take Payments?

No. Only 19.2% of analyzed mobile sites run a store platform (Web Almanac, 2025), and the same source says detecting a payment processor is not enough to call a site a store, because many non-store sites also take payments.

Do you need an online store to take payments?

No. A store platform runs a catalog, a cart and a checkout. A payment page does one thing: it moves money for work that was already agreed on.

19.2%
of mobile sites run a store platform
Web Almanac, 2025
19.9%
of desktop sites run one
Web Almanac, 2025
16.2M
sites measured in the crawl
Web Almanac, 2025

What you run

a catalog, a cart, a checkoutone page with an amount

A store sells products. A payment page settles a job.

What the buyer does

browses and adds to a cartopens the link you sent

The price and the scope were agreed before the link existed.

How the crawl counts it

an ecommerce sitenot counted at all

Detecting a payment processor alone is not sufficient to classify a site as ecommerce, because many non-store sites also take payments (Web Almanac, 2025).

View data
MetricDay zero → target
What you runa catalog, a cart, a checkout → one page with an amount
What the buyer doesbrowses and adds to a cart → opens the link you sent
How the crawl counts itan ecommerce site → not counted at all

How much of the web is actually a store?

About one in five, and it stopped growing: 17% in 2022, 19% on mobile in 2024, and 19% again in 2025.

Share of analyzed mobile sites detected as ecommerce

Web Almanac, 2025 · mobile sites, July 2025 crawl

View data
Web Almanac, 2025 · mobile sites, July 2025 crawl
ItemValue
202217%
202419%
202519%
What 100 analyzed mobile sites look like

Web Almanac, 2025 · our subtraction from the published 19.2%

View data
Web Almanac, 2025 · our subtraction from the published 19.2%
StageValue
sites measured on mobile100
run a store platform19
run none, and some of them still take payments81

The rate also depends on how big the site is.

1%
of the top 1,000 sites are stores
Web Almanac, 2025
21%
mobile adoption in the top 10M
Web Almanac, 2025
22%
desktop adoption at that rank
Web Almanac, 2025

Which platforms are those stores built on?

Four names cover most of the stores detected on mobile. Three are hosted builders; WooCommerce is self-hosted, so somebody has to maintain it.

Share of detected ecommerce sites, by platform

Web Almanac, 2025 · share of detected stores, mobile

View data
Web Almanac, 2025 · share of detected stores, mobile
ItemValue
WooCommerce44.4%
Shopify25.3%
Wix eCommerce11.1%
Squarespace Commerce9.9%

Read those against stores. Against every site measured, the same platforms look like this.

7.0%
of all sites run WooCommerce
Web Almanac, 2025
4.0%
of all sites run Shopify
Web Almanac, 2025
1.8%
of all sites run Wix eCommerce
Web Almanac, 2025

Which payment buttons do people already see?

No single one dominates. PayPal is still the most detected provider, but its share of payment detections fell from around 39% in 2022 to around 30% in 2025.

30%
of payment detections are PayPal
Web Almanac, 2025
70 of 83
geographies where PayPal leads mobile
Web Almanac, 2025
31
desktop geographies where Stripe leads
Web Almanac, 2025
PayPal’s share of payment detections

Web Almanac, 2025 · figures published as approximate

View data
Web Almanac, 2025 · figures published as approximate
ItemValue
202239%
202530%

What does your site need before a payment button works?

HTTPS on the page where the money moves, and room for third-party scripts. The browser’s payment API is only available over HTTPS (W3C Payment Request API).

Before the button, four things
  1. 01
    Serve that page over HTTPS
    The API is only exposed in a secure context, which in practice means HTTPS. The padlock is the floor, not the verdict: see what the padlock actually proves.
  2. 02
    Pick the provider your customers recognize
    The data does not crown one. Pick the button they already know and the one your bookkeeper can reconcile without a side spreadsheet.
  3. 03
    Expect the dependency surface
    Payments are a major dependency surface area: third-party scripts, redirects, fraud tooling and compliance constraints (Web Almanac, 2025).
  4. 04
    Put the link where the invoice already goes
    The link belongs in the invoice and in the reminder, not behind a catalog. The wait it shortens is measured in how long a service business waits to get paid.
The job is already agreed

A payment page settles work you quoted. It needs no catalog, no cart and no inventory to exist.

No store platform to maintain

80.8% of analyzed mobile sites run none (our subtraction from the Web Almanac’s 19.2%).

One page instead of a storefront

The crawl would not even count it as a store, which is exactly the point.

Not a compliance claim

HTTPS is a technical requirement, not a seal. This is not legal or tax advice.

If you quote the work before you do it, you do not need a store. You need one page that takes money and an invoice that points at it.

  1. 01Quote the work
  2. 02Send one payment link
  3. 03Put it in the invoice
  4. 04Reconcile it monthly

Questions owners ask

Do you need an online store to take payments on your website?

No. A store platform runs a catalog, a cart and a checkout. A payment page moves money for work already agreed on. Detecting a payment processor is not enough to call a site a store, because many non-store sites also take payments (Web Almanac, 2025).

How many websites are online stores?

19.2% of analyzed mobile sites and 19.9% of desktop sites, out of 16,213,084 sites in the July 2025 crawl (Web Almanac, 2025). Flat since 2024, after 17% in 2022.

Which payment provider should a service business use?

The data does not pick one. PayPal is still the most detected, but its share of payment detections fell from around 39% in 2022 to around 30% in 2025, and on desktop Stripe leads in 31 geographies against PayPal’s 22 (Web Almanac, 2025).

Does a payment page need HTTPS?

Yes. The browser’s Payment Request API is only available over HTTPS (W3C Payment Request API), and the wallet buttons sit on top of it. HTTPS is the floor, not proof that a site is safe.

Sources

  1. Web Almanac 2025 (HTTP Archive), Ecommerce chapter: 16,213,084 sites measured, of which 15,426,398 mobile and 12,155,374 desktop, July 2025 crawl; platform detection by Wappalyzer on the home page plus one internal page; read October 29, 2026 (2025)
  2. Web Almanac 2025 (HTTP Archive), Methodology: dataset size and crawl date, with the declared bias toward sites visited by Chrome users (2025)
  3. W3C, Payment Request API (specification, no sample): the API is only exposed in a secure context (2026)

The first meeting starts with findings, not promises.The free Business Health Report reads your business and shows you what it found, in days.

Get Your Free Business Health Report
← All posts