The problem
Short-stay marketplaces have to coordinate listings, availability, payments, and time-sensitive bookings. Without explicit expiry handling, unpaid reservations can block properties and create double-booking risk.
Loading page
Preparing the content for you.
From listing to confirmed stay.
A short-stay accommodation marketplace supporting host listings, availability, booking workflows, payment integration, and booking-expiry handling to connect accommodation providers with people looking for places to stay.
Overview
Arrivo covers the journey from a host listing to a confirmed booking. Hosts publish availability, guests select dates, and the booking workflow handles payment and confirmation.
Expiry handling is part of the design because an unpaid booking cannot hold a property indefinitely. The system releases availability when a booking is not completed in time.
Short-stay marketplaces have to coordinate listings, availability, payments, and time-sensitive bookings. Without explicit expiry handling, unpaid reservations can block properties and create double-booking risk.
Arrivo provides host listings, availability management, a booking workflow, payment integration, and automatic expiry handling for incomplete bookings.
Architecture
A high-level conceptual view of the main stages in this system.
Hosts publish property details and availability.
Guests find available properties for their dates.
A booking is created and payment is processed through a supported provider.
Completed payments confirm the stay; incomplete bookings expire and release availability.
Capabilities that are documented as part of the current implementation.
Property details and availability are managed by hosts.
Prevents the same dates from being booked twice.
Moves a reservation from selection to confirmation.
Supports Paystack and Flutterwave payment flows.
Releases availability when a booking is not completed in time.
These items are planned and are not available yet. They are listed separately so completed functionality is never confused with future work.
Ratings and reviews after a completed stay.
Location-driven discovery of available properties.
A live marketplace environment with operational monitoring.
Technology
The tools and technologies associated with the implementation.
End-to-end type safety.
Application framework and server rendering.
Marketplace and booking interfaces.
Typed data access and schema management.
Listings, bookings, and payment records.
Payment processing integration.
Alternative payment processing integration.
Challenges
The engineering constraints that shaped the design.
Availability must be reserved atomically so two guests cannot confirm the same dates.
Provider callbacks and webhooks can arrive late or more than once, so booking state must be reconciled carefully.
A booking expiring at the same moment a payment completes requires a clear conflict rule.
Outcomes
Qualitative outcomes from the design. Measured results are only reported where they have been formally evaluated.
Links
Explore the project through the destinations that exist. Missing destinations are labelled instead of being replaced with a placeholder URL.
No public link has been provided for this project yet.
No public link has been provided for this project yet.
No public link has been provided for this project yet.
No public link has been provided for this project yet.
0 of 4 external links are currently available. Unavailable links are shown deliberately rather than pointing to a placeholder destination.
Keep exploring
Browse the full portfolio or start a conversation about this project.