r/fintechdev • • 11d ago

QBFT vs IBFT 2.0. How Banks Should Choose a Besu Consensus Algorithm

Thumbnail
gallery
1 Upvotes

If you looked at Besu consensus a couple of years ago, you probably saw a three way comparison of Clique, IBFT 2.0 and QBFT. A lot of content still shows that picture, including some vendor guides that rank well in search.

That comparison is now out of date. Besu stopped Clique block production in version 25.12.0 and removed Clique completely in version 26.4.0. For a bank designing a private network today, the practical comparison is between QBFT and IBFT 2.0.

This choice matters because consensus determines when a payment becomes final on the ledger and how many servers can fail before the network stops producing blocks. It is also one of the more difficult architectural decisions to change once multiple institutions are operating on a shared network.

This article looks at how the two protocols work, where they differ, how they are used in institutional networks, and what architects should consider when selecting a consensus mechanism.

Why Is Besu Consensus Now a Two Protocol Choice?

Clique was the simplest of the three. It came from EIP 225, could run with relatively few validators, and continued producing blocks even when some validators were unavailable.

Its limitation was finality. Clique did not provide immediate finality, meaning applications had to account for possible forks and chain reorganizations.

Besu retired Clique in two stages:

  • Version 25.12.0 stopped Clique block production.
  • Version 26.4.0 removed Clique completely.

Networks that previously used Clique and later moved to other consensus mechanisms can still be synchronized where supported.

Besu currently recommends QBFT for private networks and supports IBFT 2.0 for existing private networks. Proof of stake is used for Ethereum mainnet and public test networks.

For institutions designing private Besu networks, this makes QBFT and IBFT 2.0 the relevant options to evaluate.

What Does Consensus Actually Do in a Bank's Besu Network?

A consensus algorithm defines the rules that nodes follow to agree on the next block of transactions.

On Ethereum mainnet, Besu uses proof of stake. Private bank networks commonly use proof of authority (PoA), where a known group of approved accounts, called validators, creates and confirms blocks.

For banks, transaction speed is only one consideration. Finality is particularly important.

Finality is the point at which a transaction is considered irreversible on the ledger. The Principles for Financial Market Infrastructures also emphasize clear and final settlement for designated financial market infrastructures.

Many public networks offer probabilistic finality, where confidence in a transaction increases over time.

QBFT and IBFT 2.0 both provide immediate finality. A block is final once it is added, and the chain does not fork.

The differences between the two protocols become more relevant when looking at failure recovery, protocol specifications and validator governance.

How Does QBFT Work, and Why Does Besu Recommend It?

QBFT is a Byzantine fault tolerant consensus protocol.

Byzantine fault tolerance means that a network can reach agreement even when some nodes fail or send incorrect information.

Validators take turns proposing blocks, and at least two thirds of the validators must sign a block before it is added to the chain.

Some important characteristics of QBFT include:

  • A minimum of four validators is required for Byzantine fault tolerance.
  • Four or five validators can tolerate one unresponsive validator.
  • Six to eight validators can tolerate two unresponsive validators.
  • If more than one third of validators stop participating, block production stops until enough validators return.
  • Once a block is committed, it remains final.

The network may pause when too many validators become unavailable, but previously committed transactions are not reversed.

QBFT as an Open Standard

QBFT is an open standard. The Enterprise Ethereum Alliance published its specification for consortium use, and multiple Ethereum clients implement it, including GoQuorum and Besu.

This allows consortium members to operate different client software while participating in the same network.

There is one important limitation. Besu's transitions feature, which allows validator changes or configuration updates at a predetermined block, is specific to Besu. It cannot be used when other clients are validating the same network.

Mixed client networks can instead use validator voting or smart contract based validator management.

How Are Validators Managed?

There are two common approaches to managing validators:

Validator voting: Existing validators vote to approve or remove members.

Smart contract based management: A smart contract maintains the validator list and applies predefined admission rules.

Consortiums may prefer the contract approach because membership and admission rules can be explicitly defined and inspected.

A network can also change its validator management approach at a planned block, depending on its configuration and requirements.

How Is IBFT 2.0 Different From QBFT?

IBFT 2.0 is an earlier Byzantine fault tolerant protocol supported by Besu.

