White papers / White paper 05

Custom API Integration: Connecting Old and New Systems Safely

One secured layer between your products, partners, banks and legacy systems.

White paper 05 · October 2026 · Updated 17 November 2026Download PDF

Summary

When a financial firm wants to launch something new, the hard part is often not the new product. It's connecting it to everything that already exists: the core banking or accounting system, the CRM, partner banks, open-banking providers. Each connection built in a hurry makes the next one harder.

Fintech Den™ designs and builds integration layers for exactly this. Each system connects once, to a single layer with one consistent approach to security, monitoring and change. We build connectors for older systems that lack modern APIs, regulated open-banking access, and a secure gateway using OAuth 2.0, JWT and mutual TLS.

We're a new company, and we'd rather show you how we think than make big claims. This paper covers the problem, how we'd approach it, where open-banking rules stand in the US, UK and EU, how we handle your data, and a first project small enough to judge us on.

Data protection is usually the first thing UK and EU buyers check, so we'll say it up front: we comply with the UK GDPR and the EU GDPR, and we're registered with the UK Information Commissioner's Office. The GDPR section below explains what that means for your project, from where your data is hosted to how we'd tell you about a breach.

The problem

Older core banking and accounting systems often offer batch files or proprietary interfaces instead of modern APIs. So teams build direct connections between systems as they need them. Over the years, each system ends up talking to several others, one change quietly breaks something elsewhere, and nobody holds the full map.

Security tends to suffer in the same way. Credentials, tokens and certificates are handled a little differently in every connection, which makes the whole estate harder to protect and harder to audit. Some data still arrives through screen scraping, which breaks without warning and sits uneasily with regulators and partner banks.

Open banking adds another layer of uncertainty. The rules differ by market and are still changing, so integrations built tightly around today's rules may need rework sooner than expected.

How we would approach it

We'd start by drawing the map nobody has: every system, partner and connection, with the ones causing the most trouble marked. Then we'd set up the secure gateway and move the single most painful connection onto it first.

The layer usually has three parts:

PartWhat it doesWhat we'd aim for
Open-banking APIsRegulated account data access and payment initiation, built to PSD2 today and designed to adapt to each market's standardsLess reliance on screen scraping
ConnectorsAdapters for ERP, CRM and older core systemsNew products on top of existing systems, without replacing the core
Secure gatewayOAuth 2.0, JWT and mutual TLS as standardOne consistent, auditable way of securing every connection
Every system connects once, to one secured layer, not to each other. Your products and partners; Customer apps; Partner fintechs; Internal teams; ↔; Integration layer; Secure gateway; OAuth 2.0, JWT, mutual TLS; Plug-and-play connectors; ERP, CRM and legacy cores; Open Banking APIs; Data access and payments; ↔; Banks, providers and systems; Banks and open banking; ERP and accounting; CRM; Legacy core systems; Monitoring and audit log

In the diagram, your apps and partners talk only to the layer, and the layer talks to banks, providers and internal systems. That way, replacing one of them later doesn't ripple through everything else.

We keep to a few engineering habits: versioned and documented APIs, automated contract tests for every connector, safe retries for financial operations so nothing is processed twice, and monitoring that alerts us before a partner has to.

Open banking and data rules in the US, UK and EU

Open banking is moving at a different pace in each market. That's the main reason we keep connectors separate from your products: when a standard changes, we change the connector, not your app. This is a summary for discussion, not legal advice.

MarketFrameworkWhere it stands (October 2026)What it means for the build
USCFPB open-banking rule (Section 1033)Finalised in October 2024, but blocked by a federal court and being reconsidered, including whether banks may charge for data accessConnectors built on the FDX standard the market is moving towards, with room to adapt once the rule settles
MarketFrameworkWhere it stands (October 2026)What it means for the build
UKUK open banking under the CMA Order and the Payment Services Regulations 2017In force, with commercial variable recurring payments being rolled outAccount data and payment-initiation connectors with consent and token handling
EUPSD2 today; PSD3 and the Payment Services Regulation nextPSD2 in force; new final texts published April 2026, with most rules expected around 2028Built for PSD2 now, designed to be updated for the new rules
EUInstant Payments Regulation, Verification of PayeeEuro-area obligation since 9 October 2025Payee checks inside payment-initiation flows

UK and EU GDPR compliance

An integration layer touches almost every system you have, so it needs to be clear who can see what. We comply with the UK GDPR, alongside the Data Protection Act 2018, and with the EU GDPR. On client projects where we handle personal data, you're the controller and we act as your processor. Here's what that means in practice.

AreaWhat we do
Data processing agreementWe sign one with every client, covering everything Article 28 of the UK and EU GDPR requires. We act only on your documented instructions, and everyone on your project is bound by confidentiality. Our standard agreement is ready for your legal team to review.
Collecting lessSystems collect only the personal data they need. By default we build and test with synthetic or masked data, not live customer records.
Consent recordsOpen-banking connectors record each customer's consent and when it expires, and stop data access when consent ends or is withdrawn.
Where data livesProduction systems run in your own cloud account, in the UK or EU region you choose.
Access and transfersAny access to real personal data is agreed with you first, limited to named people, logged, and removed when the task is done. If access ever involves a transfer outside the UK or EU, it's covered by the EU standard contractual clauses or the UK international data transfer agreement. Both are ready to sign.
SecurityEncryption in transit and at rest, least-privilege access, logging, and code review on every change.
Sub-processorsWe tell you which sub-processors we use, and add new ones only with your prior authorisation.
People's rightsWe help you respond when people ask to see, correct or delete their data.
BreachesIf we become aware of a personal data breach affecting your data, we tell you without undue delay, so you can meet the 72-hour deadline for reporting it to the ICO or your EU supervisory authority.
Assessments and auditsWe support your data protection impact assessments, give you the information you need to show compliance, and allow audits.
End of the workWe return or delete your personal data, whichever you choose.

