Onboard a business in seconds. Verify it at the source.
Payment providers, lenders and platforms have to know who they are onboarding, who owns them, and whether that changed this morning. Global Database returns verified company records from 400+ government registries in 200+ countries, with the filing behind every field.
0+
Government registries, collected directly0+
Countries and jurisdictions covered0M+
Company profiles0 yrs
Of filing history behind every entityWhat comes back in the response.
Six domains, one schema, the same provenance fields on every record. Values read from a filing are marked as filed. Values computed from filed figures are marked as calculated.
Registry file
The entity exactly as the register holds it, resolved from a partial name or an identifier the applicant already has.
| Field | Value | Source | Basis |
|---|---|---|---|
| legal_name | NORTHVANE PAYMENTS B.V. | KVK — NetherlandsCompany record | Filed |
| registration_number | 72118093 | KVK — NetherlandsCompany record | Filed |
| incorporated | 14 March 2018 | KVK — NetherlandsDeed of incorporation | Filed |
| registered_office | Amsterdam, Netherlands | KVK — NetherlandsRegister amendment | Filed |
| status | Active | KVK — NetherlandsCompany record | Filed |
| filing_history | 41 documents, earliest 2018 | KVK — NetherlandsDocument index | Filed |
Two fields from the applicant. Twenty-one from the register.
Start from whatever you already hold. Any of these resolves to the same record. US filers can start from an EIN, and an LEI works anywhere one has been issued.
Five teams reading one source of record.
KYB and merchant risk
Entity verification, trading status, ownership to natural persons and screening across the resolved group, returned at the speed of the application form.
Financial crime
Beneficial ownership calculated against the applicable threshold, sanctions and PEP coverage across the structure, and an evidenced trail behind every decision.
SME lending
Filed accounts line by line, charge registers, group structure and dated filing history across twelve years, joined on open identifiers.
Embedded finance
The same records behind a partner's onboarding as behind your own, so a platform can verify its business customers without building a data operation.
Go to market
Firmographics, filings and group structure for targeting and enrichment, in the same records compliance already trusts.
One record, one identifier
Open registry numbers rather than proprietary keys, so the entity compliance approved and the entity sales opened are provably the same company.
You could build this. Here is what you would be signing up for.
Most fintech teams start by pulling one or two registries directly. It works until the second market, the first schema change, or the first time compliance asks where a number came from.
01Registry connections
Every register publishes differently. Separate endpoints, formats, languages, authentication and rate limits, and several with no machine interface at all.
400+ registries already connected, in one schema.
02Entity resolution
The same company appears under different spellings, transliterations and legal forms across sources, with no shared key between them.
One resolved entity, keyed on open identifiers you can join to.
03Ownership across chains
Resolving beneficial ownership means walking every intermediate holding across jurisdictions, then applying whichever calculation the regime requires.
The full chain returned with every holding and its source.
04Change detection
Knowing that something changed means diffing every record on every cycle and deciding what counts as material, then keeping that running.
A change feed carrying only what moved, with the filing behind it.
05Provenance
Storing the filing reference, the filed date and the retrieval time for every field, and keeping it retrievable for as long as a supervisor might ask.
Attribution on every field, retained by default.
06Licensing
Public does not mean freely redistributable. Registry terms differ by jurisdiction and constrain what you may pass to your own customers.
Redistribution rights available, priced per use case.
07Keeping it running
Registers change schemas, move endpoints and go down. That maintenance never finishes and it competes with your roadmap forever.
Someone else's roadmap problem.
Perpetual KYB. The file never goes stale between reviews.
Every entity you onboard stays under watch from approval onwards, not re-checked on a refresh cycle. A merchant approved in March can be a different company by September, and each change is surfaced on the day it is filed rather than at the next review.
Everyone cites something. We cite the registry.
An onboarding decision, a declined application or a beneficial owner determination has to survive a supervisory review years later. What matters is not that a field has a source, but where that source resolves to.
One value on one merchant record. Everything beside it is what you can put in front of a supervisor or an auditor without asking us for anything.
400+ registries. Named, not implied.
Cleared before your security team asks.
How to access the data.
Seven routes into the same primary, government-sourced dataset. Pick the one that fits your stack.
API
Query any company by registry identifier. Documented endpoints, JSON responses, provenance on every field.
Bulk data feeds
Full datasets and scheduled deltas, delivered to your warehouse on your cadence.
CRM
Enrich and verify accounts inside Salesforce, HubSpot and Microsoft Dynamics 365.
Assistant connectors
Pull registry data straight into the assistant your teams already use.
Point it at your live portfolio. See what your file is missing.
Send a sample of merchants you have already onboarded. We return the resolved entities, the full ownership chains, and every field where your record and the register disagree.