Name intelligence for payments

Know when the cardholder name really matches.

Multilingual, explainable name matching for payment and identity flows.

View API documentation Merchant login

Fast API • Explainable decisions • Privacy-conscious by design

NAME COMPARISONDETERMINISTIC

CUSTOMER

МарияСоколова

CARD

MARIYASOKOLOVA

DECISIONMATCH

CONFIDENCE0.97

TRANSLITERATION_MATCH

The problem

Names rarely arrive in one neat format.

Titles disappear. Middle names become initials. Tokens move. Scripts change. Generic exact comparison rejects names that may belong to the same person.

Nymetric evaluates name structure and applies conservative, explainable rules—not string equality alone.

CustomerEleanor Grace Bennett

STRUCTURAL COMPARISON

CardE G BENNETT

Given-name initialMiddle initialSurname exact

How it works

From noisy strings to a clear decision.

Three deterministic stages turn real-world name variation into evidence your payment flow can act on.

01
Normalize
Unicode, punctuation, spacing, titles and supported orthographic variants.
02
Understand
Tokens, initials, missing components, ordering, truncation and transliteration.
03
Decide
MATCH, REVIEW or NO_MATCH with a confidence score and reason codes.

Multilingual by design

Cross-script evidence, handled deliberately.

Nymetric supports Latin, Cyrillic, Greek, Arabic, Hebrew and Korean Hangul name comparisons today. Cyrillic and Greek include Latin transliteration matching.

Arabic and Hebrew use conservative cross-script matching. Korean Hangul uses structural cross-script matching, with ambiguous cases routed to REVIEW.

LATINElena MarkovicSupported

CYRILLICЕлена МарковичSupported

GREEKΜαρία ΝικολάουSupported

ARABICسارة منصورConservative

HEBREWנועה לויConservative

KOREAN HANGUL김민수REVIEW only

Built for developers

A focused API, with an answer you can explain.

Integrate through REST and OpenAPI. Use TEST keys for deterministic sandbox behavior, optionally attach an opaque, non-personal merchantReference, and trace each response by request ID.

POST/v1/match

REQUEST

{
  "customerName": "Мария Соколова",
  "cardholderName": "MARIYA SOKOLOVA",
  "merchantReference": "payment_12345"
}

RESPONSE

{
  "decision": "MATCH",
  "score": 0.97,
  "reasonCodes": [
    "TRANSLITERATION_MATCH"
  ]
}

Read the API docs

Explainability

Understand why - not just what.

Every result carries reason codes that describe the evidence behind the decision, helping teams tune downstream workflows and investigate REVIEW cases.

NORMALIZED_EXACT_MATCH MIDDLE_NAME_MISSING GIVEN_NAME_INITIAL TOKEN_ORDER_CHANGED SINGLE_TOKEN_TYPO TRANSLITERATION_MATCH KOREAN_STRUCTURAL_MATCH

Privacy and security

Built to minimize what it retains.

No raw-name persistence by default

Customer and cardholder names are processed for the comparison without being stored in search history by default.

Scoped access

Securely stored API keys, tenant-scoped data isolation, and separate TEST and LIVE environments.

Operational visibility

Request IDs, usage metadata and audit records support traceability without retaining the compared names.

Local deterministic matching

Each comparison runs inside Nymetric. No external AI or model API is needed to produce a decision.

Designed for TLS deployment with controlled merchant access.

Start integrating

Make name matching a decision - not a guess.

Read the API docs Merchant login