Regline turns official company registries into API endpoints. Send a company name or registration number; get back the registry record as JSON, with the source and the time it was read. France, the Netherlands, Belgium, Portugal, Bahrain and more, through one call shape.
A French parent, a Dutch trading entity, a Belgian branch, a Portuguese subsidiary. Four registry sites, four search forms, one CAPTCHA, and a director's name copied by hand with an accent missing.
The enterprise KYB vendor covers the large registries well. Then a merchant with a Bahraini entity arrives, the vendor has no connector, and the check goes back to a person with a browser while the merchant waits to go live.
The case note says "verified on registry". The auditor wants the record itself, with a date. The screenshot is on a laptop that was replaced in the spring, and the registry entry has changed since.
23 endpoints across 10 registries in 8 countries. If a registry you need is not here, it is not covered yet. Ask and we will tell you whether we can build it.
Each endpoint returns the fields that registry publishes. Registries differ: some list directors, some do not. Check a sample response for the registry you care about before you rely on a field.
Pick the endpoint. Each lookup, such as a Pappers company profile or a KVK trade register search, is a hosted function with its own ID.
Call it from your onboarding flow. We open the registry in a real browser on our side, submit the search and read the result page. You do not run browsers or handle the search form.
Store the response with the case. You receive the registry's fields, the source and the retrieval time. Keep that JSON in your own case file as your record of what the registry showed when you checked.
Your process decides. Regline reports what the registry shows. Matching, risk rating and the approve or decline decision stay with your team and your policy.
Use your own numbers. The estimator only does arithmetic on what you enter: it assumes nothing about your team, and it counts only the checks that fall in countries Regline covers.
An estimate from your inputs, not a promise of results. Review time per result is your assumption to set.
"We did not replace our KYB process. We replaced the part where someone copies a SIREN and three directors from a browser into a form. The record lands in the case, the analyst reads it and makes the call."
"Our vendor had no answer for Bahrain. Two endpoints later, the Sijilat lookup sits in the same workflow as France and the Netherlands."
"The audit sample used to mean a week of hunting for screenshots. Now each file has the registry response with its retrieval time attached."
A lookup is one endpoint call. A typical check uses two: a search, then the details page.
No. Regline returns what the public registry shows at the time of the call. That is one input to your process. Whether a check is sufficient, what else you need to collect and whether to onboard the customer are decided by your own compliance process and policy, not by Regline.
No. Regline does not provide sanctions screening, PEP screening or beneficial-ownership screening. It reads the registries listed in the coverage section and returns the fields they publish. If a registry does not publish a field, the endpoint does not return it.
Each call opens the registry or source site in a browser on our side and reads the result at that moment. The response is what the source showed at call time. If the registry is out of date or wrong, the response will be too, because we report the source and do not correct it.
The response includes the source and the retrieval time alongside the registry's fields. Store that JSON in your case file. Regline is not your system of record: keeping the response, and deciding how long to keep it, is on your side.
When a registry changes its site, we repair the endpoint on our side and keep the same function ID. If the registry is down or the lookup fails, the call returns an error. It does not return an older result in place of a fresh one.
A lookup takes as long as the registry site takes to answer in a browser, so it is slower than a database query. We do not publish a latency figure. Run lookups as a background step in your onboarding flow and measure with your own cases during the trial.
Often, yes. Tell us the registry and the fields you need and we will say whether we can build an endpoint for it. Until an endpoint is listed in coverage, treat it as not covered.
Regline runs on Notte's browser infrastructure. Each endpoint is a hosted Notte function, which is why every registry uses the same call shape.
Take a trial key, pick the registries your merchants come from, and compare the responses with what your analysts record today.