Split-checkout orchestration

Split-checkout orchestration is not bill splitting.

Bill-splitting apps usually help people settle up after one person has already paid. Split-checkout orchestration happens earlier. It coordinates multiple participants before a merchant booking or order is confirmed.

PayShare coordinates participant commitment and payment state for one checkout-linked session. The merchant keeps payment processing and confirms the booking only once the group has paid. For shorter answers, see the FAQ.

PayShare FAQ →

What it means

Orchestration before confirmation — not reimbursement after.

Split-checkout orchestration is the coordination layer that lets multiple people pay toward one merchant booking or order before the merchant completes it. It manages participant joining, share progress, checkout turns, expiry, cancellation, and group completion — while payments stay on the merchant’s own Stripe account.

What PayShare coordinates

One booking or order. Multiple participant payments. One completion signal.

PayShare coordinates a group checkout session connected to a merchant booking or order. Each participant pays their own share through the merchant’s existing payment provider. PayShare tracks who has joined, who is in checkout, who has paid, when the session expires, and when the merchant should complete or cancel the booking/order.

PayShare does not collect card details, hold pooled funds, or act as merchant of record.

01

Merchant creates PayShare session

A booking or order is linked to a PayShare split.

02

Participants pay their shares

Each person opens the PayShare link and pays through the merchant’s payment provider.

03

PayShare coordinates the session

PayShare tracks joined, in-checkout, paid, expired, and completion state.

04

Merchant completes the order

Shares are captured together once the order is covered, and the merchant confirms it from those payments on Stripe.

Not BNPL, wallets, or bill splitting

Multiple payers at checkout — not one person deferring or pooling.

Buy-now-pay-later helps one customer delay their own payment. Wallets and pooled accounts collect funds before paying a merchant. Bill-splitting apps settle up after someone has already paid. PayShare is none of these — each participant pays their own share through the merchant checkout before the booking or order confirms.

Why platforms need it

Group intent already exists — checkout does not support it.

Platforms already sell group bookings, shared orders, and team registrations, but checkout often still expects one payer. Building split-checkout orchestration in-house means participant links, payment confirmation loops, expiry handling, refund coordination, completion tracking, and ongoing maintenance. PayShare packages that layer for platforms that want split checkout without rebuilding payments.

Platform integration overview →

Payment providers

PayShare runs on the merchant’s Stripe account

PayShare is not a payment processor and does not replace a merchant’s payment stack. It is a Stripe App: every share is a payment on the merchant’s own Stripe account. PayShare coordinates the group session around those payments. The merchant remains in control of its payment rails, checkout policies, fulfilment rules, and customer booking/order flow.

Payments stay on the merchant’s rails. PayShare coordinates the split.

Build vs integrate

Can a business build split checkout itself?

Businesses can build many forms of bill splitting, payment splitting, or custom checkout logic. PayShare exists for merchants and platforms that do not want to build and maintain the full split-checkout orchestration layer themselves.

A PayShare-style checkout flow needs to coordinate:

  • participant links and joined state
  • payment confirmation per share
  • expiry and cancellation rules
  • completion tracking
  • refund coordination when sessions fail
  • merchant fulfilment safety

PayShare packages this orchestration into a reusable checkout integration.

FAQ

Frequently asked questions

What is split-checkout orchestration?
The coordination layer that lets multiple people pay toward one merchant booking or order before the merchant completes it — participant state, checkout flow, expiry, and completion signalling.
Is PayShare a payment processor?
No. PayShare does not hold pooled funds or act as merchant of record. Card payments stay on the merchant’s Stripe account. On Stripe, PayShare collects a 1% application fee on completed Split payments, capped at NZD $100 equivalent per session.
How is PayShare different from an IOU app?
IOU and bill-splitting apps usually happen after one person has already paid. PayShare happens before the merchant booking or order is completed, so each person pays their own share through checkout.
What happens if the group does not complete?
If a PayShare session does not complete before expiry, the merchant’s configured cancellation and refund flow applies. PayShare coordinates expiry so the booking or order is not confirmed prematurely.

More answers on the FAQ →

Ready to integrate split checkout?

PayShare coordinates group payment sessions while your payment provider processes each charge.