Loan origination

Income evidence you can act on at origination

Doctored payslips and fabricated bank statements are trivial to produce and hard to catch by eye. Seal income and identity evidence at the moment it is captured, and the question stops being whether the document looks right.

The problem

A PDF is not evidence of anything

THE GAP

Documents are trivially editable

A payslip is a PDF. Changing a number takes seconds and leaves no visible trace. Screenshots of banking apps are worse: they carry no provenance at all and are indistinguishable from a mock-up.

THE COST

It clears serviceability

Fabricated income does not fail at the document check. It fails eighteen months later as an arrears case, by which time the loan is on book and the loss is real.

THE BIND

Manual review does not scale

Reading every document by eye is expensive, slow, and no better than chance against a competent forgery. Speed and diligence pull against each other.

How CapSeal applies

Move the trust decision to the moment of capture

CAPTURE

Seal at the source

The borrower photographs the payslip or ID through your app. CapSeal measures whether a real lens saw a real document - parallax against device motion, depth relief, screen-replay detection - and binds the result into the file.

VERIFY

One call at intake

Your origination system posts the file and receives a verdict with a basis. Sealed captures come back proven; anything else comes back with the evidence you would need to decide.

ROUTE

Automate only what is settled

Proven and declared results route automatically. Everything else goes to a human with the full report attached, so the reviewer starts informed rather than cold.

Inside your workflow

Where CapSeal sits in the loan lifecycle

CapSeal does not replace your origination process - it adds two touchpoints to the one you already run. Documents are sealed at upload, a verdict attaches at assessment, and each file routes down one of three paths. Every outcome lands back in your LOS with the proof stored on the loan file.

YOUR PROCESS • STAGE 1 Application submitted Borrower uploads income, ID and statements in your origination flow CAPSEAL: documents sealed at upload YOUR PROCESS • STAGE 2 Docs & underwriting File assessed in your LOS or origination platform as normal CAPSEAL: verdict attached to file ATTESTED-GENUINE Fast-track Straight to approval - days off time-to-yes UNVERIFIED Normal doc review Your existing checks, unchanged. Never auto-declined. TAMPERED / SYNTHETIC Held for fraud team Funding stopped; fraud team gets the file with proof attached YOUR PROCESS • STAGE 3 Funding & audit Every outcome lands back in your origination system. The proof object is stored with the loan file - replayable for responsible-lending audit, dispute or regulator review, years later, without calling CapSeal. INTEGRATION FOOTPRINT Runs beside your LOS and broker portals - an SDK at document upload and one API call at assessment. No origination-platform migration. Paper and branch applications simply route as unverified.

Note the middle path. Paper and branch applications route to your normal document review exactly as they do today - never auto-declined, and no borrower is worse off for not having used the app.

What this does not do

Where the evidence stops

CapSeal establishes that a document was captured by a real camera pointed at a real thing, and has not changed since.

  • It does not tell you whether the numbers on a genuine payslip are true. A real photograph of a real document that says the wrong thing is still a real photograph.
  • It does not verify the employer exists, or that the account belongs to the applicant.
  • For a PDF emailed in from elsewhere, it reads what provenance the file carries and reports honestly when that is nothing.

The full position is in the Product Disclosure. We would rather you knew the boundary before you bought than after.

Industry brief

The lending numbers, with every input cited

A bottom-up model of fabricated-document exposure for a digital lender writing 40,000 applications a year, built on published research from Point Predictive and industry survey data. Six pages, every assumption on the page.

$12.9M
fraud loss avoided per year, base case
1 in 10
paystubs supplied to US lenders is fabricated
$9.2B
US auto-lending fraud exposure, 43% income and employment
5x
growth in AI-generated document fraud in a single year

The honest boundary, stated in the brief itself: the model covers fabricated-income and identity documents, the category capture-time provenance directly prevents, and uses a 3% fabrication rate well below the published 1-in-10 paystub figure. It does not claim staged-borrower rings, genuine documents describing an untrue situation, or fraud that never touches a document. The figures are modelled from published ranges, not results from a named lender.

Lending brief (PDF)
Integration

Three things to wire up

  1. Capture Drop the iOS or Android SDK into the flow your users already complete. Our capture-integrity engine measures the scene on the device and seals the result before it leaves the handset.
  2. Verify One authenticated call at intake returns a verdict, a basis and a proof object. See the SDK.
  3. Route Automate on proven and declared. Send everything else to a human with the report attached.

Try the verification half right now, with no signup, at capseal.ai/check.

Stop paying for forgeries you could have caught at intake.

A pilot takes one line of your origination flow and one API call.

Book a pilot Check a file first Lending brief (PDF) The lender case, in full