Solution

MCC code cleanup for transaction feeds

TxnKit helps teams solve MCC cleanup with one safe descriptor, confidence-aware output, and warnings when identity evidence is weak.

Ask about a 100-descriptor cleanup auditInspect the API

Target intent

combine MCC context with merchant cleanup instead of treating MCC as identity.

TxnKit does not use MCC as the only merchant identity signal.

Raw descriptor

MCC 5814 MCDONALD'S F1234

API-shaped output

{
  "input": {
    "descriptor": "MCC 5814 MCDONALD'S F1234",
    "country": "CA"
  },
  "output": {
    "merchant_name": "McDonald's",
    "category": "Fast food",
    "confidence": "medium",
    "signals": [
      "processor_pattern",
      "merchant_alias",
      "category_hint"
    ],
    "warnings": [
      "review_low_confidence_matches_before_showing_logo"
    ],
    "logos": []
  }
}

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

When to use

  • You need MCC cleanup for transaction-feed UI, audit, or import review workflows.
  • You can send safe anonymized descriptors without customer PII or full statement text.
  • You want API-shaped output that a developer can inspect before wiring product UI.

When not to use

  • TxnKit does not use MCC as the only merchant identity signal.
  • 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