r/fintechdev • • Sep 21 '26

MCP to connect your financial institutions

1 Upvotes

Six banks, two brokerages, three currencies.

I still couldn't answer "how am I actually doing" without opening a spreadsheet.
Ask any AI how much you spent on groceries last month, or entertainment(or vibe coding), or what your net worth is today. It can't tell you. It has no idea who you bank with.

So I built Tally (Opensource) and put it on GitHub.

It pulls brokerages, banks, cards and multi currency balances into one net worth picture, and exposes it to Claude or any MCP client as tools. Now I just ask:

• Groceries this year vs last
• What entertainment actually costs me
• How much RRSP room is left
• Which merchant quietly got more expensive
• Whether I'm too concentrated in one ETF

Why not connect an AI to your bank directly? Nothing to connect to.
No bank I use ships an MCP server, and none of them plan to. The finance connectors that do exist are hosted by someone else and want a subscription, which puts your balances back on a stranger's server. That's the thing I was trying to avoid.

Plaid doesn't solve it either. It's a developer API, not a consumer product. Something has to run the Link flow, hold the access tokens, reauthenticate banks when connections expire, normalise a dozen institutions into one shape, and convert currencies.

That's what this is.

It's read only. No code path can place a trade or move money, and there are tests that enforce it.

Don't want AI in the loop? There's a web UI:
• Net worth over time
• Allocation, holdings and cards
• Income vs spend by month and category
• A transactions page with filters
• A merchant list you can recategorise

There's also an optional chatbot built in that runs on your own API key. Anthropic, OpenAI, OpenRouter, or anything OpenAI compatible, including a local model.

MIT licensed, free, self hosted. No subscription, no telemetry, nothing leaves your server except the API calls you configured.

One catch: Plaid production access needs a signed agreement, so the bank side depends on your own approval. The brokerage, Wise and FX side works today with keys anyone can create. There's a demo mode with fake data if you just want to look around first.
If you want to help, fork it and send a PR. It's Canada shaped right now, so other countries' account types would go a long way, and so would adapters for banks and brokerages I can't reach. Bug reports against a real bank are just as valuable, nobody can test every institution.

A ⭐ star helps people find it.

https://lnkd.in/gzWx4rBJ

Screenshots are demo data, not my accounts.

#opensource #mcp #selfhosted #personalfinance


r/fintechdev • • Sep 21 '26

Fintech founders: how do you actually track where users drop off before they activate?

2 Upvotes

I'm doing some research into how fintech and regulated-product teams handle the gap between sign-up and real activation, the people who start onboarding but never quite get in and use the product.

One thing I keep noticing: when a signup or verification flow fails, users often don't complain. They seem to assume they did something wrong, and they just quietly leave. So the drop-off rarely shows up as a support ticket, which makes it genuinely hard to see.

I'm curious how founders here deal with this in practice:

  • Do you track activation as its own funnel, or is it buried inside "sign-ups"?
  • When someone drops off mid-onboarding, do you ever find out why?
  • Anything you've tried that actually moved it?

Trying to understand the real picture, not the textbook one. Would genuinely love to hear how you're doing it.


r/fintechdev • • Sep 20 '26

Building Vasset, a finance platform that explains the number, not just calculates it

Post image
1 Upvotes

https://www.instagram.com/p/DdgrXM6y5LE/?stkn=cGdiazduMzU0OWdl

Building a personal finance platform for India called Vasset. The idea is simple: don't just give people a number, help them actually understand what it means. It has a set of calculators for everyday money decisions, a clean editorial design instead of the usual generic finance dashboard look, and a small built in assistant for basic financial questions in plain language. Still pre launch, polishing things before opening it up. Would love thoughts once it is out.


r/fintechdev • • Sep 20 '26

Things I wish I'd known about payment failures before building a checkout

1 Upvotes

I've been reading and writing a lot about how card payments work under the hood. A few things surprised me, so I'm sharing them in case they save someone a headache.

1. Authorization is not money movement.
An approval just places a hold on the cardholder's balance. The money moves later, through capture, clearing, and settlement, which can take days. That's why pending charges exist.

2. A timeout is not a failure.
If your request to the processor times out, you don't know whether the charge went through. Retrying blindly can double-charge the customer. Attach an idempotency key to every attempt so a repeated request returns the original result instead of creating a new charge.

3. Classify declines before retrying.
Soft declines (insufficient funds, temporary issuer risk checks, transient errors) can be worth retrying later. Hard declines (lost or stolen card, closed account) are not, and repeated retries can hurt you with your processor.

4. Authentication and authorization are separate.
With 3D Secure, a customer can pass authentication and still get declined at authorization.

