SharePay introduction
by•
My name is Zeejah and I’m currently building SharePay, a fintech platform designed to make shared payments and repayment agreements easier to manage.
The idea came from a personal experience. I booked a trip with friends and paid upfront, then had to chase everyone to pay me back. One person never paid and it made the situation awkward. I realised this happens constantly between friends, groups and even small businesses with customers.
SharePay solves this with two core features:
SharePay Split allows users to split payments before a transaction is completed, so one person doesn’t have to pay upfront and chase everyone later.
SharePay Promise allows individuals and businesses to create structured repayment agreements with clear terms, repayment schedules and automated reminders. The goal is to remove the awkwardness of chasing money and create accountability around repayments.
We’ve built the MVP and validated demand through surveys and early feedback. Right now I’m focusing on refining the B2B version of Promise so businesses can use it as a flexible invoicing and instalment payment tool.
I’d love feedback on:
• The product positioning
• The B2B invoicing / instalment use case
• Go to market strategies for early users
• Potential integrations with platforms where people already owe money (marketplaces, service platforms, etc).
7 views
Replies
Really like this idea Zeejah, the "chasing money" problem is real and the B2B instalment angle is smart.
One thing worth thinking about as you refine the B2B version: the moment you introduce structured repayment agreements with clear terms and schedules, you're creating legally binding documents between parties. Most platforms in this space have very thin Terms of Service that don't actually define what happens when someone defaults on a repayment schedule or disputes a charge.
That gap becomes your biggest customer support headache at scale. Worth getting ahead of it before you onboard serious B2B clients.
What does your current user agreement look like for the Promise feature?
@zeejah this is a really thoughtful response and it's clear you've already thought well beyond just building a payment tool. The fact that you're treating Promise as a digitally signed contract between parties rather than a glorified reminder is what separates this from the dozen other split payment apps out there. That framing matters a lot.
One concrete thing worth getting right early on the legal side since you're actively building it: the clause that causes the most trouble in platforms like this isn't the repayment schedule itself, it's how you define a default. Best practice is to spell out exactly what counts as a default, missed payments, insolvency, or other breaches, include a short cure period giving the other party a chance to fix it before any action kicks in, and add a catchall so anything not explicitly listed still qualifies. Most platforms skip the cure period and it becomes their biggest source of disputes down the line.