Federated channel development · Services

Composable banking & federated channel development

New capabilities live in your channels, built alongside your own team

We embed business banking capabilities into a bank's own channels, and we co-build the bank's bespoke features alongside its engineering team, built by people who have extensive experience developing and running online business banking solutions. The bank keeps its channels, its brand and its IP.

On web, that means modules, widgets, micro-frontends and APIs inside the portal your clients already use. On mobile, it can be a standalone app for iOS and Android, or the same functionality and APIs/MCPs added into a bank's existing mobile app.

Discuss a fit What "federated" means

Trusted by leading commercial banks including

Building for banks since 2016 Bank satisfaction 8.9/10 (2025) ISO 27001 certified >99.95% uptime

The problem we solve

New capabilities, live in your channels, without losing control

Banks want new business banking capabilities live in their corporate channel in months, not years.

A vendor drops in a standalone product, engine and front end together. It works, but it can feel like a different product, sit apart from the bank's design language, and be difficult for the bank to extend.
The bank's own team builds everything from scratch, which can mean a year spent on functionality that is actually conventional and widely available off the shelf.
We sit between those two: running capabilities where we already have them, joint build where the bank needs something bespoke, and a channel that behaves as one product throughout.

What "federated" means here

Architecture and team, federated the same way

Federated architecture

Technology: one shell, independently deployable parts

Micro-frontends, rules and orchestration engines, APIs/MCPs and module federation. The bank owns the channel shell, navigation, identity and design system. TreasurUp capabilities and the bank's own features load as independently deployable components into that shell. Several teams ship into one channel without blocking each other, and each component can be released and rolled back on its own.

Federated delivery and run-mode

Way of working: one squad, shared backlog

TreasurUp engineers and the bank's channel team work as one squad: shared backlog, shared definition of done, shared quality bar. The bank retains ownership and IP of every bespoke feature. Knowledge transfer is a delivery goal, not an afterthought. Work is allocated between the bank's internal team and TreasurUp based on capabilities, time-to-market and cost, in a way of working agreed with the bank.

The result: the bank's team ends the engagement more capable than it started, not more dependent.

What TreasurUp gives the bank

Three service pillars, applied to channel delivery

Delivered consistently across your web and mobile channels.

1 · Architect and design

The foundation for a channel that stays extensible

Channel architecture: module federation topology, shell vs. module boundaries, shared design system, cross-module state, SSO and entitlements
Capability blueprints for how modules slot into the bank's information architecture and data model
Integration design: core banking, payments (SWIFT, SEPA), market data, CRM, entitlement services
Legacy migration tactics: strangler patterns that ship value before the migration finishes
Security and continuous delivery by design, not retrofitted
Regulatory framing at design time: DORA, MiFID II and GDPR, including Art. 22, as design constraints

2 · Develop and implement

On the bank's stack and tooling

Implement TreasurUp capabilities already running in production, embedded as channel components
Co-develop bespoke bank features inside the same federated architecture, owned by the bank
Shared, bank-branded component library reused across our modules and the bank's
Contract-tested integrations, so independent teams deploy without breaking each other
Test automation from the start: Playwright end-to-end coverage delivered with the feature
Open source, Microsoft/.NET and Java/Kotlin/Spring, on the major clouds, in the bank's own Jira/Bitbucket/Git and CI

3 · Operate and optimize

Delivery speed balanced against channel stability

CI/CD for a federated channel: independent module pipelines, canary and blue/green releases, per-module rollback
Observability with OpenTelemetry and Grafana, uptime and latency SLOs per module, tracing across the federation
Run-support models from advisory through shared on-call, matched to the bank's operations posture and DORA obligations
Continuous capability delivery and iteration on the bank's features after go-live, on a predictable cadence
Cost and performance tuning across the channel estate

UX/UI integration options

Four ways to put a capability into your channel

Deeper integration buys tighter fit with your design system; each step also asks more of your front-end stack. Most engagements move left to right over time.

1 · Portal deep link

Navigate to the TreasurUp SPA via an SSO flow, themed with the bank's logo, fonts and colors.

Independent deployments
Quickest, standard implementation
User leaves the bank portal context

2 · iFrame integration

The TreasurUp SPA runs isolated inside the bank's React portal.

Independent deployments
Works regardless of the portal's stack or bundler
Some UI/UX friction

3 · Module federation

Loads into the bank's custom React front end as an independently deployable module.

Independent deployments
UI/UX fine-tuned to the bank's design system

4 · Node package (NPM)

Ships as a package straight into the bank's custom React front end.

UI/UX fine-tuned to the bank's design system
Deepest integration

Quickest to shipTightest fit with your design system

Engagement models

Three ways to start working together

Most engagements start with capability integration or advisory and grow into an embedded squad once the pattern is proven.

