Equifax Identity Matching vs Payscore
Equifax Identity Matching
developer.equifax.comPayscore
payscore.comSide by side
| Figure | Equifax Identity Matching | Payscore |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| API | Yes | Yes |
| Plans published | 1 | 2 |
| Spec score · Employment Verification Software | 7.9 (#6) | 7.1 (#18) |
| Founded | 1899 | Payscore, formerly The Closing Docs, was founded in October 2017 by Stephen Arifin and Mark Fiebig. |
| Headquarters | Atlanta, Georgia, United States | Seattle, Washington, United States |
| Integrations | Batch services are supported through MFT integrations, and the listed cloud environments are Snowflake and Google Cloud Platform BigQuery. | Payscore lists native integrations with Yardi, RealPage, Entrata, Resman, Rent Manager, Rentvine, and TazWorks. |
| Security | Equifax says Identity Matching data undergoes encryption and tokenization to support data privacy and compliance controls. | Payscore states that it uses 256-bit encryption, does not store applicant credentials, and accesses transaction data read-only. |
Plans
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.