How we work:
our team inside the bank, alongside yours.

We do not sell consulting hours. We deliver a result in production, built on our own technology: engineering is how we get there, not the product.

The roadmap with the bank

We always start with a proof of concept. Each stage builds on the previous one, and the bank decides when to move forward.

Stage	What we do	What the bank decides
1Proof of concept	We demonstrate the solution with the scope the bank chooses, deployed on its own infrastructure or on a Finhattan test environment.	Where it takes place, and whether the solution fits its architecture and requirements before committing to deployment.
2Deployment to production	We take to production, inside the bank, every feature the institution decides to include; for example, investment in digital assets, stablecoin payments or the full client experience in its app. The scope is tailored to each need.	Which features to include, and approves go-live after its security review and acceptance testing.
3Operation and evolution	We operate the infrastructure and evolve it: new assets, new networks and adaptation to regulatory change.	Prioritises what is added and when.
4Expansion	We add new features on the same infrastructure as the bank needs them; for example, transfers to external wallets, distribution of third-party tokenised assets or service to other institutions.	Which features to enable, each with its own risk assessment.

Deployment, phase by phase

Deployment plan at the institution

1 · We understand the bankCore system, regulation, operationsFinhattan + bank

2 · We adapt the coreProprietary, modular, customisableFinhattan

3 · We deploy insideOn the bank’s infrastructureFinhattan + bank

4 · We operate and evolveOver the long termFinhattan + bank

Our own senior engineering team, deployed to the institution.

Why it is faster and more adaptable

A core that is already builtWe start from our own technology, developed and tested. Deployment is spent adapting it to the institution, not building it from scratch, which significantly shortens timelines.
Adapted, not integratedThe infrastructure fits the bank’s architecture, regulation and operating model and is deployed inside it. The bank does not have to integrate a standard product on its own or depend on a third party’s infrastructure.
Each deployment speeds up the nextWith our forward deployed model, the experience of each deployment carries into the next, so timelines shorten with every new institution.

What we cover

A small senior team that covers every area of the deployment.

Architecture and solution designCounterpart to the bank’s architecture and risk teams, and design of the solution for the institution.
Integration with the bank’s systemsCore system, accounting, position reconciliation and client identity.
On-chain connectivityNetworks, transaction lifecycle, integration with the bank’s HSMs, and liquidity.
App and client experienceIntegration into the bank’s app, following its design system.
Infrastructure and securityDeployment, security hardening and evidence for the bank’s review.

Who does what in each transaction

The bank keeps what is already its own: its clients’ identity, the keys, its licences, its accounting and its rules. The deployed infrastructure provides everything in between.

Step	Deployed infrastructure	The bank
Client identification	Uses the identity the bank has already verified.	Keeps its onboarding process unchanged.
Pre-trade checks	Applies a configurable policy and limits engine: price, limits and suitability.	Defines the rules.
Execution	Provides the order routing and execution software.	Executes transactions under its own licences.
Custody	Runs on its HSMs, physical or in its cloud.	Holds custody, with its own keys.
Records and reconciliation	Keeps the full history of transactions and positions and reconciles it with the network.	Defines thresholds and the exceptions process.
Accounting and tax	Produces the data in the format the bank needs.	Defines its accounting model, records its entries and prepares tax reporting.

What the bank needs to get started

A technology counterpartKnows the core system, the architecture and the institution’s release process.
A risk and compliance counterpartValidates the regulatory framework and the controls that apply to the institution.
A retail business counterpartDefines the product, the target clients and the launch calendar.

Let’s talk about your institution.

Request a meeting

How we work:our team inside the bank, alongside yours.