Pilot Parameters
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.
Spend Governance
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.
Active Pool
Pool Balance
£2,140.00
71% allocated · 2 active members
Member A Equity
£1,070.00
Member B Equity
£1,070.00
Live Ledger
AWS — Production Infrastructure
12:04:18 · auth.approved
−£412.00
Linear — Team Plan
12:11:52 · auth.approved
−£96.00
Annual Stripe Issuing Pre-pay
12:18:03 · auth.declined · ceiling_exceeded
−£1,300.00
Funds Flow Architecture
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
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
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
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.
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.
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
A small, fixed cohort allows each pool to be monitored closely as the platform operates in a live environment for the first time.
The two-member, equal-ownership structure is the simplest configuration that exercises the full contribution, spend, and dissolution lifecycle.
Excluding cash withdrawals, P2P transfers, lending, and overdrafts removes the categories of activity most associated with elevated financial risk.
A limited pool count allows authorization handling, webhook processing, and ledger reconciliation to be verified under real conditions before any expansion of scope.
Built on Stripe Infrastructure
Stripe Issuing
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
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.
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.
