Split tech
Three integration stages — where we are today and what we need to continue. Click through to see our stages.
PayShare's timeline
Where we are today and where we're heading.
Stage 1 — Direct
Connect PayShare directly to your booking/order system — without relying on your provider. Direct is for businesses that own or control their checkout and/or booking database (or can add code to it). You install a small integration that creates PayShare sessions tied to your order reference, then present PayShare as an option before your default checkout runs.
What it looks like for customers
PayShare appears as a simple "Split this payment" option before the main checkout opens. It's not inside your checkout yet — but customers still get a clear confirmation, and your system receives the same completion signal.
What you need
- Access to add code to your site/checkout or booking system
- Ability to store a PayShare session/order reference (or link it to your booking ID)
Not a fit if: You can't modify your checkout or database. If that's you, ask your provider to implement PayShare for you (or use Embedded when available).
Who it's for
Businesses with developer access to their checkout or booking system.
Stage 1 connection
A quick example of how it works: your booking site provides PayShare with a webhook URL and success/cancel redirects. PayShare provides your booking site with an integration ID and API key. You add the button code — and we're working.
Your booking site → PayShare
Webhook URL, success URL, cancel URL
PayShare → your booking site
Integration ID, API key
You add
The button code
And we're working.
What we need to continue
To move from Direct (live today) through Embedded and toward Standard, we need deeper partnerships with payment providers, more merchant pilots, and feedback from developers. Get in touch to request access or share your use case.
Contact