> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/payments/customer-payments/bill-splitting.md).

# Bill Splitting

### Overview

Bill Splitting lets a Customer split the cost of a Reservation with their friends. The Reservation Holder toggles on Split the bill on the last page of the booking screen, invites other Customers, and each person pays their share at the end of the Reservation.

#### Reservation Booking

The Reservation holder can toggles on Split the bill on the final page of the booking screen, the Order Summary page, to learn about bill splitting with friends. This toggle is informational only, and the Reservation hold can invite their friends to split the bill, once the Reservation is booked.

<figure><img src="/files/FKWk8Tsm2bih8Y8CW3E8" alt=""><figcaption></figcaption></figure>

The cost of the Reservation is divided by the number of players who accept the invite. Meaning the first amount accepted is an estimate: if the number of players invited differs from the number who actually show up to the Club, the amount charged to each Customer changes. To read more, read [Failed Charges with Bill Splitting](https://podplay.gitbook.io/docs/payments/charge-errors/failed-charges-with-bill-splitting).

#### Holds at booking

When the Reservation Holder books the court, a hold is placed on their credit card for the full amount of the Reservation. This full hold stays in place even if every invited Customer has a charge failure or cancels, so the Club is guaranteed revenue for the court in case of any unforeseen circumstances.

<figure><img src="/files/rE97ehtBFsWho0SSI3bz" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**To review how much was charged to the Reservation holder or the invitees, the charge must finalize**, splits applied, and the details of the charge are visible within the specific payment, not on the Purchases tab.

Meaning, **staff must click in to a specific Reservation to see the total amount charged to a Customer after the split**, where the Authorized amount and the Captured amount are shown.
{% endhint %}

<figure><img src="/files/pOvQkH0umi2SUOsKn4Vf" alt=""><figcaption></figcaption></figure>

When an invitee accepts the invitation and agrees to pay their part, a hold is placed on that invitee's card for the likely amount of their split. Invitees see that they are paying for part of the Reservation and must toggle agreement that they are willing to pay.

<figure><img src="/files/WeYos0jHfflG0ekyhbrZ" alt=""><figcaption></figcaption></figure>

#### Seeing splits on the Dashboard

When viewing the Reservation from the Dashboard, staff will see when an Attendee is going to split the bill. This appears in the Attendees list as a dollar sign ($) in a circle under the Attendee's name, showing they have been invited to split the bill.

<figure><img src="/files/d54WZUrwx9mn6XdOMNCv" alt=""><figcaption></figcaption></figure>

#### How and when Customers are charged

Once the Reservation is over, all Attendees are charged their respective amounts. For the Reservation Holder, the hold for the full amount of the Reservation is released and they are charged the new, lower amount split with the other Customers.

#### Email receipts and notifications

Only the Reservation Holder receives an email receipt from their Reservation booking. A Customer who is invited and accepts the invitation does not receive an email receipt for their participation. No email notification is sent when an invitation is accepted, to either the invitee or the inviter. The only Bill Splitting email is sent when an invitee rejects an invite, which is the existing behavior prior to Bill Splitting. See [Automated Emails](https://podplay.gitbook.io/docs/marketing/automated-emails) for more detail.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podplay.app/payments/customer-payments/bill-splitting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
