Use case

Expense app transaction enrichment

Clean processor-wrapped card activity into merchant names, categories, confidence, and warnings before reviewers see the feed.

Answer-first summary

TxnKit fits expense apps that already receive transaction feeds and need display quality. It improves merchant-oriented metadata; it does not decide reimbursement policy, tax treatment, or receipt validity.

Raw descriptor example

POST /v1/enrich

{
  "raw_description": "SQ *JOES COFFEE 0421 TORONTO",
  "amount": 6.75,
  "currency": "CAD",
  "country": "CA",
  "mcc": "5814"
}

{
  "display_name": "Joe's Coffee",
  "category": "Food and Drink",
  "processor_hint": "square",
  "confidence": 0.72,
  "warnings": ["local_merchant_identity_not_verified"]
}

When to use

Use TxnKit when expense rows contain store numbers, processor wrappers, inconsistent casing, and local merchant uncertainty that should be visible to reviewers.

When not to use

Do not use this flow for full statements, account numbers, card numbers, customer PII, reimbursement decisions, or legal identity verification.