VerifyNow Standard KYC Bundle in South Africa

The VerifyNow Standard KYC Bundle combines South African identity photo verification with supporting identity and person-trace context. One result can include identity details, an ID photo where available, marital and deceased status, phone information, and physical or postal address fields where returned.

The bundle is available through the VerifyNow dashboard and API. The Standard KYC Bundle service page shows current access, pricing and included fields.

Standard KYC Bundle facts

What the bundle is designed to answer

The result helps a reviewer answer a focused onboarding question: do the returned identity fields and supporting context align with the South African person being onboarded?

It gathers related fields into one workflow so the reviewer can see the identity result and supporting context together. The organisation still decides which fields are relevant, what additional evidence is needed and how risk affects the customer relationship.

Information to prepare

Capture the South African ID number through an authorised onboarding channel. Associate the request with a customer or case reference that helps your team reconcile the result without placing unnecessary personal data in logs.

Give the person an appropriate privacy notice and record consent or another lawful basis for the checks included in the workflow. A service bundle should match the stated purpose. Remove fields from downstream use when they are unrelated to the decision.

How to review the combined result

Identity details

Start with the returned names, surname, date of birth and ID status. Compare them with the application and the person present in the approved onboarding journey.

ID photo

An ID photo may be returned where available. Use it as identity evidence within the workflow. A separate face-match or liveness service answers different questions when the onboarding design requires those controls.

Marital and deceased status

The combined result can include marital and deceased status where returned. Use each field for its stated purpose and read unavailable values literally. A marital-status category does not provide a marriage certificate, spouse identity or matrimonial-property regime.

Phone and address context

Phone, physical-address and postal-address data can help identify a difference that needs clarification. Source timing matters. Ask for current supporting evidence where current residence or contact control is required.

Suggested dashboard workflow

1. Confirm the onboarding purpose

Choose the bundle when its included fields fit the customer review. Record the lawful basis and internal case reference.

2. Submit the South African ID

Check all 13 digits before running the request. Correct an input error through the normal workflow instead of trying variations for the same person.

3. Review identity first

Confirm that the identity fields describe the intended person. Keep any mismatch visible while reviewing supporting context.

4. Assess field freshness and relevance

Read the returned status and source information. Decide whether a current source document or separate VerifyNow service is required for the specific risk.

5. Record the decision

Keep the transaction reference, evidence reviewed, exceptions and decision under the organisation's access and retention rules.

API integration guidance

Server-side API integrations should protect credentials, send a stable idempotency key for each business action and map every returned state explicitly. Keep unknown, unavailable, potential mismatch and completed states separate in the customer system.

Expose the full result only to users who need it. Operational screens can often show a review status and reference while a restricted evidence view holds the detailed personal information.

The VerifyNow API documentation contains the current request and response contract. The pricing page remains the source for current service cost.

Current VerifyNow service boundary

The Standard KYC Bundle supplies the listed identity verification and supporting trace fields where available. It does not certify that an organisation has completed every duty under the FIC Act, set a customer risk rating, establish source of funds or source of wealth, perform ongoing monitoring, make a legal decision, or guarantee that every returned contact field is current.

An accountable institution should apply its own risk management and compliance programme to decide which evidence, enhanced due diligence and monitoring steps are required. The Financial Intelligence Centre compliance material provides official South African guidance.

Standard KYC Bundle and Employee Bundle

The Standard KYC Bundle is aimed at customer identity and onboarding context. The Employee Bundle is framed for an authorised employee workflow and can include returned employer evidence as supporting context.

Choose the bundle whose purpose and fields match the case. A clear purpose reduces unnecessary personal-data collection and gives the reviewer a more useful result.

Standard KYC Bundle questions

Does the bundle complete FICA compliance?

The bundle supplies evidence for a customer file. The accountable institution applies its own controls, risk rating, due-diligence steps and ongoing obligations.

Is every supporting field current?

Availability and source timing vary by field. Review the returned labels and obtain current evidence when the decision requires it.

Does the bundle include face liveness?

Face Match and Passive Liveness are separate services. Add them when the approved onboarding design needs those controls.

Can I use the bundle through an API?

Yes, enabled accounts can use the API contract documented by VerifyNow. Keep the request and result inside an authorised server-side workflow.

Start a KYC bundle check

Visit the Standard KYC Bundle service page, then choose dashboard or API access for the authorised customer-onboarding process.