Skip to main content
Context.dev’s Transaction Enrichment API takes a raw card or ACH descriptor (e.g., AMZN*MKTP US) and returns:
  • title and domain: clean company name and domain
  • logos: SVG/PNG variants in light, dark, and on-background modes
  • colors: hex codes of colors from the merchant’s logo
  • industries.eic: industry + subindustry classification
  • stock: ticker and exchange for publicly traded merchants
  • And more: socials, address, links, description, slogan
Our database has 50M+ identified merchants. You can also find small and local merchants by passing mcc, city, country_gl, or phone.

Integrate Context.dev's Transaction Enrichment in your app

Open in Cursor

Prerequisites

  • A Context.dev API key. Sign up at context.dev/signup, copy the key from the dashboard (prefix ctxt_secret_), and export it:
  • An SDK (optional). Install for your language, or skip the install and call directly with curl:

Identify a transaction

POST /brand/retrieve takes a raw descriptor in transaction_info and resolves it to a merchant brand. Pass MCC and geography hints when you have them: they collapse ambiguity sharply on small or regional merchants.
10 credits per successful call

Request Parameters

Response

Handle errors

A fallback pattern that surfaces 400 as a “no match” outcome instead of an exception:
For the full error code catalog, see Troubleshooting.

Use cases

  • Personal finance apps: show actual company logos and clean names for every merchant and subscription.
  • Reconcile employee expense reports automatically: match messy expense entries to clean company names, logos, and categories.

Next steps

Prefetch for Faster Response

Hide cold-hit latency from your users.

Handle Rate Limits

Backoff strategies, client cache, and prefetch fallbacks.

Best Practices

Caching, error handling, and key hygiene.

Troubleshooting

Status codes, retry patterns, and common errors.