Zenus Bank's October 16, 2024 integration of Tuum's Accounts and Payments modules marked a change in what the bank could distribute: a banking platform for other institutions, alongside the direct service it had built for retail customers. The announcement described a completed core integration, with banks, fintechs, super apps and businesses able to embed U.S. banking capabilities in their own products.

At that point Zenus reported reach into more than 120 countries and more than a dozen BaaS partnerships under development. Chairman Mushegh Tovmasyan expected many to launch in the fourth quarter of 2024. Tuum chief revenue officer Edgardo Torres-Caballero emphasized adaptable infrastructure. The country figure described Zenus's footprint; the partnership figure described a pipeline.

The account core and the customer experience had different jobs

A subsequent Tuum case study, published on February 23, 2025, brings another supplier into the picture: Purpleplum, which provided the digital front end. Tuum supplied core banking; Purpleplum supplied configurable customer journeys. Zenus combined those components with its banking and payment infrastructure. The resulting product was intended for financial institutions that needed both underlying banking functions and a usable operating interface.

Show data tableHide data table

Scroll left or right to see all columns

The account core and the customer experience had different jobs
Layer	Documented role	Why it matters to an institutional partner
Zenus Bank	Banking services and the infrastructure offering	Connects the technology to accounts, card programmes and payment services.
Tuum	Core account and payment capabilities	Provides the account and transaction foundation beneath partner products.
Purpleplum	Configurable digital interfaces and wallet experience	Adapts onboarding, dashboards and commercial workflows to different customer groups.
Integration between components	Data synchronization, APIs and middleware	Keeps front-end actions aligned with underlying account and transaction records.

The implementation account describes customization for digital onboarding, virtual and physical card management, multi-currency accounts, corporate expenses and receivables. Its technical emphasis is on the connection between components: data synchronization and API orchestration were needed to give customers one coherent service.

For a programme manager, a balance displayed in a dashboard and a payment recorded in a banking system must agree. A configurable interface is useful only when those underlying records remain consistent. That is why the integration work matters commercially: a partner can tailor the visible experience without treating account records, payment events and operating tools as unrelated products.

Twelve months overall did not mean twelve months of coding

The full case study gives two different project durations. Selection to full operational launch took approximately 12 months; active development took about six to seven months. It says Zenus deliberately allowed additional time for capabilities including virtual accounts. That makes the timetable a useful account of product decisions, rather than a generic claim that the shortest possible implementation was best.

Show data tableHide data table

Scroll left or right to see all columns

Twelve months overall did not mean twelve months of coding
Reported measure	Period or quantity	What the figure measures
Selection to operational launch	Approximately 12 months	The overall transformation described in the later supplier case study.
Active development	About 6-7 months	A phase within the project, not an additional period to add to the overall duration.
BaaS relationships being developed	More than 12 in October 2024	The announced pipeline, with prospective Q4 launches.
International reach cited at announcement	More than 120 countries	Zenus's stated footprint, not a product-by-product availability list.

Sources for the measures: Zenus's October 2024 announcement and the later Tuum and Purpleplum implementation case study.

Tuum's customer account says migration was phased to maintain service availability. That approach gives the bank room to move operating functions in stages while keeping an existing service running. It connects the implementation timetable to continuity for customers already using the bank.

Virtual accounts made the scope decision consequential

The supplier case study identifies virtual-account functionality as a reason for extending development. It also describes personalized dashboards and tools for commercial workflows. The significance is practical: an institutional customer needs to organize activity, view its own operations and reconcile payments, as well as offer an end user somewhere to hold funds.

A bank supporting several partner brands must supply repeatable banking capabilities while accommodating different onboarding paths and operational requirements. The modular arrangement gave Zenus a way to divide that work among the account core, the user interface and its own banking platform. A change to a partner's dashboard can then be considered separately from a change to underlying banking functionality.

Later operating disclosures show the scale of the account categories discussed in the implementation. In its September 2025 to August 2026 responsible-banking report, Zenus records faster growth in virtual accounts than in card accounts. The combined figure summarizes the account portfolio as a whole. These are subsequent bank results, rather than a calculation of the share caused by the Tuum integration.

Source

Zenus 2026 PRB report, page 13

Bank-reported growth for September 2025 to August 2026. The combined figure is an aggregate of account categories. These are later operating disclosures, not a measured contribution from Tuum.

Show data tableHide data table

Scroll left or right to see all columns

Account growth after the infrastructure-bank transition (%)
Category	Year-over-year growth
Virtual accounts	206.1%
Card accounts	75.8%
Combined account portfolio	128.3%

The 2025 strategy clarified the direction of travel

Contemporary FinTech Futures coverage on October 21, 2024 described packaged payment initiation and validation, local payment-formation rules, and automated processing and settlement. Those details put the account core in the context of a working payment service: the bank needed both a record of the account and processes for moving money from it.

On July 22, 2025, Zenus announced that its dedicated retail platform would close on October 22 while institutional and fintech services continued. Embedded banking, BIN sponsorship and cross-border payments were the retained growth areas. The 2024 technology integration had already supplied a foundation for that institutional distribution model.

The same reporting cycle distinguishes transaction activity from cross-border transaction volumes. Both expanded, but their growth rates use separate bases. For the architecture described in the case study, the useful implication is that an expanding account base also brings more payment activity to reconcile and support; the disclosure does not identify a vendor-specific throughput result.

Source

Zenus 2026 PRB report, page 13

Each rate uses its own prior-period base. The report does not provide the underlying counts here or isolate Tuum-processed activity.

Show data tableHide data table

Scroll left or right to see all columns

Later payment activity grew on two reported measures (%)
Category	Reported growth versus previous period
Transaction activity	927.0%
Cross-border transaction volumes	194.8%

The completed integration, documented front-end partner and virtual-account work give the project specific substance. Its public measures remain bank and supplier accounts: the sources do not disclose independently verified cost savings, availability percentages or how many of the announced prospective partnerships went live. The commercial value lies in applying those reusable banking components to each partner's operating needs.