Failed applications in the queue
Ops teams spend hours on applications that never could have passed checksum rules. A first-pass structural check keeps reviewers focused on genuine exceptions.
Fintech & financial services
Reject mistyped or checksum-invalid ID numbers before they clog onboarding, lending intake, or accounting client files. CheckID is a hygiene layer — not a Home Affairs lookup and not a complete FICA/KYC product.
Ops teams spend hours on applications that never could have passed checksum rules. A first-pass structural check keeps reviewers focused on genuine exceptions.
Document-verification and screening vendors still charge when the ID number itself is structurally invalid. Filter those out before you pay for a fuller check.
Logging “ID captured” when the number fails Luhn creates messy case files. Record a structural pass/fail first, then run your accountable-institution steps.
Structural ID validation helps catch invalid identity numbers before your formal customer-identification and verification steps. CheckID does not replace Home Affairs verification or a full FICA/KYC solution.
Fintech and lending platforms can call the single-ID endpoint as soon as the applicant types the number. Block submit when isValid is false.
Wire it from the South African ID validation API. API Starter is for single calls; bulk backfills need Professional.
Practices that collect client IDs for SARS or CIPC filings can spot-check with the free web checker, then graduate to API when volume grows.
Compare plans on CheckID pricing for API and bulk plans.
Collect the ID number because you need it for onboarding or a lawful FICA step — not because a form template inherited extra fields. A structural check does not require storing a scanned ID book on a third-party server.
We process in memory and discard the number. Your CRM, loan origination system, or practice file still needs a retention policy. See POPIA and ID number handling.
Wallet, payments, and lending apps can fail-fast on invalid IDs before the applicant reaches document upload.
Keep origination queues clean so credit analysts are not reviewing files with impossible birth dates.
Validate client IDs when opening a new engagement file, then keep your own records — CheckID does not store them.
Call the single-ID endpoint from your application service before you create a customer record or hand the file to a KYC vendor.
# Onboarding API: reject checksum-invalid IDs before KYC
curl -s "https://api.checkid.co.za/api/v1/validate/8001015009087" \
-H "Authorization: Bearer YOUR_API_KEY"8001015009087 is the public sample ID used across CheckID docs — not a live customer number. Replace YOUR_API_KEY with a key from your dashboard. See the South African ID validation API and 5-minute South African ID validation API tutorial.
Free checker for analysts doing spot reviews. API Starter from R99/month for live application calls. Professional for bulk backfills and team access. Full comparison: CheckID pricing for API and bulk plans.
Connect the checker, API, bulk jobs, and POPIA notes without repeating a generic trust template.
No. Structural ID validation helps catch invalid identity numbers before your formal customer-identification and verification steps. CheckID does not replace Home Affairs verification or a full FICA/KYC solution.
No. Numbers are processed in memory and discarded after the response. Retention in your onboarding system remains your organisation’s decision.
Professional includes bulk API and web bulk validation for backfills and nightly imports. API Starter (R99/month) is limited to single production calls.
That the 13-digit number passes format, date encoding, citizenship digit, and Luhn checksum rules. It does not prove the applicant is the lawful holder of that number.
Check one number free, then automate the same structural step in your onboarding API.