Payment fraud in Nigerian residential tenancy most commonly takes two forms: a tenant submitting the same bank alert twice to cover two separate rent charges, and a tenant submitting a fabricated or altered bank alert that was never generated by a real transaction. Both forms of fraud are designed to be caught only after the agent has already confirmed the payment — by which point recovery is difficult and landlord trust is damaged. Leja’s fraud detection runs automatically on every payment submission and flags these patterns before you confirm anything. You see the alert, review the evidence, and decide how to proceed. Nothing is blocked automatically without your knowledge.Documentation Index
Fetch the complete documentation index at: https://internal.relvor.org/llms.txt
Use this file to discover all available pages before exploring further.
Fraud detection alerts require a Business subscription or above. See Pricing for the full tier breakdown.
The two detection types
Duplicate payment detection
When a bank alert is submitted for a payment confirmation — either through AI-assisted extraction or attached as a reference — Leja checks it against all previously confirmed payments across your organisation. If the same alert appears to have already been used to record a confirmed payment, a duplicate flag is raised. This protects against a tenant submitting one real transaction as proof of payment for two separate rent charges — or against two tenants in separate units submitting the same fabricated alert. The flag shows you:- The original payment it matches (date, amount, receipt number)
- The submission that triggered the flag
- A confidence score indicating how closely the two alerts match
- The specific signals that triggered the match (reference number match, amount and date combination, image hash similarity)
Document fabrication detection
For bank alert screenshots submitted to AI extraction, Leja cross-checks the image against known patterns for authentic bank notifications from Nigerian banks. Fabricated or altered alerts frequently show visual inconsistencies — font irregularities, altered transaction amounts, timestamp formatting that does not match the bank’s actual notification format. When fabrication signals are detected, a flag is raised with a confidence score and a description of the specific signals found. You are shown what the AI found unusual about the document so you can make an informed decision about whether to investigate further.What you see when a flag is raised
A fraud alert appears in your intelligence feed and is attached to the pending payment submission. The alert includes:| Element | Description |
|---|---|
| Flag type | Duplicate submission or document fabrication |
| Confidence score | How certain the detection is (0–100%) |
| Triggered signals | The specific indicators that caused the flag |
| Related records | Linked previous payments or matching submissions |
| Recommended action | Investigate or proceed with caution |
What you decide
When a fraud flag is raised, you have three options:- Investigate — place the payment on hold and contact the tenant or their bank to verify the transaction before confirming
- Proceed — if you have investigated and are satisfied the flag is a false positive, you can confirm the payment with the flag noted on the record
- Discard — reject the payment submission without confirming, leaving the rent charge as outstanding
Privacy — flags are private to your organisation
Fraud flags are internal to your organisation in Leja Professional. When a flag is raised:- The tenant is not automatically notified
- The flag does not appear on the tenant’s profile visible to other agents or landlords
- The flag is only visible to your organisation within Leja Professional
Fraud flags that are confirmed as fraudulent after your investigation can be escalated through your organisation’s records in Leja. This creates a documented trail useful for any subsequent legal process, but escalation is always initiated by you.