Fintech APIs & Platform for KYC, Verification & Transactions in India | Eko Platform Services
Eko Platform Services Logo
← Back to Home

Name Match API for Cross-Document Identity Verification

AI-powered name comparison trained on 100M+ Indian name records. Compare names across PAN, Aadhaar, bank, and GST records — get a match score (0–1) and category (Direct Match, Partial Match, No Match) for automated KYC decisions.

Get Sandbox Access View Documentation

Starts at ₹0.60 per match · excl. GSTView Pricing

Overview

Name Match is an AI-powered name comparison API built for India's complex naming conventions. Trained on over 100 million Indian name records, it handles initials, abbreviations, phonetic and regional spelling variants, salutation patterns, and subset matching — returning a match score (0 to 1) and match category for automated decision-making.

What Can You Verify With Name Match API?

Key details returned across all Name Match API endpoints, ready to power your KYC and onboarding workflows.

Score

Numeric match score between 0 and 1. Thresholds: 1.0 = Direct Match; 0.85–0.99 = Good Partial Match; 0.60–0.84 = Moderate Partial Match; 0.34–0.59 = Poor Partial Match; 0.00–0.33 = No Match.

Reason

Human-readable explanation of the match result — effectively the match category label along with the AI model's rationale (e.g. initials expansion, phonetic match, subset match).

Simplified API Preview

Name Match API Flow – Sample Request and Response

Send simple inputs. Get rich, verified data in seconds.

AI-powered name comparison trained on 100M+ Indian name records — returns a match score (0–1) and match category for automated KYC decisions.

REQUEST
Name 1S K Mishra
Name 2Satish Kumar Mishra
RESPONSE
200 OK
Score0.92
ReasonNames match with initials expanded

Key Features

Everything you need to integrate and scale

Indian Name Intelligence

Handles initials, middle names, abbreviations, and subset matching (e.g. Harsh Kishore → HKishore) with high accuracy.

Phonetic & Regional Variants

Understands phonetic similarities and regional spelling variations across Indian languages and naming conventions.

Context-Aware Matching

Considers name sequence, gender, regional norms, and salutation patterns (e.g. S/O, D/O) for accurate results.

Score + Category Response

Returns a 0–1 score with match categories: Direct Match (1.0), Good Partial (0.85–0.99), Moderate Partial (0.60–0.84), Poor Partial (0.34–0.59), No Match (0–0.33).

Who Should Use This API?

Lending and financial institutions
Accounting and tax platforms
Marketplace and e-commerce platforms
Enterprises performing KYC/KYB

Primary Use Cases

Cross-document KYC name validation
ITC fraud detection via GST-PAN-bank name checks
Lending name match for fraud prevention
Merchant onboarding name consistency checks
Payout reconciliation
Risk and fraud prevention

How to Integrate

Get started in minutes with our simple integration process

  1. 1

    Sign Up

    Sign up in minutes with your mobile number (OTP verify).

  2. 2

    Verify Identity

    Complete your basic KYC with PAN and address details to verify your identity.

  3. 3

    Test APIs Live

    Load funds into your wallet and test the verification APIs live — evaluate before you integrate.

  4. 4

    Integrate with AI

    Ready to build? Visit our AI hub for free plugins & tools to integrate faster.

  5. 5

    Go Live

    Start matching names in production.

Frequently Asked Questions

How does the matching work?+

Name Match uses AI trained on 100M+ Indian name records. It handles initials, phonetic variants, regional spellings, salutation patterns (S/O, D/O), subset matching, and name ordering variations.

What is the score range?+

The API returns a score from 0 to 1: Direct Match (1.0), Good Partial Match (0.85–0.99), Moderate Partial Match (0.60–0.84), Poor Partial Match (0.34–0.59), No Match (0–0.33). Set your own threshold based on risk tolerance.

What examples of Indian name variations does it handle?+

Initials (S K Mishra → Satish Kumar Mishra), subsets (Harsh Kishore → HKishore), salutations (Aditya Roy S/O Jatin), missing middle names, extra spaces, and phonetic/regional spelling variants.

Can I use this for GST ITC fraud detection?+

Yes. Cross-validating supplier PAN name, GST trade name, and bank account holder name catches fake invoice fraud that manual review misses.

How do I get started?+

Sign up at ekostore.app/eps, verify your identity with your PAN and address details, load your wallet to test the verification APIs live, then integrate and go live.

What is EPS?+

EPS (Eko Platform Services) is the technology arm of Eko, providing the developer tools, AI tools, and APIs that power modern fintech integration.

Also see:About Eko
What are the different ways to integrate with Eko EPS?+

Integrate in whichever way suits your stack: call the REST APIs directly, use our official SDKs (JavaScript and PHP) to skip request-signing boilerplate, or let an AI coding agent build the integration using our MCP server and skills. See the Developers and AI sections for each path.

How does API authentication work?+

Each request carries your static `developer_key` header plus a per-request `secret-key` header — an HMAC-SHA256 signature of the current timestamp, keyed by your access key. The access key itself is never sent over the wire. You receive UAT keys on signup and production keys after KYC.

Is there a sandbox environment for testing?+

Yes. A full sandbox environment is available immediately on signup. You can test your integration end-to-end before going live — no commitment required.

Also see:Get started
What are the sandbox and production base URLs?+

Sandbox and production share the same paths and differ only by base URL: use https://staging.eko.in/ekoapi/v3 for UAT / Sandbox, and https://api.eko.in/ekoicici/v3 for Production. A common cause of failures is calling the sandbox/staging URL with live credentials (or vice-versa) — make sure the base URL matches the keys you are using.

Do I need to whitelist my server IP?+

Production API access may require your static public (server) IP to be whitelisted. If your calls work from Postman but fail or time out from your own server, share your static public IP with us so we can whitelist it.

What response times can I expect?+

Most verification APIs return in real time with sub-second responses, and 99th-percentile latency stays under two seconds across verification endpoints. Transaction APIs (DMT, AePS, BBPS) respond within seconds.

Can the API handle high volumes?+

Yes. The API is designed to handle large-scale volumes reliably without performance degradation.

How is API usage billed?+

Usage is billed per successful API call with no minimum commitment. Volume-based pricing tiers are available — contact our team for detailed rates.

Get API Access

Sign up now and start integrating in minutes. Our team will help you go live quickly.

  • Sandbox access in minutes
  • Dedicated integration support
  • Comprehensive documentation
  • Reliable, high-volume workflows

Get Name Match API Access

Get started in 10 minutes