Transaction Enrichment {API}

No. You are not billed for failed requests or requests where we are blocked (rarely happens). Credits are only consumed on successful responses.

A transaction enrichment API converts the messy strings on bank statements ("SQ *BLUE BOTTLE OAK", "AMZN MKTPL*A12B3") into structured merchant data: clean name, official domain, logo, brand colors, category, and description. Context.dev returns the same data shape used in modern fintech UIs and personal finance apps.

POST the raw string (or array) to /v1/brand/transaction. The API tokenizes the descriptor, strips payment-processor noise (SQ*, TST*, PAY*, *PMT WA, store numbers), matches the residue against our merchant index, and returns the brand record — name, logo, domain, colors, category — in a single call.

Yes — Context.dev replaces the merchant-cleaning slice of Plaid Enrich, Ntropy, and Heron with a simpler API and richer brand data (full logos, color palette, social links). No banking institution coverage is required because it operates on the descriptor string itself.

Title (clean merchant name), official domain, high-resolution logo URLs, brand color palette, one-line and long-form description, social profiles, and industry category. Pair with the NAICS/SIC APIs if you need formal industry codes for compliance reporting.

Yes — coverage spans tens of millions of brands globally including local SMBs, regional restaurants, and subscription services. When a merchant isn't in the index, the API still returns its best guess at the cleaned name plus a confidence indicator so you can route low-confidence rows for human review.

Yes. Common use cases: auto-categorizing transactions in budgeting apps, surfacing rich merchant cards in card statements, deduplicating recurring subscriptions, and feeding fraud models with stable merchant identifiers (domain) instead of raw descriptor strings that change between processors.