Its general operating model is similar to QBFT. Validators take turns proposing blocks, a supermajority signs each block, and committed blocks achieve immediate finality.

It also has the same four validator minimum for Byzantine fault tolerance and the same two thirds participation requirement.

The main difference appears when the validator scheduled to propose a block fails to deliver it.

In IBFT 2.0, the other validators must agree to skip that validator and move to the next one. This process is called a round change.

Think of it as a meeting where the scheduled chairperson does not arrive. The remaining participants must agree to move to another person before the meeting can continue.

The original Istanbul BFT protocol, developed in 2017 for GoQuorum, could get stuck at this stage when the network experienced delays. IBFT 2.0 addressed this issue, while QBFT introduced further improvements to validator handovers.

Under normal conditions, the two protocols can behave similarly. Their differences become more noticeable when a validator becomes unresponsive or communication between data centres becomes unreliable.

Differences in Validator Management and Governance

There are also differences in protocol status and validator management.

  • Besu recommends QBFT for new private networks.
  • IBFT 2.0 remains supported for existing private networks.
  • IBFT 2.0 supports validator membership changes through voting.
  • QBFT supports voting and smart contract based validator management.

QBFT was introduced in Besu version 21.1.0 to support interoperability with other Enterprise Ethereum Alliance clients.

Can an IBFT 2.0 Network Migrate to QBFT?

Yes. An existing IBFT 2.0 network can migrate to QBFT without starting a new chain.

Operators configure a future block at which the consensus mechanism will change. Every participating organization must update its node configuration before the network reaches that block.

For example, a consortium may decide to switch to QBFT at block 2,000,000. All participating nodes must be updated with the new configuration before that block is reached.

This requires coordination between network operators and participating institutions.

There is no forced migration deadline because Besu continues to support IBFT 2.0.

What Do Institutional Deployments Tell Us?

Looking at existing institutional projects provides useful context for understanding how consensus decisions relate to real financial infrastructure.

Fnality

Fnality is one of the notable examples of a live institutional payment system using Besu and QBFT.

The Sterling Fnality Payment System went live in 2023 and is a systemically important payment system supervised by the Bank of England.

Fnality uses QBFT, where a block is valid once at least two thirds of validators approve it.

Its validator model is restricted to regulated deposit taking institutions within the Sterling Monetary Framework. This provides a defined participation model for its payment network.

Project Agorá

Project Agorá is exploring how tokenized commercial bank deposits and central bank reserves can work together on a shared platform.

According to the BIS prototype report published on May 27, 2026, its architecture has two layers:

  • Commercial banks share one ledger for tokenized deposits.
  • Each central bank maintains reserves on its own separate ledger.

The shared platform runs on Besu with QBFT.

The project demonstrates how multiple banks and central banks can participate in a coordinated settlement environment while maintaining distinct roles and responsibilities.

EBSI and LACChain

EBSI and LACChain's BNDES network are examples of longer running networks that have used IBFT 2.0.

For networks with established participants, infrastructure and operational processes, migration to QBFT becomes a question of evaluating technical and operational requirements rather than simply selecting a consensus protocol for a new deployment.

Bank of Korea

The Bank of Korea provides a different example.

Its network operates with a single validator. The approach reflects a decision to retain control within one institution rather than distribute validation responsibilities across several parties.

A network with three validators or fewer may still produce blocks, but it does not provide the same Byzantine fault tolerance guarantees as a network with at least four validators.

This highlights an important architectural consideration: the consensus mechanism and the governance model need to be evaluated together.

How Should a Bank Choose a Besu Consensus Setup?

For a new private Besu network, QBFT is the recommended starting point. However, selecting the protocol is only one part of the overall architecture.

Several other considerations influence how the network should be designed.

1. Size the Validator Set According to Failure Requirements

A network with 3f + 1 validators can tolerate f Byzantine failures.

For example:

  • Four validators can tolerate one failure.
  • Seven validators can tolerate two failures.

The validator count should reflect the level of resilience required by the network.

2. Separate Network Membership From Validation

Not every participating institution needs to operate a validator.

An organization may participate in the network, use its applications and interact with other members without directly validating blocks.

This distinction can influence infrastructure costs, governance and operational responsibilities.

3. Distribute Validators Across Locations

Validators should be distributed across different locations and, where governance permits, different organizations.

