Skip to main content
ParseTx is a batch-first transaction enrichment API built for fintech developers who are tired of shipping products with unreadable transaction descriptions. You send a raw bank statement string — the kind that looks like AMZN Mktp US*1A2B3C4D5 Amzn.com/bill WA — and ParseTx returns clean, structured JSON your app can actually use. No sales calls, no enterprise contracts, no minimum spend. Just an API key and $0.005 per request.

​
What ParseTx Returns

Every enrichment call gives you six fields for each transaction string: 
{
  "merchant": "Amazon",
  "domain": "amazon.com",
  "category": "Shopping",
  "mcc_code": "5411",
  "is_subscription": false,
  "confidence": 0.99
}
FieldTypeDescription
merchantstringCanonical, normalized merchant name (e.g. "Amazon" — never "AMZN" or "Amazon.com")
domainstring | nullVerified merchant domain — use it to render logos client-side
categorystringOne of 15 standardized categories such as "Shopping", "Food & Drink", or "Software"
mcc_codestring | null4-digit ISO 18245 Merchant Category Code, essential for accounting and compliance tooling
is_subscriptionbooleantrue if the merchant operates on a recurring billing model
confidencefloatModel confidence from 0.0 to 1.0 — set your own threshold for downstream logic

​
Why ParseTx

ParseTx is not a thin wrapper around an LLM. It’s a cache-first enrichment engine designed to be the reliable infrastructure layer your application depends on. Sub-50ms cache hits. ParseTx maintains a pre-warmed canonical merchant database seeded with the world’s top merchants. When your request matches a known entry, the result is returned from the edge in under 50ms — no AI inference, no waiting. Batch-native architecture. Submit up to 10 transactions synchronously via POST /v1/enrich, or up to 500 transactions asynchronously via POST /v1/enrich/async. No more looping through 500 sequential HTTP requests to process a bank statement. Deterministic output. Unlike raw LLM calls, ParseTx caches every resolved result. The same input string always returns the same merchant name, category, and MCC code. This consistency is essential for bookkeeping, analytics, and any downstream system that groups or deduplicates by merchant. Pay-as-you-go pricing. A flat 0.005perrequestwithnomonthlyminimum.Enrichathousandtransactionsfor0.005 per request with no monthly minimum. Enrich a thousand transactions for 5. There’s no enterprise gate, no sales demo, and no compliance questionnaire standing between you and your first API call.

​
See It in Action

Here is how ParseTx transforms a realistic Amazon transaction string into usable data: Input: 
AMZN Mktp US*1A2B3C4D5 Amzn.com/bill WA
Output: 
{
  "input": "AMZN Mktp US*1A2B3C4D5 Amzn.com/bill WA",
  "status": "complete",
  "source": "cache",
  "merchant": "Amazon",
  "domain": "amazon.com",
  "category": "Shopping",
  "mcc_code": "5411",
  "is_subscription": false,
  "confidence": 0.99
}
ParseTx strips the order ID noise, identifies the payment processor prefix, resolves the canonical merchant name, and returns a verified domain you can pass directly to a favicon service to render a logo — without ever hosting a single image file yourself.

​
Where to Go Next

Quickstart

Make your first API call in under 60 seconds. Get your key, copy a cURL command, and see enriched results immediately.

Authentication

Learn how to pass your API key, understand the two supported auth methods, and keep your credentials secure.

Enrich Endpoint

Full reference for POST /v1/enrich — request parameters, response schema, error codes, and rate limits.

Batch Processing

Process up to 500 transactions in a single async job. Covers the async endpoint and job polling.