Build client facing reservation web application -- 2

Client-facing Reservation Management We are a car service that requires a client facing web application that: • Allows clients to create and manage user accounts • Allows users to create and manage ride reservations for themselves or other passengers • Schedule and complete credit card transactions using reservation information and payment options saved in the account Accounts Users must be able to create accounts that store: • Contact information for the account holder (name, phone number, email) • Payment profiles for the account holder • Frequent addresses • Frequent passenger info (name, phone number, email) Reservations A logged in user must be able to create and manage reservations. Reservation information is stored in an existing reservation system, and will be accessed via a REST-like API. Reservation Creation • Collect required information from clients, including pickup/dropoff locations, passenger count, and passenger contact information • Retrieve quotes from existing API using passenger count and pickup/dropoff locations • Verify flight information using existing API when applicable (airport pickups) • Persist reservation in existing reservation API • Track user interactions using Google Analytics events Reservation Management • Retrieve list of all reservations for an account • Cancel scheduled reservations when allowed (time-based conditions) • Manually send reservation information to a client-provided provided email address using existing API • Send/print receipts for completed trips • Modify passenger contact info for upcoming reservations • Search for reservations by date, passenger or reservation number Transactions / Payments • Preauthorize pre-selected card for reservations 3 days prior to reservation • Receive signal (e.g., AWS SQS) that reservation has been completed • On completion, request updated amount from reservation API and settle transaction Technical Considerations • Use existing, documented in-house JSON REST-like APIs to store and read data for reservations, quotes, flight info and client communication via email and text • Use reputable third-party solutions for payment profiles, transactions, and credential/user management • Must be monitorable and use shared log consolidation service Working Agreement • Must be able to record progress against shared milestones tracked in Jira, Trello, or similar • Continued relationship for support and features a plus To be considered please provide examples of architecture and technology used on similarly completed projects.