Integration

Finicity transaction cleanup

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

Ask about a 100-descriptor cleanup auditInspect the API

Target intent

clean Finicity-fed transaction rows after aggregation.

TxnKit sits after transaction data access.

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 already receive transactions through Finicity cleanup 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 sits after transaction data access.
  • 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