use case

Borrower onboarding checks for digital lending

Check who is applying, where the money will go and what their statements say, through one integration instead of several.

the problem

What teams deal with

Applicants drop off when each check adds another wait or another screen.
Every provider returns results in its own format, so policies end up written around integrations.
Underwriters need to see why a check came back the way it did, not just a yes or no.

a typical flow

Each step is a separate API with the same request and response design. Your policy decides which steps a product needs.

apis

PAN verification API
Check that a PAN exists and is active, and see the permitted details on record, with the source and time of every field.
PAN name and date-of-birth match API
Compare the name and date of birth an applicant entered with the permitted PAN details, field by field, with a reason for every outcome.
Face match and liveness API
Compare a selfie with the photo on an identity document, and check a capture for signs of a presentation attack, as two separate results.
Bank account verification API
Check that a bank account exists and can receive funds, and compare the account holder’s name with the name you were given.
Account holder name match API
Compare the verified name on a bank account with your borrower’s name, handling initials, order and spelling variations.
Bank statement analysis API
Turn bank statement data into income, balance, obligation and repayment-capacity measures, each traceable to the transactions behind it.
Bank statement fraud detection API
Flag edits and internal inconsistencies in an uploaded bank statement, with the page, severity and confidence of each indicator.
Document tampering detection API
Flag signs that an ID or supporting document was edited, with the affected region, severity and confidence for each indicator.

good to know

Your KYC obligations remain yours. Koshio supplies checks and the evidence behind them; your policies decide what happens next.
Each result keeps its source and as-of time, so a credit file can show what was checked and when.

questions

Do I have to use every check in the flow?

No. Each API stands on its own; the flow shows a common order, and your policy decides which checks a product needs.

Tell us what your flow looks like today, and we'll show you how the checks fit into it.