tanzim
Request Demo

Turn Transaction Data Into Intelligence

Tanzim turns noisy Pakistani transaction descriptions into recognisable merchant names, logos, categories and confidence scores — ready for your bank or fintech app.

Request Demo Try the Sandbox
Working enrichment engine Built for the Pakistani Ecosystem Developer-first APIs
9:41
Transaction History
Raw
POS 8821 IMT*STORE KHI
PKR 4,820
09:38
DR CARD KAR/PSO LHR 0471
PKR 6,500
09:39
POS FP*ORDER LHR 22A
PKR 1,275
09:41
POS CHZ*PIZZA ISB 0917
PKR 2,340
09:43
POS OUTF*RETAIL KHI 5521
PKR 8,990
09:47
Why Transaction Enrichment?

One API call turns a string into a merchant

A raw transaction string is just a line of text. Tanzim resolves it into a recognisable merchant with a logo, category and directory MCC when matched. This illustrates an app presentation; amount and date come from the input, not merchant matching.

Raw Bank Transaction
POS/KHAADI PKG MALL LHR PK 8450.00 28JUN26
Khaadi
Enriched Transaction
Khaadi
PKR 0
28 Jun 2026
Category
Apparel
Subcategory
Women's Eastern
MCC
5651
Website
khaadi.com
Why local matters

Pakistan’s payments are digital. Its transaction histories still need clarity.

A payment can move instantly and still arrive in a customer’s history as a branch code, a truncated name or an unfamiliar wallet-prefixed string.

Pakistani brands. Local branch codes. Inconsistent payment descriptions. Tanzim is built around the transaction strings your customers actually see.

Recognisable transactions → categorised spending → richer insights.

Tanzim supplies the enrichment layer today. Your team builds the spending views and customer experiences on top; deeper intelligence is on the roadmap.

Built and running

A working product, not a scale claim.

910
Merchant profiles
8,279
Matching aliases
REST + JSON
Working enrichment API
Public
Interactive sandbox

Live API directory snapshot, 10 October 2026: 910 profiles and 8,279 indexed aliases. These are directory counts, not merchants matched in production. Coverage and accuracy depend on the transaction sample; a match confidence score is not an overall accuracy benchmark.

Test a transaction
Try the API

Live Demo

Paste a transaction string or upload a bank statement to see how Tanzim transforms raw transaction data into structured merchant intelligence.

POST/v1/transactions/enrich
Request
Presets
Live previewRaw input
9:41
Transaction
Tanzim enrichment
Unenriched
Original transaction string
POS/KHAADI PKG MALL LHR PK 8450.00 28JUN26
Ready to enrich
response.json
200 OK
{
  "merchant": {
    "name": "Khaadi",
    "logo_url": "/__l5e/assets-v1/e49df878-09a9-4b5a-9267-90aec2c0b465/khaadi.png",
    "category": "Fashion & Apparel",
    "subcategory": "Women's Ready-to-Wear",
    "mcc": "5651"
  },
  "location": {
    "city": "Lahore",
    "branch": "Packages Mall",
    "country": "PK"
  },
  "payment": {
    "channel": "POS",
    "instrument": "Visa Debit"
  },
  "contact": {
    "website": "khaadi.com",
    "phone": "+92 42 111 KHAADI"
  },
  "tags": [
    "retail",
    "apparel",
    "verified"
  ],
  "amount": {
    "value": 845,
    "currency": "PKR"
  },
  "timestamp": "2026-10-19T08:47:59.720Z",
  "confidence": 0.96
}
Khaadi
Fashion & Apparel · Lahore · MCC 5651
PKR 845
conf 96.0%
Designed for

Institutions building the future of finance

Banks
Fintechs
Lenders
Merchant Acquirers
Regulators
Platform

Enrichment first. Intelligence next.

Transaction enrichment is working today. The wider intelligence platform is a staged roadmap, shaped by pilot results and institution requirements.

Transaction Enrichment

Available today: merchant names, logos, categories, MCC and match confidence from raw transaction descriptions.

RawPOS 0384 MCD KHI
MerchantMcDonald's
CategoryFood & Dining
MCC5814
Available today
Input
Raw description
Identity
Merchant name
Output
Structured JSON
Review
Match confidence

What comes next

Planned layers · not available products
Phase 2

Merchant Intelligence

Deeper profiles and merchant relationships, built on a stronger local directory.

Phase 3

Customer Intelligence

Spending patterns and cash-flow insights from categorised transactions.

Phase 4

Fraud Signals

Merchant-based risk patterns to support institution-led investigation.

Phase 5

Open Banking Layer

Connected financial data APIs, subject to consent, privacy and regulatory requirements.

Direction, not a delivery commitment. Scope and timing will follow pilot evidence and partner requirements.

Developers

Built for developers.

A REST API, structured JSON and a public sandbox. Test real descriptions, inspect match confidence, then evaluate coverage on your own sample.

  • REST API
  • Merchant Names
  • JSON Responses
  • Sandbox
  • Match Confidence
  • API Docs
Read docs Get API key
tanzim.ts
// One transaction description in. Structured JSON out.
const res = await fetch("https://financial-core-production.up.railway.app/v1/enrich", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_API_KEY",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({ description: "NETFLIX.COM" })
});
const transaction = await res.json();

// Inspect merchant_name, logo_url, category,
// subcategory, mcc and confidence in the response.
Responsible evaluation

Start with a sample. Agree the safeguards.

Use synthetic or redacted descriptions in the public sandbox. Submitted strings are logged; do not include account numbers, personal identifiers or confidential customer data.

Before an institution shares a historical sample, agree the permitted fields, access, retention and deletion process. Production deployment needs a separate security and vendor review.

Tanzim does not claim SOC 2, ISO 27001 or PCI DSS certification, regulatory approval, private-network deployment or authorisation-path readiness.

Security and data considerations

Evaluate Tanzim on your transaction data.

Agree a sample, measure matching coverage and accuracy, review unmatched transactions, then discuss what production integration would require.

Request Demo Try the Sandbox