Transaction data enrichment
Turn cryptic merchant codes into branded, recognizable transactions. Transaction data enrichment with logos, colors, and company details from a single API call.
Powering agents and products with the world's data.
From statement text to a recognizable merchant.
- 1
Capture the descriptor
Take the transaction text from your existing billing data or bank feed. Include location context when available.
- 2
Identify the merchant
Send the descriptor to Retrieve Brand using by_transaction. Handle not-found responses when a merchant cannot be identified.
- 3
Enrich the display
Show the matched merchant name, domain, and available logo so people can recognize a transaction.
See the difference in real time.
Cryptic transaction codes become recognizable brands.
Transaction history
| Date | Merchant | Amount |
|---|---|---|
| 2024-10-08 | AMZN*MKTP US-XX1234 | $129.99 |
| 2024-10-07 | WALMART STORE#1234 | $64.32 |
| 2024-10-05 | TICKETMASTER*EVENT | $245.00 |
Transaction history
Amazon
Seattle, Washington
$129.99
2024-10-08
Online Marketplacesamazon.com
Walmart
Bentonville, Arkansas
$64.32
2024-10-07
Omnichannel & In-Store Retailwalmart.com
Ticketmaster
Las Vegas, Nevada
$245.00
2024-10-05
Events, Venues & Live Entertainmentticketmaster.com
- Merchants identified
- 50M+
- API response time
- 1–10s
- Identification rate
- 99%
Retrieve a brand from a transaction.
Illustrative merchant match. Available Brand fields vary by company. These fields are included in the Brand response, together with the other available company details.
// Request body
{
"type": "by_transaction",
"transaction_info": "SQ *BLUE BOTTLE OAK",
"country_gl": "us"
}
// Example response
{
"status": "ok",
"brand": {
"domain": "bluebottlecoffee.com",
"title": "Blue Bottle Coffee",
"description": "Coffee roaster and cafe company."
},
"code": 200
}Teams that need recognizable transactions.
Fintech Apps
Building the next-gen banking experience
Challenge
Users see cryptic merchant codes like "SQ *MERCHANT 1234" instead of recognizable businesses.
Solution
Instantly enrich every transaction with logos and clean merchant names via a single API call.
Impact
Users actually understand their spending. Engagement jumps, support tickets drop.
Expense Management
Teams managing corporate spend
Challenge
Finance teams wade through spreadsheets of vendor names that don't match official company names.
Solution
Automatically match messy transaction data to clean company names, logos, and categories.
Impact
Expense reports become scannable at a glance. Approvals take minutes, not hours.
B2B Invoicing Platforms
Creating professional billing experiences
Challenge
Every invoice looks generic. Clients get templated PDFs that could be from anywhere.
Solution
Pull client branding automatically and generate invoices that look custom-designed.
Impact
Each invoice reflects the client's brand. Professional, memorable, and on-brand every time.
Payment Processors
Powering commerce for millions
Challenge
Merchant statements are walls of text. Small businesses can't make sense of their revenue streams.
Solution
Transform transaction logs into visual reports with payer branding and categorization.
Impact
Merchants see who paid them, not just transaction IDs. Better insights, faster decisions.
Accounting Software
Helping businesses manage their books
Challenge
Reconciliation is painful when transaction names don't match vendor records.
Solution
Intelligently match transactions to known vendors with visual confirmation via logos.
Impact
Bookkeepers spot mismatches instantly. Month-end close happens in days, not weeks.
Personal Finance Apps
Empowering smarter spending decisions
Challenge
Users can't tell which subscription is which or remember what "AMZ*abc123" was for.
Solution
Show actual company logos and clean names for every merchant and subscription.
Impact
Users actually review their spending. Subscription management becomes obvious and actionable.
A few things to know.
More details in the API documentation.
How do I identify a merchant from transaction text?
Send POST /v1/brand/retrieve with type set to by_transaction and the raw descriptor in transaction_info. The API returns a matched Brand record or a not-found error.
What merchant data can I get?
A match can include the merchant name, domain, description, logos, brand colors, social URLs, and available industry data. Brand fields are optional, so your interface should handle missing values.
Can I provide more context for matching?
Yes. Supply country_gl, city, mcc, or phone when available. Set high_confidence_only when you want additional verification of the match.
Does this API connect to bank accounts?
Provide the transaction descriptor from your existing data source. Retrieve Brand handles merchant identification and enrichment; your application supplies its own bank feed, payment connection, and financial logic.
Turn merchant codes into brands people know.
Identify the merchant behind any transaction and show its logo, colors, and company details. One API key for brand data.