Skip to main content

​
PIN Management in Leja Professional

​
How agents and landlords manage Property Identification Numbers (PINs)

​
Creating a PIN (Property Identification Number)

Who initiates: Agent on behalf of owner, or owner directly. Owner must confirm. PIN is issued linked to the owner’s personal RIN. Required at creation:
  1. Owner must have NIN_VERIFIED personal RIN (minimum for all property types)
  2. Ownership document uploaded (C of O, deed, governor’s consent, etc.)
  3. Property address with LGA and state (required)
  4. Property type (residential, commercial, mixed-use)
If agent initiates on behalf of owner:
  • Agent’s personal RIN is attached as the listing agent node
  • Agent’s org BRN is attached if agent is org staff (null for solo agents)
  • A PropertyListingEvent record is created: LISTED
At creation, Leja:
  • Leja Professional the document hash (witnesses the ownership claim)
  • Geocodes the address (existence signal)
  • Captures Street View baseline image (stored as reference)
  • Issues PIN at PROVISIONAL tier
  • Links: owner RIN → PIN (ownership node)
  • Links: agent RIN → PIN (listing agent node, if agent initiated)
  • Links: org BRN → PIN (listing org node, if agent is org staff)

​
Managing Property Status

The MANAGING_DIRECTOR or SENIOR_AGENT (or the landlord directly) is responsible for keeping property status accurate. Status transitions: 
AVAILABLE → UNDER_OFFER
  Trigger: holding deposit received and witnessed by Leja
  Who triggers: agent confirms receipt of deposit in Leja Professional
  Effect: property locked — no competing offers can be accepted
  Double-letting prevention: any second agent viewing this PIN (Property Identification Number)
    sees UNDER_OFFER status immediately

UNDER_OFFER → OCCUPIED
  Trigger: lease signed and both parties confirm via Leja document platform
  Who triggers: agent confirms lease execution in Leja Professional
  Effect: active tenancy created, payment schedule established

OCCUPIED → AVAILABLE
  Trigger: tenancy end confirmed (normal exit or early termination)
  Who triggers: agent or system (on confirmed lease end date)
  Pre-conditions: exit inspection completed, deposit resolved

AVAILABLE → SHORT_LET_ACTIVE
  Trigger: short-let guest checks in (via Leja Stay)
  Who triggers: system (automatic on confirmed check-in)
  Effect: property not available for long-let inquiries during stay

SHORT_LET_ACTIVE → AVAILABLE
  Trigger: check-out confirmed by host
  Who triggers: system on check-out time, or host manual confirmation

​
Property Maintenance Logging

From Leja Professional side: Agents can log maintenance requests and completions manually. This feeds the PIN (Property Identification Number) maintenance history. From Resident side (automatic): Every service job processed through Resident on a property automatically feeds the PIN (Property Identification Number) maintenance history. The agent does not need to do anything — the record flows automatically. What gets logged:
  • Issue category (electrical, plumbing, structural, etc.)
  • Date reported
  • Date resolved (or marked unresolved)
  • Resolution time (days)
  • Completion confirmed by both parties
What does NOT get logged on the PIN (Property Identification Number):
  • The identity of the service provider
  • The cost of the job
  • The identity of the tenant who reported it
The PIN (Property Identification Number) shows the maintenance record of the property — not the identity of anyone involved in the maintenance.

​
PIN (Property Identification Number) and Double-Letting Prevention

This is one of the highest-value fraud prevention features. The problem in Nigeria: Multiple agents collect deposits for the same property simultaneously. The tenant pays. The agent disappears. No witness. No recourse. The Leja solution:
  1. Property is listed in Leja Professional — PIN (Property Identification Number) issued (AVAILABLE)
  2. Tenant submits holding deposit through Leja payment layer
  3. Agent confirms receipt in Leja Professional
  4. Property status changes to UNDER_OFFER immediately
  5. Status is visible to ALL parties querying that PIN (Property Identification Number)
  6. Any second agent attempting to show or collect for the same property sees UNDER_OFFER status and cannot create a competing deposit record
  7. If a second deposit is collected outside Leja:
    • Leja’s verified record layer shows who paid first and when
    • The fraudulent agent cannot deny the earlier payment was recorded
    • The evidence is permanent and attributed
This does not prevent all fraud — it makes fraud attributable and detectable. The fraudulent agent can be identified. The victim has recourse.