Team payments

On the Team plan, several people work under one shared setup and can route their paid bookings through a single company Stripe account. This page covers how the money actually flows: choosing where each service is paid into, reading the company ledger, and how refunds and chargebacks are handled across the team.

If you are setting the team up for the first time - buying seats, sharing the join link, and approving members - start with The Team plan. This page assumes that is done.

Where each service is paid into

Once a company Stripe account is connected and you are on a seat, each of your paid services can be paid into either your own Stripe account or the company account - chosen per service, not all at once. When you edit a paid service you will see a Paid into choice:

• My own Stripe - the booking is charged on your personal Stripe (Connect or Manual), exactly as it would be without a team.
• The company account - the booking is charged on the shared company Stripe account.

This lets one person run some services on the company account and others on their own - useful if, say, your team work is company-billed but you also take private bookings on the side.

Note

The Paid into choice only appears when you have both paths available: an active seat with a working company account, and your own Stripe set up. If you only have one, there is nothing to choose and every service simply uses it.

Each booking remembers which account collected it, at the moment it was paid. Changing a service’s Paid into later only affects new bookings - it never moves money that has already been taken.

The company payments ledger

Your My account page shows a Payments ledger: every booking that took real money, newest first, with refunds noted. On a team, a scope toggle appears above it:

• My payments - bookings paid into your own Stripe account.
• Company - bookings paid into the company account.

What Company shows depends on your role:

• A team admin sees the whole company account - every member’s company-billed bookings, with the member who sold each one named on the row.
• A team member sees the same tab, but scoped to their own company-billed bookings only. Members cannot see their colleagues’ payments.

Each row shows the service and session time, the booker’s name and email, the date paid, the amount (struck through if refunded), and the Stripe payment reference for cross-checking in your Stripe dashboard.

Refunds

A refund always goes back to the account that took the payment, because each booking remembers where it was charged. So a company-billed booking is refunded from the company account, and an own-billed booking from your own - even if the service’s Paid into setting has changed since, or the member who sold it has left the team.

You can refund a booking from the Bookings page (for a delivered session) or by cancelling an upcoming one. A refund can also be issued directly in Stripe; Pay2Book notices it and marks the booking Refunded automatically, so your records always match Stripe.

Who can refund a company booking

Because company bookings are paid into the shared company account, refunds and cancellations on them have a team rule:

• A team admin can always refund or cancel any member’s company booking, working from the Company view of the Bookings page.
• Whether a member can refund or cancel their own company bookings is a company setting the admin controls, on the Team page. When it is on (the default) members refund their own as usual; when it is off, only the admin does, and a member who tries is told so.

When an admin refunds or cancels a member’s booking, the member sees a note on that booking naming who did it and when, so nothing changes on their calendar without explanation.

Note

Disconnecting the company Stripe account stops new company-billed charges, but it does not prevent refunding past company bookings - the money is still on the company account, and the refund follows the booking’s original account.

Disputes and chargebacks

If a booker disputes a charge with their bank (a chargeback), Stripe pulls the funds from the account that took the payment and Pay2Book records it against the booking:

• The booking is tagged Disputed on the Bookings page, and a banner lists open disputes with an Acknowledge button to clear the notice once you have seen it.
• You respond to the dispute itself in your Stripe dashboard (submitting evidence, or accepting it). Pay2Book tracks the dispute but does not fight it for you.
• If the dispute is lost, the funds are gone, so Pay2Book records that as a refund on the booking - keeping the ledger honest about the money that left.

For a company-billed booking, the dispute is against the company account, so the team admin can see it in the company ledger; the member who sold it sees it on their own Bookings page.

Tip

Disputes are time-sensitive - banks set a deadline to respond. Keep an eye on the Disputed flag and respond promptly in Stripe.