FAQ
Common questions
Concise answers to frequent questions about FinCheckers scope, setup, and operations.
- FAQ
- 1 min read
Is FinCheckers a credit decisioning engine?
No. FinCheckers standardises financial verification workflows and reviewable findings. Credit policy and final underwriting decisions remain with your institution.
Does FinCheckers replace document storage systems of record?
No. Document bytes are handled through your configured storage path; FinCheckers owns case state, findings, and review history.
Which verification types are available?
Types are tenant-configured. Common examples include income, employment, bank-statement analysis, and document verification. See Verification concepts.
Do all API responses include findings and review data?
No. Request include=findings,review,history on reads where that context is required.
How do I know which SDK version matches my tenant?
Align the SDK major with the API major published for your tenant. Review Release notes for the version you intend to run.
Where is the product scope described for non-engineers?
- Product page
- Product overview resource
- Getting started overview
Is there a checklist before production cutover?
Yes — Deployment checklist. Pair it with Implementation guide.
How do I get access or report an environment issue?
Use Contact. Include tenant id, environment name, case id, and the failing request id when available.