---
title: "Fintech-Adjacent Apps Without Holding Money | FLUIDS"
description: "When an app only records payments and when it moves or holds funds, design choices that keep you an organizer, and when you need a licensed partner."
url: https://fluids.digital/blog/fintech-app-without-holding-money
language: en
---
[Home](https://fluids.digital/) [Blog](https://fluids.digital/blog) Fintech without holding money

[Savings circles (jam'iya)](https://fluids.digital/blog#savings-circles)

# Building a fintech-adjacent app without holding money: the organizer model

[FLUIDS Digital](https://fluids.digital/about) Published 1 November 2026 7 min read

The short answer

An app that only records and organizes payments made elsewhere, without holding balances or moving funds, follows the organizer model. Members pay each other through their own banks, then record the payment and attach a receipt in the app. Once an app collects money into an account it controls, pays it out or holds balances that users can spend or withdraw, it becomes a payment or stored-value service; in Saudi Arabia those are regulated by the Saudi Central Bank (SAMA), so confirm your model with qualified counsel before you design it.

## Key takeaways

- Recording that a payment happened is a different activity from moving or holding the money, and the product should make that difference obvious.
- Payment, wallet and stored-value services in Saudi Arabia are regulated by the Saudi Central Bank (SAMA); confirm where your product sits with qualified counsel.
- No balances, no pooled account, payments made in the member's own bank and a receipt uploaded afterwards keep an app in the organizer model.
- The organizer model gives up automatic collection and payment guarantees in exchange for a simpler, lower-risk product.
- If you need to collect, hold or disburse funds, integrate a licensed partner rather than building money movement yourself.

## When an app organizes money and when it moves or holds it

An app organizes money when it records facts about payments that happen somewhere else; it moves or holds money when funds pass through, or sit in, an account the app's operator controls. The difference sounds technical, but it decides your regulatory position, your risk and a large part of your build.

Many products people call fintech are really organizers: a jam'iya (rotating savings circle) tracker, a shared-expenses list, a family fund ledger, a rent schedule between a landlord and tenants. They need records, schedules, reminders and receipts. They do not need to touch the money, and they become much harder to build and run if they do.

Three activities usually mark the line. **Custody** means funds sit in an account the business controls, even briefly. **Transfer or processing** means the app initiates, routes or settles a payment between parties. **Stored value** means users have a balance in the app that they can spend or withdraw. An app that does none of these, and says so clearly, is in the organizer model.

Jameyatek, the savings-circle organizer FLUIDS designed and built, is a clear example. It is an organizational tool only: it does not transfer, process or store any money, and all financial arrangements between members happen outside the app, as the members' own responsibility. A payment record documents the group's arrangement; it is not a transfer executed by the app.

## Organizer, payment partner, wallet or pooled account: the models compared

There are four common ways an app can relate to the money in its workflow. They differ in what the app does with funds, in regulatory exposure and in how much there is to build.

| Model | What the app does with money | Regulatory exposure | Build and run effort | Fits |
| --- | --- | --- | --- | --- |
| Organizer | Nothing. Users pay through their own banks; the app records it and stores receipts | Lowest; data protection still applies | Lowest: records, schedules, receipts, notifications | Savings circles, family funds, shared expenses |
| Licensed payment partner | Sends users to a licensed provider's checkout or payment link; stores the outcome | Moderate; the partner carries the regulated activity, contract terms matter | Moderate: integration, reconciliation, failure handling | Marketplaces, bookings, subscriptions |
| Wallet or stored value | Users hold balances in the app, top up and withdraw | High; a regulated activity in Saudi Arabia | High: ledger, compliance controls, licensing or a licensed operator | Payment products themselves |
| Pooled account held by the business | Collects members' money into the business's account and pays it out | High, and often unclear; seek counsel before considering it | High, plus operational and trust risk | Rarely the right choice for a startup |

The table is a map, not legal advice. Where a specific product falls depends on its exact flows, and regulators look at what actually happens to the money, not at what the product calls itself. That is why the conversation with counsel belongs at the start of scoping, not after launch.

## Why the line matters in Saudi Arabia

The line matters because payment, wallet and stored-value services in Saudi Arabia are regulated by the Saudi Central Bank (SAMA). An app that holds other people's money, issues balances or moves funds between users is likely to be doing something in that regulated space, and it may need a licence or a licensed partner to do it.

Handling funds also tends to bring obligations beyond the licence itself, such as identifying customers and controls against money laundering, along with expectations about security, complaints and record keeping. Those are serious, ongoing responsibilities. For a team whose real goal is to help a group stay organized, they are usually a distraction from the product.

If your users or your company are outside Saudi Arabia, other regulators and rules apply, and they differ by country. The principle is the same everywhere: work out what your product does with money, then ask a qualified lawyer what that means where you operate.

This article explains product and engineering choices. It is not legal advice. Confirm your model, wording and flows with qualified counsel familiar with SAMA's current rules before you build.

## Design choices that keep an app in the organizer model

Staying an organizer is a set of concrete product decisions, from the data model to the button labels. These are the ones that matter most:

- **No balances.** The data model stores payment records and statuses, never a running balance that looks like money held for the user.
- **Pay in the member's own bank.** Show the recipient's name and IBAN to copy, or a link that opens the member's banking app where that is supported. The transfer happens entirely outside your product.
- **Receipt upload, then confirmation.** The member attaches a receipt to the month or request it belongs to, and the organizer confirms it after checking the receiving account. Jameyatek attaches an optional receipt to the month it belongs to.
- **Wording that matches reality.** Use "record payment" or "I've paid", not "pay now" or "send money", so no one believes the app moved the funds.
- **A plain statement of the boundary.** Say in onboarding, the help page and the terms that the app does not hold or transfer money, as Jameyatek's case study does.
- **No fees tied to transfers.** Charging per transaction implies you are part of the transaction. If the product is paid, tie the price to the service, such as a subscription for organizers.
- **Scoped visibility.** Members see only their own group's records. Receipts and bank details are personal data and should be visible only to the people who need them.

Each choice is small on its own. Together, they make a product whose behaviour, wording and data all say the same thing: this app keeps the record, and the money stays in the members' banks.

## What the organizer model gives up, and what it gains

The organizer model gives up control of the money in exchange for simplicity. Be honest with users and with yourself about both sides.

What you give up: the app cannot collect payments automatically, cannot guarantee that a member pays, and cannot release funds when conditions are met. Verification is manual, usually by an organizer comparing receipts with a bank account. Trust between members still carries the arrangement; the app makes it visible but does not secure it.

What you gain: a smaller first release, fewer integrations, no balances to reconcile, and a much lighter compliance burden, while data protection still applies. Members keep using banks they already trust. And if something goes wrong between members, the app has not been holding their money, which protects both them and you.

For most savings circles, family funds and shared-expense groups, that trade is the right one. The groups already exist and already move money between themselves; what they lack is a shared record. The organizer model supplies exactly that, as described in [tracking jam'iya payments](https://fluids.digital/blog/savings-group-payment-tracking).

## When you need a licensed payment partner

You need a licensed partner when the product's value depends on the app itself collecting, holding or paying out money. Typical signs:

- Users expect to pay inside the app and have the payment confirmed automatically.
- The business wants to collect a pool and release it on a date or condition.
- You want automatic recurring debits instead of reminders.
- Your revenue model takes a share of each transaction.
- Users ask to see a balance they can withdraw.

In those cases, integrate a bank or a payment provider authorised to carry out that activity, and let them hold and move the funds. Your product then stores references to the partner's transactions instead of the money itself. The partner's terms, fees and onboarding requirements become part of your scope, and counsel should still review the flow.

An organizer can evolve. If you design payment records with room for an external transaction reference from the start, a later integration attaches to the same records rather than replacing them. Jameyatek shows the organizer end of that spectrum; the patterns also carry over to [family and staff fund apps](https://fluids.digital/blog/family-fund-app).

FLUIDS designs and builds products on both sides of this line for companies and founders in Saudi Arabia and the GCC. Read the [Jameyatek case study](https://fluids.digital/projects/jameyatek), our overview of [fintech products](https://fluids.digital/industries/fintech), or how we approach [custom software development](https://fluids.digital/custom-software) when a workflow does not fit an existing tool. If you are still deciding what a jam'iya product should include, start with the [jam'iya app guide](https://fluids.digital/blog/jamiya-app).

Built by FLUIDS

## Jameyatek

![Jameyatek payment receipts screen in Arabic: a confirmed bank-transfer receipt for one month, a receipt awaiting review with confirm and reject buttons, and a log of confirmed receipts](https://fluids.digital/images/projects/jameyatek/04.webp)

An organizational tool for shared savings groups — track commitments and schedule payouts in one place.

[Read the Jameyatek case study](https://fluids.digital/projects/jameyatek)

## Frequently asked questions

**Does an app that tracks payments need a SAMA licence?**

It depends on what the app does with the money. An app that only records payments made elsewhere is in a different position from one that holds or moves funds, but only qualified counsel can confirm where a specific product sits.

**What is the organizer model?**

It is a product design in which users pay each other through their own banks and the app only records the payments, schedules and receipts. Jameyatek follows it: it does not transfer, process or store any money.

**Can an organizer app add in-app payments later?**

Yes, by integrating a licensed partner that holds and moves the funds. Designing payment records with room for an external transaction reference makes that step easier.

**Is showing an IBAN in the app the same as processing a payment?**

Showing details so a member can transfer from their own bank is generally different from initiating or settling the payment, but confirm your exact flow with counsel.

**Can FLUIDS build a fintech-adjacent app for us?**

Yes. We map what your product does with money first, recommend that you confirm the model with counsel, and then scope either an organizer design or a licensed-partner integration. Scope, price and timeline are agreed in a written proposal before development.

## Further reading

- [Saudi Central Bank (SAMA)](https://www.sama.gov.sa/)
- [Jameyatek case study](https://fluids.digital/projects/jameyatek)

In this article

When an app organizes money and when it moves or holds it Organizer, payment partner, wallet or pooled account: the models compared Why the line matters in Saudi Arabia Design choices that keep an app in the organizer model What the organizer model gives up, and what it gains When you need a licensed payment partner Questions

Planning a similar product? We design, build and launch it, and you own the code.

[Discuss your project on WhatsApp](https://wa.me/966559508798?text=Hi%20FLUIDS%2C%20I%20read%20your%20article%20%22Fintech%20without%20holding%20money%22%20and%20would%20like%20to%20discuss%20a%20similar%20project.)

Related development services

## From the idea to a working product

- [Custom software development](https://fluids.digital/custom-software)
- [Mobile app MVP guide](https://fluids.digital/mvp-development/mobile-app)

Savings circles (jam'iya)

## Keep reading

[### Jam'iya apps Jam'iya app: how to organize a savings circle digitally](https://fluids.digital/blog/jamiya-app) [### Jam'iya payment tracking Tracking jam'iya payments: monthly records, receipts and the commitment rate](https://fluids.digital/blog/savings-group-payment-tracking) [### Family and staff fund apps Family and staff fund apps: contributions, requests and transparency](https://fluids.digital/blog/family-fund-app) [### Jam'iya turn schedules Fair payout order in a jam'iya: turn schedules, shares and swaps](https://fluids.digital/blog/rotating-savings-turn-schedule)

## Turn the idea into a written scope

A short call to understand your users and workflow, then a written proposal covering scope, timeline and price before development starts.

[Start on WhatsApp](https://wa.me/966559508798?text=Hi%20FLUIDS%2C%20I%20read%20your%20article%20%22Fintech%20without%20holding%20money%22%20and%20would%20like%20to%20discuss%20a%20similar%20project.)