Developers

Add group checkout without rebuilding your payment stack.

Stripe is live today. PayShare adds Split with others beside Pay now. Install PayShare from the Stripe App Marketplace, start each split from your server with a Stripe order proof, and guest shares are charged on your own Stripe account. Your Stripe secret stays on your server.

Install on StripeView documentation

Scroll to explore

How you integrate

Merchant or platform.

Pick the path that matches who controls the checkout.

Merchants

You run your own website or booking checkout. Install PayShare on the Stripe account that takes the money, add the button, and start splits from your server.

  • Next.js and React use the official component
  • WordPress, PHP and plain HTML use hosted PayShare.js
  • Payments stay on your Stripe account

If a platform runs your checkout, install PayShare and connect it to your platform with a one-time code.

Install on StripeMerchant guide

Platforms

You run checkout for many merchants. Add PayShare to your product once, and each merchant connects their own Stripe account with a one-time code.

  • One button on your shared checkout
  • Signed server-to-server connection requests
  • Merchant Stripe accounts resolved on your server

Register your platform in the PayShare Stripe App. PayShare activates merchant connections once your setup is confirmed.

Platform guideContact PayShare

What PayShare provides

A live group session — not a rebuilt checkout.

The product is the hosted multi-party session your customers enter after they choose Split with others. You keep Pay now and your Stripe account; PayShare runs the group experience you would otherwise have to design, ship, and keep correct yourself.

  • People join one live session

    Invite by link or QR. Organiser and participants land in the same PayShare-hosted session for that booking or order — with join and progress already built.

  • The right number of places

    Session capacity is enforced for the group. Only the correct headcount can hold places in that checkout session.

  • One share each

    Each participant pays their share once against the live session. The group stays coherent as people join and pay — without you inventing parallel “who paid what” UI.

  • A real session over time

    Progress, holds, and expiry belong to the hosted session so the group does not stay open forever. Shares are captured together only when the whole order is covered.

You could attempt that coordination on top of your existing payments — but you would be rebuilding the live group session. PayShare is that layer, so Split with others sits beside Pay now instead of becoming a custom multi-party checkout project.

Architecture

How PayShare fits

The group session runs on PayShare. The money moves on your Stripe account. Nothing flows through a PayShare wallet.

  1. 1
    Your checkout

    Split with others

    The customer selects Split with others beside Pay now.

  2. 2
    Your server

    Order proof

    Your server creates an unpaid Stripe PaymentIntent for the order and asks PayShare to start the session.

  3. 3
    PayShare

    Group session

    The organiser invites the group. Everyone joins, chooses their share and pays.

  4. 4
    Your Stripe

    Authorise, then capture

    Each share is authorised on your Stripe account and captured together when the order is covered.

  5. 5
    Your server

    Order confirmed

    You confirm the order from Stripe payment events, not from the browser return.

Legend: navy = PayShare · green = payments on your Stripe account · light blue = your checkout and server.

Integration effort

Built to fit around the checkout you already have.

PayShare is not a replacement payment stack. Install PayShare in Stripe, add the button and one server route, and confirm orders from Stripe.

PayShare-hosted group UX means you do not need to build

  • Invitations and QR / link sharing
  • Participant joining UI
  • Participant progress UI
  • Split-session state machine
  • Expiry and cancellation handling UX
  • Group completion rules UI
  • Group payment coordination screens
  • · PayShare runs on Stripe. Checkouts on other payment providers are not supported.
  • · Enterprise custom frontends can require more checkout surface work.
  • · Run a full group payment in Stripe test mode before going live.

Integration model last updated: September 2026. We do not publish a guaranteed calendar-time for connection — it depends on your existing application.

Safety

Is PayShare safe to connect to our checkout?

PayShare reduces integration risk by working around your existing Stripe setup — not by claiming “zero risk” or replacing security reviews.

Your payment account stays yours

Participant payments run on your own Stripe account, and payouts, disputes and reporting stay in your Stripe Dashboard.

No credential handoff

PayShare is installed as a Stripe App. Your Stripe secret key stays on your server — never paste it into PayShare.

Server-side session start

Start splits from your server with a Stripe order proof. PayShare reads the amount and currency from Stripe, never from the browser.

Confirm from Stripe

Mark an order paid from Stripe payment events. Return URLs are for display only and must not mark an order paid.

Test mode first

PayShare works in Stripe test mode on the same path, so you can run the full flow before taking live payments.

PayShare does not hold group funds

PayShare coordinates session state; it does not create a pooled PayShare wallet or hold customer balances. PayShare does not become merchant of record.

Trust & security →

What you build

Button → order proof → session → your Stripe.

You keep booking, inventory, Stripe, settlement and fulfilment. PayShare is the group session your checkout hands off to.

  1. 01

    Show Split with others

    Add the official button beside Pay now. It calls a route on your own server.

  2. 02

    Start the session from your server

    Create an unpaid Stripe PaymentIntent for the trusted order total, send it to PayShare, and redirect the customer to the returned sessionUrl.

  3. 03

    Shares are charged on your Stripe

    PayShare creates each guest’s payment on your Stripe account, authorises it, and captures every share together once the order is covered.

  4. 04

    Confirm from Stripe

    Each share carries your order reference in its metadata. Mark the order paid when one session’s succeeded shares cover the total.

Documentation

Everything you need to integrate.

The PayShare documentation covers install, checkout, starting a split, completion, refunds, testing and errors, for merchants and platforms.

OverviewHow PayShare works, who owns what, and what moves the money.Read →Stripe merchant guideAdd Split with others to your own checkout and start splits from your server.Read →Stripe platform guideOffer PayShare to every merchant on your platform, connected with one-time codes.Read →OpenAPIMachine-readable description of the public API.Read →
View documentationFor AI assistants

Ready to install PayShare for Stripe?

Install from the Stripe App Marketplace, then follow the setup steps in the PayShare Stripe App.

Get PayShareView documentation