Built for
Onboard the business, not just the person who signed up.
Assess a business and, where relevant, its owners, officials, permits, location and risk before onboarding.
What it does
Personal checks within a KYB workflow require applicable consent or authority and a defined purpose.
Business and directors in one request
Scope entity, ownership and official checks to the onboarding decision and the evidence available for the relevant jurisdiction.
KRA and compliance
Tax and permit information can be included where relevant sources or supporting records are available.
Premises confirmation
Where the onboarding standard requires it, a field assignment can gather physical evidence about premises or business operations.
Ongoing monitoring
Re-screening or monitoring may be configured where supported and appropriate to the relationship and service scope.
What this verifies
Evidence held together under one defensible record.
- Business registration and status
- Directors and ultimate beneficial ownership
- Director identity and liveness
- KRA PIN and tax compliance
- Premises and operations
- Sanctions, PEP and adverse media
How it works
- Step 01
Merchant request
The merchant provides business details and identifies relevant owners or officials. The purpose and authority for any personal checks are established.
- Step 02
Business verification
The agreed entity, ownership and tax checks are conducted against available sources or supporting documents.
- Step 03
Signatory identity
Where an individual is checked, the workflow makes the purpose, scope and applicable consent or authority explicit.
- Step 04
Enable and monitor
Return the findings and any unresolved items so the client can make its onboarding decision. Revalidation depends on configuration and source availability.
Results and exceptions
What you receive
Depending on the agreed scope, the verification record may include request status, check-level findings and available supporting evidence in a report or other decision-ready output.
When evidence needs attention
Mismatches, incomplete information or unavailable sources may require clarification or review. An unresolved item should be distinguished from a confirmed result.
Verification layers used
These are shared layers of DPAVerify, combined as the request and evidence require.
Datapoint Verify
Entity and personal checks scoped to the onboarding purpose and available evidence.
Learn moreDatapoint Field
Premises visit and operations confirmation where the merchant tier calls for it.
Learn moreDatapoint Intelligence
Review and monitoring options where supported and configured for the agreed scope.
Learn moreAccess and delivery
The available route depends on the solution, request scope and agreed operating model.
Related solutions
Pair this with another DPAVerify solution.
FAQ
DPAVerify Merchant: frequently asked questions
The agreed scope may include registration, ownership, officials, permits, risk screening and physical evidence. Availability depends on jurisdiction, source access and selected checks.
Yes. Personal checks may be included where relevant to the business decision, with purpose and applicable consent or authority established for the individual.
Re-screening or monitoring may be configured for supported sources and agreed intervals. Coverage and update behaviour depend on the service scope.
Timing depends on the checks requested, source responsiveness, information completeness and any field work required. Confirm the expected timeframe for the agreed scope.
Onboard a merchant
Approve the merchant before the money moves.
Describe your merchant onboarding decision and we'll help define the relevant checks and evidence.