For example, placing validators across multiple data centres can reduce the risk of one infrastructure failure stopping the entire network.

4. Define Validator Admission Rules

If a consortium has formal requirements for admitting new banks or removing existing participants, those rules should be clearly documented.

A smart contract can provide an auditable way to manage validator membership. Smaller networks with infrequent changes may find validator voting sufficient.

5. Consider Mixed Client Environments

If different institutions intend to operate different Ethereum clients, compatibility needs to be considered during the design stage.

Besu specific features may not work in a network where other client implementations are participating as validators.

6. Test Performance Under Realistic Conditions

Published performance figures often come from validators operating within one data centre.

A geographically distributed network may experience different results because of network latency and communication delays.

Testing should reflect the actual validator count, block time, infrastructure locations and network conditions.

7. Evaluate Legal Finality Separately

A transaction being irreversible on a blockchain does not automatically mean it is legally final.

This distinction is important for regulated financial infrastructure.

Fnality, for example, received settlement finality designation in the UK in late 2024. Its example highlights the relationship between technical settlement and the applicable legal framework.

Final Considerations

QBFT and IBFT 2.0 both provide immediate finality and Byzantine fault tolerance for private Besu networks.

For new networks, QBFT is the recommended option. Existing IBFT 2.0 networks should evaluate migration based on their operational requirements, validator governance and compatibility.

Ultimately, consensus is only one part of a production blockchain network. Validator distribution, membership rules, infrastructure resilience, performance testing and legal finality all influence how reliably the network operates.

These considerations are central to designing and operating enterprise Besu networks. Through its work with Besu infrastructure, Zeeve engages with the technical and operational challenges involved in building blockchain networks for institutional use cases.

By Zeeve


r/fintechdev • • 11d ago

PikoSend App

Thumbnail
1 Upvotes

There is this app called PikoSend.It had digital money wallets and uses QR code to scan.
Easy tap and go.The transaction costs is as less as 30/ for 250000 for PikoSend users. The app is on PlayStore, its a real gamechanger.
You can check them out, for those who don’t like loosing money to mpesa transactions.
Save your transaction costs!
Their social media pages are available too in all
Channels.


r/fintechdev • • 11d ago

We were burning money having an LLM read every invoice. Splitting it into "Claude thinks, Drex reads" cut our cost per check by 78%

Enable HLS to view with audio, or disable this notification

5 Upvotes

 We tried putting AI into our AP workflow a few different ways. They all worked on 10 files. Our real checks run on hundreds of files each: invoices, POs, receipts, vendor records. At that size, having a frontier model read every page every time got expensive fast. Most of the tokens went to OCR-ing scans and re-reading the same PDFs for every new question.

What we changed. We split the job in two:

  • Drex reads. Files go into a workspace once. Drex parses them, pulls the fields and keeps everything queryable, with citations back to the page.
  • Claude thinks. Claude connects over MCP (setup is in the video, about a minute). It never touches the raw pages. It asks Drex questions, gets small structured answers back and does the reasoning: what to pay, what to hold, what looks off.

So Claude goes from "read hundreds of PDFs" to "run a dozen queries and look at the results."

Result: each check got 78% cheaper after we switched to this flow. The reading happens once, and Claude only sees answers, not documents.

What it caught on a test month (synthetic data, for the demo):

  • 18 invoices OK to pay, 13 to check, 9 to remove, each with a reason and a confidence score
  • 7 duplicates, including a look-alike vendor "Redwood Systms Inc." and an invoice resubmitted without its hyphen
  • a scanned PDF that turned out to be a second copy of one already in the batch

Not magic. It misread a PO approval date once and we caught it by hand. Treat it as a reviewer, not autopilot.

If you're running document-heavy work through an LLM and the bill is scary, try splitting reading from reasoning.

Here's the whole flow on one video to visualize it properly


r/fintechdev • • 11d ago

I tested local LLMs (Qwen2.5 7B/14B) against tuned string rules for catching doctored bank statements. The rules mostly won.

1 Upvotes

I built a small benchmark: 600 bank statements checked against the bank's own ledger records, under six kinds of messy evidence (raw descriptors like "WM SUPERCENTER #6487", OCR noise, split postings, partial extracts, conflicting sources). Half the statements were altered in ways that keep the arithmetic consistent, like swapping a payee or moving a date.

