A human ambition behind the transformation
For Bank CTBC Indonesia, digital banking is not simply a technology channel. It is one of the primary ways the bank serves retail and corporate customers, builds trust, and makes everyday banking more convenient.
The bank had already established both Internet Banking (IB) and Mobile Banking (MB). Its ambition was to make these channels feel like parts of one connected banking relationship—not separate products that customers had to learn and navigate differently.
That ambition mattered because customers increasingly move between digital touchpoints. They may begin a task on one platform and complete it on another. Bank CTBC Indonesia therefore sought a more consistent, integrated, and user-friendly experience while strengthening the operational foundation for future digital service development.
Suitmedia worked as the strategic and implementation partner, helping the bank bring two independently operated platforms into a more cohesive digital ecosystem.
The business constraint beneath the visible problem
1. Different channels were creating one fragmented relationship
Before the initiative, Bank CTBC Indonesia’s IB and MB platforms were operated by two separate vendors. This has produced differences in system architecture, user interface design, workflows, and feature availability.
The visible problem was inconsistency. A customer using both channels could encounter different interfaces, navigation patterns, or transaction journeys. Not every feature was fully reflected across both platforms, making it harder to understand which channel supported a particular banking need.
For customers, the issue was more than visual variation. When familiar actions change from one platform to another, customers must spend additional effort learning the system. That can create confusion and weaken confidence, particularly when customers expect a bank’s digital services to behave as one connected experience.
The operational symptoms were equally important. Managing two different systems increased technical complexity and limited efficiency. Each platform could evolve according to its own structure, but the bank had less ability to maintain a common experience across channels.
This distinction between symptom and root cause shaped the project. The problem was not simply that the screens looked different. The deeper issue was that the channels had developed independently, with differences in architecture, workflows, features, and vendor management reinforcing one another.
2. The cost of maintaining the status quo
If left unaddressed, the fragmented setup could negatively affect customer satisfaction and digital engagement. Inconsistent experiences may make customers less likely to use digital banking confidently or regularly, which could slow the growth of Internet Banking and Mobile Banking utilization.
The status quo also created constraints on operational velocity. When two platforms require separate approaches, aligning a new feature or customer journey becomes more difficult. The bank must consider how the capability will work in each channel, whether the experience remains understandable, and whether existing functions continue to operate as expected.
System resilience was also relevant to the transformation. The source material does not claim that either platform was unreliable, but it does establish that separate systems increased technical complexity. Reducing unnecessary fragmentation was therefore important to creating a more manageable foundation for future development.
The bank also needed to protect the value already embedded in its existing services. Unification could not come at the expense of established workflows or current functionality. The challenge was to create a more coherent environment while migrating existing features without significantly altering how customers and the bank already carried out their processes.
That requirement made the initiative a balancing exercise. Bank CTBC Indonesia needed change where inconsistency was creating friction, but continuity where established workflows were already serving customers and operations.
How the solution connected decisions to outcomes
1. Establishing one view of the existing experience
Suitmedia began with a comprehensive assessment of the current IB and MB platforms. This included creating a feature inventory, mapping user flows, and identifying pain points.
This first decision mattered because integration could not be approached responsibly by designing a new interface in isolation. The bank first needed a clear picture of what already existed across both channels: which features were available, how users moved through them, where the experiences diverged, and which established processes needed to be preserved.
The assessment also provided a basis for preventing functional regression. If features were consolidated without a complete inventory, some existing capabilities could be overlooked or become unavailable in the unified environment. By reviewing the platforms before defining the future experience, the project could treat the current ecosystem as a set of capabilities to be carried forward—not simply a set of screens to be replaced.
The operational obstacle was the independence of the two existing platforms. Their separate vendor arrangements and differing structures meant that integration involved more than aligning visual elements. Suitmedia’s approach addressed this by examining both platforms together, allowing the project team to identify differences in features, workflows, and user experience before developing the common framework.
2. Designing consistency without disrupting familiar banking tasks
Based on the assessment, Suitmedia designed an integrated UI/UX framework for IB and MB. The framework harmonized visual elements, navigation structures, and design components across both channels.
This decision mattered because consistency is most valuable when it reduces cognitive effort. Customers should not need to relearn the logic of digital banking merely because they change devices or channels. A shared visual and navigational language helps make the relationship between the two platforms clearer.
At the same time, the project was not designed to significantly alter established workflows. That constraint was strategically important. In banking, familiar processes carry operational value: customers know how to complete common tasks, and internal stakeholders understand how those journeys function. Changing everything at once could create new friction while attempting to remove existing friction.
The resulting approach sought a middle path. Suitmedia standardized the experience where differences were creating confusion, while maintaining existing functionality and workflows wherever continuity was important. This was not a cosmetic redesign; it was an effort to create a common operating logic across two channels without forcing unnecessary behavioral change.
Validation and refinement formed part of this stage. The design was reviewed and refined before development and deployment, helping ensure that the proposed experience addressed identified pain points and remained aligned with the bank’s requirements.
3. Moving from separate platforms toward a centralized system
After the integrated UI/UX framework was finalized, the design was developed and deployed into a centralized CMS system covering both migrated existing features and newly developed functionalities.
The move to a single CMS mattered because a consistent customer experience requires more than a shared design document. The underlying system must support common structures and coordinated management across the channels. Centralization created the basis for presenting IB and MB as parts of one ecosystem rather than as entirely separate digital products.
The implementation challenge was to bring together existing capabilities without interfering with current processes or features. Suitmedia addressed this by combining migration with standardization: existing functions were consolidated into the unified system, while the experience around them was aligned through common design and user-flow principles.
This approach also supported future product expansion and innovation. The project did not only resolve present inconsistencies; it created a scalable digital platform for Bank CTBC Indonesia’s future development. The strategic value lies in reducing the distance between today’s channels and tomorrow’s capabilities.
4. Extending the ecosystem with capabilities customers increasingly expect
The unified environment also introduced enhanced capabilities: online registration, QRIS payments, biometric authentication, e-wallet top-ups, and account unbinding features.
These additions addressed different parts of the digital banking relationship. Online registration supports a more accessible entry into digital banking. QRIS payments and e-wallet top-ups simplify everyday transactions, while biometric authentication strengthens the security experience. Account unbinding provides customers with greater control over their connected banking relationships.
The rationale was not to add features for their own sake. New capabilities had to contribute to the bank’s broader objectives: strengthen security, improve operational efficiency, and elevate the overall customer experience.
Introducing these functions within the same unified ecosystem also reduced the risk of creating another layer of fragmentation. Rather than adding capabilities independently to separate channels, the project placed them within a more consistent environment, supporting clearer journeys and a more coherent digital proposition.
Evidence of a stronger operating model
1. A more coherent experience across IB and MB
The project achieved the successful unification of user flows and interface design across Internet Banking and Mobile Banking. Bank CTBC Indonesia was supported in delivering a more cohesive and intuitive experience aligned with the expectations of today’s digital customers.
This outcome directly addressed the original customer-facing problem. Users of both platforms were given greater clarity and consistency in how the channels look, operate, and guide them through banking tasks.
The available evidence does not provide adoption, retention, transaction-volume, or customer-satisfaction figures. It therefore would be inappropriate to claim a quantified increase in digital usage or engagement. The confirmed impact is qualitative: the digital banking experience became more cohesive, user-friendly, and consistent across both platforms.
That consistency has practical importance. Customers who move between IB and MB can encounter a more connected experience, while the bank has a clearer foundation for managing the relationship across digital touchpoints.
2. A more scalable foundation for continued development
The unified CMS system brought migrated existing functionalities and newly developed capabilities into one centralized environment. This created a stronger basis for coordinating the digital banking experience and supporting future product expansion and innovation.
The project also strengthened stakeholder confidence in the future-readiness of Bank CTBC Indonesia’s digital banking infrastructure. This does not mean that every future challenge has been eliminated. It means the bank now has a more coherent platform foundation from which future development can be considered.
The operational benefit is therefore connected to both present and future work. In the immediate term, the bank gained alignment across interfaces, user flows, and feature availability. As a second-order effect, the centralized approach can make future digital initiatives easier to frame around a shared ecosystem rather than separate channel decisions.
3. New capabilities within a connected customer journey
The addition of online registration, QRIS payments, biometric authentication, e-wallet top-ups, and account unbinding expanded the role of the digital ecosystem. These capabilities were intended to improve accessibility, convenience, security, and customer control.
Their significance comes from being introduced alongside the integration effort. A bank can add individual features and still leave customers with a fragmented experience. Here, the new capabilities were developed as part of a broader effort to standardize the digital journey across channels.
The result is a more future-ready experience without evidence of unsupported claims about scale or performance. The project shows that operational efficiency and customer experience can be addressed together when platform structure, user journeys, and new capabilities are considered as connected decisions.
What the experience reveals about durable transformation
1. Integration begins with understanding, not redesign
The first durable lesson is that enterprise transformation should begin by understanding the systems and journeys already in operation. The feature inventory, user-flow mapping, and pain-point assessment created the shared basis needed to make responsible decisions.
This principle is especially relevant when platforms have evolved independently. Leaders may see interface inconsistency as the immediate issue, but the underlying causes can include different architectures, workflows, vendors, and feature sets. Without examining those causes, a redesign may improve appearance while leaving the operating problem intact.
2. Standardization must protect useful continuity
The second lesson is that consistency does not require abandoning everything familiar. Bank CTBC Indonesia sought to standardize the user experience while migrating existing functionalities without significantly altering established workflows.
That balance is important in regulated and customer-sensitive environments. Transformation succeeds when it removes unnecessary complexity without introducing avoidable disruption. The right question is not “How much can we change?” but “Which differences create friction, and which existing behaviors should be preserved?”
3. Customer experience depends on the operating model behind it
A consistent experience cannot be sustained by design alone. The move toward a centralized CMS system connected the user-facing framework with a more unified way of managing digital capabilities.
This is why the project’s value extends beyond visual alignment. The bank’s future experience depends on whether new features can be added, maintained, and expanded through a coherent foundation. Customer experience becomes more durable when the operating model supports it.
4. New features create more value when they reinforce a clear system
Online registration, QRIS payments, biometric authentication, e-wallet top-ups, and account unbinding each address a specific customer or security need. Their broader value increases when they are introduced within a consistent ecosystem rather than separate channel experiences.
For enterprise leaders, this is a reminder that feature roadmaps should be assessed not only by what each feature does, but also by how well it strengthens the overall customer journey. A connected system makes individual improvements easier to understand and more valuable as part of the relationship.
Strategic Insights for the C-Suite
- Treat fragmented channels as an operating-model issue, not only a design issue.
Different interfaces often reflect deeper differences in systems, workflows, ownership, or vendor structures. Executives should address the underlying operating model if they want customer experience improvements to last. - Use transformation to remove friction without discarding institutional knowledge.
Established workflows contain valuable experience from customers and operating teams. The strongest transformations preserve what works while standardizing the areas that create confusion, duplication, or unnecessary complexity. - Build one customer experience on one coherent foundation.
A shared design language is important, but it must be supported by systems that allow capabilities to be managed consistently. Centralization can create the conditions for clearer governance and more scalable future development. - Judge new capabilities by how they strengthen the whole journey.
Online registration, payments, authentication, and account controls should not be evaluated as isolated features. Their strategic value is greater when they make the full relationship simpler, safer, and more coherent across channels.
