Shared budgets and settle-up, inside your product.
Your users split costs and settle up inside your app. You never build or maintain the money math.
Ten open positions
Three payments
Live today in TripGoGo. Every shared budget in the app runs on SplitGoGo.
Your users already plan together. The moment money comes up, they leave.
A group forms in your product. They pick dates, build a list, agree who is paying for what. Then somebody opens a different app to work out who owes whom, and the conversation that mattered finishes somewhere else.
That moment is worth keeping. It is where a group commits, where a plan stops being hypothetical, and where your product either stays useful or hands the relationship to a spreadsheet.
What your users get
Three things every group needs, and the three reasons they go looking elsewhere when a product does not have them.
Mixed currencies that still add up
A group paying in four currencies sees one honest total. The rate is captured at the moment a cost is recorded, so nobody's share moves later because a rate did.
One balance per person
Every cost the group records rolls into a single number per member, recalculated the moment anything changes. No stale totals and no reconciling two versions of the truth.
Budget and split in one place
Most tools do one or the other. A group tracks what it planned to spend and what it actually owes in the same ledger, so the two can never quietly disagree.
Live today in TripGoGo
TripGoGo is a group travel planner and our first embed partner. Every shared budget, cost and settle-up inside it runs on SplitGoGo, under TripGoGo's own brand.
Recorded in the live product. TripGoGo kept its own screens and brand; SplitGoGo supplies the ledger, the splits and the balances behind them.
What you do not build
The parts that look like a week in a spec and take a quarter to get right, then keep taking your time forever.
Currency that holds still
The rate is captured when a cost is recorded, so a group's total does not shift next week because a market did.
Rounding that balances
A cost that will not divide evenly still sums to the exact total. Nobody is quietly short a cent, so nobody has to argue about one.
Settle-up worth trusting
The fewest payments that close a group out, recomputed every time somebody adds a cost or changes their mind.
Staying in sync
Your app hears about every change as it happens, so what a user is looking at is what the ledger actually says.
Who it's for
SplitGoGo is sold two ways.
Embed it in your product
Travel planners, event apps, roommate and rent apps, family finance and expense tools. If your users share a financial context, you can add budgeting and splitting through one integration instead of building it and then owning it.
Use it directly
Roommates, couples, friend groups and families will get one source of truth for who paid what, who owes whom, and how the group is tracking against its budget.
Not available yet. The platform ships to partners first.
Built to be easy to say yes to
The questions your risk and legal reviewers are going to ask, answered before they ask them.
We never touch the money
SplitGoGo works out who owes whom. Your users pay each other however they already do, so there are no funds to hold and no payment rail in the middle.
One tenant cannot see another
Every query is scoped to the tenant that owns the data. Your users and their balances are isolated from every other partner on the platform.
Only what the ledger needs
There is a written list of what SplitGoGo deliberately does not collect, and documented retention and deletion for everything it does.
Paperwork you can read now
The data processing agreement and the full sub-processor list are published, not something you have to ask for.
Request a demo
SplitGoGo is in early access. Tell us about your app and we will walk you through what an embed would look like for your users.