Santiago Garcia

Posted on Apr 8

How to Enrich Transaction Data with One API Call (and Why Your App Needs It)

#javascript #fintech #api #webdev

If you've ever built a fintech app, a personal finance dashboard, or any product that deals with bank transactions, you know the pain: raw transaction strings like NFLX*NETFLIX.COM, AMZN MKTP US, or SQ *BLUE BOTTLE are completely useless to end users.

Decoding those strings manually — matching them to real merchant names, categories, logos, and contact info — is a rabbit hole that costs weeks of engineering time and never quite works well enough.

That's where transaction data enrichment APIs come in. And in this post, I'll walk you through how to integrate one in literally three steps.

Why Enrich Transaction Data?

Before we get into the code, let's think about what enriched data unlocks:

Better UX: Show "Netflix" with a logo instead of "NFLX*NETFLIX.COM 866-579-7172 CA"
Smarter categorization: Automatically tag spending as "Streaming", "Food & Drink", "Travel", etc.
Subscription detection: Know which charges are recurring without building your own ML model
Contact info on demand: Let users reach out to merchants directly from your app
Carbon footprint insights: Some APIs even return CO2 impact data per merchant category

All of this becomes possible when you stop treating transaction data as a raw string and start treating it as structured, enrichable information.

The API Approach

Easy Enrichment is a transaction data intelligence platform that takes a raw bank transaction description and returns 20+ structured fields in a single API call. Let's see how it works.

Step 1: Get Your API Key

Sign up at easyenrichment.com — it's free to start, no credit card required. You'll get an API key instantly from the dashboard.

Step 2: Make Your First Request

curl -X POST https://api.easyenrichment.com/enrich \
  -H "Authorization: Bearer enrich_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"merchantName": "AMZN MKTP US"}'

Step 3: Use the Response

The response comes back with everything you need:

{
  "merchant_name": "Amazon",
  "category": "shopping",
  "subcategory": "marketplace",
  "logo_url": "https://img.logo.dev/amazon.com",
  "domain": "amazon.com",
  "mcc_code": "5999",
  "is_subscription": false,
  "is_online_only": true,
  "confidence": 0.97,
  "contact_phone": "+1 888-280-4331",
  "contact_email": "cs-reply@amazon.com",  "country": "US"
}

That's it. One API call. 20+ fields. No complex setup, no training your own model, no maintaining merchant databases.

JavaScript Integration Example

Here's how you'd integrate this in a Node.js backend:

async function enrichTransaction(rawDescription) {
  const response = await fetch('https://api.easyenrichment.com/enrich', {
    method: 'POST',
    headers: {
      'Authorization': `Bearer ${process.env.ENRICHMENT_API_KEY}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({ merchantName: rawDescription }),
  });

  if (!response.ok) {
    throw new Error(`Enrichment failed: ${response.status}`);
  }

  return response.json();
}

// Usage
const txData = await enrichTransaction('NFLX*NETFLIX.COM');
console.log(txData.merchant_name); // "Netflix"
console.log(txData.category);      // "streaming"
console.log(txData.logo_url);      // "https://img.logo.dev/netflix.com"

The 5 Endpoints You Get

Easy Enrichment isn't just for bank transactions. The API covers five data types:

POST /enrich — Bank transaction codes → merchant data (1¢/req)
POST /enrich/company — Company name → industry, size, HQ, social profiles (2¢/req)
POST /enrich/domain — Website URL → company info, tech stack, contacts (1¢/req)
POST /enrich/social — Person name → LinkedIn, Twitter, Instagram, YouTube (1¢/req)
POST /enrich/person — Person name → job title, company, location (2¢/req)

For most fintech use cases, /enrich is your primary endpoint. But if you're building something like a CRM or a B2B tool, the company and person endpoints are incredibly useful too.

Pricing: Pay Per Request, No Subscriptions

One thing I appreciate about this model: no monthly minimums, no commitments. You top up your balance (starting from $10) and pay per request. For most apps at early stages, you're looking at pennies per day.

Compared to building and maintaining your own merchant recognition system — which could easily be a 3-6 month engineering project — this is a no-brainer.

When to Use Data Enrichment

Here are some concrete use cases where this API shines:

Personal finance apps: Categorize and display transactions with merchant logos
Expense management tools: Auto-classify business expenses by MCC code
Banking apps: Give users clear merchant names and contact info when they dispute charges
Accounting software: Link transactions to company profiles and invoice data
Subscription trackers: Identify recurring charges automatically using is_subscription

Wrapping Up

Transaction data enrichment is one of those things that seems like a small UX improvement but actually unlocks a huge amount of product functionality. Instead of showing users cryptic bank codes, you can show them real merchant names, logos, categories, and contact info.

If you're building in the fintech space and want to skip the months of work required to build this yourself, give Easy Enrichment a try — the free tier is generous and the API is straightforward to integrate.

Have questions or built something cool with transaction enrichment? Drop a comment below!

Disclaimer: I'm sharing this tool because I found it useful for a project. Always evaluate APIs based on your own use case and requirements.

DEV Community