logo
Fortiro alternative

Looking for a Fortiro alternative? — Self-serve PDF fraud detection for AU lenders and proptech

Australian lenders, brokers, and proptech platforms know Fortiro as a local document fraud detection player covering Xero/MYOB payslip fraud, bank statement manipulation, and adjacent patterns. htpbe? solves the same core problem at the file layer — and ships it as a self-serve REST API with public pricing, free test keys, and same-day integration.

~3 sec
per document
35 checks
forensic layers
From $15
per month
1,500+
docs / month on Growth
Scope

htpbe? analyzes the structural layer of the PDF file — producer, xref, metadata, image streams, signature chain. We don't replace identity verification or income-source connections (Open Banking, Basiq). We catch the forged or edited PDF the applicant uploaded. Fortiro has its own approach and Australian customer base; this page describes how htpbe? fits a different deployment pattern (engineering teams shipping AU lending or proptech flows), not a feature-by-feature audit.

How it looks

One REST call, one deterministic verdict

Upload the PDF. The API returns INTACT, MODIFIED, or INCONCLUSIVE with named markers — in about three seconds.

What this looks like

Why AU lender and proptech teams evaluate htpbe? alongside Fortiro

Three real fraud mechanics we catch at the structural PDF layer.

01

Self-serve developer experience

Sign up, get an API key, ship the integration the same day. No sales call, no procurement process, no minimum contract. Test keys are free on every plan — your engineers prototype against deterministic test fixtures before any commercial decision.

02

Public, predictable pricing in USD

Plans from $15/mo (30 requests) to $499/mo (1,500 requests). Enterprise unlimited is a contract conversation. AU teams can budget the integration without local sales engagement.

03

AU-specific fraud patterns covered

Xero / MYOB payslip fraud, AU bank statement manipulation, fake superannuation statement detection, fake NDIS document detection, and right-to-work document fraud are core AU patterns with dedicated tech-page coverage. Producer signatures from Xero, MYOB, ANZ, CommBank, NAB, Westpac, MyGov / ATO are recognised.

How htpbe? is positioned

$15/mo
starter plan, 30 requests included — public pricing on /pricing
~3 sec
per PDF analyzed via API
No sales call
self-serve sign-up, API key in under a minute

When htpbe? makes sense (and when Fortiro might fit you better)

Want a developer API in USD? htpbe? Want a managed AU-local platform? Look at both.

Honest sizing: pick the tool whose deployment model and locale match yours.

htpbe? is built for engineering teams shipping AU lending and proptech flows that want a clean REST API with global infrastructure, public USD pricing, and same-day integration. If your team prefers a managed AU-local platform with operator UI and AU-based account management, Fortiro and similar players are positioned for that — a fair reason to evaluate them. Both serve real AU document fraud needs; the right answer depends on whether you want a primitive your engineers integrate or a managed product with local relationship management.

Results in under 3 seconds30 to 1,500+ documents/monthFrom $15/mo
How it works

Five forensic layers, one deterministic verdict

Every PDF we receive passes through the same structural pipeline — no model training, no thresholds to tune.

01

Metadata analysis

Creation and modification timestamps, producer and creator fields, XMP metadata — the first layer exposes basic tampering.

02

File structure

Xref tables, trailer chain, incremental updates. Any edit after export leaves a structural fingerprint here.

03

Digital signatures

Signature chain integrity and post-signature modifications produce deterministic markers. Certainty-level signal.

04

Content integrity

Fonts, objects, embedded content, page assembly. Multi-session edits and inserted objects are visible at this layer.

05

Verdict with markers

Deterministic output: INTACT / MODIFIED / INCONCLUSIVE, with named markers for every finding — suitable for audit trail.

Document types

PDFs we analyze for AU lending and proptech workflows

Every type listed below is analyzed at the structural file layer — not the rendered image.

Xero payslip PDFMYOB payslip PDFAU bank statement PDFSuperannuation statement PDFNDIS document PDFRight-to-work document PDFAU tax assessment notice PDF
What htpbe? checks

Detection capabilities

Deterministic structural signals. No probabilistic scores, no model training.

Producer signature analysis (AU-specific tools)

Authentic AU payslips come from payroll engines (Xero Payroll, MYOB AccountRight, KeyPay, Employment Hero). Bank statements come from ANZ, CommBank, NAB, Westpac, ING, Macquarie, Bendigo. Super statements from Australian Super, REST, HESTA, AustralianRetirementTrust. htpbe? recognises the producer signatures and flags desktop fabrications.

Incremental update detection

Edits to a real PDF leave incremental update markers in the xref chain. htpbe? flags these as MODIFIED at high confidence even when the visual layout looks pristine.

Balance arithmetic verification

Running balance is verified row-by-row across AU bank statements (previous balance + transaction = new balance). Edited transactions break the chain unless every dependent balance was also adjusted.

Digital signature chain validation

AU-government-issued PDFs (ATO Notice of Assessment, MyGov documents) often carry digital signatures. htpbe? validates the signature chain and flags invalidated or removed signatures.

Image-stream artefact detection

Lifted-and-pasted logos and headers from AU bank or employer sites leave compression artefacts that differ from authentic embedded content. The image-stream metadata exposes paste operations.

Cross-document fingerprint analysis

When multiple "different" employer letters or bank statements from a single AU applicant pool share fingerprints, the API surfaces the shared signatures — useful for catching synthetic-identity rings.

Integrate in minutes

A Fortiro alternative your engineers can ship today

Buyers can skip this section — developers, the integration is two HTTP calls.

Step 1 — submit the PDF

curl -X POST https://api.htpbe.tech/v1/analyze \
  -H "Authorization: Bearer $HTPBE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://your-storage/applicant-payslip.pdf"}'

Step 2 — read the verdict

{
  "id": "f1o2r3t4-5i6r-7o8a-9z0u-a1b2c3d4e5f6",
  "status": "modified",
  "modification_confidence": "high",
  "modification_markers": [
    "Two cross-reference tables — incremental update",
    "Modification date 9 days after creation date",
    "PDF editor producer detected"
  ],
  "producer": "Adobe Acrobat Pro",
  "creator": "Xero Payroll",
  "creation_date": 1707091200,
  "modification_date": 1707868800,
  "has_digital_signature": false,
  "xref_count": 2,
  "has_incremental_updates": true
}

Original came from Xero Payroll — institutional source. 9 days later it was opened in Adobe Acrobat Pro and re-saved, adding a second xref. Verdict: modified at high confidence. The applicant edited a real Xero payslip after issuance — likely to bump the salary figure for the AU lending or rental application.

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 verified 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

Yes. Xero and MYOB payslip fraud, AU bank statement manipulation, fake superannuation statement detection, fake NDIS document detection, and right-to-work document fraud all have dedicated tech-page coverage with AU-recognised producer signatures (Xero, MYOB, KeyPay, Employment Hero, ANZ, CommBank, NAB, Westpac, ATO, MyGov).
Plans start at $15/mo (30 requests) and go to $499/mo (1,500 requests) with public USD pricing on /pricing. Enterprise unlimited is a contract conversation. Fortiro pricing is on their site or via their sales team — transparent self-serve pricing is one of the deliberate differences in our positioning.
On-premise / private deployment is available on the Enterprise plan — see /api or contact us via /journalists for details. The default cloud deployment runs on global infrastructure; talk to us if your APRA / AU-data-residency requirements call for a region-locked deployment.
Yes. Sign up for the free tier — test API keys are included on every plan, including free. Run our test PDF fixtures through your integration without consuming live quota. No card on free tier.

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.