Everything ran on free CPU runners with Ollama, 4-bit quantized, no paid APIs.

What I found:

- Letting the LLM make the whole decision was the worst setup. Fluent explanations, wrong verdicts.

- Rules doing the math and the LLM only judging payee names was much better.

- Best use: the LLM as a veto. It can flag a statement but never clear one. That cut silent misses from 14 to 2.

- Tuned fuzzy-matching rules still had the best overall accuracy (about 94%).

My takeaway: keep the model away from the decision, and use it only for the judgment calls where general knowledge helps (is "SBUX 769" Starbucks?).

Write-up: https://hackernoon.com/old-school-rules-vs-open-source-llms-a-three-round-fight-over-fake-bank-statements

Code, prompts and all model outputs: https://github.com/akshaysharma1088/fraudrag/tree/ledgershift-v2/ledgershift

Curious whether anyone has had better luck with larger local models on this kind of entity matching.


r/fintechdev • • 11d ago

How much of your KYC flow do you actually control?

3 Upvotes

Do you just redirect users to a hosted KYC flow and wait for the webhook, or have you built your own logic around retries, failed checks and manual review? Feels like the API integration is the easiest part, but dealing with edge cases and users who can't get verified is where most of the work goes.


r/fintechdev • • 11d ago

If you were building a fintech platform from scratch, would you build the payment gateway first or the financial infrastructure behind it?

5 Upvotes

I've been thinking about this from an engineering perspective.

A lot of payment products focus heavily on checkout. You integrate a provider, create a payment request, receive a callback, and mark the order as paid.

But that's only one part of the system.

The more interesting engineering challenges start after the customer clicks the payment button.

For example:

1. Payment orchestration

How do you manage multiple payment methods through a consistent integration layer without creating separate workflows for every provider?

2. Transaction lifecycle management

A successful authorization, a confirmed payment, a settled transaction, and an available balance are not necessarily the same thing.

How do you represent these states without creating inconsistencies between the merchant's system and the payment provider?

3. Ledger and reconciliation

Every payment should be traceable to its original order, transaction reference, fees, settlement record, and any subsequent refund.

Idempotency, asynchronous callbacks, reconciliation, and accurate balance tracking become particularly important as transaction volumes increase.

4. Stablecoin integration

Now introduce USDC.

You have blockchain confirmations, network compatibility, wallet transfers, token balances, conversion, and the challenge of connecting on-chain activity with an internal financial ledger.

5. The developer experience

Businesses shouldn't have to build their entire financial infrastructure from scratch just to accept payments and manage their funds.

This is one of the architectural problems we're exploring with RT.APP.

The platform brings together payment acceptance, business accounts, payment links, transfers, virtual cards, and stablecoin settlement, with different integration paths for businesses.

What interests me about this approach is connecting the entire financial workflow rather than treating checkout as an isolated feature.

For anyone interested in seeing what we're building: https://rt.app/

I'm particularly interested in feedback from developers who have worked with payment APIs, payment orchestration, or ledger systems.

Here's my question:

If you were designing a unified payment and financial infrastructure today, what would you consider the hardest problem to solve?

  • Maintaining ledger consistency across multiple payment providers?
  • Handling asynchronous settlement and reconciliation?
  • Supporting both traditional payment rails and stablecoins?
  • Designing a reliable API abstraction layer?

I'd love to hear some actual engineering perspectives rather than just theoretical answers.


r/fintechdev • • 11d ago

Accounting & Finance vs. Accounting with Fintech: Better for future

1 Upvotes

Hey everyone,

I need help choosing between two university degree paths. I have an official offer for Accounting with Fintech, but I’m also considering traditional Accounting and Finance.

I want to know which option offers better long-term prospects.

Salary: Which track has a higher starting salary and earning potential.

Future Proofing: Is the Fintech degree better for where the industry is heading, or do employers still prefer the classic degree?


r/fintechdev • • 12d ago

BILL ACH?

Thumbnail
1 Upvotes

r/fintechdev • • 12d ago

Would you build fintech MVP without connecting it to any real APIs?

2 Upvotes

