Employment verification in seconds, not days
The problem nobody wants to own
Every recruiter, landlord, and credit bureau in South Africa runs into the same wall. Before they approve a lease, a loan, or a role, they need to confirm that the applicant is actually employed — and roughly how much they earn. Today, that confirmation happens by phone. HR departments receive a steady stream of calls from people they do not know, asking for salary details about employees who may or may not have given consent. It is slow, it is inconsistent, and it is a POPIA grey zone nobody enjoys defending.
How FinVeil changes the flow
FinVeil already ingests payroll data for its core stress-scoring product. Once that data is in the system, minting an employment credential is almost free. The employer uploads payroll as usual. FinVeil mints a PAYROLL_CREDENTIAL and an EMPLOYMENT_VERIFICATION token, anchors them into the next Merkle batch on Stellar, and hands the employee a shareable link: finveil.io/verify/employment/<id>. When a recruiter, landlord, or credit bureau opens the link, they see confirmed employment data — employer, tenure, employment status, and a salary band — without ever seeing the exact salary and without ever calling HR.
Why this is POPIA-safe
Two design choices do the heavy lifting. First, the verifier never sees the exact salary — only a coarse salary band, which is enough for almost every real-world verification use case. Second, the employee is always the one who initiates the share. Consent is recorded, the link is revocable, and every view is audit-logged against the employer's tenant. HR stops being the gatekeeper for third-party queries, which is both faster and more defensible under POPIA.
The developer story
For verifiers that want to integrate directly, FinVeil exposes a single endpoint: POST /api/v1/verify/employment with a token id. The response is a small, stable JSON shape — valid, employeeName, employerName, tenure, salaryBand, employmentStatus, verifiedAt. Credit bureaus and payroll-integration partners can wire it into their existing KYC flows in an afternoon.
Where to go next
Employment verification is the first concrete, sellable use case sitting on top of FinVeil's tokenization primitive — but it is not the last. The same infrastructure already mints advances, vouchers, payroll receipts, expenses and invoices. If you want to see how the employment flow actually works end to end, the product page is the fastest way in: /products/finveil-token.