Rental Income Fraud Detection – the structural-PDF layer Snappt-style tools do not provide
Property managers and PropTech platforms screen rental applications under FCRA – every adverse action has to stand up to a denial dispute. Visual review and Snappt-style content-verification miss the structural fingerprint of a real pay stub edited in a PDF tool. A single API call surfaces those edits with named markers your team can cite in an adverse-action letter as part of your own FCRA-compliant process.
HTPBE? analyzes the structural layer of the PDF file – the layer that records every edit, even invisible ones. We don’t inspect holograms, phone photos, or ID biometrics. If your fraud problem is a digitally fabricated or edited income document, we’re the most specific tool for it.
Phone photos and scanned paper documents are outside scope – require digital PDF uploads for best results.
The problem
Why rental income fraud bypasses Snappt-style verifications
Snappt-style platforms verify the content of an income document – the employer name, the wage figure, the math – against expected patterns. A real pay stub from a real employer, opened in a PDF editor and re-saved with one figure changed, still passes content review: the formatting is right, the math reconciles after both gross and net are nudged. The structural fingerprint of the editing session lives in the file, not on the page.
Fabricated pay stubs and doctored bank statements are the two most common rental-income-fraud vectors. Eviction costs a property manager $3,500 or more on average – a number that dwarfs any lease payment the fraudulent tenant ever paid. Australian and UK applicants often attach payslips exported from Xero – see Xero payslip fraud detection.
Open-banking income vendors only work when the applicant connects the bank – the applicants who forged the pay stub rarely do. HTPBE? operates on the binary structure of the PDF the applicant actually uploaded, covering utility bills and employment letters as well as income documents – standalone, no bank-connect consent required.
Common proof-of-income fraud patterns
- Pay stub generated with an online pay-stub tool – no real employer behind it
- Running balance edited on a bank statement to show padded savings
- Legitimate utility bill with the name field replaced to establish residency
- Real pay stub opened in a PDF editor with the salary figure inflated
- Tax return modified to support a higher declared income
What this looks like
Document fraud in 2026 – three concrete patterns
Three real fraud mechanics we catch at the structural PDF layer.
Pay stub generated with an online pay-stub tool – no real employer behind it
Running balance edited on a bank statement to show padded savings
Legitimate utility bill with the name field replaced to establish residency
Real pay stub opened in a PDF editor with the salary figure inflated
Tax return modified to support a higher declared income
The detection gap
KYC platforms check the document. HTPBE? checks the file.
Two different checks – both matter.
KYC & identity platforms
Plaid · Persona · Alloy · Jumio
- Is this a real bank statement template?
- Does the account number match the identity?
- Is the document format consistent with the issuing bank?
Detects fake documents. Does not detect edited real documents.
HTPBE? tamper detection API
Structural PDF integrity
- Was this specific PDF file modified after it was generated?
- Does the file carry evidence of editing after export?
- Were digital signatures valid at the time of signing?
What HTPBE? checks
What the API detects in income documents
Five forensic layers analyzed on every request – results in under 3 seconds
Income documents judged on the file
However closely it copies an ADP, Workday or Paychex layout, a pay stub comes back MODIFIED when the file itself carries evidence of editing or fabrication, whatever tool produced it. INCONCLUSIVE means HTPBE? cannot confirm the file as an untouched original – a reason for manual review, not proof of fraud.
Character overlay on the original
Changing a figure on an existing pay stub leaves a structural trace. HTPBE? flags it without reading the page – it never looks at what the figures say.
Post-issuance edit detection
Editing a pay stub or bank statement after export leaves structural evidence behind. HTPBE? flags it as MODIFIED.
Values overlaid on a scan
Some forgers lay replacement values over a scanned document instead of editing the original. HTPBE? flags the overlay – a clean forensic signal that content was altered on top of an image.
Dates that disagree
When the dates recorded inside a pay stub disagree with each other, HTPBE? flags it – a direct tampering signal.
Share with engineering
Wire this into your intake pipeline in under a day
Two API calls – one POST to submit the PDF, one GET to retrieve the verdict. Forward this page to your engineering team; the full API reference, quotas, and copy-paste examples in cURL, JavaScript, Python, PHP, Go, and Ruby are one click away.
Pricing
Self-serve plans, no sales call
All plans include the same forensic checks. Pick the quota that matches your monthly document volume.
manualStarter
30 credits/mo
Manual spot-checks and integration testing
most commonGrowth
350 credits/mo
Active document processing pipelines
high volumePro
1,500 credits/mo
High-volume automation and API integrations
Enterprise (unlimited, on-premise available) — see full pricing
API key on signup. Free test environment on every plan. No card required.
Customer Stories
Teams that stopped document fraud
Compliance, finance, and risk teams use HTPBE? to catch manipulated PDFs before they become costly mistakes.
Caught an invoice where the total had been changed by less than a thousand dollars. Without this I would have approved it without a second look.
Sarah M.
AP Manager
United States
We had three applicants in the same week with bank statements that looked completely fine. Two of them were flagged as modified. You simply cannot see this by reading the document — it is in the file structure.
Lars V.
Risk Analyst, Online Lending
Netherlands
Salary slips were coming with altered figures. We identified two problematic files before the placement was finalised.
Priya K.
HR Operations Lead
India
Since we started checking documents this way, we stopped two applications early in the process that would have been very difficult to reverse later.
Julien R.
Fraud Analyst, Fintech
France
Some applicants were sending PDFs that looked authentic but had been edited in ways not visible to the eye. We now ask for checked originals when something is flagged. Already saved us from a few bad decisions.
Marta S.
Compliance Coordinator
Spain
One invoice was caught because there was a mismatch between the document dates and structure. That particular case would have cost us significantly.
Tariq A.
Finance Manager
United Arab Emirates
FAQ
Frequently asked questions
How does the API detect a fabricated pay stub?
Can it catch pay stubs from online generator tools?
modified when the file itself carries evidence of editing or fabrication, whatever tool produced it. An inconclusive result means HTPBE? cannot confirm the file as an untouched original – a reason for manual review, not proof of fraud. Checking with the employer is a sensible next step.What does ‘inconclusive’ mean for a pay stub?
inconclusive verdict means HTPBE? cannot confirm the pay stub as an untouched original. In the tenant screening context it is a reason for manual review, not proof of fraud.Can HTPBE? integrate with AppFolio, Yardi, RealPage, or Buildium?
Secure your workflow
Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.