A fabricated pay stub qualifies a tenant who would fail a real income source-of-truth check — and your intake flow has no structural check on the file
Property managers and proptech platforms accept pay stubs and bank statements as income proof. Applicants fabricate them in Microsoft Word, or edit a real document to raise the salary figure, export to PDF, upload. The file looks right. OCR extracts the right numbers. No existing tool in most rental pipelines checks whether the PDF was issued by a real payroll engine or assembled on a desktop. HTPBE? provides that structural check — as a self-serve REST API your engineering team integrates in a day.
HTPBE? analyzes the structural layer of the PDF file — producer, xref, metadata, image streams. We don't replace identity proofing or income-source connections. We catch the forged or edited PDF the applicant uploaded. Snappt has its own approach and customer base; this page describes how HTPBE? fits a different buyer pattern (engineering teams shipping rental application flows), not a feature-by-feature audit of Snappt.
What this looks like
How rental income fraud gets through current intake flows
Three real fraud mechanics we catch at the structural PDF layer.
Pay stub edited to inflate gross pay
Applicant downloads a real ADP pay stub showing $3,400/month. They open it in any PDF editor, change the figure to $5,800, save. The xref chain shows a second cross-reference table — structural evidence of a post-issuance edit that visual review and OCR both miss. The inflated figure passes the income-to-rent ratio check.
Pay stub fabricated in Word using a real employer's template
No employer involved. The applicant creates a pay stub in Microsoft Word using the company logo from LinkedIn, types the desired salary, exports to PDF. The producer field shows Microsoft Word — not ADP, Paychex, Gusto, or Workday. Real employer pay stubs always carry the payroll engine's producer signature.
Bank statement with edited balances
Applicant downloads a Chase Online Banking statement showing a $1,200 balance. They open it in any PDF editor, add fictitious direct deposits, raise the balance to $8,400, re-export. The running balance arithmetic breaks at the inserted transaction — structural evidence the file was tampered with after the bank issued it.
How HTPBE? is positioned
Why the current rental intake flow misses this
OCR reads the income figure. It does not read whether the file carrying it came from a real payroll engine.
The structural layer is the gap most proptech stacks do not yet close.
OCR-based income extraction (AWS Textract, Google Document AI, FormFree, Plaid Income) reads what is printed on the document — it cannot detect that the underlying PDF was created in Word or edited after the payroll engine issued it. Identity proofing (Persona, Onfido, Alloy) confirms who the applicant is — it does not inspect the PDF the applicant uploaded for structural fraud. Manual review by a leasing agent reads the document visually — it cannot see the second xref table or the producer-field mismatch. HTPBE? closes this specific gap: it reads the structural layer of every submitted PDF and flags fabricated or edited documents before they influence a rental decision.
Document types
PDFs we analyze for proptech and rental application flows
Every type listed below is analyzed at the structural file layer — not the rendered image.
What HTPBE? checks
Detection capabilities
Deterministic structural signals. No probabilistic scores, no model training.
Producer signature analysis
Authentic pay stubs, bank statements, and employer letters carry institutional producer signatures (payroll engines, banking systems, HRMS). When the producer field shows Microsoft Word, LibreOffice, or a generator-tool fingerprint, the document was authored on a desktop — flagged accordingly.
Incremental update detection
Edits to a real PDF (changed amounts, dates, names) leave incremental update markers in the xref chain. HTPBE? flags these as MODIFIED at high confidence even when the visual layout looks pristine.
Digital signature chain validation
Many large employers and banks digitally sign their PDFs. HTPBE? validates the signature chain and flags invalidated or removed signatures — a core indicator of post-issuance tampering.
Image-stream artefact detection
Lifted-and-pasted logos, signatures, and headers leave compression and object-structure artefacts that differ from authentic embedded content. The image-stream metadata exposes paste operations.
Cross-document fingerprint analysis
When multiple "different" employer letters from the same applicant pool share font subset prefixes, image hashes, or producer signatures, the API surfaces the shared fingerprints — useful for catching collusion or rental-fraud rings.
Single-session creation pattern
Applicant-fabricated PDFs are typically produced in one shot — CreationDate equals ModDate, single xref, no incremental update history. Real institutional production systems often carry richer history.
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
$15/mo
30 checks/mo
Manual spot-checks and integration testing
most commonGrowth
$149/mo
350 checks/mo
Active document processing pipelines
high volumePro
$499/mo
1,500 checks/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
Is HTPBE? a direct feature replacement for Snappt?
How do you compare on price?
Does HTPBE? catch the same document types as Snappt?
Can we evaluate before committing?
Secure your workflow
Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.