Live delivery
Property transaction and escrow platform
iRealty
Property technology for agents and international investors, with escrow that accounts exactly for money held for each seller.
The Challenge
A Delivery Shaped Around the Whole System.
Build more than listings and checkout: a buyer’s payment has to move through a stateful property transaction, keep seller funds isolated, route commission correctly and remain explainable if a payment provider or follow-up action fails.
What We Delivered
Cuesoft provides ongoing backend architecture, infrastructure and database work across AWS and GCP, including the escrow routing, transaction state model and reconciliation controls behind property payments.
Product and Interface Design
Experience Design Is Part of the Delivery.
Escrow Is Visible, Not an Internal Ledger
The transaction interface separates the amount funded for escrow protection, the iRealty fee and the property price. A buyer can see the status, property, verified counterparty and receipt alongside the financial breakdown rather than treating escrow as a promise hidden behind a Pay button.
A Timeline Guides the Next Safe Action
The design renders different transaction paths for an inspection, agent sale or rental, and developer purchase. It tells a user when a tour is confirmed, when proof needs review, when funds can be released, when a refund applies and where to raise a dispute.
Role-Aware Transaction Views
Seekers, landlords, agents, developers and administrators each have dedicated transaction lists and detail views. The interface gives each party a clear picture of the same transaction without asking them to interpret an internal operations screen.
System Architecture
The Technical Foundation.
A Stateful Transaction, Not a Payment Receipt
Each property transaction has a buyer, seller, property, payment reference, exact kobo amounts, acceptance deadline and explicit lifecycle. Only pending and in-progress transactions are allowed to represent money still held in escrow.
Exact Amounts and Separated Responsibilities
Escrow balances are held per seller in integer kobo. The transaction captures gross amount, the amount held, commission and expenses separately, so the platform can account for each movement instead of deriving it from a UI total.
Serverless Application Delivery on GCP
The API and client are delivered through Firebase App Hosting on Google Cloud, with managed PostgreSQL and Redis services providing the transactional and rate-limit layers.
Engineering Work
Details That Make the Difference.
Commission Routing Is Configured by Transaction Type
The platform creates a Paystack revenue subaccount and percentage split codes for inspections, sales and rentals. When a commission changes, the corresponding provider split is updated instead of relying on a stale value hidden in application code.
Funds Are Reconciled Per Seller
A reconciliation service proves that each seller’s escrow balance equals the sum of that seller’s still-held property transactions. It deliberately does not settle for a platform-wide total, because an over-credit for one seller can hide an under-credit for another.
The Payment Path Is Designed for Interruption
Funding intents hold a payment reference, exact breakdown and expiry. The flow detects lost listing reservations, avoids double local funding, moves ambiguous provider outcomes into reconciliation or refund states, and retries post-commit effects safely.
One Active Property Transaction at a Time
The database constrains the active transaction shape for a listing while the service uses idempotent intent recovery. This keeps concurrent buyers from creating two live money paths for the same property.
Cost and Operating Design
Spend Less on Idle Infrastructure.
Scale-to-Zero Is a Deliberate Operating Posture
The platform avoids paying for permanently idle application instances. Durable payment and reconciliation states make that possible: work can be resumed and made visible instead of assuming every background action runs continuously.
Managed Data Services Reduce Routine Operations
Managed PostgreSQL and Redis keep the transactional and shared rate-limit layers available without a separate database-operations programme. The deployment keeps termination protection on the managed data services.
Technical Capabilities
- 01Product and UI design
- 02Payment orchestration
- 03Escrow reconciliation
- 04Cloud infrastructure
- 05Database engineering
- 06AWS
- 07Google Cloud