# BRAINIAC Payment Failure Pattern Analyzer

> BRAINIAC Payment Failure Pattern Analyzer is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.04/call, status unknown (last checked 2026-11-12).

Analyzes a set of transactions to detect payment failure patterns, declined charges, and recurring failure behavior by merchant

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/payment-intelligence/failure-pattern-analyze?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-payment-failure-pattern-analyzer-eee113e4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_h6dBl0f3I03ylyyIdk5-K

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability brainiac-payment-failure-pattern-analyzer-eee113e4 -d '<json body>'
```

Example prompt: Can you analyze these transactions for payment failure patterns? I have a list of 50 transactions including some declined and failed direct debits from UtilityCo — tell me which ones failed, why, and if there's a pattern by merchant.

## When to prefer this

Use this endpoint when you have a structured or semi-structured set of transaction records and need to identify which ones represent payment failures, declines, or recurring failure behavior — without connecting to a bank or Open Banking provider. It is especially useful for agents doing pre-screening, compliance review, or customer-support triage on supplied data. Prefer it over generic LLM analysis when you need structured output with per-merchant failure counts and explicit limitation attestations.

## Known failure modes

- Transactions missing status or description fields may not be classified correctly
- No bank connection means only supplied rows are analyzed — missing transactions are not fetched
- Ambiguous status text may not trigger failure detection
- Empty or malformed CSV/JSON input returns no items
- Over-limit inputs (>200KB text, >400 merchants) are rejected
- Insufficient context (no dates, no merchant names) produces low-confidence findings

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a list of transactions flagged as failures or declines with reason tokens, per-merchant failure counts, high-level findings, a status field, a checkedAt timestamp, and explicit limitation disclosures (no bank connection, no affordability decision, no invented values). Also includes boolean flags such as bankConnected, openBankingConnected, incomeInvented, and affordabilityDecision.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "csv": {
   "type": "string",
   "maxLength": 200000
  },
  "asOf": {
   "type": "string",
   "maxLength": 40
  },
  "file": {
   "type": "object",
   "required": [
    "mediaType",
    "fileBase64"
   ],
   "properties": {
    "filename": {
     "type": "string",
     "maxLength": 180,
     "minLength": 1
    },
    "mediaType": {
     "enum": [
      "text/plain",
      "text/csv",
      "application/json"
     ],
     "type": "string"
    },
    "fileBase64": {
     "type": "string",
     "maxLength": 12000000,
     "minLength": 1
    }
   },
   "additionalProperties": false
  },
  "json": {
   "type": "string",
   "maxLength": 200000
  },
  "text": {
   "type": "string",
   "maxLength": 200000
  },
  "accounts": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "name": {
      "type": "string",
      "maxLength": 200
     },
     "type": {
      "type": "string",
      "maxLength": 80
     },
     "currency": {
      "type": "string",
      "maxLength": 12
     }
    },
    "additionalProperties": false
   },
   "maxItems": 100
  },
  "merchants": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "name": {
      "type": "string",
      "maxLength": 200
     },
     "aliases": {
      "type": "array",
      "items": {
       "type": "string",
       "maxLength": 200
      },
      "maxItems": 20
     },
     "category": {
      "type": "string",
      "maxLength": 120
     }
    },
    "additionalProperties": false
   },
   "maxItems": 400
  },
  "corrections": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "to": {
      "type": "string",
      "maxLength": 120
     },
     "from": {
      "type": "string",
      "maxLength": 120
     },
     "merchant": {
      "type": "string",
      "maxLength": 200
     },
     "transactionId": {
      "type": "string",
      "maxLength": 80
     }
    },
    "additionalProperties": false
   },
   "maxItems": 400
  },
  "transactions": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "mcc": {
      "type": "string",
      "maxLength": 20
     },
     "date": {
      "type": "string",
      "maxLength": 40
     },
     "amount": {
      "type": "n
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "items": [
   {
    "id": "TX-1",
    "date": "2026-10-02",
    "amount": -50,
    "status": "failed",
    "currency": "GBP",
    "merchant": "UtilityCo",
    "accountId": "",
    "description": "Direct debit failed insufficient funds",
    "reasonToken": "failed",
    "bankConnected": false,
    "amountSupplied": true,
    "openBankingConnected": false
   },
   {
    "id": "TX-2",
    "date": "2026-10-09",
    "amount": -50,
    "status": "declined",
    "currency": "GBP",
    "merchant": "UtilityCo",
    "accountId": "",
    "description": "Direct debit declined",
    "reasonToken": "declined",
    "bankConnected": false,
    "amountSupplied": true,
    "openBankingConnected": false
   }
  ],
  "status": "analyzed",
  "findings": [
   {
    "code": "payment_failures",
    "kind": "observation",
    "detail": "Failure-like statuses or wording were found in supplied transactions only.",
    "subject": ""
   }
  ],
  "patterns": [
   {
    "merchant": "utilityco",
    "failureCount": 2
   }
  ],
  "checkedAt": "2026-11-04T21:00:00.000Z",
  "limitations": [
   "Transactions, accounts, merchants, and category corrections are copied only from labeled fields supplied by the caller.",
   "No bank account is connected and no Open Banking credentials are required or used.",
   "Income, affordability, and merchant identity are derived only from supplied rows. Missing values are not invented.",
   "Recurring and subscription detection use date spacing and description/merchant similarity from the supplied set only.",
   "An affordability or credit decision is never produced."
  ],
  "failureCount": 2,
  "bankConnected": false,
  "incomeInvented": false,
  "credentialsRequired": false,
  "openBankingConnected": false,
  "affordabilityDecision": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-payment-failure-pattern-analyzer-eee113e4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