Where we stand on registrations and certifications. We'd rather be precise than impressive.

ItemWhere it stands
ICO (UK)Registered with the Information Commissioner's Office.
EU to UK data flowsThe EU recognises UK data protection law as adequate. The European Commission renewed that decision in December 2025, and it runs until December 2031.

For EU firms under DORA. If you're an EU financial entity, our DORA information sheet gives you what you need to record us in your register of ICT third-party providers: our company details, the services we provide, where data is processed and the subcontractors we use. We'll also work through the DORA contract terms with your team.

How we work

Since we can't yet show you years of past projects, we'd like to show you our process instead, in writing, before you commit.

The people you'll work with. You deal directly with our leadership. There's no account manager in between.

RoleWhat they look after on your project
Chief Executive OfficerThe relationship, scope, security and data protection, and fit with your partner and product plans
Chief Technology OfficerIntegration design and API standards, technology choices, gateway reliability, technical risk, final technical sign-off, and on some projects the relationship and scope
Head of EngineeringConnector builds, contract testing, monitoring and releases
Head of Visual DesignThe developer portal, API documentation and operations dashboards

Company and working hours. Fintech Den™ is a trading name of ROMBI PIXEL LTD, a UK company registered in England and Wales (no. 15947340) with its registered office in Bury St. Edmunds. We run on Central European Time (CET), so our working day overlaps with business hours across the UK and EU. For US clients, our afternoon overlaps with the East Coast morning, and we schedule calls in that window.

The practical side. We quote and invoice in euros, US dollars or pounds, whichever suits your finance team, and EU clients can pay by SEPA transfer to our euro account. Proposals spell out scope, milestones, payment points and VAT treatment, and payments are tied to milestones you can check. Our master services agreement is ready for your legal team, and we're open to discussing governing law and other terms.

Habits you can hold us to. We send a written summary within one working day of every call. You get a short written update every week and a demo every two weeks. Risks go in a shared log as soon as we spot them, and nothing changes scope without your written agreement.

What the first 90 days usually look like. We'd put the secure gateway in place and move one priority connection onto it, releasing it in stages.

The gateway and one priority connection go live first. Weeks 1 to 2; Assessment; Map systems and partners; Agree security requirements; Choose the first connection; Weeks 3 to 8; Gateway and connector; Secure gateway set up; First connector built; Contract tests and docs; Weeks 9 to 12; Staged go-live; Release in stages; Monitoring and alerts on; Plan the next connections; Scope signed off; Test results reviewed; Decide next steps; Every week a written update. Every two weeks a demo. No scope change without your written OK.

You can stop at any checkpoint and keep everything we've produced so far.

Starting a conversation

The first call is mostly us listening. We'll probably ask about:

  1. Which systems, banks and partners need to connect, and which connections cause the most trouble today.
  2. Which older or vendor systems have no modern API.
  3. Whether you rely on screen scraping anywhere, and for what.
  4. Which open-banking markets matter to you: the UK, the EU, the US or several.
  5. What security, hosting and audit requirements your partner banks set.

If it looks like we can help, we'll suggest one of these as a first step. Timings are typical, not fixed, and we'll confirm them in a written proposal.

OptionTypical lengthWhat you'd receive
Integration assessmentAbout 2 weeksA map of your systems and connections, a priority list, a proposed design and a fixed-scope plan
First connection liveAbout 3 monthsThe secure gateway plus one priority connection in production, with monitoring and documentation
Wider roll-outAgreed togetherMore connections moved over in stages, a developer portal and handover

If it doesn't look like a good fit, we'll tell you, and where we can, we'll point you to someone better placed.

Before the call, we're happy to send our trust pack: our data processing agreement and the EU and UK transfer clauses, plus the DORA information sheet if you're an EU financial firm. We are working towards IASME Cyber Assurance and the NCSC-backed Cyber Essentials certification.

To arrange a call, email contact@fintechden.com. We'll reply within one working day.

Common questions

How do you connect a new product to legacy systems that have no modern APIs?

Through one integration layer. Each system connects once, to a single layer with one consistent approach to security, monitoring and change. We build connectors for older systems that lack modern APIs, and a secure gateway using OAuth 2.0, JWT and mutual TLS.

How long does a first integration take?

An integration assessment takes about 2 weeks. The secure gateway plus one priority connection in production takes about 3 months, with monitoring and documentation. Further connections are moved over in stages.

How do you stop a payment or other financial operation being processed twice?

We build safe retries for financial operations so nothing is processed twice. We also keep APIs versioned and documented, run automated contract tests for every connector, and monitor connections so that we are alerted before a partner has to tell us.

Sources

More white papers

Ready to Talk About Your Project?

Book a discovery call and we'll mostly listen. Not sure which service fits? Start with a fixed-price Discovery Sprint. We work on Central European Time and reply within one working day.

Discovery call Contact