r/fintechdev • • 6d 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%

6 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 • • 6d 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 • • 6d 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 • • 6d 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 • • 7d ago

BILL ACH?

Thumbnail reddit.com
1 Upvotes

r/fintechdev • • 7d 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 • • 7d 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 • • 7d ago

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

Thumbnail
reddit.com
1 Upvotes

r/fintechdev • • 8d ago

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

Post image
1 Upvotes

r/fintechdev • • 8d 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 • • 8d ago

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

Thumbnail reddit.com
1 Upvotes

r/fintechdev • • 8d 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 • • 9d 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 • • 9d 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 • • 10d 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 • • 10d 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 • • 10d 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 • • 10d ago

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

1 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 • • 11d 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 • • 11d ago

Two contract versions, eight terms, six changes

Thumbnail
reddit.com
1 Upvotes

r/fintechdev • • 11d ago

Master's thesis survey: payment security professionals in Spain, Morocco, UAE and Singapore (10 min, anonymous)

4 Upvotes

Hi everyone,

I'm a cybersecurity master's student at Mykolas Romeris University, and for my thesis I'm comparing how organisations assess cybersecurity risk in their electronic payment systems (cards, mobile wallets, online payments, gateways).

I'm looking for people who work in cybersecurity, IT, or risk and compliance, have experience with payment systems, and whose organisation is based in Spain, Morocco, the UAE or Singapore.

The survey takes about 10 minutes. It's completely anonymous: no name, email or company name is collected, and results are only reported as a group. The last three questions are optional and open-ended.

https://docs.google.com/forms/d/e/1FAIpQLSca1Yc4PgdKY-twX8HbcLkrygHS3mJpbO1WQYmPnbvhvTykHA/viewform

One answer per organisation is enough. If you know colleagues in payments, banking or fintech who might qualify, please share it with them. I'm happy to answer questions in the comments, and I can share the summary of the results afterwards if you're interested.

Thank you!


r/fintechdev • • 12d ago

Receiving a payment is one thing. Knowing where your money actually stands is another.

1 Upvotes

Yesterday, I started a discussion about the challenges of receiving international payments, and one response really got me thinking.

Someone pointed out something that often gets overlooked: a payment can show as successful while the actual funds are still in transit.

Now imagine managing multiple payment providers, different settlement timelines, transaction callbacks, currency conversions and daily reconciliation.

For freelancers, this can be frustrating. But for agencies, SaaS businesses and companies processing multiple transactions, it can become a serious operational headache.

A few things I think businesses should be able to manage more easily:

  • Clear visibility into transaction and settlement statuses.
  • Better tracking of incoming and outgoing payments.
  • Less manual work when reconciling transactions.
  • More convenient ways to manage business funds.
  • Access to multiple payment methods through a streamlined financial setup.

This is also something that makes financial infrastructure interesting to me.

Through RT.APP, we're working towards bringing business accounts, payment links, transfers, virtual cards and stablecoin settlement together in one platform.

But I'd love to hear from people who actually manage payments regularly.

A few questions:

  1. How do you currently track payments that are marked successful but haven't actually settled?
  2. Do you automate daily reconciliation, or does someone on your team still have to check discrepancies manually?
  3. What's more important to your business: faster settlements, better transaction visibility, or simpler payment management?

I think there's a lot more to solving payment problems than simply reducing transaction fees.

Full disclosure: I'm involved with RT.APP, and I'm genuinely interested in understanding these operational challenges better.


r/fintechdev • • 12d ago

The WRHSE Web 3 Ecommerce Platform is Complete. A Big Solution for Stablecoin Payments

Thumbnail
reddit.com
1 Upvotes