Predictable participation
Clear dates, contribution amounts, payout order, and program rules from the start.
Infrastructure for bank-led collective savings
Turn trustedsaving intostructured growth.
Stashr is building the operating layer banks need to launch structured rotating savings programs for founders, SMEs, and communities—without building the full system from scratch.
Built for bank partners
Founder & SME focus
Non-custodial design
Contribute · form the pool · pay out in turn · repeat
Stashr is building the program layer. Partner banks would retain every regulated responsibility.
The problem
A proven savings behavior still runs on informal tools.
Many savings circles still depend on chat threads, spreadsheets, memory, and manual trust. That creates weak records, avoidable disputes, and no scalable way for banks to support the behavior.
Today — fragmented, manual, difficult to verify
With Stashr — structured, visible, ready to scale
What informality costs
- Contributions tracked in chat threads and notebooks, if they are tracked at all
- Payout order remembered, disputed, or renegotiated mid-term
- Late payments chased by hand, with no record of the chase
- Silent defaults that surface only when a payout falls due
- No statements, no history, nothing a bank could ever read
What structure returns
- Every contribution recorded against a member, a cycle, and a slot
- Slot order set or drawn, then locked for the term
- Defaults open resolutions that are tracked to closure
- Payouts confirmed by both sides before they are closed
- Statements, exports, and a tamper-evident audit trail
ROSCA, explained simply
One contribution. One shared pool. A rotating payout.
A ROSCA—also known as a jamiyya or chit circle—is a group that saves together. Everyone contributes a fixed amount. One participant receives the full pool each cycle. The process repeats until everyone has received once.
Phase 01Every member contributes
Every participant contributes the same agreed amount on the same schedule.
Cycle
01 / 10
Recipient
Member 01
Pool
AED 0
Status
Forming
Example program10 members · AED 1,000 each · AED 10,000 rotating pool
0
Members
AED 0
Contribution per cycle
AED 0
Pool per cycle
0
Cycles to complete
0
Payout per member
Stashr adds clearer rules, records, coordination, and a path to bank-led operation.
The platform Stashr is building
From informal circle to
structured financial program.
The current foundation supports group setup, enrollment, schedule design, and slot order. The roadmap extends the platform across the full savings-program lifecycle.
01
Program setup
Define the group, contribution amount, frequency, term, and payout order.
02
Participant onboarding
Invite, review, and organize participants around clear program rules.
03
Schedules & rotation
Create a clear cycle of contributions, pooled amounts, and rotating payouts.
04
Contributions & payouts
The roadmap supports coordinated payment status, reconciliation, and payout confirmation.
05
Exceptions & defaults
Planned workflows make missed contributions, corrections, and resolutions easier to manage.
06
Reporting & auditability
Give participants, operators, and future bank partners a clearer shared record.
Value for participants
Structure for the people who save together.
Stashr starts with founders and SMEs, where coordinated pooled capital can support disciplined planning and business growth. The same model can expand to other trusted communities over time.
Visible pooled capital
Participants can understand what has been contributed, what comes next, and when their turn arrives.
More trust, fewer disputes
A shared record reduces uncertainty and gives every participant the same view of the program.
The designed operating model
Ten steps. One clear savings cycle.
The full platform vision, from group setup to reporting. Scroll—or tap—to follow the planned operating flow.
01Create the circleDefine contribution, size, frequency, and term.
02Enroll approved businessesThe bank connects eligible founders and SMEs to the cohort.
03Set or draw the slot orderFix the payout order, or draw it by lot — recorded either way.
04Lock the termsThe schedule is fixed. From here, change means correction — with a trail.
05Reconcile contributionsEach payment is matched to a business, cycle, and slot.
06Execute payout workflowIn a bank-led deployment, operations advances the pool to the cycle recipient.
07Confirm receiptThe recipient confirms. A payout closes only when both sides agree.
08Manage defaultsLate or missed contributions open a resolution, tracked to closure.
09Generate statementsEvery member gets a statement; the circle gets exports.
10Prepare verification recordsFuture deployments can hash and externally verify selected events where required.
Create circleSetup · 01
Founder Growth Cohort
AED 1,000
10
Monthly
10 cycles
Create circle
MembersReview · 6 of 10 shown
| Member | Invited | Status |
|---|---|---|
| AMA. Mansoori | 2026-01-02 | Approved |
| RKR. Kapoor | 2026-01-02 | Approved |
| LHL. Haddad | 2026-01-03 | Pending review |
| SOS. Okafor | 2026-01-04 | Invited |
| MRM. Rahal | — | Draft invite |
Slot orderRotation · drawn by lot
| Slot | Member | Receives |
|---|---|---|
| 01 | A. Mansoori | Cycle 01 |
| 02 | R. Kapoor | Cycle 02 |
| 03 | L. Haddad | Cycle 03 |
| 04 | S. Okafor | Cycle 04 |
| 05 | M. Rahal | Cycle 05 |
Draw by lotOrder recorded
TermsLocked
| Term | Value |
|---|---|
| Contribution | AED 1,000 / business / cycle |
| Members · Slots | 10 · 10 |
| First cycle | 2026-02-01 |
| Final payout | 2026-11-01 |
Terms lockedsched_ref 8f3a…9c1e
From this point, any change is a correction — recorded, reasoned, and visible.
ContributionsCycle 04 · in progress
| Member | C1 | C2 | C3 | C4 |
|---|---|---|---|---|
| A. Mansoori | 1,000 | 1,000 | 1,000 | 1,000 |
| R. Kapoor | 1,000 | 1,000 | 1,000 | 1,000 |
| L. Haddad | 1,000 | 1,000 | 1,000 | — |
| S. Okafor | 1,000 | 1,000 | 1,000 | 1,000 |
9 of 10 received · AED 9,000 of AED 10,000 recorded.
Payout — Cycle 03Sent
| Field | Record |
|---|---|
| Recipient | L. Haddad · Slot 03 |
| Amount | AED 10,000 |
| Marked sent | 2026-04-05 14:22 |
| Recorded by | Organizer |
Awaiting business confirmation
Payout — Cycle 03Confirmed
| Confirmation | State |
|---|---|
| Sent by bank operations | Recorded |
| Received by member | Confirmed |
| Payout status | Closed |
A payout closes only when both sides agree. Two signatures beat one memory.
Resolutions1 open case
| Case | Subject | Status |
|---|---|---|
| R-07 | Member 07 · Cycle 04 contribution · 6 days overdue | Late |
| R-07.1 | Resolution — pay by 15 Mar, agreed with program operator | Open |
| R-02 | Member 04 · Cycle 02 · resolved in full | Closed |
Nothing is silent. Every default has an owner, a plan, and an outcome.
Statement — L. HaddadThrough cycle 04
| Line | Amount |
|---|---|
| Contributions paid (4 × 1,000) | AED 4,000 |
| Pool received (Cycle 03) | AED 10,000 |
| Remaining contributions (6 × 1,000) | AED 6,000 |
| Position | Net +AED 6,000 |
Export PDFExport CSV
Audit trailIllustrative future verification
| Event | Hash | Proof |
|---|---|---|
| #118 Contribution recorded | 0x7f3a…c9 | Example proof |
| #122 Payout confirmed | 0x41be…02 | Example proof |
| #124 Correction reverses #118 | 0x9d07…5f | Example proof |
This future-state view shows how selected records could be externally verified without exposing customer PII.
Step 01 / 10
Setup
Product boundary
A working foundation,
with a clear build path.
The current foundation covers program formation and scheduling. Transaction operations, reporting, bank connectivity, and external verification remain roadmap capabilities.
Foundation and designed extensions
Clearly staged- Identity & accessAccounts, roles, and organizer permissions.
- Circle formationCreation, configuration, and term definition.
- Derived schedulesCycles, due dates, and payouts generated from the terms.
- Invites & member reviewInvitation flow with organizer approval.
- Rotation engineSlot ordering, set or drawn, with the rotation advanced per cycle.
- Transaction workflows — roadmapContribution, payout, and confirmation operations are part of the planned buildout.
- Defaults & resolutions — roadmapStructured exception handling is planned for later program operations.
- Corrections — roadmapFuture records are designed to preserve the original entry and reason.
- Statements & exports — roadmapMember reporting and program-level exports are planned capabilities.
- Privacy-conscious event modelThe current design creates a foundation for a clear operational history.
- External verification — future optionThe architecture can add a provider-neutral verification layer where required.
Not in the MVP — by design
Deliberately absent- No walletStashr does not store value for anyone.
- No Stashr-held balanceThere is no balance to hold. Money never sits on the platform.
- No payment initiationStashr does not move, route, or execute money.
- No automated KYC / AMLIdentity verification belongs with regulated institutions.
- No bank integration — yetThat is the Version 2 trajectory, stated plainly below.
- No lending products todayCredit-linked modules are conditional future phases, not current claims.
- No protection pool todayNo guarantee fund is offered or implied.
- No AI features in productThe record is deterministic. Nothing about it is guessed.
A platform that is precise about what it does not do is one a bank can reason about. The boundary is not a gap in the pitch — the boundary is the pitch.
Illustrative product experience
One clear view of every savings program.
These demonstration screens show how the platform is designed to connect setup, contributions, payouts, exceptions, and reporting.
01 / 08
Scroll or drag to explore
Founder Growth CohortCycle 04 of 10 · Monthly
Members
10 / 10
Pool / cycle
10,000 AED
Collected C4
9,000 AED
Open cases
1
| Recent activity | By | When |
|---|---|---|
| Contribution recorded — S. Okafor, C4 1,000 | Organizer | 04-02 09:14 |
| Payout confirmed — L. Haddad, C3 10,000 | Member | 04-05 18:40 |
| Resolution opened — Member 07, C4 | System | 04-07 00:01 |
Create circleStep 2 of 4 — Members
1 · Terms2 · Members3 · Slots4 · Review
| Invite | Contact | Status |
|---|---|---|
| A. Mansoori | a.mansoori@… | Joined |
| R. Kapoor | r.kapoor@… | Joined |
| L. Haddad | l.haddad@… | Invited |
Send invitesAdd member
Contribution matrixAED · per cycle2
| Member | C1 | C2 | C3 | C4 | Total |
|---|---|---|---|---|---|
| A. Mansoori | 1,000 | 1,000 | 1,000 | 1,000 | 4,000 |
| R. Kapoor | 1,000 | 1,000 | 1,000 | 1,000 | 4,000 |
| L. Haddad | 1,000 | 1,000 | 1,000 | — | 3,000 |
| S. Okafor | 1,000 | 1,000 | 1,000 | 1,000 | 4,000 |
| M. Rahal | 1,000 | 1,000 | 1,000 | 1,000 | 4,000 |
| Member 07 | 1,000 | 1,000 | 1,000 | late | 3,000 |
PayoutsDual-confirmation4
| Cycle | Recipient | Amount | State |
|---|---|---|---|
| C1 | A. Mansoori | 10,000 | Sent · Received |
| C2 | R. Kapoor | 10,000 | Sent · Received |
| C3 | L. Haddad | 10,000 | Sent · Received |
| C4 | S. Okafor | 10,000 | Pending pool close |
A payout closes only when bank operations marks it sent and the recipient confirms receipt.
Members10 of 10 confirmed
| Member | Slot | Contributed | Standing |
|---|---|---|---|
| AMA. Mansoori | 01 | 4,000 | Good |
| RKR. Kapoor | 02 | 4,000 | Good |
| LHL. Haddad | 03 | 3,000 | C4 due |
| M7Member 07 | 07 | 3,000 | Case open |
ScheduleDerived from locked terms
| Cycle | Due date | Recipient | State |
|---|---|---|---|
| 01 | 2026-02-01 | A. Mansoori | Complete |
| 02 | 2026-03-01 | R. Kapoor | Complete |
| 03 | 2026-04-01 | L. Haddad | Complete |
| 04 | 2026-05-01 | S. Okafor | Current |
| 05 | 2026-06-01 | M. Rahal | Scheduled |
Ledger & auditProvenance on every line1
| Event | Example hash | Future proof |
|---|---|---|
| #118 Contribution — S. Okafor, C4 | 0x7f3a…c9 | Illustrative |
| #122 Payout confirmed — L. Haddad, C3 | 0x41be…02 | Illustrative |
| #124 Correction — reverses #118 · wrong cycle3 | 0x9d07…5f | Illustrative |
| #125 Contribution re-recorded — S. Okafor, C4 | 0x2c8e…7a | Illustrative |
A correction never edits history. It reverses an entry and adds its own — the trail stays whole.
Member statement — L. HaddadIssued 2026-04-30
| Line | Amount |
|---|---|
| Contributions paid · 4 cycles | AED 4,000 |
| Pool received · Cycle 03 | AED 10,000 |
| Contributions remaining · 6 cycles | AED 6,000 |
| Corrections affecting statement | 0 |
Export PDFExport CSV
Product demonstration · all data illustrative · no live customer information
Your circleMember view
Your slot
03
Cycle
04 / 10
AED 1,000Due 05-01
AED 10,000Received
Through cycle 04PDF · CSV
Open statement
1Provenance and audit chips on every recorded event
2Monospaced ledger numerals — figures read as records, not marketing
3Correction trails that reverse entries without erasing history
4Dual-confirmation states on every payout
For organizers
Run the circle. Keep the trust.
Lose the spreadsheet.
If you are the person everyone trusts to hold the list, Stashr is built for you. The circle stays exactly as human as it always was — the record-keeping stops being your burden to carry alone.
The record, kept for you
No more reconciling chat threads against a notebook the night before a payout. Contributions, cycles, and slots live in one place every member can see.
Fairness you can point to
The slot order is fixed and visible from day one. When a disagreement starts, it ends at the record — not at your doorstep.
Authority without awkwardness
Late payments become cases with resolutions and deadlines — a process, not a personal confrontation between friends.
The circle was always built on trust.
Stashr simply gives trust a paper trail.
Communities
Employers & teams
Associations & clubs
Founders & friend groups
Faith communities
Designed for bank-led deployment
A faster path to structured savings programs.
Stashr is being built as a technology and program layer for banks. A future partner bank would own the customer relationship, accounts, compliance, money movement, and every regulated activity.
One program · two clearly defined roles
The bank owns
Regulated domain- B1Customer relationship & accounts
- B2KYC, AML & eligibility
- B3Custody & money movement
- B4Regulated products & financial risk
- B5Eligibility
- B6Regulated financial products
- B7Financial risk
Stashr owns
Operating layer- S1Program & group coordination
- S2Schedules, rotation & workflows
- S3Reconciliation & reporting tools
- S4Operational records & audit support
- S5Reporting
- S6Structured records
- S7Audit evidence
Stashr provides the configurable operating layer
The bank provides the regulated financial layer
Stashr is not a bank and does not claim to provide regulated financial services today.
Enterprise controls & architecture
A clear system of record, designed to grow with institutions.
The current foundation uses PostgreSQL and PII-conscious event records. The architecture is designed so future bank deployments can add provider-neutral verification and external anchoring where required.
01A dependable source of truth
Core program data is designed to remain in a clear, conventional application record.
02Privacy-conscious event records
The current build records selected events without placing personal data into external proofs.
03Verification when the model requires it
External anchoring remains a roadmap capability—not a claim that a live bank ledger is operating today.
The commercial case for banks
A new savings opportunity without a new operating stack.
Stashr is designed to help banks serve an established financial behavior with a configurable platform, clearer operations, and a faster path to market.
01 / 05
Existing bank infrastructure
Scroll to activate the programme layer
B-01
Faster go-to-market
Start from a purpose-built program layer instead of building every workflow from the ground up.
B-02
Customer acquisition
Reach founders, SMEs, and communities through a savings behavior already built on trusted networks.
B-03
Deposit potential
Bank-led programs can create recurring contribution activity and deeper primary-account relationships.
B-04
Engagement & retention
Each cycle creates a reason for participants to return, contribute, and stay connected to the bank.
B-05
Operational visibility
Structured workflows make schedules, exceptions, contribution status, and payout progress easier to follow.
B-06
Auditable workflows
A consistent event history can support operations, oversight, reporting, and future control requirements.
B-07
Future product expansion
With the right approvals, savings behavior can become a foundation for new services and capital pathways.
B-08
Flexible commercial model
The business can grow through bank partnerships, platform licensing, implementation, support, reporting, and future modules.
Roadmap/ a staged platform buildout
From structured circles to a broader financial operating layer.
Stashr begins with the operating foundation for rotating savings. Each later stage depends on product maturity, bank partnerships, security review, and the right legal and regulatory pathway.
Stage 1Current build
Structured savings foundation
The current foundation focuses on group setup, invite-based enrollment, schedule design, slot order, and a privacy-conscious event history.
Stage 2Next
Bank-led savings programs
The roadmap moves toward pilot-ready program operations, reconciliation, reporting, security review, and bank partnership—while the bank retains regulated responsibilities.
Stage 3Future modules
Capital pathways & protection
Subject to partner, legal, Shariah, and regulatory approval, future modules may include:
- Early-access or accelerated payout pathways
- Structured default and resolution handling
- Protection and risk-mitigation layers
- Formally reviewed Shariah-aligned structures
Stage 4Long-term vision
A modular financial platform
Over time, Stashr can support more segments, more institutions, expanded reporting, financial-behavior intelligence, and regulated modules delivered through the right partners.
Frequently asked questions
Clear answers about the product, buyer, and roadmap.
Stashr is building the operating layer for structured rotating savings programs. It turns an informal group-saving model into clearer workflows, records, reporting, and future bank-led infrastructure.
A ROSCA is a group that contributes a fixed amount on a regular schedule. The full pooled amount goes to one participant each cycle until everyone has received once. It is also known as a jamiyya, gameya, susu, or chit circle in different markets.
The commercial buyer is expected to be a bank or financial institution. The programs are designed to serve founders, SMEs, and other trusted communities that save collectively.
No. Founders and SMEs are the starting focus because structured pooled capital can be especially useful for business planning and growth. The same operating model can support other communities and segments over time.
Stashr is designed to shorten the path to a structured savings product. It can support customer acquisition, recurring deposits, engagement, operational visibility, reporting, and future product expansion without requiring the bank to build every workflow from scratch.
No. The current product is non-custodial and has no live bank integration. In a future bank-led model, the partner institution would own the accounts, custody, compliance, and money movement. Stashr would provide the operating software.
The planned B2B model can include bank partnerships, platform licensing, implementation, support, reporting, and future modular services. Commercial terms would depend on the partner and deployment model.
The roadmap moves from the current group-management foundation toward bank-led savings programs, contribution and payout operations, default handling, protection layers, expanded reporting, and future capital-access pathways.
Potentially, but not by claim alone. The rotating savings model is interest-free in principle. Any Shariah-aligned or regulated module would require formal review, certification where relevant, the right institutional partner, and all necessary approvals.
Stashr is building toward the bank-led model described here. Bank integration, custody, licensing, and regulated modules are not presented as live today.
Build the next generation of structured savings
Turn an established behavior into scalable financial infrastructure.
We are building for banks, investors, and ecosystem partners who see the opportunity in collective saving, clearer coordination, and long-term capital access.
A focused conversation starts here.