Model	Best for	Commercial shape
Capability integration	Plugging a defined TreasurUp component or module into an existing channel	Fixed scope, milestone-based
Embedded federated squad	Ongoing joint delivery of TreasurUp capabilities plus bespoke bank features, our primary model	Dedicated team, monthly
Architecture and advisory	Design authority, reviews, and enablement of the bank's own team	Time and material, or retainer

What the bank gets

More competitive, faster to innovate

Your bank's web or mobile channel, sharpened through collaborative delivery between your channel team and TreasurUp. One experience for the user.

A live business banking capability in months, using product that already runs at other banks.
Competitive edge, since most solutions are designed and developed with other banks to grow Daily Business Banking.
One channel that looks and behaves as a single product.
Its own engineering team levelled up on the domain through shared delivery.
Compliance-ready delivery, with DORA, MiFID II and GDPR handled from day one.
Independently deployable modules, so change risk stays low and releases stay small.

Why TreasurUp

Banking-channel domain expertise, built for the long run

8.9/10

Bank satisfaction

Banks rate working with TreasurUp 8.9 out of 10 (TreasurUp client survey, 2025).

European banks in production

Composable capabilities that already run, not a roadmap slide: working product ready to embed, at Nordea, Handelsbanken, Rabobank, KBC, OP, LBBW and Sparkassen.

Engineering depth, one roof

Architecture, build, innovate and run under one roof, with extensive experience in online business banking transaction initiation solutions. Every solution is tailored to the specific bank.

How an engagement runs

Five phases, one squad throughout

Phase 0 · 2-4 weeks

Discovery and fit: business workshops, channel audit, capability mapping, target architecture, a delivery plan with a first milestone.

Phase 1

Architecture and foundations: federation topology, design system alignment, CI/CD setup, security baseline, integration contracts.

Phase 2

First capability live: one TreasurUp module end to end, proving the pattern, the pipeline and the joint way of working.

Phase 3

Federated delivery: parallel tracks for TreasurUp capabilities and the bank's bespoke features, one squad, one backlog.

Phase 4

Operate and iterate: run, monitor, extend, with new capabilities on a predictable cadence.

Governance and compliance

Compliance built into delivery, not bolted on afterward

DORA reaches us contractually as an ICT third-party provider to the bank. We design, build and operate with that as a hard requirement, alongside MiFID II conduct rules and GDPR.

Area	Bank	TreasurUp
Channel shell, identity, navigation	Manages	Advises
Design system	Manages	Contributes components
TreasurUp capability modules	Consumes, configures	Builds, maintains
Bespoke bank features	Defines requirements	Co-builds, transfers knowledge
Integration contracts	Joint management	Joint management
Production operations	Sets bank posture	Supports per model
Regulatory accountability	Responsible	Delivers to requirement

FAQ

What digital channel leads ask us

No. The bank keeps its channel, its brand and its IP. TreasurUp engineers and the bank's channel team work as one squad, with a shared backlog and a shared definition of done, not as a separate team working around yours. Work is allocated between the bank's internal team and TreasurUp based on capabilities, time-to-market and cost, in a way of working agreed with the bank. The engagement is designed so your team ends it more capable, not more dependent.

It depends on how much your front-end stack can absorb today. A portal deep link with SSO is the fastest to ship and needs the least from your stack, but the user briefly leaves the portal context. Module federation or an NPM package into your own React front end give the tightest fit with your design system and the deepest integration, at the cost of more upfront alignment. Most banks start at deep link or iFrame and move toward module federation as the pattern proves out.

Through the federated architecture, not through discipline alone. The bank owns the channel shell, navigation, identity and design system; TreasurUp capabilities and the bank's own features load as components into that shell, sharing a bank-branded component library. Contract-tested integrations let independent teams deploy without breaking each other, so several teams can ship into one channel and the client still experiences a single product.

DORA reaches TreasurUp contractually as an ICT third-party provider to the bank, and we design, build and operate with that as a hard requirement, alongside MiFID II conduct rules and GDPR, including Art. 22 for automated decisions. Regulatory accountability stays with the bank; TreasurUp delivers to that requirement. Compliance is designed in at Phase 0 and Phase 1, not bolted on at the end.

Start with capability integration, plugging one defined TreasurUp component into your existing channel on a fixed scope, or with architecture and advisory if what you need first is design authority and enablement for your own team. Most engagements start there and grow into an embedded federated squad, our primary model, once the pattern is proven with a first capability live.

Map your channel against this pattern

A discovery and fit conversation runs 2 to 4 weeks: channel audit, capability mapping and a delivery plan with a first milestone.

Discuss a fit

Custom channel propositions for daily business banking

Composable platform and tailored services