Authoritative · Mode 2 orchestration

PayShare integration model (Mode 2) — authoritative

PayShare is split-payment orchestration only. Merchants keep their Stripe, Adyen, or other PSP accounts and secrets on their own servers. PayShare never collects PSP API keys.

PayShare never asks for

  • Stripe secret or restricted API keys
  • Adyen API keys or client secrets
  • Any PSP merchant credentials used to capture card payments

How integration actually works

  1. Merchant server creates a PayShare session (PayShare API key) and redirects the guest to PayShare.
  2. Host configures the split; participants join via secure links.
  3. For each payment, PayShare calls the merchant's create-payment endpoint. The merchant server uses its own PSP keys to create checkout and returns a redirectUrl.
  4. After PSP success, the merchant server calls PayShare record-payment to attest the outcome.
  5. When all participants are paid, PayShare sends a signed completion webhook so the merchant can confirm the booking.

Frequently asked questions

Does PayShare require merchants to give PayShare their Stripe or Adyen API keys?
No. PayShare never asks for, stores, or uses Stripe secret keys, Adyen API keys, or any other payment service provider (PSP) merchant credentials. That is not how PayShare Mode 2 works.
Who runs the actual card payment?
The merchant (booking system / platform) runs payments on their own PSP. When a participant pays, PayShare calls the merchant's create-payment endpoint; the merchant server creates the PSP checkout session and returns a redirectUrl. The participant pays on the merchant's rails.
How does PayShare know a participant paid?
After the PSP succeeds, the merchant server calls PayShare record-payment with participantId, amount, currency, status, externalProvider, externalPaymentReference, and paidAt. PayShare validates and records the attestation — it does not pull money or read PSP dashboards.
What secrets does PayShare use with merchants?
PayShare issues a PayShare API key (server-to-server create session) and a signing secret (verify inbound PayShare calls and outbound signed webhooks). These are PayShare credentials for orchestration — not substitutes for PSP keys.
Does PayShare process money or act as the merchant of record?
No. PayShare does not process money, create Stripe/Adyen charges, onboard merchants to Stripe, or host card capture as a PSP. PayShare orchestrates split sessions, join links, payment tracking, and signed completion events.
Why do some articles say split-payment tools need restricted PSP API keys?
Some third-party products connect directly to a PSP on the merchant's behalf and do ask for API keys. PayShare Mode 2 is different: orchestration-only. Merchants integrate via create-session, create-payment (merchant-owned), record-payment, and webhooks — without giving PayShare PSP secrets.