Inspiration

Our late grandfather started one of the first travel agencies in London. In our family, we became the people everyone trusted to find a good flight deal. Building Flyte AI felt like coming back to that, just in a different way.

We'd already built Flyte AI, and we were looking for a way to get it into consumers' hands. When we saw this hackathon, we thought, why not use PayPal for that? We built on Flyte with PayPal checkout and added voice, so people could talk through their trip as well as type it.

The hackathon also helped us refine what we'd built. As we explored what PayPal offers, we started thinking it could become Flyte's primary payment method. Flyte Pal gave us a way to put that idea into practice.

Umar and I love coding and building things together, and this felt like a good opportunity to bring Flyte to more people.

What it does

Flyte Pal lets you search for flights by voice or text. Both share the same conversation, so you can switch between them.

The agent searches live fares through the Flyte AI API and checks the price again before checkout. You approve payment in PayPal's own window, and your demo booking appears under Your trips.

The hackathon version uses live flight search, PayPal sandbox payments of $0.01, and simulated bookings. No real money moves and no real tickets are issued.

How we built it

Flyte AI existed before the hackathon. For this event, we built Flyte Pal's conversational interface, voice experience, PayPal checkout, and an isolated demo environment.

The frontend uses Next.js, React, and TypeScript on Vercel. ElevenLabs handles speech-to-text and text-to-speech, with GSAP and Motion for animation.

PayPal's JavaScript SDK provides the checkout buttons. Our server creates and captures orders, verifies webhooks, and handles refunds. Payment amounts come from the confirmed fare on the server.

Challenges we ran into

One real sandbox purchase caught a mistake our tests had missed. PayPal returned the order references in a different part of the capture response than our test data assumed. We corrected the test data, watched 11 tests fail, and fixed the payment handling.

Voice had its own challenges: letting someone interrupt the agent while preventing the microphone from treating the agent's spoken response as a new request.

We also needed judges to try the complete flow with live fares while keeping payments and bookings inside the demo environment.

Accomplishments we're proud of

We connected a flight request to live search, PayPal approval, and a simulated booking on the trips page.

We also brought our existing payment safeguards into the PayPal integration: server-set amounts, protection against duplicate payment processing, and automatic refunds when a payment can't be used.

What's next for Flyte Pal

We want to add price watches with a user-set spending cap, fare splitting through PayPal invoices, and real bookings once Flyte opens booking. We're also considering PayPal as Flyte's primary payment method.

Built With

Share this project:

Updates

Submission history