Trust & Safety

No fake GCash screenshots.
No vanishing tenants.

Tuluyan runs trust at the infrastructure level. Every booking and tenancy is tied to a verified government ID and a real, confirmed payment — not a screenshot, not a promise.

Four pillars

How Tuluyan keeps every
transaction safe

We built trust into the infrastructure, not as an afterthought. Here's what that means in practice.

01

Verified Identity Checks

Every guest, tenant, and unit owner must complete government ID verification before their first transaction. By connecting every booking, lease, and agreement to a verified individual, Tuluyan helps create a safer, more transparent platform for everyone involved.

Government ID required from all parties
Selfie match with submitted ID
Verified badge displayed on profile
Operators can view verification status
02

No Payment Screenshots. Ever.

No "I already sent it." No proof-of-payment screenshots. No guessing whether funds actually arrived. Tuluyan confirms bookings, leases, and dues only after payment has cleared, giving operators confidence that every confirmed transaction is backed by real funds, not promises.

GCash, Maya, QR Ph, and cards supported
Booking only confirmed after payment clears
Operator payout after check-out
Full transaction record on both sides
03

Real Properties. Real Operators.

Every property on Tuluyan is reviewed before it becomes visible on the platform. We verify operators, review listing information, and require supporting documentation before approval. The result is a marketplace built on accountability, not anonymous listings.

Operator ID required at signup
Property details checked before approval
No ghost listings or unverified hosts
Verified operator badge on every listing
04

Reputation follows everyone

In most systems, people start over every time they move to a new property. On Tuluyan, trust carries forward. Guests, tenants, unit owners, and operators build a reputation through every stay, payment, and agreement. Responsible users are rewarded with smoother approvals, while repeated issues become visible before decisions are made.

Transaction history across all properties
Operator reviews visible to other operators
Guests can review operators too
Unresolved flags visible before booking
Step by step

What happens before a booking is confirmed

Every transaction on Tuluyan goes through the same sequence. There are no shortcuts.

1

Guest or tenant submits a request

A guest selects dates, or a tenant applies for a lease. No money moves at this stage — it's just a request.

2

ID verification is required

Before the booking can proceed, the guest uploads a valid government ID and a selfie. This is checked against their account. First-time users must complete this before any booking is accepted.

3

Operator reviews and accepts

The operator sees the request, the guest's verified profile, and their platform reputation. They can accept or decline based on what they see.

4

Payment is collected in full

The guest pays through GCash, Maya, QR Ph, or card. The booking isn't confirmed until payment clears — not pending, not a screenshot: cleared.

5

Booking confirmed. Both sides notified.

The guest receives their booking reference. The operator sees the confirmed reservation on their dashboard. After check-out, both parties can leave a review.

Situations every Filipino operator recognizes

Here's exactly what happens on Tuluyan when these come up.

Guest sends a fake payment screenshot

On Tuluyan, this can't happen. Payment is confirmed through a real-time gateway — there's no manual confirmation step where a screenshot could be accepted. The booking stays unconfirmed until actual funds clear.

Handled at the infrastructure level

Tenant skips rent and disappears

The tenant's non-payment is recorded in their platform history and marked on their profile. Other operators on Tuluyan will see this flag before accepting a future rental application. The record doesn't reset.

Reputation system flags carry forward

Operator lists a property that doesn't exist

Properties are reviewed before they appear publicly. Operator ID and property details are checked during the verification process. Listings that can't be verified don't go live.

Prevented at the listing approval stage

Guest damages the property

The operator files a report on the platform. The incident is attached to the guest's verified profile. Because the guest's ID is already on file, there's a real person accountable — not an anonymous account.

Identity on file, report on record

Questions about trust & safety

Every transaction, accounted for.

Start free and bring your property onto a platform where both sides of every deal are protected from day one.

No credit card required until you're ready to go live.