Skip to content

FOR BANKS, CITIES AND INFRASTRUCTURE PARTNERS

The physical service layer for digital banking.

Concept stage · no existing partnerships, licences or certifications

  • One endpoint

    Several institutions

  • Shared infrastructure

    Independent access point

  • Software-defined services

    Hardware-backed execution

  • European architecture

    Institution-controlled services

PHYSICAL SERVICE LAYER

The physical service layer for digital banking.

Institutions keep the account, the relationship and the authorization. FILIAR executes the physical service on shared infrastructure — a concept developed together with banks, cities and technology partners.

The bank owns the relationship. FILIAR executes the physical service.

FILIAR is not a bank and holds no account. It executes physical banking services on behalf of the institution that owns the customer relationship.

Architecture baseline v0.1 · intended design, not a running platform

  • Digital bank / fintech

    Offer physical services without building a proprietary branch estate.

  • Established bank

    Move suitable standardized branch processes onto shared physical infrastructure.

  • City / location partner

    Keep access to banking services without a traditional full-service branch.

Which perspective are you working from?

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

Active perspective: Bank

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

  • interfaces
  • identity
  • orchestration
Discuss terminal integration

Challenges we hear

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

Sensible next steps

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

Services as modules, not as a bundle.

An institution switches on what fits its model. The rest stays off.

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.

Current architecture

  • Cash
  • Deposit
  • Transfer
  • Account
  • Statements
  • Documents
  • Cards
  • Verify
  • Support
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 THE ENDPOINT CAN GROW

The financial relationship doesn't end with the bank account. Neither should the physical endpoint.

FILIAR is designed first around physical banking services. The same session-based, institution-controlled architecture could later carry other regulated financial services. The first extension being explored is FILIAR Invest.

And the endpoint can go further.

The app stays personal. FILIAR adds space, context and physical service.

Architecture exploration

  • Cash
  • Transfer
  • Account
  • Documents
  • Support
  • Invest

FILIAR Invest is an architectural extension currently being explored. Availability would depend on institution integrations, technical interfaces and regulatory requirements.

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.

FILIAR isn’t being built for one bank. It’s being built with the right partners.

We’re looking for banks, cities, municipalities, manufacturers, investors and technology partners to help build a shared physical service layer for banking in Europe.

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.

Partner category

We use your details solely to process your enquiry. See our privacy policy for details. privacy policy