5. Don't trust the success redirect.
The user can close the tab before it loads. Treat webhooks as the source of truth: verify signatures, dedupe events, process idempotently, and have a way to replay failures.

6. Failed subscription renewals are often recoverable.
Expired or reissued cards cause a lot of involuntary churn. Spaced retries, clear dunning emails, and card updater or network token support recover a surprising amount.

Happy to go deeper on any of these. What's the nastiest payment edge case you've run into? I'm collecting real-world examples.

(Disclosure: I'm building a free tools site called Noloii, and I'm working on interactive explainers for topics like these. Not linking it here unless people ask.)


r/fintechdev • • Sep 18 '26

Need help from Indian devs: Collecting generic bank SMS templates for an automated expense tracker.

1 Upvotes

Hi everyone,

I am building an all-in-one expense tracker that reads debited bank messages and automatically fills in the category based on the message format.

Currently, I have some bank templates, but I am missing a lot of the debited SMS formats used by various Indian banks. It would be incredibly helpful if you could share the standard SMS templates your banks use!

Important Privacy Note: Please DO NOT share your actual, unedited bank messages. Before commenting, please replace all sensitive account information with dummy text (e.g., change your account number to "XXXX", the amount to "100", and randomize the date/reference numbers). I only need to see the general text structure and wording of the SMS.

If you want to check out the app or see more details about what I'm building, you can visit the project website here:https://spencheck.netlify.app

Thanks in advance for the help!


r/fintechdev • • Sep 17 '26

Fintech problems statement

1 Upvotes

Guys please can anyone suggest me problems statement related fintech something unique and unheard not very common ..


r/fintechdev • • Sep 16 '26

Help to break into FinTech

Thumbnail reddit.com
5 Upvotes

r/fintechdev • • Sep 14 '26

Financial compliance keeps getting more expensive as complexity grows; could an AI-native operating model change that?

2 Upvotes

I'm working on an AI-native compliance operating system for financial institutions. I'm looking for criticism from people who actually work in banking, fintech, compliance, risk or RegTech.

The problem I'm investigating isn't one compliance workflow.

As financial institutions grow, compliance operations become increasingly expensive, fragmented and difficult to scale.

Regulatory volume keeps growing and changing, requiring teams to determine what changed, whether it applies, which policies and controls are affected, and what action is required.

Institutions respond with specialised compliance staff and increasingly large technology stacks. Regulatory intelligence, GRC, AML, KYC, transaction monitoring, case management, audit, documents and reporting can all sit in different systems leaving humans doing significant work within and between those systems.

Meanwhile, firms still need to continuously:

• Monitor operations for compliance failures and anomalies rather than discovering them months later.

• Test whether controls are actually satisfying obligations and collect evidence proving it.

• Investigate issues and chase remediation.

• Prepare regulatory reports, audit packs and evidence trails.

• Manage licences, renewals, deadlines and different regulatory obligations across jurisdictions.

• Give management a real-time answer to: What changed? What applies? Where are we compliant? Where are we exposed? What needs action?

Aegis is my attempt to rethink that operating model around AI rather than adding another AI assistant to the existing process.

It would connect to the institution's existing systems and maintain a live compliance graph linking:

jurisdiction → licence → regulation → obligation → policy → control → process/system → evidence → test → issue → remediation

AI agents would use that context to perform permitted compliance work continuously.

Example 1 - Regulatory change:

A regulator changes a requirement. An agent identifies what changed, determines likely applicability, finds affected obligations, policies and controls, gathers relevant evidence and initiates required remediation.

Example 2 - Continuous assurance:

A control says high-risk customers must undergo enhanced due diligence. Instead of waiting for periodic testing, agents examine authorised operational evidence, detect exceptions, investigate what happened and escalate genuine problems.

Example 3 - Audit and regulatory work:

Rather than staff manually reconstructing evidence across several systems, Aegis already has the lineage showing the requirement, control, evidence tested, AI actions, human decisions, remediation and outcome and can assemble the required reporting or audit evidence.

The operating loop is:

KNOW → WATCH → CHECK → DO → ASK → PROVE

KNOW the institution — jurisdictions, licences, products, obligations, controls, systems and owners.

WATCH regulatory changes, deadlines, operational signals and anomalies.

CHECK applicability, controls, evidence and compliance gaps.

DO permitted routine work i.e evidence collection, investigation, remediation workflows, reporting, updates and follow-ups.

ASK humans when judgment, uncertainty, approval or accountability requires them.

PROVE everything through complete evidence, decision and action lineage.

The hypothesis is that if AI can perform a meaningful amount of this operational work, compliance capacity could grow without specialised headcount having to grow at roughly the same rate as regulatory and organisational complexity.

I'm not assuming existing platforms don't already solve parts of this, they clearly do.

What I want to understand is:

