Identity match, account match and phone signals explained
Identity, account and phone checks answer different questions. A valid format, reachable phone or valid bank account does not establish that a named person owns the identifier or is the current actor. A decision policy should specify which assertion each signal supports.
Identity and electronic identity
Name-and-ID matching compares submitted attributes with a supported source. Consent-based electronic identity can authenticate a user or share attributes through a specific scheme. Neither should be generalized beyond supported fields and scheme assurance. Document OCR extracts data; extracting a name is not database matching.
Accounts and cards
Bank account validity, bank account holder-name match and cardholder-name checks have different coverage and access paths. BIN or IBAN checks address structure or routing information. A card-network feature may depend on issuer support; do not turn a country listing into a guarantee for every card.
Phone checks
OTP can demonstrate access to a channel at a moment in time. Line type describes a telephone category. Subscriber-name matching compares identity attributes where the product supports it. SIM-swap signals report a different risk condition. The current GridZen Twilio adapter uses phone validity and line type, not subscriber-name matching.
Download public country CSV (Chinese source fields)
Sources and scope
Research cutoff: 2026-10-07. Public summary prepared 2026-10-09; no new country audit is implied.