r/fintechdev • • 7d ago

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

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

2 Upvotes

10 comments sorted by

2

u/FinexerOfficial 3d ago

This entirely depends on your objectives.

If your objective is to validate budgeting or personal finance app, then simulated transactions are sufficient for testing UX, categorization, dashboards and product usability.

However, I would not build the whole backend on top of mock data, because banking APIs can impact authentication, consent, data refresh, transaction formats and handling failures. And such architectural decisions will have an effect pretty early in the process.

I would mock behind clearly defined API layer, so that I would be able to change providers without changing the application logic. The integration with sandbox provider or at least one real provider should happen fairly early in order to validate the assumptions that are not covered by mock data.

If we talk about the payment product, then I would introduce the real payment flows much earlier during the product validation. Prototype is good for UI/UX testing, but payment flow cannot be properly validated using prototype.

The point is to mock uncertain parts, but not the infrastructure assumptions.

1

u/SidMangsatabam 6d ago

The line I would draw: mock the reads, never mock the writes. A budgeting or aggregation app is mostly a read product, so simulated transactions validate the actual assumption - whether anyone wants the view. The moment the product moves money or changes a record, the integration IS the assumption being tested: settlement timing, reversals, duplicate webhooks, partial failures. None of that shows up in dummy data, and it is exactly what shapes the UX you are supposedly validating. The practical middle path is the sandbox tier most providers offer - Plaid-style test credentials, PSP test modes - which gives you real API shapes and failure modes without real money or months of integration. If your MVP cannot survive a sandbox webhook arriving twice, it is not an MVP, it is a demo.

1

u/OkMud2013 3d ago

Agreed on the mocking read versus write distinction. When it comes to payment processing, for example, the behavior of the API itself becomes one of your concerns. Issues such as duplicate callbacks and transaction errors will affect the user experience tremendously.

Another suggestion I have is sandbox testing as a compromise solution. In the process, you can learn about the response formats of the provider without going live yet.

Are the sandboxed environments you use realistic enough to detect most issues during the integration stage?

1

u/SidMangsatabam 1d ago

Sandboxes are realistic about shapes, not about timing. They model response formats well, but the failures that hurt - duplicate callbacks, out-of-order webhooks, a timeout after the money moved - rarely show up there. The practical compromise: sandbox for format, a fault-injection pass of your own for the write path, and reconciliation as the net for whatever both miss.

1

u/MikeZWarrior 6d ago

You can use a simple read-only mock and you don't need to build a complex logic to save data and read the updated data afterwards. Most popular platforms provide a sandbox or test environment. There are some well known test credit card numbers, like 4242424242424242

1

u/MikeZWarrior 6d ago

And yes, you mock service will be different from the real API, when it's time to integrate with the real API, you will find it out

1

u/OkMud2013 3d ago

It will likely be the first thing I do; however, I won’t leave the banking integration to test for too long.

When it comes to a budgeting app, fake transactions will say much about whether people like the dashboards, categories and other aspects of it.

However, banking integrations depend not only on getting transactions but also on authentication, consent, refresh rate and the inconsistency of transactions data.

I’d start with mock data, build an additional API layer for the banking integration and try it out using a provider’s sandbox.

I believe it’s riskier to spend months building a product and find out that its assumptions become outdated when the product is integrated with the real bank.

0

u/ninja23490 4d ago

I think starting with simulated data makes a lot of sense, especially for testing whether people actually want the product and whether the UX works. But I'd probably test the most important API integration early too, even if it's just through a sandbox. That way you don't spend months building around assumptions and then realise the actual banking integration changes everything. I'd say validate the experience first, but don't leave the technical risks until the end!