Solution

Low-confidence transaction warnings

TxnKit helps teams solve low-confidence warnings 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

return warnings instead of fake certainty for ambiguous transactions.

TxnKit does not force logos or websites onto weak matches.

Raw descriptor

POS PURCHASE 742 MAIN ST CAFE

API-shaped output

{
  "input": {
    "descriptor": "POS PURCHASE 742 MAIN ST CAFE",
    "country": "CA"
  },
  "output": {
    "merchant_name": "Main St Cafe",
    "category": "Restaurant",
    "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 low-confidence warnings 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 force logos or websites onto weak matches.
  • 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