Raw descriptors are cryptic. Astrada Enrichment matches each transaction to a verified business — clean name and logo, category, and street-level location — fast enough to use at authorization.
We don't just clean up messy strings. Each transaction is matched against a database of verified businesses — so the record you receive describes the merchant, not the processor's abbreviation of it.
// what the network sends "descriptor": "TST* HNK 042 NEW YO", "mcc": "5812" // what your platform receives — enrichment.merchant.created { "merchant": { "name": "Hanoi Kitchen", "category": "Restaurants" }, "location": { "address": "114 Ludlow St", "city": "New York", "state": "NY", "postalCode": "10002", "phoneNumber": "+1212…" }, "_links": { "message": { "href": "/transaction-messages/b3a3c651…" }, "merchant": { "href": "https://hanoikitchen.nyc" }, "merchant-logo": { "href": "https://cdn…/logo.png" } } }
Every field below arrives on the same API as your real-time network feed — no second integration, no second vendor.
Physical transactions resolve to a street address, city, region, and postal code — not just a city guess. Built for receipt matching. Latitude/longitude is on the roadmap.
Brand logos, merchant websites, and phone numbers on matched transactions — the details that make a feed instantly recognizable and cut "what is this charge?" tickets.
Even unmatched transactions come back cleaned: normalized capitalization and structure, noise removed, misplaced data sorted into the right fields. Nothing raw ever reaches your UI.
Merchant-level data and line-item detail land on the same transaction record: recognizable to users, itemized for the books.
Every transaction resolved to a verified business, with the identity and context your platform needs.
Line-item settlement detail, itemized on transactions that support it — straight from the network.
Clean names, logos, and locations mean users recognize their purchases — fewer support tickets, faster approvals, shorter dispute cycles.
Persistent merchant IDs and four-tier categories make GL coding, policy rules, and merchant-level reporting reliable — no regexes on descriptors.
Enrichment returns fast enough to sit inside your authorization flow — so a resolved merchant and category can inform policy while the transaction is still open, not after it settles.
Enrichment ships on the same API as your network feed. Turn it on with a config change — no second integration.