Scheduling-link-level Split Payment

The link-level split is per recipient.

Each entry means:

“If a booking is taken by this connected host, divide their incoming payment according to this split configuration.”

The form pulls recipients from the meeting’s own member list and only shows hosts who have a connected Stripe Standard account.

When a link-level split exists for a booking’s host, it completely overrides the workspace-level (admin) split for that booking.

1. Round-robin meetings — Hosts A, B, C assigned

The dropdown shows whichever of A, B, or C have Stripe Standard connected.

You can configure:

• 0 entries

• 1 entry

• 2 entries

• or all 3 entries

(one entry per host)

Example

Booking fee = $100

Configured splits:

• Host A → host gets 70%

• Host B → host gets 60%

• Host C → no configuration

Key takeaway

You are not routing payments.

Round-robin still selects hosts normally.

You are only configuring:

“How should this host’s payment be divided if they receive the booking?”

If you want predictable behavior, configure a split entry for every connected round-robin host.

2. One-on-one and Group meetings — single host

These meeting types always have one host.

The dropdown shows that single host (only if Stripe-connected).

You can configure at most one split entry.

Example

Booking fee = $100

Host = Alice

Configuration:

• Host gets 80%

Important note

For one-on-one and group meetings, this feature effectively behaves as:

“Override the workspace-level split for this specific host.”

Although the UI technically supports multiple recipients, only one host is eligible here.

3. Multi-host meetings — unsupported

Multi-host meetings do not support scheduling-link-level split payments.

The form is intentionally blocked:

Why?

In multi-host meetings:

• multiple hosts attend the same booking

• Stripe Connect cannot cleanly split a single payment across multiple destination accounts in this scenario

Because of this complexity, link-level split payment is not supported.

What happens instead?

Multi-host bookings fall back to:

• the workspace-level (admin) split configuration, if present

The split applies to:

• whichever host is considered the booking’s payable.user

Summary