UK Payments Regulatory Review (Stripe Connect)
We are a UK startup building a platform for residents' associations. We need a short written view on whether our payments architecture means we are carrying on a regulated activity in the UK, or whether that sits with Stripe.
This is a focused desk review. We have set out the architecture in full below so that no discovery is needed. We are looking for a clear answer to one question, with the reasoning, in plain English.
The architecture
We are build a mobile platform for residents' associations, which we call communities. Residents buy event tickets and paid club memberships from their own community through the app.
Payments work as follows. Each community is onboarded as a Stripe connected account. When a resident buys a ticket, Stripe takes the card payment and the funds settle into that community's own connected account. Our platofrm takes a commission using Stripe's application fee mechanism at the point of the transaction. Funds are paid out automatically from the connected account to the community's own bank account on Stripe's standard payout schedule.
Our platform does not hold, control or have access to community funds at any point. It does not operate a ledger and does not record balances. Where the app displays a community balance, it is read live from Stripe's API and not stored by us.
We have not yet chosen between Stripe Connect Standard, Express and Custom accounts, and part of what we want to understand is whether that choice matters here.
Separately, and not part of the launch, we may later add a community wallet holding a stored balance, with a virtual card issued against it so that a committee can spend community funds directly. We would like a view on that too, but as a forward-looking note rather than the main question.
Questions we need answered
1. On the architecture described, does the patofrm carry on a regulated activity under the Payment Services Regulations 2017 or the Electronic Money Regulations 2011, such that FCA authorisation or registration would be required? A direct yes or no first, then the reasoning.
2. Does the choice between Stripe Connect Standard, Express and Custom accounts change that answer, and which is the safest for staying outside the perimeter?
3. Does taking our commission through Stripe's application fee mechanism affect the analysis in any way?
4. What specific changes to this design would bring us inside the perimeter? We are thinking of things like holding balances, controlling or delaying payouts, or routing funds through our own account. A short list is more useful to us than a long explanation.
5. Looking ahead to the stored-balance wallet and virtual card: in broad terms, what would we need, and what are the usual routes? For example becoming an agent or distributor of an authorised firm, partnering with an e-money institution, or seeking our own authorisation.
Deliverable
A written note of one to two pages, in plain English, structured against the five questions above. Question one answered in the first paragraph.
specifically the PSRs 2017, the EMRs 2011 and the FCA perimeter.
Budget and timing
Fixed price $200. Written note required within five working days of award. Please do not propose an hourly arrangement or a scoping call before quoting; everything you need is above.
Screening questions
1. In one sentence, based on the architecture described, do you think Keys is likely to require FCA authorisation, and why?
2. Have you advised a platform or marketplace using Stripe Connect? Tell us briefly what the arrangement was.
3. Please confirm you can deliver the written note within five working days for the fixed budget.