Choose a service
Open a connected service from the dashboard. The service label, input type and portal-credit charge are shown before submission.
01 · User guide
From workspace to report
SmartVerify gives client users a controlled workspace for identity, background, property, business and vehicle checks. Admins provision accounts and manage credits; clients submit and review their own authorised work.
Confirm the purpose
Enter a specific lawful purpose, confirm authority, approve the displayed charge and add biometric consent when an ID photograph is requested.
Review the outcome
Use Verification history and the report view. A provider result is evidence to assess—not an automatic fraud-clearance, hiring or credit decision.
Statuses you will see
- Completed
- Provider response was received and normalised.
- Manual review
- Outcome is unknown, incomplete or needs human assessment. Do not retry.
- Pending
- Submitted or awaiting provider confirmation.
Report and history
History shows date, service, masked input, status, credits and result language. Reports include the provider source, a confidential-data notice and the recorded lawful purpose. Keep access restricted to authorised users.
Understand the lifecycle →02 · Service matrix
What is connected today
These are the current API-connected dashboard services. Names below follow the client portal. Portal credits are configured per release and are not a promise of permanent supplier pricing.
| Portal service | Code | Category | State |
|---|---|---|---|
| ID + Photo (Real-Time) | identity_check | Identity | API connected |
| SA ID (Basic) | said_verification | Identity | API connected |
| Refugee / Asylum ID | refugee_verification | Identity | API connected |
| Employee Bundle | employee_bundle | Bundles | API connected |
| Standard KYC Bundle | kyc_bundle | Bundles | API connected |
| Address Lookup | address_lookup | Background | API connected |
| Consumer/Person Trace | consumer_trace | Background | API connected |
| Trace by Phone | phone_trace | Background | API connected |
| Property Search by ID | property_search | Property | API connected |
| Marital Status (Real-Time) | marital_status | Identity | API connected |
| Alive/Deceased Status (Real-Time) | alive_status | Identity | API connected |
| AML/PEP/Sanctions | aml_screening | AML/PEP | API connected |
| CIPC Company Verification | cipc_company | CIPC | API connected |
| CIPC Director Search | cipc_director | CIPC | API connected |
| Vehicle Check | vehicle_check | Vehicle | API connected |
Gated / upload-dependent
⌁Future dashboard services
Face Match · Age Estimate · Passive Liveness · Document Authenticate · Smart ID Card Scanner · Driver’s Licence Barcode Verification · Vehicle Licence Disc Scanner · Africa ID Verification
03 · SmartVerify API
Build on the portal abstraction
Your integration targets SmartVerify—not the supplier directly. The portal owns authentication, validation, consent evidence, credit reservation, idempotency and report normalisation.
POST
/api/v1/verificationsBearer token · client scopeCreate a verification request. The endpoint is authenticated and may reserve portal credits before the provider completes.
{
"service_code": "said_verification",
"subject": "8001015009087",
"idempotency_key": "onboarding-2026-0001",
"purpose": "Employee onboarding for ACME (case 8421)",
"authority_confirmed": true,
"charge_approved": true
}Requiredservice_code, subject, idempotency_key, purpose, authority_confirmed, charge_approved
Conditionalbiometric_consent is required for
identity_check only.Replay safeReuse the same idempotency key to retrieve the existing request. Do not create a new key after an uncertain provider result.
GET
/api/v1/walletCurrent client credit balanceGET
/api/v1/verificationsAuthenticated verification historyGET
/api/v1/verifications/{id}One normalised reportPOST
/api/v1/loginIssue an API session/token (rate limited)Response semantics
201New request completed or normalised.
202
manual_review: provider outcome is uncertain; credits remain reserved and support should review.200Idempotent replay of an existing request.
422 / 401 / 503Validation, authentication or provider availability failure. A rejected validation is documented as no provider request sent.
04 · Provider contract
SmartVerify ↔ VerifyNow
The upstream contract is documented by VerifyNow. The table below records the fixed integration mapping; it is not an instruction to call paid endpoints from a browser or test environment.
| SmartVerify service | VerifyNow route | Provider payload selector |
|---|---|---|
| ID + Photo (Real-Time) | POST /verify | reportType=home_affairs_id_photo |
| SA ID (Basic) | POST /verify | reportType=said_verification |
| Refugee / Asylum ID | POST /refugee-verification | refugeeFileNumber |
| AML/PEP/Sanctions | POST /aml-screening | name, entity, country, dataset |
| Consumer/Person Trace | POST /consumer-trace-lite | idNumber |
| Address Lookup | POST /address-lookup | idNumber |
| Property Search | POST /property-search | idNumber |
| CIPC checks | POST /cipc | registration/report type |
| Vehicle Check | POST /vehicle-check | registrationNumber, optional VIN |
| Phone Lookup | POST /verify | reportType=contact_enquiry, contact number |
| Marital / Alive Status | POST /verify | documented real-time report type |
Never put the VerifyNow credential in frontend code.
SmartVerify sends upstream requests server-to-server. API keys, bearer tokens, provider references and raw payloads are confidential and are deliberately absent from this site.
05 · Safeguards
Responsible use is part of the API
POPIA & purpose limitation
State why the lookup is needed, minimise the data submitted, restrict report access and retain evidence of authority.
Consent & authority
Confirm consent or another lawful authority. ID-photo checks additionally require explicit biometric consent.
Credit & idempotency
A no-record result may still be chargeable. Use one idempotency key per lookup and wait for support on timeout.
Human decisions
Manual review is not a positive or negative identity decision. Do not use a report as the sole basis for employment, credit or access decisions.
Safe testing rule
This documentation was verified without making paid VerifyNow requests. Use fixtures, validation failures and mocks for integration tests. Never place real ID numbers, names or provider credentials in examples, logs or client-side code.
06 · Sources
Authoritative references
Terminology is aligned to the SmartVerify client portal and the upstream provider documentation. For current transport details, consult:
- VerifyNow API Documentation ↗
- SmartVerify Client Portal ↗ (authenticated workspace)
Documentation build: 2026-09 · SmartVerify portal cache version v=51. Service availability and provider contracts can change; the portal response and release notes are authoritative.