Grep · sample report

Payment Provider Detector — Detects the payment processors, checkout tools and payment methods each website uses, with the evidence for each.

workbatchoperational
Inputs used for this sample
Payment Provider Detector

Websites (one per line): store-a.com
store-b.com

Payment Provider Detection: store-a.com Is Not a Store, store-b.com Unreachable

Interpretation: store-a.com redirected to the www.store-a.com host and serves a Japanese-language information blog about tableware, not a merchant checkout. store-b.com could not be reached from this environment. No payment provider was detected for either site. All checks were run on 2026-10-05.

Website Platform Primary processor Other providers Payment methods shown Evidence Confidence
store-a.com (final host: www.store-a.com) unknown (page text only; no page source was parsed, and no platform signature was seen in the fetched content) not detected none found none shown Homepage fetch, 2026-10-05 shows an article-style site with an affiliate text link to an outside shop, and no cart or checkout Low
store-b.com unchecked unchecked unchecked unchecked Fetches of https://store-b.com, http://store-b.com and https://www.store-b.com each returned "502 Could not connect to the requested URL" on 2026-10-05 Low

Notes

Do next

  1. Confirm the intended domains with the requester (for example the actual shop behind store-a.com's affiliate link, or the correct spelling of store-b.com).
  2. Retry store-b.com later, or from another region, and check whether the domain resolves.
  3. Rerun the page-source extraction for both sites once the HTML fetch tool is working.
  4. If a real merchant is identified, check its cart, checkout entry, privacy policy and help pages for processor names.

Coverage

store-b.com was unreachable on all three tried variants. Page source for both sites, privacy and terms pages, and external case-study searches were not checked.

Sources