Objective: Add active dns legally to a web dev currently underway…Develop a legally compliant flight reservation and itinerary system using an approved Global Distribution System (GDS) such as Amadeus, Sabre, or Travelport. The system must comply with all GDS terms, airline booking rules, consumer protection laws, and payment regulations. The platform is intended to provide lawful flight itineraries or reservations, not airline tickets unless ticketing is explicitly enabled. Technical Requirements: 1. GDS Access and Configuration The system must integrate with an officially licensed GDS account (Amadeus, Sabre, or Travelport) obtained through a registered travel agency or accredited entity. API credentials must be securely stored and used strictly according to GDS documentation. All API calls must be logged for audit and compliance purposes. 2. Flight Search and Availability Implement real-time flight availability searches using the GDS air shopping or availability APIs. Searches must return accurate flight segments, schedules, and airlines based on user inputs (origin, destination, dates, passenger count). 3. PNR Creation (Compliant Use Only) The system may create Passenger Name Records (PNRs) only where permitted under GDS and airline rules. PNRs must represent legitimate reservation intent and must not be created for speculative, deceptive, or bulk purposes. Each PNR must correctly store passenger name data, flight segments, contact details, and booking status codes. 4. Ticketing Status Handling If no e-ticket is issued, the system must clearly mark the booking as “Not Ticketed.” Ticket numbers must not be fabricated or implied. Time-to-live (TTL) and airline auto-cancellation rules must be tracked and enforced automatically. 5. Reservation Lifecycle Management The system must monitor PNR expiration, handle automatic cancellations, and prevent reuse of expired or cancelled booking references. Users must be informed that unticketed reservations may be cancelled by the airline at any time. 6. Itinerary PDF Generation Generate professional itinerary or reservation summary PDFs based on real GDS data. PDFs may include passenger names, flight routes, dates, airline names, and PNR. Documents must clearly state “This is not a ticket” and must not visually resemble boarding passes or airline e-tickets. Airline logos or trademarks may only be used if legally permitted. 7. Email Delivery System Automate email delivery of the itinerary PDF shortly after reservation creation. Emails must clearly explain the reservation status, any applicable expiration times, and include support contact information. 8. Payment Processing (If Enabled) Payments may only be collected for service or processing fees, not for airline tickets unless ticketing is implemented. Payment gateways must be compliant (e.g., Stripe or equivalent), and refund and dispute policies must be clearly disclosed. 9. Security and Data Protection Passenger data must be stored securely and handled in compliance with applicable data protection laws (e.g., GDPR). GDS credentials must be protected using secure environment variables or key management systems. 10. Administrative Controls Provide an admin interface to monitor reservations, PNR status, API activity, errors, and cancellations. The system must support audit review if requested by GDS or airline partners. 11. Compliance Assurance The system must not attempt to bypass GDS controls, create misleading documents, simulate ticketing, or evade airline or GDS monitoring. Any functionality that risks non-compliance must be flagged and reviewed before implementation.