Skip to main content

Leja Stay — Short-Let and Travel

Trust-native short-let where both parties carry full Trust Graphs


Leja Stay is not a standalone product. It is the short-let surface of Track 3 (guest side) and Leja Professional (host side). The host lists a property in Leja Professional with a Property RIN. The guest books through Resident. Payment flows through Leja’s payment layer. Both Trust Graphs update simultaneously.

What Makes Leja Stay Different from Airbnb

Airbnb has anonymous guests with no verifiable residential history. Leja has RIN holders — both host and guest carry full Trust Graphs. What the host sees about a guest (before accepting):
  • Trust Graph tier
  • Previous Leja Stay behavior (if any)
  • Tenancy exit quality from Track 1 (do they leave places well?)
  • Maintenance behavior signal (do they report issues or hide them?)
  • Identity verification level
  • Any active fraud flags
What the guest sees about a host and property:
  • Everything in the Property RIN public view: maintenance history, condition rating, utility status, dispute history, neighborhood trust score
  • Short-let specific ratings from previous guests
  • Check-in reliability score (has this host ever been a no-show?)
  • Listing accuracy rating (does the place match the description?)
  • Host response time pattern
  • Previous guest review summaries (anonymized)

The Booking Flow

1. Guest searches Leja Stay (within Resident, Track 3)
   - Dates, location (LGA), price band, property type
   - Resident advocate support surfaces compatible properties (trust-tier matched)

2. Guest views property listing
   - Property RIN data shown: condition, maintenance, history
   - Host Trust Graph shown: verification tier, ratings, response time

3. Guest submits booking request
   - Leja holds booking payment (not released to host until check-in confirmed)
   - Property status changes to SHORT_LET_ACTIVE

4. Check-in
   - Both parties confirm check-in through Resident
   - Exact address was already shared after booking accepted
   - Booking payment released to host

5. Stay in progress
   - Resident advocate support monitors milestone timings (check-out approaching)

6. Check-out
   - Both parties confirm check-out through Resident
   - Host submits condition assessment (any damage? deductions?)
   - Guest submits rating of host and property
   - Security hold released if no damage claim

7. Trust Graph updates (both sides):
   Guest: SHORT_LET_COMPLETED event (Track 1 + Track 3)
   Host: SHORT_LET_HOSTED event (Leja Professional + Property RIN)

Weight in the Trust Graph

Short-let events carry lighter weight than long-term tenancy events:
Weight model:
  1 monthly tenancy payment ≈ 10 nights of short-let (0.1x per night)
  Reason: lower stakes, shorter relationship, limited behavioral signal

Exception: a short-let DISPUTE carries full weight regardless of duration
  Reason: disputes reveal character regardless of duration
  A guest who damages a property on a one-night stay and disputes
  the charge is showing exactly who they are.
Repeat booking signal: If a guest books the same host again, and the host accepts, this is a strong trust signal for both parties. It is surfaced prominently in both Trust Graphs. Repeat hire in services, repeat booking in stays — both are the strongest trust signals on the platform.

Trust Matching for Leja Stay

The Resident advocate layer surfaces compatible pairings:
  • Gold-tier guests surfaced to Gold-tier hosts
  • Bronze-tier guests surfaced to hosts who accept new users
  • Budget compatibility matched from Track 1 rent band history
  • Area preference derived from past tenancies and search behavior
The AI does not prevent lower-tier guests from booking. Every tier has compatible options. The system matches intelligently — it does not gatekeep.

Revenue from Leja Stay

  • Booking transaction fee: % of booking amount
  • Security hold processing fee: small flat fee per transaction
  • Cancellation refund processing fee (where applicable)
See 09_Revenue_Model/03_payment_layer_fees.md for full detail.