# EPC SEPA VOP BIC Portfolio Status Monitor (`plym-actor-factory/eu-epc-sepa-vop-bic-portfolio-status-monitor`) Actor

Watch EPC SEPA Verification of Payee (VOP) participant BICs; emit APPEARED/DROPPED/STATUS\_CHANGED/ROLE\_CHANGED/LEAVING\_CHANGED and attribute events from the official EPC VOP Register of Participants CSV. Not an EBA PSD2 twin; not an IBAN validator; not a full VOP dump billed as rows.

- **URL**: https://apify.com/plym-actor-factory/eu-epc-sepa-vop-bic-portfolio-status-monitor.md
- **Developed by:** [Daniel Witney](https://apify.com/plym-actor-factory) (community)
- **Categories:** AI, Automation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 epc sepa vop status event delivereds

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

## EPC SEPA VOP BIC Portfolio Status Monitor

Watch a private list of **EPC SEPA Verification of Payee (VOP)** participant **BICs** and emit typed portfolio events when the official **EPC Register of Participants** CSV changes.

**Source:** public EPC VOP participants CSV (no API key).\
**PPE:** `epc-sepa-vop-status-event-delivered` @ **$0.02** + `apify-actor-start` @ **$0.00005**.\
**Not:** an EBA PSD2 PI/EMI twin; not an IBAN validator/enricher; not SCT/SDD multi-scheme dump billing; not a full VOP register dump billed as rows.

### Events

| Event | Meaning |
|-------|---------|
| APPEARED | BIC newly present on the VOP register |
| DROPPED | BIC absent from the published CSV (snapshot absence) |
| STATUS\_CHANGED | Ready for operations ↔ Pending EDS registration (or ABSENT) |
| ROLE\_CHANGED | Requesting/Responding PSP role set changed |
| LEAVING\_CHANGED | Scheme Leaving Date set/cleared/changed |
| NAME/COUNTRY/ADDRESS/CITY/READINESS/OPTIONS\_CHANGED | Attribute diffs (opt-in `attributes` signal group) |

Plus non-billable `RUN_STATUS` health rows every run.

### Cadence honesty

EPC republishes the Register of Participants CSV periodically (Last-Modified observed ~daily during VOP rollout). This Actor does **not** invent intraday ticks beyond what the CSV carries.

### Input

- `bics` / `vopBics` — watchlist
- `sourceMode` — `fixture` (default Store health) or `live`
- `signalGroups` — `directory`, `status`, `attributes`
- `emitFixtureDemoEvents` — fixture demo diffs for local QA

### Legal / compliance

Uses the public EPC SEPA scheme participant register export. Operators remain responsible for lawful use, retention, and downstream compliance decisions. Cite EPC as the source of record.

# Actor input Schema

## `bics` (type: `array`):

ISO 9362 BICs (8 or 11 chars) to monitor against the official EPC SEPA Verification of Payee Register of Participants CSV. Invalid entries skipped with no charge. Not a full VOP dump bill. Not an EBA PSD2 PI twin; not an IBAN validator.

## `vopBics` (type: `array`):

Optional alias for bics — same durable BIC keys, merged into the watchlist.

## `signalGroups` (type: `array`):

Which change groups to evaluate: directory (APPEARED/DROPPED), status (STATUS/ROLE/LEAVING), attributes (NAME/COUNTRY/ADDRESS/CITY/READINESS/OPTIONS). Default: directory+status.

## `maxRunSeconds` (type: `integer`):

Wall-clock budget (CSV download + parse + watchlist diff).

## `maxEvents` (type: `integer`):

Stop after this many unique change events are delivered (does not include RUN\_STATUS).

## `resumeFromCheckpoint` (type: `boolean`):

If true, resume BIC snapshots and seen event\_uids from the default Key-Value Store.

## `sourceMode` (type: `string`):

fixture = Store/CI health default (no network; RUN\_STATUS only unless emitFixtureDemoEvents=true). live = official EPC VOP Register of Participants CSV (no API key; honest EPC republish lag).

## `emitFixtureDemoEvents` (type: `boolean`):

When sourceMode=fixture, if true emit deterministic demo APPEARED/DROPPED/STATUS/ROLE/LEAVING events from fixtures/demo-bundle.json (for local QA). Default false = Store health path (RUN\_STATUS only).

## `maxTotalChargeUsd` (type: `number`):

Soft budget hint for operators; platform PPE limits still apply.

## `asOfHint` (type: `string`):

Optional YYYY-MM-DD override when Last-Modified is unavailable.

## `epcVopCsvUrl` (type: `string`):

Optional override of the official EPC VOP participants CSV URL (default: EPC public Register of Participants export).

## Actor input object example

```json
{
  "bics": [
    "ICBKATWWXXX",
    "RVSAAT2S029",
    "ASPKAT2LXXX",
    "NABAATWWXXX",
    "SPPOAT21XXX",
    "BAWAATWWXXX"
  ],
  "signalGroups": [
    "directory",
    "status"
  ],
  "maxRunSeconds": 180,
  "maxEvents": 500,
  "resumeFromCheckpoint": true,
  "sourceMode": "fixture",
  "emitFixtureDemoEvents": false,
  "maxTotalChargeUsd": 1
}
```

# Actor output Schema

## `OUTPUT` (type: `string`):

JSON summary: delivered, charged, runStatus, checkpoint, stats, EPC SEPA VOP VOP coverage limits

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("plym-actor-factory/eu-epc-sepa-vop-bic-portfolio-status-monitor").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("plym-actor-factory/eu-epc-sepa-vop-bic-portfolio-status-monitor").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 '{}' |
apify call plym-actor-factory/eu-epc-sepa-vop-bic-portfolio-status-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,plym-actor-factory/eu-epc-sepa-vop-bic-portfolio-status-monitor"
        }
    }
}
```

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/UpU045JFXJfla6ial/builds/vrvvZ7e6uleqBQqUG/openapi.json