Pre-launch · design partners
Know the business
is actually real.
Regista resolves a company against the official corporate registry — not against a document the applicant uploaded. Registration status, registered address, directors, and every discrepancy between what was claimed and what the record says.
- Source
- Official registries
- Evidence
- Stored per check
- First market
- Nigeria · CAC
- Entity
- Adaeze Logistics Ltd
- Registration
- RC 1284993
- Registry status
- Active
- Incorporated
- 12.03.2019
Directors of record
- Okonkwo, C.matches application
- Balogun, N.not disclosed
A director on the registry record was not disclosed on the application. Surfaced before onboarding, not after a dispute.
§ 01 — The problem
Most onboarding is a document review,
not a verification
Across lenders, payment providers and marketplaces the same pattern repeats: the applicant supplies the evidence, a person decides it looks right, and nothing is checked against the source.
- 01
A PDF is not a verification
Most onboarding still ends with someone opening a scanned certificate and deciding it looks right. Nothing is checked against the source registry, and nothing is recorded about who decided what.
- 02
Directors are the actual risk
The entity may be real while the people behind it are not who they claim. Ownership and directorship rarely get checked at all, because doing it by hand across registries is slow work.
- 03
It does not survive an audit
When a regulator or partner asks how a business was onboarded eighteen months ago, the answer is usually a folder of email attachments and nobody's memory.
§ 02 — Method
Four steps, none of which involve a PDF
- 01
Submit an entity
Send a registration number, or a name and country. One POST, no dashboard work, no file uploads.
- 02
We check the source
The entity is resolved against the official registry rather than a document supplied by the applicant, and matched across name variants and spelling differences.
- 03
You get a structured answer
Registration status, registered address, directors and officers, and the discrepancies between what was claimed and what the registry says.
- 04
The record persists
Every check is stored with its evidence and a timestamp, so the decision can be reconstructed years later without relying on anyone's inbox.
§ 03 — Register
What works today, and what does not
We would rather lose a deal to an honest roadmap than win one and be found out during integration. This table is the real state of the system.
| Market | Registry | Checks | Status |
|---|---|---|---|
| Nigeria | Corporate Affairs Commission (CAC) | Entity existence, RC number, registered address, directors, status | In development |
| Kenya | Business Registration Service (BRS) | Entity existence, registration number, directors | Planned |
| Ghana | Office of the Registrar of Companies | Entity existence, registration number, directors | Planned |
| South Africa | CIPC | Entity existence, registration number, directors | Planned |
Nothing here is marked in service yet. When Nigeria goes live that row changes, and nothing else on this page does.
§ 04 — Interface
One call, and an answer you can act on
No dashboard workflow, no document uploads, no queue of analysts. The response is shaped to be consumed by onboarding logic, and to still make sense to a compliance reviewer reading it two years later.
curl https://api.registahq.com/v1/verifications \
-H "Authorization: Bearer $REGISTA_KEY" \
-d '{
"country": "NG",
"registration_number": "RC1284993",
"claimed": {
"name": "Adaeze Logistics Limited",
"directors": ["Chidinma Okonkwo"]
}
}'{
"id": "ver_01hzx9km4",
"status": "match",
"entity": {
"name": "ADAEZE LOGISTICS LIMITED",
"registration_number": "RC1284993",
"registry_status": "ACTIVE",
"incorporated_on": "2019-03-12"
},
"discrepancies": [
{
"field": "directors",
"severity": "review",
"detail": "Registry lists a director not
disclosed by the applicant."
}
],
"evidence": {
"source": "CAC",
"retrieved_at": "2026-09-05T09:14:22Z"
}
}This is the planned interface, not a live endpoint. We publish it now so design partners can tell us where it is wrong before it hardens. If a field here would not fit your onboarding flow, that is exactly what we want to hear.
§ 05 — Application
Who it is for
- Lenders
- Confirm a borrower is a real, active entity and that the person signing controls it, before money moves.
- Payment providers
- Onboard merchants without a queue of analysts opening PDFs, and keep the evidence trail your regulator will ask for.
- B2B marketplaces
- Verify suppliers at sign-up rather than after the first dispute, and re-check them as their registry status changes.
- Enterprise procurement
- Screen vendors against the registry at onboarding, and keep that screening current across a long supplier list.
§ 05.1 — Data handling
Practices, stated plainly
We hold no compliance certifications. Claiming otherwise would be the fastest way to lose the only thing this product sells.
- Data minimisation
- We store the registry response and the query that produced it. We do not ask for, or want, customer documents you are not required to send.
- Encryption
- TLS in transit and encryption at rest via managed cloud services. Standard practice, stated plainly rather than dressed up as a certification.
- Evidence retention
- Each verification is stored with the raw registry response, so an audit years later reconstructs the decision rather than trusting a summary.
- Regional data handling
- Nigerian data handled in line with NDPR obligations. As we add markets we will meet each market's requirements before we launch there, not after.
§ 06 — Questions
Straight answers
What is actually live today?
Nigeria (CAC) is in active development with design partners. Every other market on the coverage table is labelled planned, and will stay labelled that way until it genuinely works. We would rather tell you what does not exist yet than have you find out during an integration.
How is this different from identity verification?
Identity verification answers whether a person is who they say they are. Regista answers whether a business is real, currently registered, and controlled by the people claiming to control it. Most teams need both, and they are different data sources.
Where does the data come from?
Official corporate registries, resolved at the time of the request. We do not resell scraped datasets of unknown age, and every response carries the timestamp of when the source was read.
Do you hold any compliance certifications?
No. We are pre-launch and we are not going to claim otherwise. Our data handling practices are described on this page, and we are happy to walk any prospective design partner through them in detail. Certification is on the roadmap for when it is real.
What does the design partner programme involve?
A small number of teams who integrate early, get direct access to us, and shape what gets built. In exchange we want honest feedback and permission to learn from your onboarding flow. Commercial terms are deliberately open at this stage.
When can we integrate?
Join the waitlist and tell us your use case. We are onboarding design partners in sequence rather than opening a self-serve signup we cannot yet support properly.
§ 07 — Access
We are onboarding a small number of teams
Not a launch list. A short queue of teams who integrate early, get us on a direct line, and shape what gets built before the interface hardens.
- 01Direct access to the people building it, not a support desk
- 02Your onboarding flow shapes the interface
- 03Commercial terms deliberately open at this stage
- 04We tell you what does not work yet, every time