Bubble developer needed-transaction/ledger system

Jobs / Freelance
1

Hi Bubble community,

I’m looking for a senior Bubble developer to help build the core

architecture of a transaction / ledger-based application.

Scope (architecture-first, not UI-heavy):

- Transaction + Balance data model

- From/to balance transactions

- Immutable (locked) transactions

- Reversal-only corrections

- Option sets for transaction type and status

- Clean privacy rules (user vs admin)

- Minimal internal UI for testing (no polish required)

This is not a marketplace or basic CRUD app.

Data integrity and correctness matter more than speed.

Please reply with:

- Relevant Bubble projects (especially finance / ledger-style apps)

- Your hourly rate

- Estimated hours for the above scope

- Availability in the coming weeks/months

Thanks,

Nichole / Gord

2 Likes
2

Hey @anon79875262 :waving_hand:

Welcome to the Bubble Community :tada:

Are you wanting to connect to a bank account?

3

Hi there @anon79875262 will send you a message feel free to email

nocodeembassey@gmail.com

book a call

Or visit

nocodeembassey.com

4

Thanks for asking — no, this is not a bank integration at this stage.

The scope is a ledger-first internal accounting system:

  • Virtual balances only

  • No direct bank writes

  • No payment rails in v1

When external accounts are introduced later, the ledger remains the source of truth and bank activity is treated as external events that generate ledger entries — never the other way around.

Right now the focus is:

  • Immutable transaction architecture

  • Reversal-only corrections

  • Strong privacy + audit enforcement

I’m intentionally separating ledger integrity from payment connectivity.

1 Like
5

Got it. Thanks for the clarity, that definitely simplifies things.

It might be worth a chat to see if we might be a good fit.

Relevant bubble projects and hourly rates are available on our site.

We can chat to discuss in details an estimate of hours and availability in the coming weeks/months. :blush:

Hope to hear from you soon.

6

Hey @anon79875262 , sent you a DM, lets chat!

7

Hey @anon79875262 ,

Maybe you’d like to see some other options. Kindly check DM. Thanks.

Best,
Jayson Tobes
BDR, RapidDev

8

Hey Nichole, just an FYI - truly immutable transactions will not be supported through Bubble’s native database features. Of course, you could still leverage front-end & other capabilities from Bubble but if you want cryptographically enforced immutability you’ll need to either:

  1. Store transactions as smart contract calls on an existing public chains like Ethereum, Polygon, or Solana, OR store transactions on permissions/enterprise chains like Hyperledger, Fabric, Corda
  2. Use an external database like EventstoreDB, Postgres via Supabase or DynamoDB via AWS, and then maintain it like a database that is append-only and doesn’t allow update/deletes

Both of these approaches are quite a bit more complicated than building natively in Bubble (especially nr. 1). If building on Bubble database you can block users from changing/deleting records in front-end & via API but you can’t stop a Bubble admin from changing the database in the editor. If I were you I’d question whether the data integrity is as important as you make it out to be - blockchain based databases are usually overkill for the vast majority of use cases.

9

Spot on regarding the Bubble Editor—though to be fair, this applies to almost all traditional software stacks (SQL, AWS, etc.), where the System Owner or Root User technically always has direct access to the raw data.
In my experience, when clients ask for this, they are usually concerned with Application-Level Immutability (ensuring that Staff, Admins, and Users and roles cannot alter transactions via the dashboard or API). For 99% of business use cases, a strict append-only schema with Privacy Rules is the right Phase 1 solution without the massive overhead of external chains.

1 Like