{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/banking-data.watch-alert/",
    "json": "https://www.anchorterminal.com/niches/banking-data.watch-alert/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/banking-data.watch-alert/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/banking-data.watch-alert/index.min.md"
  },
  "markdown": "Four or more companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 5 | 4 | 16 | 7 | 3 |\n\n## What counts as done\n\nA webhook or scheduled check reports a new matching transaction to the channel, and states when the account was last refreshed.\n\nMeasured, for our own tests: the alert arrives within the provider's stated refresh interval.\n\nHow agents ask for it: tell me when a big charge lands; alert me if my balance drops below 500; watch for my salary; notify me about new transactions\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **BankMCP (noskillish (open-source project))**: create_watch rules (balance threshold, large debit, payee match, missing payment) post to a webhook; watches store last_checked and a consent_expiring event fires 7 days ahead. Checks run at most four times a day.\n- **MX Platform API (MX Technologies, Inc.)**: The webhook index lists Transactions webhooks for created, updated or deleted transactions and Aggregation webhooks with counts of new data; members carry aggregated_at. Default aggregation is about every three hours.\n- **Plaid (Plaid Inc.)**: SYNC_UPDATES_AVAILABLE fires when new transactions arrive, checks run one to four times a day by institution, and /item/get reports last_successful_update for freshness.\n- **Powens (Powens SAS)**: CONNECTION_SYNCED and USER_SYNCED webhooks deliver new data after each synchronisation for permanent users, and accounts carry last_update for freshness.\n- **Tink (Tink AB)**: account-booked-transactions:modified and account-transactions:modified webhooks fire on new, updated or deleted transactions with the earliest and latest modified dates, and refresh:finished marks each refresh.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Belvo (Belvo Tecnologias Ltda.)**: new_transactions_available fires after each recurrent refresh, but the default refresh is every seven days, so alerts lag by up to a week unless a faster rate is bought.\n- **Flinks (Flinks Technology Inc.)**: Webhooks deliver data after a refresh, but nightly refresh is at most daily and fails for banks needing MFA, so watches go quiet for part of the base.\n- **Salt Edge Account Information (Salt Edge Limited)**: Success callbacks fire whenever a connection's data changes and background_refresh exists, but the callback names the connection, not the transaction, so the agent re-reads to find what is new.\n- **Yodlee Core API (Yodlee, Inc.)**: Notification events can be subscribed for data updates and refreshes, and accounts carry lastUpdated, but the event payload signals that data changed, not which transaction, so the agent must re-read.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Basiq (Basiq Pty Ltd)**: Webhooks cover users and consents 'to name a few'; the event-type list is served by an authenticated API call, so whether a new-transaction event exists was not established.\n- **Teller (Teller, Inc.)**: Not read: teller.io's robots.txt disallows ClaudeBot, Claude-Web and anthropic-ai, so the docs were not fetched.\n\n- not this job: Akoya (Akoya LLC): Webhooks carry only maintenance and consent events; there is no transaction event, so the agent polls.\n- not this job: Enable Banking (Enable Banking Oy): Webhooks cover payment status only; account data must be polled by the agent, at most four times a day in the background.\n- not this job: GoCardless Bank Account Data (GoCardless Ltd): The Bank Account Data endpoints and guides show no data webhooks; the agent must poll under bank caps as low as four calls a day per endpoint.\n- not this job: TrueLayer (TrueLayer Limited): Data API webhooks only signal that an async request finished; there is no new-transaction event, so the agent polls under bank caps.\n- not this job: Yapily (Yapily Ltd): Webhook categories cover payment status, async processing and categorisation completion; none fires on a new account transaction, so the agent polls under the four-a-day cap.\n\n## What stops agents finishing\n\n- four unattended reads a day, so alerts lag\n- consent lapses with no event, so the watch goes quiet\n\n## Around it\n\nBefore: banking-data.connect-consent. After: notifications.push, messaging.send.\n\n## Where this comes from\n\nWeight 7 of 100 in Bank data \u0026 open banking: 3 of 41 accounts (Leggen alerts, Driggsby big-charge detection, Tiller anomaly finding); BankMCP and Plaid document watches and webhooks\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/banking-data.watch-alert.json, or the MCP tool get_use_case with id banking-data.watch-alert. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Watch accounts and alert on new or unusual transactions",
        "url": ""
      }
    ],
    "description": "Watch accounts and alert on new or unusual transactions: 5 companies fully do it, 4 with a limit, 16 carry the tag. Every listing in Bank data \u0026 open banking with the reason and a source.",
    "facts": null,
    "h1": "Watch accounts and alert on new or unusual transactions",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/banking-data.watch-alert/",
    "published": "",
    "section": "agents",
    "title": "Watch accounts and alert on new or unusual transactions | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/banking-data.watch-alert/"
  },
  "tokens": {
    "markdown": 1400,
    "slim": 280
  },
  "version": 1
}
