Open-banking reconciliation layer for informal group expenses
Problem
Builders of apps for amateur sports groups (padel, football, running) need a simple flow: one member pays €80 for a court, the app splits it, everyone repays by ordinary bank transfer, and the app auto-detects who has paid. Existing options fail the use case: Stripe Connect onboarding is too business-oriented, and read-only open banking (TrueLayer/Plaid/Yapily) forces personal-account users to re-authenticate every 90-180 days and can't reliably match transfers without reference codes.
Opportunity
A purpose-built reconciliation API for P2P group settlements: connect a personal bank account once, read incoming transfers, and match them to expected splits (amount + smart matching heuristics), with EU-first coverage. Every club treasurer and group-trip app currently hacks this together or gives up.
Market analysis
Real and underserved niche — the replies in the thread itself call it a 'regulatory and product nightmare', which is both the warning and the moat. The AISP plumbing is commoditized (GoCardless Bank Account Data, TrueLayer, Plaid, Powens), but nobody has packaged smart P2P transfer matching for group-expense apps, because the 90-day PSD2 re-auth and fuzzy matching are structural, not incidental, problems.
Market · B2B2C: developers of club-management, group-trip and team-sports apps in the EU, plus club treasurers drowning in manual repayment tracking; demand is scattered across every sports-group app forum.
Pricing · AISP data APIs run from freemium (GoCardless Bank Account Data, ex-Nordigen) to per-connection enterprise plans; GoCardless collections charge 0.5% + $0.05 per transaction — a reconciliation API for app developers could plausibly sit at a flat SaaS fee per app per month.
Pros
- + Sharp, recurring pain: every club and group-trip app hits this wall and gives up.
- + B2B2C API play avoids consumer acquisition costs entirely.
- + Freemium AISP backends (GoCardless Bank Account Data) make the MVP cheap to build.
Cons
- − PSD2 forces personal-account re-authentication every 90-180 days — a built-in churn machine.
- − Matching transfers without reference codes is genuinely error-prone (five people each owing €20).
- − Licensed AISPs could ship smart matching as a checkbox feature and squeeze the thin layer.
Existing / similar tools
Source
r/AppIdeas (Reddit)
The design choice that makes or breaks this product is who connects a bank: if every group member must link their personal account, the 90-day re-auth requirement multiplies churn across the whole group and one lapsed consent breaks the experience. The viable shape is organizer-side only — the treasurer or trip-planner connects one account, everyone else just pays by ordinary SEPA transfer — which shrinks the regulatory surface to a single consent per group. That leaves fuzzy matching as the actual product: heuristics over amount, sender name, and timing must be confidently approximate, surfacing ‘probably these two payments cover Alice and Bob’ rather than pretending to be exact. Note the ground is also moving under PSD3, which may yet soften the 90-day rule and quietly remove part of the moat.