Stop being the bank for your group trip.

TripPot is an AI agent for the money side of a group trip. It reads the booking confirmations, works out who owes what, collects from everyone with PayPal invoices and pays each supplier as soon as the pot covers it.

collected of €4,425.00 from 12 travellers

  1. Paid Riad Dar Zitoun deposit€864.00
  2. Paid Marrakech Transfers€240.00
  3. Paid Atlas Desert Tours€1,305.00
  4. Paid Riad Dar Zitoun balanceYou approved it€2,016.00
The example trip, replayed: everyone pays in two rounds and the agent pays each supplier.

Somebody always ends up holding everyone’s money.

They put the deposit on their own card. They work out a fair split when three people skip the desert tour and one wants the single room. Then they spend weeks chasing eleven friends before every supplier deadline.

TripPot takes that job. You paste the bookings and approve the big payments.

38%
of American travellers have not received all the money owed to them from a group trip.[1]
47%
of Gen Z have gone into debt covering a group expense they expected to be repaid for.[2]
20%
of Gen Z who owe money have muted or ignored a group chat to avoid paying someone back.[2]

From confirmation emails to paid suppliers

Here is what it does with the example trip: 12 friends, a riad, a desert tour and airport transfers in Marrakech.

  1. Read the bookings

    Paste the confirmation emails. Claude finds each supplier, its total and when each part has to be paid.

    Claude Haiku 5.5

    From reservations@riad-dar-zitoun.example

    Booking confirmed: Riad Dar Zitoun, 14 to 18 May 2027

    Total: 2,880.00 EUR (breakfast included). Payment schedule: 30% deposit due by 1 March 2027, remaining balance due 15 April 2027. Payments via PayPal to payments@riad-dar-zitoun.example.

    Deposit €864.00 by 1 Mar 2027Balance €2,016.00 by 15 Apr 2027
  2. Split the costs

    Write a note per person, like “skips the desert tour”. The agent decides who pays for what, and the sums are done in code, to the cent.

    Claude Opus 5.5

    TravellerRiadDesertTotal
    Ana RibeiroSkips the desert tour232.50–€252.50
    Rui CostaWants the single room322.50145.00€487.50
    Joana Pires232.50145.00€397.50

    And 9 more. The shares add up to €4,425.00 exactly.

  3. Collect from everyone

    Each traveller gets a PayPal invoice per payment date, due 10 days before the supplier needs the money. Late payers get a reminder.

    PayPal Invoicing

    Invoice from Miguel Gomes for Marrakech May 2027

    To Ana Ribeiro

    Paid
    Riad Dar Zitoun 30% deposit€69.75

    Due 19 Feb 2027, 10 days before the riad needs it. Partial payments allowed.

    Next: €182.75 due 5 Apr 2027 for the riad balance and transfers

  4. Pay the suppliers

    When the pot covers a deadline, the agent pays that supplier and writes down why. Anything above your limit waits for you.

    PayPal Payouts and webhooks

    1. Paid Riad Dar Zitoun €864.00 with PayPal Payouts

      The pot holds €1,046.75 and the deposit is due 1 Mar 2027.

    2. Riad Dar Zitoun balance, €2,016.00, is over your €1,500.00 limit

      The money is set aside. It goes out when you approve it.

      Approve and pay

The whole trip on one screen

The pot with a line for each supplier deadline, every payment in and out on a timeline, and the agent beside it.

The TripPot dashboard for Marrakech May 2027: the pot with €182.75 in it, the payment timeline, and the agent answering who still owes money

Try the split yourself

Change who goes on the desert tour or who gets the single room. Every invoice updates with the same rules the app uses, and the shares still add up to the bookings, to the cent.

Each traveller’s two invoices for the example trip. Change who goes to the desert tour or who has the single room.
TravellerDesertSingleTotal
Miguel Gomes€397.50
Ana Ribeiro€252.50
Rui Costa€487.50
Joana Pires€397.50
Tiago Matos€252.50
Inês Lopes€397.50
Pedro Alves€397.50
Sofia Nunes€252.50
Diogo Faria€397.50
Marta Silva€397.50
Hugo Santos€397.50
Rita Moreira€397.50
Bookings €4,425.00 (riad €2,880.00, desert 9 × €145.00, transfers €240.00)Shares €4,425.00 match to the cent

Ask it anything. It answers from the live numbers.

The agent reads the pot, the invoices and the deadlines through its tools, then answers in plain words. It also acts on its own when a payment comes in, and writes down why.

