FOR BANKS, CITIES AND INFRASTRUCTURE PARTNERS

Come with us through FILIAR.

Follow one visit to a FILIAR endpoint. Then see what runs behind it and where your organisation fits.

Start the walk-through

Concept stage · no existing partnerships, licences or certifications

FILIAR OS · WALK-THROUGH

Nine moments, from first touch to clean goodbye.

Pick your perspective below. Each step shows what the person sees, and what it means for you.

Perspective

You are viewing FILIAR as · Bank

How does FILIAR become a physical access layer for our banking ecosystem?

Step 01 · ArriveContext step
A calm screen that says what this place can do.
Your service, visible
The endpoint announces cash, printing and advice — services your customers would otherwise need a branch for.
Step 02 · StartContext step
Useful before anyone logs in.
Your customers’ entry
Card, app, smartphone or service code: every route leads back to your authentication.
Step 03 · ConnectIn focus
The bank recognises its customer. FILIAR keeps no credentials.
Your authorisation
Approval happens in your banking app. FILIAR only receives a scoped session and stores no credentials.
Card, app, NFC or service code. FILIAR is designed to recognise the institution, then ask for approval in the customer’s own banking app.
Endpoint 04 · Berlin WeddingApproval required
Establish connection
FILIAR is designed to recognise your institution. No login data is stored.
01 Method selected
02 Institution detected
03 Approval in banking app
04 Securely connected
Bank card
Banking app
Smartphone (NFC)
Service code
Your authorisation
Illustrative interface · fictional data
Behind the interfaceAuthorisation stays with the bank. The endpoint only receives a scoped session — no credentials are stored.
Step 04 · Home bankIn focus
Once connected, the screen belongs to the bank.
Your experience
After connection the screen shows your customer’s home bank — balances, activity, actions.
A personal greeting, balances, recent activity and the actions this customer uses most — in the connected institution’s experience.
Endpoint 04 · Berlin WeddingSecurely connected
Good afternoon
Current account ••4417
Withdraw cash
Transfer
Statements & documents
More
Recent activity
Card payment · today
Credit · 27.08.
Direct debit · 26.08.
Your experience
Illustrative interface · fictional data
Behind the interfaceFILIAR OS switches from the neutral start to the connected home. The same endpoint can serve customers of several institutions.
Step 05 · TransactIn focus
A physical transaction, one clear step at a time.
You decide, FILIAR executes
You authorise the withdrawal; the endpoint dispenses cash and handles the receipt.
Withdrawing cash follows five visible steps: amount, review, approval, dispense, receipt. The customer always knows where they are.
Endpoint 04 · Berlin WeddingWithdraw cash
01 Amount
02 Review
03 Approval
04 Dispense
05 Receipt
Take €150.00
Please take your cash from the dispenser.
You decide, FILIAR executes
Illustrative interface · fictional data
Behind the interfaceThe bank authorises; the endpoint executes the physical part — dispensing cash and printing or sending the receipt.
Step 06 · ServicesContext step
One service catalogue. Each endpoint shows what it can really do.
Your modules
Cash, payments, documents and portfolio run as modules you choose to offer.
Step 07 · HelpIn focus
Help is part of the system, not an afterthought.
Your advisers, further out
Video advice, callback and appointments bring your service team to places without a branch.
“Advice & support” offers every channel side by side: ask Filo, instant help, callback, video advice, an on-site appointment, or reporting a technical problem.
Endpoint 04 · Berlin WeddingService team · approx. 2 min
Advice & support
Ask Filo
Instant help
Arrange callback
Start video advice
Book on-site appointment
Report technical problem
Your advisers, further out
Illustrative interface · fictional data
Behind the interfaceFilo, the built-in assistant, answers questions and can start the right flow. Video advice only appears where the endpoint has camera and microphone.
Step 08 · CloseContext step
A clean goodbye.
Session hygiene
The bank connection is cut and local data cleared — the session is designed to leave nothing of your customer behind.
Step 09 · OperateContext step
Behind the glass: a fleet, not a single machine.
Not your operating burden
Fleet status and updates are handled centrally, not by your branch staff.

01 / 09 · Arrive

Endpoint 04 · Berlin WeddingReady · no active connection

