# Detect which payment gateway an online store uses

**Use case:** 

Bulk-check store URLs to see which payment gateway, PSP, wallet and BNPL provider each site uses (Stripe, Adyen, PayPal, Klarna and 30+ more). Demo uses public test stores.

## Input

```json
{
  "startUrls": [
    "https://www.saucedemo.com",
    "https://sauce-demo.myshopify.com"
  ],
  "crawlExtraPages": false,
  "maxConcurrency": 5
}
```

## Output

```json
{
  "url": {
    "label": "Store URL",
    "format": "string"
  },
  "platform": {
    "label": "E-commerce platform",
    "format": "string"
  },
  "providers": {
    "label": "Detected providers",
    "format": "array"
  },
  "error": {
    "label": "Error if site could not be fetched",
    "format": "string"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Payments Stack Detector - Tech Stack for PSPs Actor is ready to run with the inputs already set for "Detect which payment gateway an online store uses". [Sign up or log in](https://console.apify.com/create-task-from-example/OFanLxkWtff5uhwg7) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Detect which payment gateway an online store uses" task

The Payments Stack Detector - Tech Stack for PSPs Actor will start running based on the input automatically. You can also change all the input fields, like store urls, also check /cart and /checkout, and more, to match your specific use case.

### 3. Receive the "Detect which payment gateway an online store uses" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as store url, e-commerce platform, detected providers, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Detect which payment gateway an online store uses" task via API](https://apify.com/sterlingverify/payments-stack-detector.md).

## About this Actor

This example demonstrates how to use [Payments Stack Detector - Tech Stack for PSPs](https://apify.com/sterlingverify/payments-stack-detector.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/sterlingverify/payments-stack-detector.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

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 full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/sterlingverify/payments-stack-detector.md

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`).