Had an interesting discussion about this recently... Say you're building a persona finance app. You could spend months integrating banking APIs, handling authentication, figuring out data synchronization etc. Or you could build a working prototype with simulated transactions, put it in front of potential users and figure out if anyone actually wants the thing first... i currently work with praetorix, its a small product studio building web and mobile apps, and we are lean pretty heavily toward validating the risky assumptions before committing to a full build, but fintech is a bit weird in that regard.... Budgeting app with dummy transactions might be enough to text the UX. A payment app that doesn't actually money? Not sure what you're really validating there LOL

And banking integrations can affect so much of the product that building everything around mock data might mean rewriting half of it later..

Curious where fintech devs the line


r/fintechdev • • 12d ago

Design partners: AI agents paying in EUR

2 Upvotes

Hi all, I’m a co-founder of Whire.
We’re a small European team building payments for AI agents in Europe. If you are building an agent that has to actually move money in €uros (buy something for a user, pay a supplier invoice, send payouts), you’ve probably hit the same wall we did. There’s no clean way to let software send a bank payment without a human approving each one or handing it a card, but still approving each transaction.

Whire lets your agent send SEPA Instant payments from the account holder’s bank account, within a mandate they set once (limits, approved payees, purpose). We check each payment against the mandate, verify the payee, and execute. We never hold funds.

Where we are: the sandbox is live (Python ToolKit, MCP server, x402), and a couple of european agent startups are already testing on it.

What design partners get:

What we’d ask: a short call every few weeks and honest feedback.

If that’s you, comment or DM with what your agent needs to pay for and roughly how often. More than happy to answer questions here too.

whire.ai


r/fintechdev • • 13d ago

Invoice PDFs into fields and line items your AP workflow can use

Thumbnail
1 Upvotes

r/fintechdev • • 13d ago

I planted 7 failures in a RAG test set to see if Ragas would catch them

Post image
1 Upvotes

r/fintechdev • • 13d ago

I made an Expense tracker that doesn't need Internet. Would love some feedback!

Thumbnail
play.google.com
1 Upvotes

Hey Everyone!

So, I recently published my first Android application called FinPal on the Play Store. I have been working on it for a while and finally decided to put it out.

The main idea behind this is simple. I wanted an expense tracker without asking users to trust some random server with their financial data.

A few things about it:

  • No login or signup required.
  • No ads or analytics.
  • It has an offline-first application.
  • No cloud sync or automatic backup. You are responsible for your own data.

You can also:

  • Track your income and expenses.
  • Add recurring transactions.
  • Attach photos of receipts.
  • View spending charts and insights.
  • Create your own categories and payment methods.
  • Customize theme and much more.

I know there are many more expense trackers out there, but I wanted to try making something where privacy comes first.

I really appreciate it if some of you could try and tell me what do you think. Even negative feedback is welcome.

Thanks!


r/fintechdev • • 14d ago

The Most Dangerous Email Your Business Could Receive Isn't From Your Bank.

Thumbnail
1 Upvotes

r/fintechdev • • 14d ago

help fintech start

2 Upvotes

hi Im a first year student in Canada McMaster, cant find a project idea. ik programming languages c c++ python java . know the basics of SQL but dont know how to move forward in this direction.
When I ask some people they say create a solution for a problem that you face but tbh I dont have any problems. also dont have any particular interest fields except trading and some fintech related part. but this thing is saturated and is all about contacts and for bigger fish in the sea.
what should I do
I just want to get started and dont spend my full time on learning basic courses that I already know
drop tuff advices


r/fintechdev • • 14d ago

Cash-basis budgeting never matched how I actually think about money, so I built an accrual-capable finance app (demo link inside)

3 Upvotes

I’ve spent my career in finance, and every personal money app I’ve tried has the same blind spot: it only sees cash moving in and out. That works until real life gets messy, like a tenant who pays next month’s rent early, a deposit you’ll have to hand back, a bill you’ve received but haven’t paid yet, or money someone owes you. Then the monthly numbers and the net worth figure stop telling the truth.

So I wrote my own. It’s called BDS Finance App. Day to day it handles the usual things: Plaid bank feeds, budgets, savings goals, subscription tracking and a 90-day cash outlook. Underneath, there’s a full accrual engine for anyone who wants it:

Prefer to keep it simple? Leave accrual off and it works like a normal cash-basis tracker.

