VerifyNow guide
What Is VerifyNow Credit Score Check? South Africa
Clear guidance on VerifyNow, credit-score requests, identity verification, POPIA consent, and when external credit bureau data may be needed.

What Is VerifyNow Credit Score Check? South Africa
People sometimes search for "VerifyNow credit score check" when they are really trying to answer a broader risk question: can I trust this customer, verify their identity, prevent fraud, and keep a clear compliance record?
The important distinction is this: VerifyNow is an identity verification and risk-workflow platform. VerifyNow does not operate as a consumer credit bureau and does not maintain its own consumer credit profiles. Where a business has a lawful and necessary reason to use credit bureau information, that data must come from an approved third-party credit information provider or registered credit bureau, with the correct purpose, consent, and controls.
For many onboarding journeys, a credit score is not the first or most useful check. The safer starting point is to verify the person, confirm the risk signals that matter, and only layer credit bureau data where the product or decision genuinely requires it.
Why this distinction matters
Credit data is sensitive. Using it when you do not need it can create POPIA, customer-trust, and operational risk. A business should not treat a credit score as a general trust shortcut for every onboarding decision.
Ask these questions first:
- Do we need to verify identity, or do we need to assess creditworthiness?
- Is this a fraud-prevention or KYC workflow?
- Are we making a lending, affordability, rental, payment-terms, or credit-risk decision?
- Do we have a lawful basis and clear customer notice?
- Are we using an approved external credit-data source where credit data is actually required?
If the goal is ordinary account onboarding, seller verification, payout protection, or fraud prevention, identity verification and related risk checks may be the correct first step.
What VerifyNow helps with
VerifyNow helps South African businesses build verification workflows around identity, fraud prevention, and compliance evidence.
Typical checks include:
- South African ID verification
- Face match or liveness where the user must be linked to the account
- Document authentication where the document itself needs review
- Bank account verification for payout or account-ownership workflows
- AML, PEP, and sanctions screening
- Company and director verification for business customers
- Consumer trace or phone trace where lawful and relevant to the use case
- Audit references that show what was checked and when
This stack is useful for onboarding, risk review, compliance operations, and fraud prevention. It is not the same thing as issuing a consumer credit report.
When external credit bureau data may be relevant
Credit bureau data may be relevant where the business is making a decision that actually depends on credit risk or affordability. Examples include:
- Lending or credit-provider decisions
- Buy-now-pay-later or instalment products
- Rental, leasing, or payment-term approvals
- High-value goods released before payment
- Internal affordability or repayment-risk workflows
In those cases, the credit bureau component should be sourced from an approved provider under the appropriate legal basis. VerifyNow can still sit alongside that process by verifying the identity first and helping the business keep a defensible audit trail.
Credit checks versus identity verification
| Question | Better starting point |
|---|---|
| Is this person who they claim to be? | Identity verification |
| Is the bank account controlled by the customer? | Bank account verification |
| Is this customer a PEP or sanctions risk? | AML/PEP screening |
| Is this company active and who are its directors? | Company verification |
| Can this person afford credit or repay a loan? | External credit bureau or affordability process |
| Is this a general fraud-prevention onboarding flow? | Identity verification plus risk-based checks |
The safest workflows often combine checks, but each check should have a clear purpose.
POPIA and consent considerations
Whether you are verifying identity or using credit bureau data, you should be able to explain why the check is needed and what will happen to the data.
A safer process includes:
- A clear customer notice
- Consent or another lawful processing basis where applicable
- Minimal collection of personal information
- Role-based access to sensitive results
- Secure storage
- Retention limits
- A record of the decision made from the result
For credit-related data, the purpose should be especially specific. Do not ask for a credit report if your real need is simply to confirm identity or prevent account fraud.
How to decide what your business needs
Use the risk and decision type to choose the right workflow.
Use identity verification when:
- A new customer is creating an account
- You need to reduce impersonation risk
- A marketplace seller, contractor, or supplier is being onboarded
- You need a FICA-aligned identity evidence trail
- You need to connect a person to a profile, transaction, or account
Add bank account verification when:
- You are paying funds out
- The customer changes bank details
- Debit order or account ownership risk matters
- A supplier, seller, or partner account needs payout protection
Add external credit bureau data only when:
- The decision is genuinely credit, affordability, repayment, or payment-risk related
- The customer has been given the right notice
- You have the correct legal basis and provider relationship
- Your internal policy explains how the result is used
This keeps the business from over-collecting data while still protecting high-risk decisions.
Example workflows
Marketplace seller onboarding
Start with identity verification, company verification where the seller is a business, bank account verification for payouts, and AML/PEP screening for higher-risk sellers. If the marketplace offers credit or instalments, external credit bureau data may be layered separately.
See marketplace verification workflows for a fuller example.
General customer onboarding
Start with ID verification and fraud-prevention checks. Only add credit bureau data if the customer is applying for credit terms, deferred payment, lending, or another product where creditworthiness is part of the decision.
Business onboarding
Use company and director verification, representative identity checks, AML/PEP screening where required, and bank account verification where payments are involved.
FAQ
Is VerifyNow a credit bureau?
No. VerifyNow is not a consumer credit bureau and does not maintain its own consumer credit profiles.
Can VerifyNow help with credit-risk workflows?
VerifyNow can support the identity, consent, fraud-prevention, and audit-trail parts of a credit-risk workflow. Where actual credit bureau data is needed, it should come from an approved third-party credit information provider or registered credit bureau.
Do I need a credit score for FICA?
Not usually. FICA customer due diligence focuses on identifying and verifying customers, understanding risk, keeping records, and applying risk-based controls. A credit score is not a universal FICA requirement.
Is identity verification enough for lending?
No. Lending or affordability decisions may need additional checks, including external credit bureau data, affordability assessment, and the business's own credit policy. Identity verification is still an important first layer because it helps confirm who the applicant is.
Start with the right check
If your team is asking for a "credit score check," pause and identify the real decision. If the decision is identity, fraud prevention, payout protection, or KYC, start with VerifyNow's verification stack. If the decision is lending or affordability, layer approved credit bureau data alongside identity verification under the right controls.
Explore VerifyNow KYC workflows