Voya hotel cancellation: Android wireframes on Agoda's Demand API

PM101 Mid-Course case, Masters' Union. Voya is a start-up Android app that sells hotel rooms sourced from Agoda. This repository designs the flow for cancelling an existing booking: information architecture, logic flow, sixteen low-fidelity wireframes with design, developer and business notes, and a product note.

Team: Om Umrania, Param Parekh, Shabareesh Parlakota, Arushi Gupta, Manya Mahajan.

Submission

• presentation/final-submission.pdf: the 13-page submission (11 core pages and a 2-page product note). Source: presentation/deck.html, generated by presentation/src/build.py.
• wireframes/screens/: each wireframe A to P as a PNG. wireframes/design-notes.md has the notes for each.
• flows/: information architecture and logic-flow diagrams (PNG and text).
• docs/: API integration notes, assumptions, requirements, edge-case matrix, QA register, change log, product note.
• prototype/: an interactive Next.js prototype that uses simulated Agoda API responses. It makes no real bookings, payments or Agoda calls.

How the cancellation flow works

1. My trips reads Voya's own booking table. Booking details reads status from Agoda's Booking Detail.
2. Cancel booking calls Cancel Preview, which returns a reference, the policy text, what was paid and what would be refunded.
3. The traveler reviews the estimated refund with hotel and dates, and chooses Keep booking or Yes, cancel booking.
4. Voya sends Confirm with the reference and refund amount from the Preview. Success is HTTP 200 with an empty body.
5. Voya reads Booking Detail and shows Cancellation confirmed only when the status says cancelled. If Confirm gets no reply, Voya checks the status before any retry.
6. Fee waiver is a separate path, offered only when isFeeWaiverAllowed is true. The hotel decides.

Evidence tags

[D] documented by Agoda, [A] Voya assumption or design decision, [V] needs validation with Agoda. Open validation items: the cancellation cutoff (one day before check-in versus 12:00 AM on the check-in date), fee-waiver reason values and statuses, account permissions, and how the traveler's refund settles under Partner Fulfillment. See docs/assumptions.md.

Example data

All hotels, prices, dates and IDs are invented. Demo date: Sunday 25 October 2026. Stay: Thursday 10 December to Saturday 12 December 2026 at Sample Hotel, Bengaluru. Refund fixtures are separate bookings: ₹18,240 (VY-1042), ₹12,000 (VY-1057), ₹0 (VY-1063).

Run the prototype

cd prototype
npm install
npm run dev

Build check: npm run build. Rebuild the deck: python3 presentation/src/build.py && python3 presentation/src/render.py (needs Python with Playwright and Chromium).

Sources

Agoda Demand API documentation: https://developer.agoda.com/demand/ (cancel-bookings, fee-waiver-cancellation, retrieve-bookings, json-search-api, appendix, best-practices-certification-process).