Legal
Verification Access Terms
Terms for third parties who verify payroll receipts or employment data via FinVeil.
Last updated: 16 April 2026
1. Who these terms apply to
These terms apply to any person or organisation (“Verifier”) that uses FinVeil's verification endpoints or portal to confirm the authenticity of payroll receipts, employment data, or other tokenised records issued through the FinVeil platform.
2. Verification purpose
FinVeil's verification service confirms that a specific record was issued through the FinVeil platform at the stated time. Verification responses are limited to confirming authenticity and basic metadata. They do not constitute financial advice, credit assessments, or employment references.
3. Data minimality
Verification responses are designed to return the minimum information necessary to confirm authenticity of a transaction receipt (payment proof). Verifiers will receive only the data fields relevant to the verification request — typically the transaction identifier, amount, timestamp, and merkle anchor. FinVeil does not disclose full payroll records, stress scores, counterparty identifiers, or other sensitive data through the verification service.
4. Prohibited re-sharing
Verifiers must not:
- Share, sell, or distribute verification results to any third party
- Use verification results for purposes other than the specific transaction for which verification was requested
- Aggregate verification data across multiple employees or employers to build profiles, databases, or datasets
- Cache or store verification results beyond the period necessary for the immediate transaction (maximum 30 days)
- Use verification results for marketing, profiling, or any form of unsolicited contact with the data subject
5. Permissible verification purposes
Verification may be used for:
- Confirming payroll receipt authenticity for lending or credit decisions
- Employment verification for rental applications or background checks
- Confirming the validity of tokenised receipts presented by the data subject
- Regulatory or compliance checks where the data subject has provided consent
6. Consent requirements
Verifiers must have obtained consent from the data subject (employee) or have another lawful basis under POPIA before requesting verification. FinVeil may require proof of consent before processing verification requests. Verification requests without valid consent may be declined.
7. Rate limits and access
Verification requests are subject to rate limits. Bulk or automated verification requires prior written agreement with FinVeil. Abuse of the verification service, including excessive requests or attempts to enumerate records, will result in immediate suspension.
8. Liability
Verification responses confirm that a record exists in the FinVeil system as stated. FinVeil does not warrant the accuracy of the underlying data provided by the employer. Verifiers rely on verification results at their own risk. FinVeil's liability is limited to re-performing the verification at no charge.
9. Audit and compliance
All verification requests are logged in FinVeil's audit trail. FinVeil reserves the right to audit Verifier usage and to suspend access if these terms are breached. Verifiers must cooperate with any audit requests within 14 business days.
10. Governing law
These terms are governed by the laws of the Republic of South Africa, including the Protection of Personal Information Act (POPIA). Any dispute shall be referred to the courts of the Gauteng Division of the High Court, Pretoria.
These terms should be read alongside the Privacy Policy.