Equifax Identity Matching vs Verification Exchange
Equifax Identity Matching
developer.equifax.comVerification Exchange
equifax.com.auSide by side
| Figure | Equifax Identity Matching | Verification Exchange |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| API | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Employment Verification Software | 7.9 (#6) | 7.3 (#16) |
| Purpose | Identity Matching identifies and links customer information across disconnected data sources, including when names or addresses vary. | Verification Exchange provides instant, consumer-consented access to verified employment income data from source to support lending decisions. |
| Security | Equifax says Identity Matching data undergoes encryption and tokenization to support data privacy and compliance controls. | Equifax says encryption and access management are used across data provision, storage, and verifier access, and that its Australian businesses, including Verification Exchange, are covered by ISO 27001 certification. |
Plans
Verification Exchange
- Verifier subscription (Employment Income or Employment verification)Priced on request
In their own words
Equifax Identity Matching
Equifax Identity Matching links customer information held in disconnected sources, including records where names or addresses differ. It assigns persistent consumer identifiers and can create consumer, household, and address keys, helping organizations form a single customer view. Equifax says it compares multiple datasets and data-element combinations, and can combine company records with consumer credit and specialty finance data. Matching and updates are described as cloud-based and near real time, with incremental key changes available through delta services. Delivery options include batch services, an online API, and cloud-native Keying as a Service in Snowflake or Google Cloud Platform BigQuery environments. Confidential Keying keeps raw personal information in a customer cloud environment. Data is encrypted and tokenized, usage is regulated by GLBA, and processes are regularly validated. OAuth 2.0 client credentials secure APIs; production access requires credentials and whitelisted IP addresses. Pricing is on request.
Verification Exchange
Verification Exchange has no write-up on Specifiction yet; its figures are above.