Touch the screen

Banking and branch services at this location

Cash available
Printer ready
Advice 08–20

Your service, visible

Illustrative interface · fictional data

BEHIND THE WALK-THROUGH

The service architecture underneath.

What you just saw runs on this: shared service modules, execution modes per endpoint, and a network model several institutions can use.

Example profile

Regional bank with its own branches

Illustrative configurations, not real institutions.

Infrastructure: FILIAR

One endpoint. Multiple institutions.

Session recognised — the service surface is resolved from configuration and session.

Institution A

Cash
Deposit
Statements
Support

Switch between example configurations — the hardware stays the same.

The architecture is designed to extend.

Today's service modules are the foundation. Further layers are anticipated in the architecture — designed, not active yet.

The endpoint can grow

Future architecture

FILIAR Invest
A physical workspace for the digital investment relationship.
- Portfolio
- Markets
- Watchlists
- Orders
- Savings plans
- Investment documents
- Broker support
Potential service layer · Status: Architecture exploration

Future modules are architecture explorations. No commitment, no date, no product.

WHERE PARTNERS FIT

You’ve seen the system. Now find your place in it.

Your choice stays active and shapes the rest of this page.

Active perspective: Bank

Keep physical presence without carrying it alone.

A shared service layer lets several institutions share one physical access point while keeping their own customer relationship.

Possible role in the project

Define the service scope, connect authentication and ledger, decide what is enabled for customers.

Modules in focus

Bank interfaces
Identity & consent
Session orchestration

Challenges we hear

Branch coverage under cost pressure
Self-service limited to cash
Direct-bank customers without physical access

Sensible next steps

1Scope a pilot region together
2Review the role split in detail
3Check integration with existing terminals

FROM WALK-THROUGH TO PILOT

Start with the use case. Build from there.

01DiscoverUnderstand the physical service requirement.
02ValidateIdentify viable services, integration needs and constraints.
03Co-designDesign the customer journey and physical experience.
04PrototypeTest the experience with the FILIAR concept.
05PilotDeploy into a controlled environment.
06ScaleExpand the physical service layer.

CHALLENGE ADVISOR

Start with your physical banking challenge.

Demo access on request

The FILIAR Terminal OS concept demo is shown to institutional partners only. Send a request and we will arrange controlled access.

01Request demo
02We review your request
03Controlled access

Request demo access

Technical whitepapers

Two working documents describe the concept in depth. We share them on request rather than publish them as open downloads.

No automatic download, no tracking pixel, no marketing list. Every request is handled by hand.

NEXT STEP

Let’s look at your case together.

You know the system and your role in it. Tell us about your location, institution or infrastructure — we reply personally.

BankExplore a bank pilot: which physical services should your customers reach first?

Initiated by Niels Jan Lopian. An independent European effort, open to co-development.

Talk to us

Tell us where you’re starting from. We reply personally.

Come with us through FILIAR.

Nine moments, from first touch to clean goodbye.

A calm screen that says what this place can do.

Useful before anyone logs in.

The bank recognises its customer. FILIAR keeps no credentials.

Once connected, the screen belongs to the bank.

A physical transaction, one clear step at a time.

One service catalogue. Each endpoint shows what it can really do.

Help is part of the system, not an afterthought.

A clean goodbye.

Behind the glass: a fleet, not a single machine.

The service architecture underneath.

One endpoint. Multiple institutions.

The architecture is designed to extend.

FILIAR Invest

You’ve seen the system. Now find your place in it.

Keep physical presence without carrying it alone.

Start with the use case. Build from there.

Start with your physical banking challenge.

Demo access on request

Technical whitepapers

Let’s look at your case together.

Talk to us

A calm screen that says what this place can do.

Useful before anyone logs in.

The bank recognises its customer. FILIAR keeps no credentials.

Once connected, the screen belongs to the bank.

A physical transaction, one clear step at a time.

One service catalogue. Each endpoint shows what it can really do.

Help is part of the system, not an afterthought.

A clean goodbye.

Behind the glass: a fleet, not a single machine.

One endpoint. Multiple institutions.

The architecture is designed to extend.

FILIAR Invest

Keep physical presence without carrying it alone.

Start with your physical banking challenge.

Demo access on request