Solution

Merchant logo metadata API

TxnKit helps teams solve merchant logo metadata 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 reviewed logo variant metadata for transaction UIs.

TxnKit does not fetch or mutate logos during online enrichment.

Raw descriptor

STARBUCKS STORE 04821

API-shaped output

{
  "input": {
    "descriptor": "STARBUCKS STORE 04821",
    "country": "CA"
  },
  "output": {
    "merchant_name": "Starbucks",
    "category": "Coffee shop",
    "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.

No public merchant-logo examples

TxnKit explains logo metadata without presenting unlicensed merchant marks as sample output. Low-confidence responses should suppress logo display.

Supported variant field

FieldUse
format, width, heightChoose assets sized for transaction rows, receipt detail, and profile views.
theme, background, shapePick light, dark, transparent, square, rounded, or monochrome-safe variants.
purpose, source, confidencePrefer reviewed logo metadata and suppress weak identity matches.

When to use

  • You need merchant logo metadata 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 fetch or mutate logos during online enrichment.
  • 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