Skip to content
Bilişim

Digital Channel Projects

Not an app, but a platform architecture that generates apps.

Mobile and internet banking, digital wallet apps, PIN-free payment experiences, partner portals, developer experience. A production model that derives every screen from components instead of writing it from scratch.

Discuss Your Project →Frequently asked questions
Screens generated from unique designs; new screens 8× faster, new apps 7× faster
133 → 2,581
Mobile payments for millions of users; transaction time at the station cut radically
90 days PIN-free
Credit card module on the mobile channel, delivered on schedule
13+ services · 3 card types

When organizations come to us

What we do

Signal 01

Business rules sit on the client side; every small change takes days of app store approval.

Signal 02

With no ready components, every screen is coded from scratch; development cost is high.

Signal 03

There is no shared infrastructure for the bank’s and its subsidiaries’ apps; technology investment is duplicated.

Signal 04

A mandatory PIN on every transaction slows the experience; loyalty rewards stay closed-loop.

Signal 05

UAT and go-live of credit, debit and virtual card modules on the mobile channel involve many stakeholders and a tight schedule.

Response 01Core SDK

Central management of integration and workflows; repetitive code disappears.

Response 02UI SDK

A reusable component library generated from modules; screens are assembled by configuration in minutes.

Response 03Orchestration middleware

Business rules in one place; even if the core system changes, the mobile channel is unaffected; a core banking migration costs the mobile channel close to zero.

Response 04PIN-free and contextual payment experiences

Time-limited PIN-free transactions for users who complete KYC, open-loop cashback, host-to-host services, instant reconciliation queries.

Response 05Card and mobile integration programs

Application, card details, payments, limits, virtual card, statements; multi-stakeholder parallel agile teams; UAT and go-live management.

Response 06Partner and developer portals

Standard partner APIs, sandbox, documentation.

Reference architecture

Zero business rules on the client: screen definitions and flows come from the server, and core banking stays behind the adapter layer.

Technical design decisions

  • Zero business rules on the client
  • Server-defined screens, changes without an app release
  • Isolation from core banking changes through the adapter layer
  • Component versioning and backward compatibility
  • Security: device binding, short-lived tokens, fraud signal integration
  1. 01
    Native apps and webiOS / Android / responsive web
  2. 02
    UI SDKDesign system, component library, screens by configuration
  3. 03
    Core SDKIdentity, session, secure communication, flow engine
  4. 04
    Orchestration middlewareBusiness rules, campaigns, content, flow definitions; channel-independent
  5. 05
    AdaptersCore banking, cards, payments, KYC, notifications
  6. 06
    ObservabilityEnd-to-end tracing, client telemetry

Frequently asked questions

Do we have to rewrite our current mobile app, or is a gradual transition possible?
A gradual transition is possible. The SDK + middleware layer is set up beside the existing app; screens move module by module to the new component infrastructure. The user sees a single app, while two architectures coexist behind it for a defined period.
Does moving business rules into middleware affect core banking?
No. The middleware sits between the channel and the core systems and talks to them through adapters. Even if core banking changes, the mobile channel is unaffected; this is the design that brings the cost of a core migration to the mobile channel close to zero.
What can be changed without an app store release?
Screen definitions, flows, business rules, campaigns and content. These are defined on the server side and released without republishing the app. Only new native capabilities require a store release.
How is the security model built?
Device binding, short-lived tokens, certificate pinning, session and device management, integration with fraud signals and the controls required by banking regulation are part of the SDK; they are not rebuilt in every app.
Are the SDK and middleware handed over to the organization? Does it create a dependency?
Yes, they are handed over. The platform is the organization’s asset; it is delivered with source code, documentation and knowledge transfer. The organization’s team produces new screens by configuration itself; the goal is competence, not dependency.
How are accessibility and performance targets handled?
The component library is designed to accessibility standards; performance budgets (launch time, screen transitions) are defined and monitored in production through client telemetry.

Related projects

All projects →
Digital Banking02

A next-generation mobile platform for a participation bank

Core SDK + UI SDK + orchestration middleware: 2,581 screens from 133 designs; new screens 8× and new apps 7× faster.

2,581 screens
Payment Technologies09

Mobile card integration program

Multi-stakeholder, on-schedule UAT and go-live of credit, debit and virtual card modules on the mobile channel.

13+ services
Energy · Retail12

GRC and a next-generation wallet at a fuel retailer

A GRC platform that automates risk and compliance controls in one layer; 90-day PIN-free mobile payment and instant cashback for millions of users.

100% digital

Let’s assess your project together.

In the first meeting we go through architectural risks, scale needs and compliance requirements together.

Discuss Your Project →