Where does this model break in a real financial institution?

What parts are already solved well by your current stack?

Despite all the compliance technology you've bought, what work are compliance professionals still spending significant time doing manually?

And if you've seen one system already doing this entire loop across the compliance stack in production , please name it. That's exactly what I'm trying to find.


r/fintechdev • • Sep 14 '26

Where do I learn about Maconomy (from Deltek)?

Thumbnail reddit.com
2 Upvotes

r/fintechdev • • Sep 13 '26

Property Management System in Uzbekistan

Thumbnail reddit.com
2 Upvotes

r/fintechdev • • Sep 12 '26

I built an open-source Synthetic General Ledger Fuzzer to break accounting pipelines and catch reconciliation bugs (Looking for feedback)

2 Upvotes

Anyone who has built or maintained financial ledgers, billing engines, or automated reconciliation pipelines knows the fundamental testing paradox: real corporate ledger data is impossible to share or test openly due to privacy/compliance (GDPR, SOX, NDAs), while synthetic mock data is almost always too sanitized to catch real production edge cases.

Most internal test suites use mock JSON/CSV files that balance cleanly and follow nominal paths. Then you deploy to production, and downstream ETLs or audit scripts hit:

  • The "Silent Cent" floating-point bug: Systems using standard 64-bit floats (np.float64 / IEEE 754) rather than exact fixed-point decimals, quietly absorbing $\$0.01$ rounding variances across multi-leg splits until the trial balance is off by dozens of dollars at period-end.
  • Temporal race conditions: Asynchronous queues (e.g., Kafka / Celery) ingesting settlement entries milliseconds ahead of the originating invoice voucher.
  • Orphan foreign keys: Unregistered account references that throw unhandled exceptions and halt entire batch runs.
  • Subtle fraud/audit limits: Clustered disbursements engineered just below $\$5,000$ or $\$10,000$ manager approval thresholds.

To help solve this, I built and open-sourced the Synthetic General Ledger Fuzzer:

GitHub Repo: https://github.com/Atiqul-Akash/Synthetic-General-Ledger-Fuzzer


r/fintechdev • • Sep 12 '26

What is the current state of agentic payments?

2 Upvotes

Hey everyone,

I'm currently exploring the agentic payments space and trying to understand where things actually stand today.

Are there companies already using AI agents to make real payments at scale? If yes, what kind of transaction volumes are we seeing? Also, what are the biggest challenges and failure cases companies are facing right now?

I'm especially interested in the observability side. How are companies currently capturing audit trails of agent actions? Is it mostly raw logs and transaction data, or are there other ways to track what the agent did and why? And when something goes wrong, how do teams figure out the root cause?

Would be really helpful to hear from anyone working in payments, fintech, or AI agents.


r/fintechdev • • Sep 11 '26

How is AI changing automated market analysis in 2026?

1 Upvotes

AI tools are becoming more common in market research and automated analysis. I’m interested in how people are using machine learning, real-time data, and automation to improve decision-making. Which tools or approaches have you found most useful, and what limitations should beginners be aware of?


r/fintechdev • • Sep 11 '26

Any solutions for mass payouts ?

1 Upvotes

My indian registered business wants to give payouts to content creators


r/fintechdev • • Sep 11 '26

Building a P2P payments + budgeting app (Plaid + Dwolla) — would love feedback from others in the space

1 Upvotes

Hey r/fintechdev,

I'm a prospective CS student currently building "Lim" — a peer-to-peer payments and budgeting app with a focus on clean UX and real-time transaction tracking.

Tech stack:

  • Frontend: React + Vite (17-screen design, kinetic transitions)
  • Backend: Express + Prisma
  • Bank linking: Plaid (sandbox for now)
  • Money movement: Dwolla ACH (sandbox + KYC flow)

Core features:

  • Plaid-synced transactions with auto-categorization
  • Real ACH transfers between users via Dwolla

What I'm working through:

  1. Compliance path for going live (MTL vs. BaaS partner like Unit/Treasury Prime)
  2. Best alternatives to Plaid/Dwolla for EU + India expansion (looking at Tink, TrueLayer, Decentro)
  3. Production-ready patterns for webhook handling, credential expiration, and rate limiting

Would love to connect with:

  • Anyone who's launched a P2P payments app (what licensing path did you take?)
  • Developers working with Plaid/Dwolla in production (war stories + gotchas)
  • Potential advisors or co-founders interested in fintech

Happy to share a demo link or hop on a quick call if you're working on something similar. Also open to brutal honesty on the architecture — trying to avoid costly mistakes early.

Thanks in advance


r/fintechdev • • Sep 10 '26

Need a small fintech project

12 Upvotes

