Compare

Teller transaction enrichment alternative

TxnKit is a focused cleanup layer for teams evaluating Teller. Use it when the transaction feed already exists and the visible merchant row still looks unfinished.

Ask about a 100-descriptor cleanup auditInspect the API

Target intent

Teller-backed apps looking for merchant cleanup after transaction ingestion.

TxnKit is not account-linking infrastructure.

Raw descriptor

TST*MAIN ST CAFE

API-shaped output

{
  "normalized_merchant": "main st cafe",
  "display_name": "Main St Cafe",
  "category": null,
  "subcategory": null,
  "website": null,
  "logos": {
    "preferred": null,
    "variants": [],
    "warnings": [
      "no_verified_logo_for_local_merchant"
    ]
  },
  "confidence": 0.56,
  "recurring_hint": false,
  "processor_hint": "toast",
  "location_hint": null,
  "signals": [
    "removed_toast_prefix"
  ],
  "warnings": [
    "local_merchant_identity_not_verified"
  ]
}

Low-confidence results should keep fallback labels and warnings visible instead of forcing a guessed logo or website.

When to use

  • You already receive transaction data and need a narrower Teller alternative for display enrichment.
  • Your app needs merchant names, categories, confidence, warnings, and logo-ready metadata.
  • You want deterministic enrichment behavior without live LLM, crawler, logo-provider, or third-party enrichment calls.

When not to use

  • TxnKit is not account-linking infrastructure.
  • Do not use TxnKit to process card numbers, account numbers, full statements, bank credentials, emails, phone numbers, addresses, customer names, or customer PII.
  • Do not use TxnKit when the product requirement is guaranteed merchant identity, every-merchant resolution, or contracted uptime terms.

Proof surfaces

The public contract is POST /v1/enrich, backed by the OpenAPI file, benchmark examples, privacy rules, and deterministic request-path tests.

OpenAPI · Benchmark · Security · Pricing

Related pages