# Payments Stack Detector - Tech Stack for PSPs (`sterlingverify/payments-stack-detector`) Actor

Payment tech stack detector: find which payment gateway or PSP a website uses (Stripe, Adyen, PayPal, Klarna, Shopify Payments, Checkout.com and 30+ more). Bulk-check store URLs to build PSP sales lead lists and research competitors' merchants.

- **URL**: https://apify.com/sterlingverify/payments-stack-detector.md
- **Developed by:** [Luke Mangan](https://apify.com/sterlingverify) (community)
- **Categories:** Lead generation, E-commerce, Developer tools
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 site analyseds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Payments Stack Detector

**Payments Stack Detector** finds which payment provider a website uses, in bulk. Paste a list of online store URLs and get each store's PSPs, gateways, wallets and buy-now-pay-later options, plus its e-commerce platform. It's built for **PSP lead lists**: finding merchants that use a given provider (for example, every store in your list that runs Stripe or Klarna) and competitor research for payments sales teams.

**Best for:** PSP, acquirer and payment gateway sales teams, ISOs and agents prospecting merchants, and anyone sizing up a competitor's merchant base or migration targets.

### Build a PSP lead list: find merchants using a given provider

1. Collect a list of store URLs (from your CRM, a directory, a trade show list or a market you want to enter).
2. Run them through Payments Stack Detector.
3. Filter the results by `providers.provider` (for example `Adyen`, `Stripe`, `Klarna` or `Worldpay`) to get the merchants on that provider, or by `platform` (for example `Shopify` or `WooCommerce`).
4. Export to CSV or Excel for your CRM, or schedule the run to re-check the list regularly and spot changes.

### Competitor research for payments sales teams

- **Competitive displacement:** list the merchants in your target segment that use a competitor's gateway.
- **Wallet and BNPL coverage:** see which stores already offer Apple Pay, Google Pay, Klarna or Clearpay and which don't (an upsell opening).
- **Platform targeting:** find Shopify, WooCommerce or Magento stores for platform-specific payment offers.
- **Account research:** check a prospect's current setup before a sales call.

### What does Payments Stack Detector do?

For each URL it returns the **payment service providers, gateways, wallets and BNPL** it can see in public HTML, script tags and response headers (homepage plus `/cart` and `/checkout`). It detects about 30 providers, including Stripe, Adyen, Checkout.com, PayPal/Braintree, Klarna, Clearpay/Afterpay, Shopify Payments, Square, Worldpay, Opayo, GoCardless, Mollie, Amazon Pay, Apple Pay, Google Pay, Trustly, Revolut, SumUp, Laybuy, Zip, Affirm and Paddle, plus platforms (Shopify, WooCommerce, Magento, BigCommerce, Wix, Squarespace). Each detection includes the evidence found and a confidence level.

### How to find which payment provider a website uses

1. Add store URLs to **Store URLs** (`startUrls`).
2. Leave **Also check /cart and /checkout** on for better coverage.
3. Click **Start**, then download the results as JSON, CSV or Excel.

### Input

`startUrls` (list), `crawlExtraPages` (bool), `maxConcurrency`.

### Output (per site)

`url, platform, providers[{provider, category, evidence[], confidence}], pagesChecked, error`

### Limits

Only static HTML is fetched (no JS execution, no checkout submission). Providers loaded only after login/checkout steps may be missed. Respect site terms; low request rate.

### Pricing (pay-per-event)

- `site-analysed`: **$0.004** per site ($4 / 1,000).
- Example: 10,000 sites cost $40.00.

### Example input

```json
{
  "startUrls": [
    "https://www.allbirds.com"
  ],
  "crawlExtraPages": true
}
```

### Example output

Values below are illustrative.

```json
{
  "url": "https://www.allbirds.com",
  "platform": "Shopify",
  "providers": [
    {
      "provider": "Shopify Payments",
      "category": "psp",
      "evidence": [
        "shopify-payment-button"
      ],
      "confidence": "high"
    },
    {
      "provider": "PayPal",
      "category": "wallet",
      "evidence": [
        "paypal-button"
      ],
      "confidence": "medium"
    }
  ],
  "pagesChecked": [
    "https://www.allbirds.com/"
  ],
  "error": null
}
```

### Use it via API, schedules and integrations

Run it in Apify Console, or call it from your own code with the Apify API or the Python and JavaScript clients. Save an input as a task and add a schedule to run it regularly, and send results to Slack, email, webhooks, Zapier, Make or n8n with Apify integrations. AI agents can find and run it through the Apify MCP server.

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("sterlingverify/payments-stack-detector").call(run_input={"startUrls": ["https://www.allbirds.com"]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)
```

### FAQ

#### Which payment providers can it detect?

About 30, including Stripe, Adyen, Checkout.com, PayPal/Braintree, Klarna, Clearpay/Afterpay, Shopify Payments, Square, Worldpay, Opayo, GoCardless, Mollie, Amazon Pay, Apple Pay and Google Pay, plus platforms such as Shopify, WooCommerce and Magento.

#### Can I find all merchants using Stripe (or Adyen, Klarna...)?

It checks the URLs you give it; it doesn't discover stores on its own. Supply a list of stores in your target market, then filter the output by provider to build your lead list.

#### Does it run JavaScript or place test orders?

No. It reads only publicly served HTML, script tags and headers, so providers that appear only after login or later checkout steps can be missed.

### Disclaimer

Detection is heuristic, based only on publicly served page code. Use responsibly and in line with target sites' terms.

Platform usage is included in the per-event price; you pay only for results.

### Related sterlingVerify tools

Part of the sterlingVerify UK payments, KYB and data toolkit on Apify Store:

- [Merchant Website Compliance Checker for Onboarding](https://apify.com/sterlingverify/merchant-compliance-checker): onboarding review of a merchant's website
- [PCI Readiness Scanner](https://apify.com/sterlingverify/pci-readiness-scanner): passive checkout security check with a likely SAQ type
- [MCC Checker](https://apify.com/sterlingverify/mcc-checker): check a merchant's MCC against its website or description
- [PSP Status Monitor](https://apify.com/sterlingverify/psp-status-monitor): outage alerts from payment provider status pages
- [UK Company Check](https://apify.com/sterlingverify/uk-company-check): Companies House, VAT and UK sanctions KYB check in one call

# Actor input Schema

## `startUrls` (type: `array`):

Homepages or checkout/cart pages

## `crawlExtraPages` (type: `boolean`):

Fetch common cart/checkout paths too

## `maxConcurrency` (type: `integer`):

Parallel sites

## `userAgent` (type: `string`):

Default identifies as a research bot. Some sites block bots (reported as error).

## Actor input object example

```json
{
  "startUrls": [
    "https://www.allbirds.com"
  ],
  "crawlExtraPages": true,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

All results in the default dataset

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        "https://www.allbirds.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("sterlingverify/payments-stack-detector").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "startUrls": ["https://www.allbirds.com"] }

# Run the Actor and wait for it to finish
run = client.actor("sterlingverify/payments-stack-detector").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    "https://www.allbirds.com"
  ]
}' |
apify call sterlingverify/payments-stack-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,sterlingverify/payments-stack-detector"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Y0wfeKEa6YMYbWgbH/builds/wfErB4iSUYTjyQXFd/openapi.json