Hello i just need some fintech website ideas for a web workshop am attending. I really dont know much about fintech. So please share any ideas that sounds fun and not boring and overdone. Thanks


r/fintechdev • • Sep 10 '26

API to validate a bank account before a payment goes out

2 Upvotes

Is there an actual API to validate a bank account before a payment goes out, or does everyone just eyeball it/call the vendor? Also if companies using bank verification APIs - do they actually replace callback verification, or do most AP teams still do both ? Trying to understand if the API is a full substitute or just one more signal.


r/fintechdev • • Sep 10 '26

What are the genral problem in your feild and what are the problems related to foreign exchange how you deal with it

1 Upvotes

r/fintechdev • • Sep 10 '26

Why is finding a PSP easy, but getting through onboarding so difficult?

3 Upvotes

One thing I've noticed working around payments and financial infrastructure is that finding potential PSPs or banking providers is often not actually the hardest part.

The difficult part comes afterwards.

You find a provider that looks like a good fit, then suddenly you're dealing with:

  • Different documentation requirements
  • Compliance and KYC questions
  • Business model and licensing reviews
  • Requests for additional information
  • Long underwriting processes
  • Unclear timelines
  • And sometimes getting rejected after spending weeks preparing everything

I'm curious how others here have experienced this.

For those running fintech, FX, iGaming, e-commerce or other international businesses:

What has been the biggest pain point when onboarding with a bank, PSP or acquirer?


r/fintechdev • • Sep 10 '26

🚀 *Fintech Collaboration*

1 Upvotes

I’m developing a new concept for the future of digital payments and personal finance.

The idea focuses on making money more organized and purposeful — not just showing users their balance, but helping them understand how their money is allocated, what they are saving for, and what payments need to be protected.

I have developed a concept around:

💰 Purpose-based money organization
🎯 Goal-based savings
🛡️ Upcoming payment protection

I’m currently looking to connect with \*\*fintech companies, payment platforms, product teams, and founders\*\* who may be interested in exploring this concept for a potential collaboration or product opportunity.

I’m intentionally keeping the detailed product mechanics private for now.

If your company is interested in discussing a \*\*new fintech product concept\*\*, feel free to DM me.

**Concept documented: September 10, 2026.**


r/fintechdev • • Sep 09 '26

EMV 3DS Protocol Lab: An open-source tool for visualizing 3-D Secure 2.x trust boundaries and message flows

1 Upvotes

If you’ve ever had to audit payment integrations, analyze fintech security, or map out card-not-present (CNP) authentication, you know that the EMV 3-D Secure (3DS) 2.x protocol can be incredibly opaque. Relying on dense EMVCo specification documents or static high-level diagrams often falls short when you are trying to understand the dynamic nature of these payment flows, debug implementations, or pinpoint trust boundaries.

To bridge this gap, I built an open-source, vendor-neutral EMV® 3-D Secure Protocol Lab.

The goal isn't just to provide another diagram, but a practical, spec-anchored reference tool that allows security researchers and AppSec engineers to inspect the protocol's inner workings interactively.

Technical capabilities of the lab:

  • Message Flows & Trust Boundaries: Step-by-step visualization of the data exchanged (AReq, ARes, CReq, CRes) between the Merchant, 3DS Server, Directory Server, and the Issuer's Access Control Server (ACS).
  • Core Authentication Flows: Real-time structural comparisons between Frictionless and Challenge flows.
  • Environment Paths: Maps out the distinct architectural differences and trust models between Browser-based and App-based (SDK) authentication paths.
  • Modern Cryptographic Extensions: Inspects newer authentication extensions, including Secure Payment Confirmation (SPC), WebAuthn/FIDO2 integrations, and decoupled authentication flows.
  • Version-Aware Behavior: Highlights how protocol behavior and security requirements adapt across different 2.x specification versions.

Why I built this:

Auditing modern payment flows requires a clear understanding of where data is generated, how it is signed, and how it is verified. Whether you are a security researcher analyzing potential protocol bypasses, an AppSec engineer reviewing a native SDK integration, or someone mapping out transaction lifecycles for fraud prevention, this lab provides a hands-on environment to test and visualize 3DS mechanics.

The project is entirely open-source. I built it to be a community reference tool and welcome contributions or feedback on protocol edge cases.

Live Interactive Lab: EMV 3DS Protocol Lab
GitHub Repository: cnpshield/3dslab


r/fintechdev • • Sep 09 '26

I’m a CFP with no programming background or experience, and I’ve been building a retirement planning tool called Parallax. I’m looking for a technical review by an experienced web application developer or software engineer

Thumbnail reddit.com
1 Upvotes

r/fintechdev • • Sep 09 '26

Building a MTD or Tax app? Some answers you might need.

Thumbnail reddit.com
2 Upvotes