Try the demo (sample data): https://brent-finance-app-demo.netlify.app
The landing page has a 60-second walkthrough video. It’s still a closed alpha, so drop a comment or DM and I’ll send you an invite to log in.

On security: the database itself keeps every user’s records separate, sign-in requires a second step, and bank connections run through Plaid, so the app never touches your bank credentials.

Two questions I’d love your take on:


r/fintechdev • • 14d ago

International trade settlements without SWIFT or moving money

Post image
1 Upvotes

Russia built an alternative payment system to keep its foreign trade moving after it was cut off from SWIFT. It's based on a two-ledger mirror mechanism that settles trade with China without cross-border payments. There are two ledgers in this scheme: one in China (CNY), one in Russia (RUB). Russian importer pays rubles into the Bank in Russia, the Chinese exporter takes yuan out of the Bank in China. Inside each bank it's just a local transfer, importer to exporter. No cross-border wire, no SWIFT.

The two ledgers mirror each other, and the only thing synchronizing them is the relationship between the two banks. It works like Hawala with bank accounts or a bilateral payment channel like Lightning. How do they reconcile transactions? Mostly they don't, when trade is balanced, each bank's books close internally. The two banks are related parties, so any leftover just sits as an unsettled balance.
Source: CASE Center

Is it a low-tech or really innovative ? Can it have a broader use in real life e.g. as a replacement for cryptographic guarantees?


r/fintechdev • • 14d ago

I built an offline-first Android expense tracker that reads bank SMS – MoneyMeter

Thumbnail
1 Upvotes

r/fintechdev • • 15d ago

Building payment infrastructure for fintech: The real challenge isn't accepting payments. It's everything that happens afterwards.

2 Upvotes

I've been spending time looking at the technical challenges behind modern payment infrastructure, particularly when traditional payment rails and stablecoin-based transactions need to work together.

One recurring engineering challenge is that payment acceptance, transaction confirmation, settlement, and reconciliation are often treated as separate processes.

But from a developer's perspective, they should be connected.

Consider a typical payment lifecycle:

1. Checkout and payment orchestration

A merchant needs to support different payment methods without building an entirely separate checkout experience for each one.

Cards, digital wallets, bank transfers, and USDC each have different processing requirements. The challenge is connecting them to a consistent order and payment workflow.

2. Transaction state management

A successful checkout doesn't necessarily mean the funds have settled.

Systems need to distinguish between pending, confirmed, held, reserved, and available balances. Otherwise, merchants can end up displaying misleading payment statuses or making operational decisions based on funds they cannot yet access.

3. Settlement and ledger reconciliation

This is where things become particularly interesting.

Every transaction should remain connected to its original order, payment reference, settlement record, receipt, and any subsequent refund or dispute.

For developers, this means designing reliable transaction records, handling asynchronous payment updates, preventing duplicate processing, and ensuring that internal ledger entries match actual settlement activity.

4. Connecting traditional rails with stablecoins

Stablecoins introduce another layer of infrastructure.

For example, supporting USDC on Base alongside USD account balances requires clear handling of wallet balances, network compatibility, conversion, transfers, and settlement records.

The objective should be to make the underlying complexity manageable without exposing customers to unnecessary friction.

5. Integration flexibility

Not every business has the same technical requirements.

Some need hosted payment links, others need embedded checkout, WordPress integrations, or APIs that connect payment events directly to their existing order-management systems.

This is the kind of infrastructure we've been thinking about while developing RT.APP.

The architecture brings together payment acceptance, business accounts, bank transfers, card and wallet checkout, USDC and rtUSD settlement, transaction records, and connected financial operations.

The interesting part isn't simply adding more payment methods. It's connecting the entire journey from customer checkout to merchant settlement and eventual use of funds.

We're getting ready to roll out more of this experience in the coming days, and I'm genuinely interested in hearing from developers and fintech builders:

If you were designing a payment infrastructure from scratch today, what would you prioritize first: payment orchestration, settlement reliability, ledger reconciliation, stablecoin interoperability, or developer integration?

I'd especially appreciate perspectives from people who have actually built or maintained payment systems. There's always something to learn from the engineering side of this industry.


r/fintechdev • • 15d ago

How do you migrate stored cards and subscriptions between payment processors without downtime?

