A stranger wants to open an account. There is a name, a photograph and a piece of plastic with an official seal. Somewhere else, perhaps in a government database, is another version of that person. Somewhere else again is a financial record. The difficulty is getting those fragments to agree before the stranger gives up and closes the app.
- MetaMap combines identity evidence in workflows businesses can configure.
- Its experience is particularly rooted in Latin America and Africa.
- Incode acquired it in June 2024; the current website routes prospects to its parent.
That is the everyday problem behind MetaMap. Founded in San Francisco in 2017 as Mati, the company built software for businesses that need to recognize customers they have never met. Its customers have included payment providers, lenders, insurers and cryptocurrency exchanges. The person taking the selfie is the user. The business deciding whether to accept that person is the buyer.
An ID is only the first clue
MetaMap’s company history presents identity as an access problem: useful information exists, but it is fragmented or difficult to interpret. The ambition was to let businesses serve people they would otherwise struggle to evaluate. Its published company page reports more than 600 businesses across more than 50 countries. Those are MetaMap’s figures, rather than an independent census.
Consider Eversend, an Africa-focused financial platform featured in MetaMap’s customer marketing. Eversend’s June 2024 help guide asks users for an address, a government-issued ID and a short biometric video. It also warns that unclear submissions may require another attempt. Behind the phrase “verify your identity” sits a remarkably physical task: lighting, a camera, a readable document, a face that stays in view.
MetaMap’s expertise lies in combining that capture process with other evidence. Its government-check catalog lists country-specific sources, including Brazil’s CPF records and identity checks in African markets. A supported passport scan and an available government lookup are different capabilities. That distinction matters when a business expands across a border.
The product is the sequence
The platform gives businesses a workflow builder. Teams choose checks, configure requirements and arrange the experience around a particular service or country. Document verification examines the ID; biometrics compare faces and test liveness; watchlist screening looks for risk signals. Financial tools can add bank information or credit checks where available. A result then becomes something an operations team can review.
There are three delivery routes. A direct link sends the user to a prebuilt experience. An SDK embeds that experience in an app or website. An API lets developers build their own interface. MetaMap’s published integration guide estimated five minutes for a direct link, four hours to five days for an SDK, and one to two weeks for an API. These were implementation estimates, not promises about every project.
Company estimates · implementation time · not verification speed
The tradeoff is design control against engineering work. A lending team testing a new market might value the link; a product team with an established onboarding experience might want the API. The dashboard serves another audience: compliance and operations staff reviewing results, audit trails and analytics.
Jumio and Sumsub offer overlapping verification and workflow capabilities. MetaMap’s argument therefore depends on the particular mix of regional data, configuration and implementation support a customer needs. A long tool menu alone cannot establish which provider fits a business.
The bill behind the dashboard
MetaMap sells verification software and data services to businesses through commercial arrangements. Its biometric update explicitly describes premium configurations that cost extra. Earlier marketing advertised 300 free verifications over three months. A buyer should treat that as historical trial material and obtain current terms through the Incode sales route.
One unusually concrete cost story concerns MetaMap’s own software. A November 2023 Preset case study describes rising renewal costs at its previous embedded-analytics supplier. MetaMap evaluated alternatives and switched to Preset, reporting savings above 50%. Reusable charts and data models maintained outside the BI tool helped avoid duplicated definitions. The useful lesson is specific: examine the renewal economics and portability of the tools that become part of your product.
After switching embedded BI providers. Preset customer case study, November 2023; no dollar baseline disclosed.
The founder who changed his mind
Capital tells a larger version of the story. Mati announced a $13.5 million Series A in November 2020, led by Tribe Capital. A $70 million Series B followed in December 2021, also led by Tribe, with investors including Craft Ventures. The expansion plans included building a larger technology team in India.
In a May 2024 interview with Endeavor Poland, Victor said he had nearly gone bankrupt several times and struggled with early fundraising. That account supplies a useful corrective to the later funding announcements: access to capital had been a recurring difficulty.
Yet ambition remained expensive. In his public explanation of the Incode sale, founder Filip Victor described weaker fintech conditions affecting customers and the bigger balance sheet needed for his identity-research ambitions. He had previously opposed selling. Cross-border infrastructure, privacy and data-custody work changed the calculation.
“we needed a lot more money”Filip Victor, explaining the Incode transaction
Incode announced the acquisition on June 11, 2024. A tangible product consequence followed: MetaMap said Incode’s passive liveness technology replaced its traditional selfie-photo feature, with rollout completed that September. The check could assess liveness without asking users to perform particular head movements.
A better camera still needs a working database
The smaller reversals are revealing too. In January 2025, MetaMap explained that it had restored simpler document-type codes after feedback on a trial format. The lesson for product teams is easy to copy: a more elaborate representation has to justify the work it creates downstream.
There are also limits that software cannot wish away. MetaMap’s documentation provides retry and timeout settings for data-provider outages. Its status page records country-specific interruptions. The practical inference is that onboarding needs a plan for an unavailable database, alongside a plan for a suspicious document. A business still has to choose its evidence, review exceptions and decide whom to serve. MetaMap’s contribution is making that sequence easier to assemble.