Integration

Teller transaction enrichment

TxnKit helps Teller enrichment workflows return cleaner merchant display metadata after the transaction feed is already available.

Ask about a 100-descriptor cleanup auditInspect the API

Target intent

enrich Teller-backed transaction descriptors for UI display.

TxnKit does not replace Teller account connectivity.

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 transactions through Teller enrichment and need cleaner UI rows.
  • You want a one-descriptor enrichment API with bounded response fields.
  • You need fallback warnings for ambiguous descriptors instead of silent overconfidence.

When not to use

  • TxnKit does not replace Teller account connectivity.
  • 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