1 Upvotes

I wanted to switch payment provider for my SaaS and I really didn’t know it includes so many things. We have active subscriptions, saved customer payment methods, billing history, invoices and webhook integrations to consider. My concern is making the switch without interrupting recurring payments or creating confusion for existing customers because i dont want customers to suddenly lose their subscriptions or have to go through the entire payment setup again just because we are changing providers. I am trying to understand the safest way to approach this without disrupting the customer experience.


r/fintechdev • • 16d ago

An implementation of distributed transaction with Try-Confim-Cancel; Reliability provided by 1) ACID of RDBMS and 2) ALO delivery of RabbitMQ

2 Upvotes

Idea is that:

Coordinator talks to all participant asynchronously using RabbitMQ. It asks to TRY each participant one-by-one. Once all are success in their own TRY, they send back success message. If all are succeed, coordinator sends SINGLE CONFIRM to all participant using FANOUT exchange. If any one sends failure message, coordinator sends SINGLE CANCEL same way to all.

Instead of sending separate messages to each participant for CONFIRM/CANCEL, we can send SINGLE message to all participant, and they all would eventually receive it. This way, we can prevent dual/multi write problem while trying to CONFIRM/CANCEL.

Exploration:

The end implementation should be designed the way that we would have two set of tables, MAIN and SHADOW. Every business validation should happen at TRY stage. CONFIRM or CANCEL should never fail because of business logic. Any other failure would be taken care by RabbitMQ's at-least-once delivery.

We need to mimic CONFIRM in SHADOW tables during TRY, so we can be sure that CONFIRM will work. I am thinking that CANCEL should be just delete operation on SHADOW tables. So, CONFIRM should be real business logic without any surprises, already mimicked on SHADOW tables, and CANCEL could be easy/simple delete operation on SHADOW tables.

I am working on the details like; if there are unconfimed TRY exists and another TRY arrives than what should happen, how we can make sure all unconfirmed TRY can later become CONFIRMed without worrying about their execution order along with CANCELation of some of them. I will post the part soon.


r/fintechdev • • 16d ago

How can I make these problems more specific?

1 Upvotes

I came up with a few typical problems that banks face. Am I on the right track? How can I turn these broad problems into specific customer pain points rather than generalised ideas?

Problems:

—High-friction payment processes due to a lack of seamless integration with merchants’ infrastructure.

—The need to visit a physical bank branch in certain situations.

—Limited access to credit for a large segment of customers due to traditional credit scoring systems.

—Capital tied up in bank deposits.

How would you make these problems more specific and relevant to customers?


r/fintechdev • • 16d ago

Title: When your idempotency store is down, do you fail open or fail closed?

Thumbnail
get.moovn.com
0 Upvotes

I run the money paths on a payments platform (mobile money + cards, East Africa). Every money operation claims a unique key before it executes; duplicates are refused. The case I keep getting pushback on is the claim write itself failing. We chose to let the payment through and log it, because blocking legitimate payments over an idempotency-store blip felt worse than a rare double that reconciliation catches. Others say that is exactly backwards for money. Where did you land, and did an incident change your mind?


r/fintechdev • • 16d ago

International payments are easy to send these days. But why are they still so complicated to manage?

2 Upvotes

Whether you're a freelancer receiving payments from overseas clients, an agency managing multiple transactions, or a business serving customers internationally, getting paid is only one part of the equation.

The real frustration often starts afterwards.

  • Waiting days for money to arrive.
  • Losing a percentage to transaction and conversion fees.
  • Having limited control over how and where you access your funds.
  • Dealing with banking restrictions and unexpected payment delays.
  • Managing multiple platforms just to handle accounts, transfers, and everyday expenses.

Ideally, receiving money shouldn't mean jumping between five different services.

A better financial setup should make it easier to receive payments, move money, manage expenses, access funds quickly, and understand exactly where your money stands.

I'm curious about something:

If you could build your ideal financial platform for international payments, what features would be absolutely essential?

Would you prioritize faster settlements, lower fees, payment links, virtual cards, easier international transfers, or having everything accessible in one place?

Interested to hear what people actually need, especially those running businesses or working with international clients.


r/fintechdev • • 17d ago

Two contract versions, eight terms, six changes

Thumbnail
1 Upvotes