Straight answers on data, consent, pricing and onboarding.

Credfex is an employment credential exchange. Employers issue verifiable records of employment (tenure, designation, exit status and more), professionals hold those records in a personal wallet, and authorised verifiers such as background screening agencies and hiring teams confirm them instantly, with the professional's consent.

A traditional check relies on emails and phone calls to a former employer, which can take days and depends on who picks up. Credfex verifies against a record the employer itself issued and digitally signed, so the answer is instant, tamper-evident and fully auditable.

The employer remains the issuer of record and can correct or revoke what it has issued. The professional controls who is allowed to view a credential. Credfex acts as a processor and never sells or shares data with third parties beyond an authorised verification.

Nothing. Issuing credentials on Credfex is free for employers, regardless of headcount. We earn from verifiers who pay per confirmed verification.

Three ways: a secure REST API that plugs into your HRMS or payroll system, bulk Excel or CSV uploads from the employer portal, or one-by-one issuance from the portal itself. Most teams start with bulk upload and move to API once the process is bedded in.

Yes. Many employers issue an employment credential at the time of joining and update it on exit so the record is always current.

Authorised users in your organisation can amend or revoke a credential from the portal at any time. Every change is versioned and shows in the audit trail, and the professional is notified.

When the record exists on Credfex the response is returned automatically through the portal or API. If a record is not yet on the exchange we tell you immediately so you can fall back to your existing process without losing time.

Yes. Every verification is tied to an explicit consent from the professional, captured either through Credfex or passed through from your own onboarding flow. The consent reference is stored alongside the verification report.

The employer-issued fields (organisation, employee ID, designation, dates of employment, exit type and eligibility for rehire where the employer chooses to share it), the issuer signature, timestamp, consent reference and a unique report ID you can cite in your own reports.

Yes. The verification API is designed for screening platforms and ATS integrations, with sandbox keys, webhooks for asynchronous results and per-client billing.

Yes. Holding, viewing and sharing your credentials is free, always.

Yes. Consent is granular and revocable. You can approve a single verifier, set a time limit or withdraw consent at any point from your wallet.

You can raise a dispute directly from the credential. The employer is notified, the credential is flagged as under review to any verifier, and you are kept informed until it is resolved.

No. Pay-as-you-go accounts are billed per successful verification with no monthly minimum. Enterprise agreements add volume pricing, SSO and dedicated support.

Employers can be live within a day using bulk upload. API integrations typically take one to two sprints depending on your HRMS. Verifiers get portal access immediately after KYC.

Yes. Every integration account includes a sandbox environment with synthetic data so you can build and test without touching production records.