LetzPool LetzPool Request Access
PILOT · STRIPE ISSUING INTEGRATION · APPROVAL PENDING

Shared Spend Infrastructure
for Commercial Co-Principals.

Two verified co-principals co-fund a shared pool balance. LetzPool coordinates pre-funded virtual cards issued on Stripe's network, with spend controls enforced at the point of authorisation. LetzPool does not hold or move funds.

No credit extended · Funds held by Stripe · Limited pilot cohort

Pilot Parameters

A deliberately limited scope

The current pilot operates within a fixed set of constraints. These are not temporary limitations to be removed — they define the boundaries of the controlled rollout.

01

Maximum 2 verified participants

Per pool, both identity-verified before activation.

02

Equal ownership structure

Pool equity is split evenly and calculated on every read.

03

Virtual cards only

No physical card issuance during the pilot.

04

No cash withdrawals

ATM and cash-equivalent MCCs are blocked at the network level.

05

No peer-to-peer transfers

Funds move only between a member and the pool, never between members.

06

No lending

No credit is extended at any point — spend is limited to funds already contributed.

07

No overdrafts

Authorisations exceeding the available balance are declined automatically.

08

Limited pilot cohort

A small, fixed number of active pools, admitted on an invitation basis.

Who It's For

Built for verified commercial co-principals

LetzPool is not a consumer product. It is designed for commercial use cases in which exactly two verified co-principals constitute a pooled spend entity for authorised collective expenditure against shared commercial obligations.

Venture Launchpad

Pre-incorporation co-founders

Two founders building a commercial venture before Companies House incorporation. Banks routinely refuse accounts without an active company number. LetzPool lets both co-principals pool seed capital and issue individual virtual cards for early operational spend — AWS, legal drafts, domain registrations — with real-time mutual visibility, before the corporate structure exists.

Commercial · Pre-incorporation · Shared ops budget

Shared Project Build

Joint-venture trade contractors

Two independent trade contractors entering a temporary unincorporated joint venture — say, a bricklayer and a carpenter executing a single commercial property renovation together. Rather than one party carrying all financial liability, they form a project-bound pool funded by the client's upfront deposit. Both purchase materials directly at trade merchants with dual-card access and full mutual transparency.

Commercial · Project-bound · Client deposit funded

Campaign Wallet

Co-production creative partners

A freelance videographer and creative director partnering as equal co-principals to execute a single corporate marketing campaign. They establish a project-bound pool capped at exactly two members. Location permits, camera kit rentals, and production costs are drawn down in real time from the shared balance — keeping campaign accounting entirely separate from each individual's freelance practice.

Commercial · Campaign-bound · Client reconciliation

LetzPool is not designed or presented for personal, family, or household use. The pooled entity is always the spending entity — individual members are not.

Spend Governance

Pre-funded spending, with controls enforced at authorisation

Both members see the same pool balance in real time. Every card transaction is checked against the remaining balance before it is authorised — spending beyond the available funds is not possible.

LetzPool — Live App Screens
Pools Home

Pools Home

Both members see the active pool and live balance at a glance.

Live Ledger — Build Site A · Materials

Pool Contribution — Lee Jordan

Payment confirmed via Stripe webhook

+£2,500.00

Pool Contribution — Andy White

Payment confirmed via Stripe webhook

+£2,500.00

🕐

Andy White spent £300.00 at Roc…

Authorized Hold · Pending Settlement

−£300.00

🕐

Lee Jordan spent £450.00 at Roc…

Authorized Hold · Pending Settlement

−£450.00

pool balance £4,250.00 · 15% allocated · Healthy Runway
£2,125.00 equity per member · 2/2 capacity
every authorisation checked against pool balance before approval

Funds Flow Architecture

Two flows, kept separate

All movement of money happens within Stripe's infrastructure. LetzPool's role is limited to coordinating ledger state and applying spend controls — it sits outside the regulated flow of funds.

Financial Flow — within Stripe

Members
↓ Contributions (PaymentIntents)
Stripe Infrastructure
Issuing · Custody · Card Network
↑ Refund-to-Source
Members

Contributions move from members to Stripe. On dissolution, each member's remaining balance is refunded individually back to its source — funds never pass through LetzPool.

Governance Flow — LetzPool

Stripe Webhook Event
↓ Authorization / Ledger Event
LetzPool Ledger
Spend Controls · Balance Calculation
↑ Approve / Decline Response
Stripe Authorization

LetzPool receives authorization and ledger events from Stripe, evaluates them against pool rules, and returns an approve or decline decision. No funds are received, held, or transmitted at this layer.

Platform Capabilities

What the ledger does

Shared Visibility

Both members see the same pool balance, contributions, and transaction history at all times.

Each authorisation, contribution, and refund updates a single ledger record. Equity is recalculated on every read from underlying records — it is not stored as a separate value that could drift out of sync.

Built-In Spending Controls

Spending is limited to the funds already contributed to the pool. There is no mechanism to spend beyond this.

Each authorisation request is evaluated against the pool's remaining balance before a response is returned to Stripe. If the requested amount would exceed the available balance, the authorisation is declined.

Automatic Refund-to-Source

When a pool is closed, each member's remaining share is returned to where it came from.

On dissolution, each member's equal share of the remaining balance is refunded independently to their original funding card via a separate Stripe refund. Refunds are not combined or routed between members.

Why the Pilot is Restricted

Restrictions are part of the design

Controlled rollout

A small, fixed cohort allows each pool to be monitored closely as the platform operates in a live environment for the first time.

Operational validation

The two-member, equal-ownership structure is the simplest configuration that exercises the full contribution, spend, and dissolution lifecycle.

Risk management

Excluding cash withdrawals, P2P transfers, lending, and overdrafts removes the categories of activity most associated with elevated financial risk.

Infrastructure testing

A limited pool count allows authorization handling, webhook processing, and ledger reconciliation to be verified under real conditions before any expansion of scope.

Stripe Infrastructure Integration

Two dependencies, each handling a regulated function

Stripe Issuing

Card issuance and authorization

Stripe issues each virtual card, holds the underlying funds, and is the sole party authorising or declining individual transactions on the card network. LetzPool's role is to respond to Stripe's authorization webhook with an approve or decline decision based on pool rules.

Stripe Identity

Identity verification

Every member completes document-based identity verification through Stripe Identity before a pool is activated or a card is issued. Verification status is set server-side via Stripe webhook and cannot be altered by either member.

Non-custodial by design.

LetzPool is designed as a non-custodial spend orchestration platform. Stripe holds all funds, issues all cards, and executes every transaction on the card network — LetzPool coordinates ledger state and applies spend controls, without holding, receiving, or transmitting customer funds.

Stripe Issuing Stripe Identity Non-custodial