Ask TripPot

Marrakech May 2027

Who still owes money?

Calling get_trip_overviewdone

Eleven travellers still owe money for the balance instalment, due 5 Apr 2027:

Diogo, Hugo, Inês, Joana, Marta, Miguel, Pedro and Rita each owe €327.75.

Rui owes €390.75.

Sofia and Tiago each owe €182.75.

Ana has paid in full.

The total outstanding is €3,600.50. No reminders have been sent yet.

A real answer, from live data

What it did on its own

From the agent’s log, newest last. Every action keeps its reason.

  1. Ana Ribeiro paid €182.75 for “Riad Dar Zitoun balance + Marrakech Transfers full payment”

    Payment in, from a PayPal webhook

  2. Paid Riad Dar Zitoun €864.00 (30% deposit)

    Riad Dar Zitoun 30% deposit (€864.00, due 2027-03-01) is funded, within the autopay limit, and the pot balance of €1,046.75 covers it.

    Paid supplier with PayPal Payouts

  3. I paid the Riad Dar Zitoun 30% deposit of €864.00 from the pot. It was funded, under the autopay limit, and covered by the pot balance. That leaves about €182.75 in the pot.

    Agent, on its own: new payments funded a supplier deadline

It moves money, so the rules are in the code, not the prompt

Ten steps from an email to a paid supplier. Claude handles the parts that need judgment, PayPal moves the money, and our code decides when it may move.

  1. 1People

    Confirmation emails

    Pasted by the organizer

  2. 2Claude

    Read the bookings

    Claude Haiku 5.5, structured output

  3. 3Claude

    Plan the split

    Claude Opus 5.5, structured output

  4. 4Our code

    Shares and instalments

    Integer cents, largest remainder

  5. 5PayPal

    Invoices

    PayPal Invoicing v2, partial payments

  6. 6People

    Travellers pay

    Each from their own invoice

  7. 7PayPal

    Webhooks

    Signature checked, duplicates ignored

  8. 8Our code

    The pot

    Funds deadlines in date order

  9. 9Our code

    Guardrails

    Funded, under the limit, paid once

  10. 10PayPal

    Payouts

    Batch id derived from the deadline

Claude makes the judgment calls: what a confirmation says, who takes part in what, what to answer. Amounts, due dates and balances are computed in code, and only code can release a payout.

  • A supplier is paid only when the pot covers that deadline and every earlier one.
  • Payments above the organizer's autopay limit wait for approval.
  • Each deadline is paid once. PayPal rejects a repeat payout.
  • If PayPal refuses a payout, the money stays set aside and the refusal is logged.
  • Reminders go out at most once per invoice every 24 hours.
  • Everything the agent does is logged with its reason.

For anyone who collects money for a trip

  • Friends planning a trip

    A villa for someone's 30th, a ski chalet, a stag weekend. One person books, and everyone pays their own part on time.

  • Travel agents and consultants

    Group tours with deposits and balance dates. Collect from each traveller instead of one lead booker, and pay suppliers on schedule.

  • Clubs, schools and choirs

    Tours paid in instalments, where the treasurer needs to see who is behind without keeping a spreadsheet.

Questions

Does real money move in the demo?

No. Everything runs in the PayPal sandbox. The invoices, payments and payouts are real PayPal API calls, made with test accounts.

Can the AI pay the wrong supplier, or pay twice?

The agent can only ask to pay a deadline the pot has already covered, to the payee read from that booking. The code checks the pot, the autopay limit and the deadline's status before anything goes out, and the Payouts batch id comes from the deadline, so PayPal refuses a second payout for it.

What does the AI decide, and what doesn't it?

Claude reads the confirmation emails, decides who takes part in each booking and who owes a supplement, and answers questions. It never does the sums: shares, instalments and balances are calculated in code, to the cent.

What happens when someone doesn't pay?

Their invoice stays open and accepts partial payments. The agent can remind them, at most once a day per invoice. Suppliers are only paid once the pot covers each deadline, so a late payer delays a payout instead of the organizer paying it from their own card.

What if PayPal refuses a payout?

The money stays set aside for that supplier, the refusal is logged with PayPal's reason, and the organizer can try again with Pay now.

Who decides on the big payments?

The organizer sets an autopay limit when creating the trip. Anything above it waits for them to press Approve and pay.

Watch it pay a supplier

Open the example trip, press Pay as traveller on a few rows and see the pot fill. No sign-up, and everything runs in the PayPal sandbox.