Skip to main content
Bank and card statements arrive as unstructured line-item text, SQ *BLUE BOTTLE COFFEE OAKLAND, AMZN MKTP US*2X4B1QT0, UBER *EATS 8005928996 CA. Users don’t recognize the charge, support tickets follow, and spend categorization breaks. The Transaction API resolves that text to the real merchant in a single call, returning the company’s name, domain, industry, and logo, so banking, spend-tracking, and accounting apps can categorize spend and show a feed people actually recognize.

Show merchants, not codes

Raw transaction descriptors like SQ *BLUE BOTTLE COFFEE OAKLAND are unreadable. The Transaction API resolves that line-item text to a real merchant, name, domain, industry, and logo, in a single call, so banking and spend-tracking apps can show a clean, recognizable feed.

Transaction feed

A statement-style feed where each charge shows the recognized merchant and logo, with the original bank descriptor kept underneath for reference.

Want a bank feed with recognizable merchant logos? This prompt gives your AI coding tool everything it needs to build it in your framework.

Open in Cursor

Descriptor enrichment

Show the raw-to-recognized transformation directly, useful in a transaction detail view or when confirming a match.

Want to show raw descriptors resolving to real merchants? This prompt gives your AI coding tool everything it needs to build it in your framework.

Open in Cursor

Implementation

1

Send the descriptor

POST the raw line-item text as transactionLabel, with a countryCode to disambiguate merchants that share a name across regions. Keep the call on your server so the API key stays secret.
2

Use the response

The identified merchant comes back as a full brand record, use name as the display label, industry as the spend category, and render the logo from domain via the Logo API: https://cdn.brandfetch.io/domain/{domain}/w/40/h/40/fallback/lettermark?c=YOUR_CLIENT_ID.
3

Cache and fall back

The same descriptor recurs across statements, cache resolutions by normalized descriptor text. When a descriptor can’t be resolved, keep showing the raw text rather than guessing.

Pricing

The Transaction API is an enterprise product. Requests count as brand fetches, the shared usage unit across the Brand API, Brand Context API, and Transaction API, so a single quota pool covers all three.

Measuring impact

Enrichment works when people recognize their charges, so track the merchant match rate on incoming descriptors and the drop in “what is this charge?” support tickets and disputes. Envestnet | Yodlee used this pattern to improve merchant identification across its network.

Going further

Transaction API reference

Request and response shape, including countryCode.

Brand API

The response is a full brand record: colors, socials, and company details.

Get started

Create a free account and start building.