Summary

  • Raiffeisen Bank JSC sells a regulated transaction and account-continuity surface: accounts that receive, hold, verify, move and document money through Ukrainian payment rails, foreign-exchange controls, business workflows and mobile channels during a war.
  • The strongest public evidence is not a single tariff. It is a stack of NBU status, license, current financial figures, SEP payment-rail rules, Raiffeisen Business Online workflow details, MyRaif usage disclosures, RBI's Ukraine resilience statements and public app-store signals.
  • The evidence supports the bank's role as a large, systemically important Ukrainian bank, but the thesis remains unproven without private unit economics, channel-level reliability data and retention evidence that shows how many customers stay because switching would break payments or delay compliance-sensitive transactions.

The transaction that cannot break

Imagine a mid-sized Ukrainian exporter on a Friday afternoon. Payroll is due. A foreign-currency incoming payment is somewhere between the sender, correspondent banks and the company's local account. The accountant needs evidence that the payment is moving, the finance director needs to know whether currency-control documents will be requested, and the owner needs the money credited before suppliers tighten delivery terms. If the bank's app is unavailable, the branch is closed during an air alert, or a compliance review stalls a payment without a clear route for documents, the problem is not a bad user experience. It is liquidity cost, reputational cost and sometimes a broken production schedule.

That is the economic puzzle around Raiffeisen Bank JSC. A basic account can look like a commodity until the customer needs it to keep working under pressure. The paid unit is a regulated transaction and account-continuity surface. A customer buys the ability to keep accounts, cards, business payments, foreign-exchange operations, online documents, payment tracking, branch fallback and regulatory evidence moving with fewer failure points than a cheaper or simpler substitute. The unit is costly because it has to combine balance-sheet capacity, NBU supervision, payment-system access, cyber resilience, compliance staff, branch and ATM logistics, customer support, digital product development and wartime contingency work. Public evidence can show the size of that surface and some proof points around operation, but it cannot show the per-customer margin or the exact reliability record.

The bank's official identity is not in dispute. The National Bank of Ukraine's institution page lists "Raiffeisen Bank Joint Stock Company", Code ID NBU 300335 and EDRPOU code 14305909, with website https://raiffeisen.ua, a solvent status, foreign-bank-group classification, Deposit Guarantee Fund participation and systemic importance (https://bank.gov.ua/en/supervision/institutions/14305909). The Ukrainian version of the same NBU page also lists the substantial direct owners as Raiffeisen Bank International AG of Austria and the European Bank for Reconstruction and Development, and names Natalia Gurina as chair of the management board and Andrii Stepanenko as chair of the supervisory board (https://bank.gov.ua/ua/supervision/institutions/14305909). The NBU ownership page records the bank's old names, from Aval to Raiffeisen Bank Aval and then AT "Raiffeisen Bank" from 17 May 2021 (https://bank.gov.ua/supervision/registration/shareholders/300335).

Those details matter because this article is not trying to value Raiffeisen Bank International as a global group. Group facts explain capital, governance, technology and sanctions pressure. They do not prove the Ukrainian bank's account economics. For this subject, the useful question is narrower: why would a Ukrainian individual, entrepreneur or corporate treasurer keep paying attention to Raiffeisen rather than migrate to PrivatBank, Oschadbank, monobank, PUMB, UkrSibbank, OTP, Credit Agricole, a payment processor, a cash workaround, a delayed transaction or a lawful offshore structure?

The answer starts with failure cost. In ordinary times a customer might switch banks for lower account fees, better app design or a smoother onboarding path. In wartime Ukraine, switching has extra costs. Counterparties must update account details. Salary projects, card limits, tax templates, signatory rights, foreign-currency payment procedures, loan covenants, guarantees and merchant acquiring links must be re-established. If the old account is the account customers already know, migration itself becomes a risk event. Raiffeisen's own Raiffeisen Business Online page describes the bank's move to a single MFO 300335 and says that, during a transition period, incoming payments sent to old closed accounts with MFO 380805 were automatically credited to the new account, while customers were notified about counterparties still paying old details (https://raiffeisen.ua/en/aem/biznesu/onlain-servisy/raiffeisen-business-online.html). That is a small public window into a large hidden cost: account metadata is part of the customer's operating system.

The license defines the surface

The NBU banking license is the legal foundation of the product. The license PDF for NBU code 300335 gives the bank name, code, EDRPOU, Kyiv address and banking license number 10. It lists core operations: attracting repayable funds and banking metals from the public, opening and maintaining current, correspondent and escrow accounts, and granting credit from attracted funds at the bank's own risk (https://bank.gov.ua/files/Licences_bank/300335.pdf). Older license entries in the same file also show a broader historical menu that included payment instruments, foreign-currency operations, securities activity, safe boxes, factoring, leasing, collection and correspondent accounts.

For customers, that is the difference between an app front end and a bank. The continuity surface begins with permission to take deposits, maintain accounts and move money. It then extends into the bank's operating choices: how it supports current accounts, how it responds when a payment needs compliance review, how it keeps remote access working, how it gives businesses evidence of payment status, and how it maintains fallback capacity when the digital channel is not enough.

Raiffeisen's public website gives a practical view of that bundle. The homepage presents private, business, premium and corporate client segments; current accounts, cards, deposits, custody services, foreign-exchange services, acquiring, salary projects, account opening for private entrepreneurs, cash management, open banking, Raiffeisen Business Online and branch information all sit in the public menu (https://raiffeisen.ua/en). This is not proof of pricing power by itself. It is evidence that the bank sells a broad account relationship rather than a single payment app.

The business side is more revealing. Raiffeisen Business Online is described as internet and mobile banking for business. The page offers remote registration and key activation with electronic signatures, deposit opening without a branch visit, online loans for private entrepreneurs, credit-operation information, business-card controls, currency transactions, electronic document workflow, access-rights management, information-security materials and SWIFT GPI payment tracking (https://raiffeisen.ua/en/aem/biznesu/onlain-servisy/raiffeisen-business-online.html). The system's value is not only that a customer can click buttons. It is that several expensive bank functions are being folded into the account: authentication, document handling, payment creation, foreign-currency support, signatory control and operational evidence.

The retail side has a similar continuity angle. The MyRaif page says the mobile bank can manage finances without branches and queues, supports cards, deposits, loans, transfers, payments, currency exchange and branch or ATM search, and reports more than 800,000 active users, more than 200,000 clients connected to the updated cashback function and more than 2 million transactions daily (https://raiffeisen.ua/uk/aem/pryvatnym-osobam/onlain-servisy/myraif.html). App-store listings are not audited operating statistics, but Apple's page for MyRaif repeats the 800,000 user and daily transaction claims and shows a 4.8 rating from 81,000 ratings, while the Raiffeisen Business Online app page shows a 4.9 rating from 12,000 ratings (https://apps.apple.com/ua/app/myraif-mobile-bank/id1582978231 and https://apps.apple.com/ua/app/raiffeisen-business-online/id1500897229). These are market signals, not final proof of reliability. They show adoption and visible customer engagement around the channel where switching cost is created.

SEP turns bank reliability into public infrastructure

Raiffeisen's account continuity depends on Ukraine's national payment rails. The NBU describes SEP, the System of Electronic Payments, as the national electronic payment system for hryvnia settlements between banks and clients within Ukraine; the NBU is both operator and settlement bank. SEP handles more than 99 percent of interbank payments in Ukraine, is a systemically important payment system, is an RTGS system, operates 24/7 after the SEP 4 generation, and processes an average 1.2 million payments per day worth UAH 653 billion (https://bank.gov.ua/en/payments/sep). This matters because Raiffeisen's customers are not just buying an app. They are buying the bank's ability to participate reliably in a national settlement layer whose failure would affect payroll, supplier settlement, taxes, treasury movement and card-account funding.

The next layer is instant transfer. The NBU says instant credit transfers are account-to-account payment transactions delivered immediately after acceptance at any time in a 24-hour day, that SEP 4.1 providing instant credit transfers launched in December 2024, and that payment service providers rendering credit transfer services must provide instant credit transfer under NBU requirements (https://bank.gov.ua/en/payments/ips). In the long run, this pushes bank accounts closer to card-like speed and raises customer expectations. It also lowers the tolerance for old batch habits. A bank whose business customers depend on account transfers must keep up with the NBU's instant-payment and ISO 20022 direction or risk losing the transaction relationship to banks and fintech interfaces that make the payment feel immediate.

Open banking adds another pressure. The NBU defines open banking as secure, structured data exchange between account-servicing payment service providers and third-party payment service providers through specialized APIs, with user consent, for account information and payment initiation services. The NBU's open-banking page says account-servicing providers must set up specialized interfaces, provide continuous real-time access to user accounts for authorized third parties, publish technical documents and verify third-party authorization through the Payment Infrastructure Register (https://bank.gov.ua/en/payments/open-banking). Raiffeisen's own open-banking customer page says data is shared only with valid customer consent, only to the allowed extent, and that customers can withdraw consent (https://raiffeisen.ua/en/aem/pryvatnym-osobam/onlain-servisy/open-banking.html).

This changes the switching-cost story. Open banking can make account data more portable and reduce lock-in based on information opacity. But it also rewards banks that have clean account data, stable APIs, strong consent flows and trustworthy authentication. If the customer can see balances across banks and initiate payments from elsewhere, the bank has less room to hide behind account inertia. It has to earn continuity with uptime, accuracy, support, compliance clarity and integrated services.

What the current NBU numbers show

The bank is large enough for continuity to be a real product, not a rhetorical claim. The NBU's current supervisory data page links to bank-level spreadsheets, including aggregated balance-sheet accounts and structural-unit counts (https://bank.gov.ua/en/statistic/supervision-statist). In the NBU balance table dated 1 June 2026, Raiffeisen Bank JSC is listed under banks owned by foreign bank groups with total assets of UAH 280.5 billion, customer loans and receivables of UAH 92.5 billion, cash and equivalents of UAH 38.5 billion, securities at fair value through other comprehensive income of UAH 60.0 billion, securities at amortised cost of UAH 21.2 billion, total liabilities of UAH 224.8 billion, amounts due to customers of UAH 213.1 billion and total equity capital of UAH 42.3 billion (https://bank.gov.ua/files/stat/aggregation_2026-06-01_eng.xlsx).

The same spreadsheet's financial-results tab shows Raiffeisen with net interest income of about UAH 8.44 billion, commission income of UAH 3.30 billion, commission expenses of UAH 2.36 billion, net commission income of UAH 940.7 million, administrative and other operating expenses of UAH 4.67 billion, payroll costs of UAH 1.97 billion and profit after tax of about UAH 2.63 billion for the year-to-date table through the reporting date (https://bank.gov.ua/files/stat/aggregation_2026-06-01_eng.xlsx). These numbers prove scale and profitability in the public record. They do not prove that a specific digital account, business package or cash-management module earns an attractive margin. That distinction is important. The transaction-continuity thesis is an inference from the revenue mix, service footprint and channel evidence, not a disclosed product profit statement.

The deposit side also supports the account-continuity lens. Amounts due to customers of UAH 213.1 billion are not just funding. They represent balances that customers have decided to leave with the bank. Some of those balances are rate-sensitive deposits. Some are operational current accounts. Some are retail balances tied to cards and app habits. Some are corporate liquidity balances tied to payroll, tax, supplier and foreign-currency workflows. The public table does not divide them into the exact customer behaviors that matter most. But it shows that Raiffeisen's account surface is large enough that even small frictions in migration could matter economically.

Branch and unit data complicate the digital story. The NBU structural-unit table dated 1 April 2026 shows Raiffeisen Bank JSC with 496 operating structural units, down from 1,186 in the older start of the table and 502 to 504 through several recent years (https://bank.gov.ua/files/stat/Kil_pidr_2026-04-01_eng.xlsx). RBI's annual report uses a narrower "business outlets" figure of 266 for Ukraine at year-end 2025, along with around 1,250 ATMs and about 3 million customers (https://www.rbinternational.com/content/dam/rbi/ho/investors/results-reports/annual-reports/rbi/2026-03-02%20RBI%20Annual%20Report%202025.pdf.coredownload.pdf). The difference likely reflects definitions, not necessarily a contradiction: NBU structural units and RBI business outlets need not count the same thing. The economic point is that Raiffeisen is still carrying physical reach while also pushing customers toward remote channels. That hybrid cost base is expensive, but in Ukraine it can also be part of the value proposition.

The cost structure implied by the public record is not the cost structure of a pure app bank. A regulated Ukrainian bank has to maintain capital, liquidity, compliance controls, cash logistics, branch operations, staff training, cyber defenses, software, electronic signatures, customer support, payment-system participation, currency-control handling and audit evidence. Raiffeisen's public financial table shows administrative and operating expenses running at several billion hryvnias in the year-to-date period. The bank's business pages show a service suite that demands specialists, not only code: cash manager services for corporate clients, payroll projects, merchant acquiring, documentary operations, custody, foreign-exchange services and Raiffeisen Business Online support. If the customer pays for continuity, the bank's cost base is the reason continuity is not cheap.

Revenue logic follows from that cost base, but the public record only lets the analysis go so far. The bank can earn from net interest income on customer balances and loans, fees and commissions on accounts, cards, payments, cash management and acquiring, foreign-exchange spread, credit products and corporate services. Public figures show material net interest income and commission income. They do not show which customers subsidize which services, whether digital account bundles are high-margin, or whether war-related continuity investments are recovered in fees, spread, cross-selling or lower churn. The evidence supports the idea that continuity is monetizable. It does not prove the margin of the paid unit.

That is why the unit must be valued as a switching-cost surface rather than a visible tariff. A firm does not necessarily pay a line item called "continuity." It pays account fees, payment fees, foreign-exchange costs, loan margins, custody charges, payroll fees, acquiring charges, card fees, interest spread and staff time. It also pays by keeping balances with a bank instead of shopping every hryvnia of deposit yield. The bank's reward is embedded in the relationship. The customer's reward is reduced disruption.

Wartime continuity is part of the product

RBI's 2025 annual report gives the clearest public wartime operating claim. In the interview section, RBI describes Raiffeisenbank Ukraine as the country's fourth-largest bank and "the largest foreign bank by far", operating 266 business outlets, maintaining around 1,250 ATMs and serving approximately 3 million customers. It says ATM availability was 97 percent despite bombing campaigns and associated power outages; that none of the bank's critical processes had failed during the war; that 99 percent of branches had generators; that branches in cities close to the front, such as Kharkiv and Dnipro, were relocated underground; that all customer transactions are processed in the cloud; and that Raiffeisenbank Ukraine had never ceased lending, especially in energy and agriculture (https://www.rbinternational.com/content/dam/rbi/ho/investors/results-reports/annual-reports/rbi/2026-03-02%20RBI%20Annual%20Report%202025.pdf.coredownload.pdf).

These claims come from the parent company's annual report, not a Ukrainian supervisory uptime audit. They should be treated as official group disclosure about the Ukrainian unit, not as independent proof from a regulator. Still, they are strong evidence for the thesis because they name the operational proof points a customer would care about: branch power, ATM availability, relocated branches, cloud processing, critical-process continuity and lending during the war. A bank account that continues through power outages and attacks is not the same product as a bank account that works only when infrastructure is calm.

The war also changes the buyer's calculus. In a peaceful banking market, an app with lower fees and faster onboarding can pull customers away. In a country under attack, customers may still value app convenience, but the comparison becomes wider. Does the bank have a branch or ATM fallback? Can staff answer about compliance documents? Will payroll and taxes clear? Can a business still get credit for energy or agriculture assets? Does the bank's ownership and capital position give confidence that it will not disappear during a stress cycle? Does the mobile channel work when local infrastructure is damaged? These are not abstract "trust" questions. They are failure-cost questions.

Raiffeisen's recent public financing notices fit the same pattern. In June 2026, the bank said it and the EBRD had received the first European Union grant in Ukraine under the Ukraine Investment Framework to help businesses insure investments financed by Raiffeisen and the EBRD against war-related risks (https://raiffeisen.ua/en/news/pershiy-v-ukrani-grant-yes-na-pokrittya-voyennih-rizikiv-dopomozhe-biznesu-strahuvati-investici-profinansovani-raiffeisen-bankom-ta-yebrr-2345). The bank also announced participation with EBRD and the Green Climate Fund in a climate-focused facility intended to fund agribusiness, commercial transport, pharmaceuticals and other companies investing in sustainability projects (https://raiffeisen.ua/en/news/yebrr-i-gcf-nadali-raiffeisen-banku-50-mln-yevro-dlya-zelenogo-finansuvannya-ukrainskogo-biznesu-2330). These announcements do not prove account margins. They do show why the account relationship can be bundled with credit, grant access, documentation and institutional finance.

The operating logic is especially strong for SMEs. A business may first choose a bank because it needs a current account. Over time the bank touches payroll, merchant acquiring, tax payments, counterparty payments, loans, guarantee documents, currency exchange, online signing, credit lines and support calls. The more of those functions are tied to one bank, the higher the switching cost. Continuity becomes a product when a bank makes it less risky for a business to stay open and more expensive to move every dependency elsewhere.

The Ukrainian banking market has serious substitutes. PrivatBank has enormous scale. Oschadbank has state backing and a large legacy network. Monobank, operating through Universal Bank, set a high bar for consumer digital experience. PUMB, UkrSibbank, OTP, Credit Agricole, ProCredit and other banks give corporate and retail clients alternatives. Payment processors and merchant platforms can abstract parts of the transaction experience. Cash can be a last resort for some small retail flows. A lawful offshore account can sometimes help international business settlement. These substitutes keep Raiffeisen honest. But they do not remove migration cost once the customer has built workflows around Raiffeisen's regulated account.

Compliance is a service and a bottleneck

Sanctions and compliance pressure are not side issues for this bank. RBI's 2025 annual report says the consequences of Russia's war of aggression against Ukraine remained a key challenge for the management board. It states that RBI had significantly reduced activities in Russia since the beginning of the war and taken extensive measures to minimize risks related to tightened sanctions and compliance requirements. It also says 2025 discussions focused on compliance process enhancement, prevention of money laundering and terrorist financing, and financial sanctions, particularly full compliance with European and international sanctions packages (https://www.rbinternational.com/content/dam/rbi/ho/investors/results-reports/annual-reports/rbi/2026-03-02%20RBI%20Annual%20Report%202025.pdf.coredownload.pdf).

For the Ukrainian unit, the parent group's Russia problem is context, not evidence that Ukrainian customer service is weak. The public record does not show that Raiffeisen Bank JSC's Ukrainian account operations are impaired by the Russian subsidiary's legal and sanctions exposure. But the context changes what the customer is buying. A bank in this group must satisfy NBU expectations, Ukrainian wartime controls, international correspondent-bank scrutiny, group compliance rules and sanctions expectations from European and U.S. frameworks. Cross-border payments, foreign-currency operations, trade finance and certain counterparties can be subject to deeper review. That review can protect the customer from a worse outcome, but it can also create payment friction.

This is why compliance has to be decomposed. Compliance cost is staff, systems, screening, training, escalation and auditability. Failure cost is a blocked payment, a rejected transfer, an inquiry from a correspondent bank, a frozen relationship or a missed delivery. Switching cost is the work of recreating documents, signatory authority, payment templates and bank explanations somewhere else. A customer does not buy "trust" as a mood. It buys a lower probability that compliance-sensitive money movement fails at the worst time, and a better process when it does require review.

Raiffeisen Business Online's public features are relevant here because they show the operational pieces around that review. SWIFT GPI tracking gives business users payment visibility. Electronic document workflow gives them a route for documents. Access-rights settings let a business control who can sign or see account actions. Currency transactions and business-card controls turn regulated actions into digital workflows rather than branch visits (https://raiffeisen.ua/en/aem/biznesu/onlain-servisy/raiffeisen-business-online.html). These features do not eliminate compliance holds. They reduce the cost of navigating them.

Corporate cash-management services also point to the relationship layer. Raiffeisen's "Cash manager" page describes services for corporate clients that support liquidity management, payment preparation and treasury processes, positioning the bank as part of a company's financial operating routine (https://raiffeisen.ua/en/korporativnim-kliyentam/rahunki-i-platezhi/specialni-poslugi-cash-manager). If a corporate client uses the bank only as a once-a-month payment outlet, switching is easier. If the bank is embedded in cash positioning, salary projects, acquiring, foreign-currency payments and credit, migration becomes a project.

The compliance burden also explains why a cheaper substitute may not be cheaper. A payment processor can simplify collection. A fast consumer app can make transfers feel effortless. A foreign bank can serve some international treasury needs. But none of those substitutes automatically replaces the Ukrainian regulated bank account, local clearing membership, tax-payment interface, NBU supervision, Deposit Guarantee Fund participation, branch and ATM fallback, hryvnia settlement and domestic business-account controls. The relevant comparison is not app against app. It is full account continuity against the cost of a broken or fragmented account stack.

Digital continuity has supplier and cyber costs

The public record also points to supplier dependence. RBI's annual report describes information and cyber security as a high-priority group topic and says the group takes technical and organizational measures against unauthorized access, hacking, malware, DDoS attacks, ATM fraud, data leaks, phishing, disclosure of sensitive information and other threats. It says head-office processes are ISO 27001 certified, that the scope covers core banking processes, mission-critical support processes, banking products, required IT infrastructure, locations and employees, and security processes for subsidiaries. It also says the Digital Operational Resilience Act shaped group work in 2025 through ICT incident handling, testing, provider monitoring, data restore tests, penetration tests, business-continuity tests and crisis exercises (https://www.rbinternational.com/content/dam/rbi/ho/investors/results-reports/annual-reports/rbi/2026-03-02%20RBI%20Annual%20Report%202025.pdf.coredownload.pdf).

Again, this is group evidence. It is useful because a Ukrainian foreign-bank subsidiary can benefit from group security capabilities, but it is not a standalone Ukrainian uptime audit. The public record says RBI improved technical measures that blocked DDoS attempts without business impact and that no customer services were affected by increased supplier and supply-chain incidents in 2025. That gives context for why digital account continuity is expensive: the bank is not only buying software features. It is buying security monitoring, incident response, supplier oversight, restore testing and staff training. A customer sees a mobile login screen. The bank sees a regulated service that must stay available while phishing, account takeover and wartime disruption remain active risks.

This is especially important for Ukraine because physical disruption and cyber disruption can converge. A power outage can push traffic from branch to mobile. A damaged local network can make cloud processing more important. A branch relocation can force customers to use remote signing. A phishing wave can create support demand just when staff are managing wartime operations. A bank that treats digital continuity as a cheap app feature risks underpricing the true cost of keeping accounts usable.

Raiffeisen's own service architecture is visible at the edge. MyRaif is the consumer app. Raiffeisen Business Online is the business channel. Open banking is the consented data and payment-initiation interface. SEP and instant transfers are the national account-rail context. Branches and ATMs are fallback and cash-access context. Corporate cash manager and salary projects are relationship tools. The point is not that every user uses every tool. The point is that the paid unit becomes more valuable when the tools reinforce each other. A customer with only a debit card is easier to move than a customer with accounts, payroll, acquiring, RBO access rights, foreign-currency documents, loans and supplier payment routines.

The bank's cost base has a labour component that cannot be automated away. RBO support, compliance review, account opening, credit decisions, problem payments, branch security, generator logistics, cyber training, treasury products and foreign-currency supervision all require staff. NBU financial data showing payroll costs near UAH 1.97 billion in the year-to-date table gives a rough public signal of that labour intensity, although it does not divide staff by product line (https://bank.gov.ua/files/stat/aggregation_2026-06-01_eng.xlsx). If the bank has pricing power, it is not because labour disappears. It is because customers may pay, directly or indirectly, to avoid the labour and delay of moving a complex banking relationship.

Market signals show pressure, not proof

Public reviews and app-store pages are useful only if they are treated with restraint. The Apple App Store page for MyRaif shows a high rating and large review base, while individual reviews include both praise for convenience and complaints about login, interface changes, support responses and specific payment or card frictions (https://apps.apple.com/ua/app/myraif-mobile-bank/id1582978231). The Raiffeisen Business Online app page also shows a high rating and a sizable review base, with comments that suggest business users care about reliability, document flow and speed (https://apps.apple.com/ua/app/raiffeisen-business-online/id1500897229). These pages cannot prove outage rates, churn or customer lifetime value. They do show the pressure surface: customers expect bank-grade reliability from an app and punish friction even when the underlying banking relationship is hard to move.

That market pressure is healthy. It means switching cost is not absolute. A bank can lose customers if an app becomes painful, if support is slow, if compliance communication is opaque, if cash access is weak, if competitors offer better credit terms, or if corporate treasurers decide the group relationship brings more reputational burden than benefit. Raiffeisen's public record gives reasons customers might stay. It does not give the retention curve that would prove how many stay despite dissatisfaction.

For retail users, the substitutes are obvious. PrivatBank and monobank set expectations for Ukrainian consumer banking that are hard for every incumbent to meet. If a user only needs a card, quick transfers and bill payments, the lowest-friction mobile experience can win. MyRaif's reported daily transaction volume helps, but it does not settle the question. The bank's defence is strongest when the user also values salary arrangements, deposits, credit history, branch and ATM reach, cash access, family habit or a preference for an international banking group. It is weaker when the user wants only a slick consumer interface.

For business users, the substitute set is more complex. A firm can move some merchant acceptance to a processor, hold another bank account for payroll, keep foreign-currency operations elsewhere, use a separate accounting integration, or delay payment until documentation clears. Each substitute solves one part of the problem and creates a coordination cost. Raiffeisen's business case is strongest when a customer wants one regulated account relationship to handle current accounts, RBO access controls, currency payments, payment visibility, document handling, loans, salary work and branch fallback. It is weaker when a customer has the staff and systems to multi-bank cheaply.

For corporate clients, parent-bank context can be an advantage and a liability at the same time. The NBU identifies Raiffeisen as a foreign-bank-group institution with direct ownership by RBI and EBRD (https://bank.gov.ua/ua/supervision/institutions/14305909). The advantage is institutional capacity, governance, access to EBRD facilities and the credibility of a large European banking group. The liability is that RBI's Russian subsidiary remains a recurring reputational and regulatory topic in the group's own report. Customers deciding on cross-border settlement may see the same group fact in two ways: a sign of international scale or a reason for extra due diligence.

The public record suggests Raiffeisen's Ukrainian unit has enough local operating evidence to stand on its own. The NBU numbers show a large Ukrainian bank with substantial customer liabilities, equity and profit. The RBI report gives Ukraine-specific operating claims. Raiffeisen's own pages show service functionality. App pages show adoption signals. EBRD-linked announcements show financing relationships. But the parent context cannot be ignored. In a sanctions-sensitive environment, the bank's ability to make compliance friction predictable is part of what customers buy.

Why the unit is costly to deliver

The regulated transaction and account-continuity surface has at least six cost layers.

First, liquidity and capital. The bank has to hold enough liquidity and capital to keep customers comfortable, satisfy supervisors and support lending. The NBU's figures for assets, liabilities, customer balances and equity show the size of that balance sheet. The customer may experience this as confidence that balances, payments and credit lines are not sitting on a thin operator.

Second, payment-rail participation. SEP access is not a marketing feature. It requires technical connectivity, settlement discipline, NBU rule compliance, business continuity and operational monitoring. As Ukraine's instant-transfer and open-banking requirements deepen, the bank must keep its account infrastructure current.

Third, compliance. Financial monitoring, sanctions screening, currency-control documentation, fraud controls and correspondent-bank expectations add friction and cost. The bank has to protect itself and customers from bad payments while also giving legitimate customers a route through review.

Fourth, digital operations. Apps, web banking, electronic signatures, data interfaces, access rights, SWIFT GPI visibility, authentication and customer support must stay useful. Customer adoption makes the system valuable, but it also raises expectations.

Fifth, physical fallback. Branches, structural units, ATMs, generators, staff safety, underground relocations and cash logistics cost money. In Ukraine this is not legacy decoration. It is part of continuity.

Sixth, relationship breadth. Salary projects, merchant acquiring, loans, cash management, foreign-currency services, deposits, credit cards and custody can all create stickiness. The more functions tied to the bank, the more expensive it is for the customer to recreate the relationship elsewhere.

The important economic point is that these layers are not always paid for separately. A bank account can look free or cheap while the customer pays through balances, fees, spread, product bundling and tolerance of administrative friction. The bank's public profit and commission figures show that the relationship can produce income. They do not show whether continuity investment earns attractive incremental returns.

Data locality is really account locality

The assigned topic includes data sovereignty and locality, but for Raiffeisen the useful public question is not whether every byte sits in a named Ukrainian facility. The public record does not disclose that level of architecture. RBI's annual report says all customer transactions in Ukraine are processed in the cloud so that they can be executed even if local infrastructure is destroyed. That is an operational claim about survivability, not a data-residency map. The more defensible point is that Raiffeisen's account relationship is local where it has to be local: it is a Ukrainian licensed bank, supervised by the NBU, participating in Ukrainian payment rails, handling hryvnia settlement, subject to Ukrainian banking and financial-monitoring requirements, and connected to local branch, ATM and support infrastructure.

That distinction matters to customers. A Ukrainian company can use international software, foreign payment processors or offshore structures for some flows, but it still needs a lawful domestic settlement account for payroll, tax, supplier payments, local collections, loans and hryvnia liquidity. The data around those flows has to be accurate enough for statements, audits, currency supervision, tax records and management reporting. Portability is useful only if the receiving bank can preserve those control points. If account history, signatory rights, access permissions, payment templates, salary files, counterparty references and foreign-currency documents are hard to migrate cleanly, the data itself becomes part of the switching cost.

Open banking can reduce that cost at the margin. The NBU's model is designed around consented access to account information and payment initiation through specialized interfaces. That should make it easier for authorized third-party providers to build dashboards, treasury tools and payment-initiation services across accounts. Yet open banking does not remove the need for the underlying regulated account. It can let a customer see or initiate from another interface, but it does not itself supply the bank license, credit line, payment-system settlement, compliance review, branch fallback or relationship manager. In that sense, data portability increases pressure on Raiffeisen to be technically clean, while account locality keeps the bank relevant.

Raiffeisen's own open-banking page is careful about consent. It says the bank transmits data only when the customer has given valid consent, within the scope of that consent, and that consent can be withdrawn. This is not glamorous, but it is a core part of account continuity. A corporate treasurer wants data to move only when authorized. A retail customer wants a third-party service to see only the information allowed. A bank that mishandles consent can lose confidence quickly. A bank that makes consent too painful can lose the front-end relationship to easier tools. The value is in the balance: enough openness to reduce user friction, enough control to satisfy banking customers and supervisors.

The cloud-processing statement from RBI is more economically interesting than a normal technology disclosure because it appears in the context of destroyed local infrastructure. In peacetime, cloud migration can be a cost-efficiency or product-speed story. In Ukraine, the public framing is continuity. If a branch, local office or municipal infrastructure point is damaged, the bank still needs transactions to execute. That makes cloud processing part of the account product. It also creates dependency on group technology, third-party providers, telecommunications, cyber controls and recovery discipline. The article cannot audit those dependencies from the outside. It can observe that the bank has explicitly tied cloud processing to wartime transaction continuity.

The branch network remains relevant because data locality is not enough. A business might complete documents online, but it may still need a branch for certain cash, identification, account-management or emergency interactions. A retail customer may prefer mobile banking until a card is blocked, an ATM matters, or a family member needs help. RBI's generator and underground-branch disclosures show why the physical layer is not simply legacy cost. The bank is trying to preserve local service points while shifting transaction processing and documents into resilient digital channels. That hybrid model is expensive, but it is also what makes the switching-cost problem credible.

Where switching cost appears

The strongest switching-cost case is not the individual who holds a small card balance and pays bills once a month. That user can move faster than a complex business customer. The strongest case is the customer with multiple dependencies. A payroll client has employees expecting salary on time. A merchant client has acquiring, refunds and reconciliation. An agricultural borrower has seasonal credit and payment timing. An exporter has foreign-currency documentation and settlement questions. A public-sector supplier may have contracts, tax evidence and audit trails. A family with deposits, credit and daily payments has habit and relationship history. In each case, the cost of moving is the cost of recreating a working pattern.

A treasury decision illustrates the point. Suppose a company uses Raiffeisen for current accounts, RBO, foreign-currency payments, salary files and a credit line. A rival bank offers lower payment fees. The visible saving may be easy to calculate. The hidden migration cost is slower: new signatory files, new account details for customers and suppliers, new access rights, new templates, new staff training, new support contacts, new integration work, possible compliance re-review, loan documentation and the risk that a payment breaks during the handover. If the firm has little slack, even a few failed or delayed transactions can wipe out the fee saving. That is the switching-cost mechanism.

Another case is a retail user during a local disruption. The user may have a favourite app elsewhere, but if Raiffeisen provides a functioning card, ATM network, branch help, deposit relationship and mobile transfer channel, the bank can stay in the wallet. It does not have to be the only bank. It has to remain one of the accounts the customer is unwilling to close. Multi-banking weakens exclusive loyalty but can still preserve revenue if Raiffeisen remains the trusted fallback for certain balances or transactions.

A third case is a compliance-sensitive cross-border payment. The customer may not love extra questions, but a bank that gives a clear document route and payment-status evidence can be preferable to a cheaper provider that leaves the customer uncertain. The cost of compliance is not only the fee. It is the staff time spent assembling documents, waiting for review, explaining delays to counterparties and proving the payment trail later. If Raiffeisen Business Online's document workflow and SWIFT GPI features reduce uncertainty, they are part of the paid unit even when not priced separately.

Switching cost can also decay. If customers become comfortable with multiple banks, if accounting tools make account migration easier, if open banking enables reliable third-party payment initiation, if competitors offer better corporate support, or if Raiffeisen's app experience deteriorates, the bank's embedded position weakens. The public app reviews are a reminder of that risk. High ratings show broad use, but individual complaints show that customers compare the channel with a high standard. Switching cost is not permission to underperform. It is a temporary advantage that must be renewed through service.

This is why Raiffeisen's unit should not be reduced to "trust." Trust is an output of fewer failed payments, faster resolution, predictable compliance, useful fallback, clear statements, secure access and a belief that the bank will still operate when local conditions are poor. If any of those pieces fail, the word loses economic meaning. If they work, customers may keep accounts open even when another provider looks cheaper on one line of the price table.

What public evidence cannot prove

The public evidence does not reveal three decisive categories.

The first is economics. The public record does not show customer acquisition cost, monthly active customers by product, churn, product-level margin, account package profitability, treasury service margin, fee waiver policy, foreign-exchange spread by customer type, card interchange economics, corporate cash-management pricing or how much of the net interest income is tied to sticky operational balances rather than rate-sensitive deposits. Without those figures, the article cannot say the continuity surface is definitively high margin. It can say the public record is consistent with a bank that can monetize continuity through a broad relationship.

The second is reliability. RBI's public statements about ATM availability, generators, cloud transaction processing and no failed critical processes are important, but they are not a granular incident history. Public records do not show MyRaif monthly uptime, RBO outage duration, failed payment rates, branch closure days, compliance hold turnaround time, average support response time, recovery time after power events, user lockout rates, or whether service levels differ sharply by customer segment. These are the facts that would turn the continuity claim from persuasive to measurable.

The third is retention. Public app ratings and customer counts show scale, but not why customers remain. The missing evidence is account switching data, salary-project renewal, corporate churn, multi-bank wallet share, card activity by cohort, complaint resolution time, and whether customers who complain about digital friction keep using Raiffeisen because their payments, payroll or loans are too costly to move. This is the core of the switching-cost thesis. It remains partly unproven until retention data is visible.

These gaps do not weaken the subject. They define it. The strongest public conclusion is not that Raiffeisen's Ukrainian account is immune to competition. It is that the bank operates a large, regulated, wartime-tested account surface where continuity can rationally matter more than the headline account price. The thesis would be reversed if private data showed high churn among active business customers, weak app reliability, slow compliance processing, falling operational deposits, limited use of RBO by serious corporate clients, or customer migration to rivals without meaningful friction.

Evidence register

Judgement

Raiffeisen Bank JSC's public record supports a specific judgement: the bank's Ukrainian account is not best understood as a commodity container for money. It is a regulated continuity surface with settlement access, compliance work, digital channels, branch and ATM fallback, wartime logistics and institutional finance links. Customers can and do compare it with other banks and fintech interfaces. But if a customer has embedded Raiffeisen in payroll, foreign-currency documentation, business payments, credit, acquiring, cash management or everyday app habits, the cost of a broken payment or delayed migration can be larger than the visible account fee.

The bank's challenge is to keep that advantage practical. A continuity product is renewed every time a payment posts, a document is accepted, an ATM works during a power problem, a support team solves an access issue, or a compliance question is answered before it becomes a business delay. It is weakened every time the customer feels that the bank adds friction without reducing risk. That is why the most important future evidence will be operational, not promotional.

That does not mean Raiffeisen has a protected moat. Open banking reduces some information lock-in. Instant payments raise the baseline for every bank. Ukrainian digital competitors keep user-experience pressure high. Parent-level Russia exposure creates reputational and compliance scrutiny that the Ukrainian unit has to manage carefully. The bank's own public record therefore supports a disciplined, not triumphalist, thesis: continuity can create switching cost, but only if the bank keeps payment rails, digital access, compliance processing and fallback channels working better than the alternatives.

The conclusion strength is medium to strong on scale, status and operating surface because NBU and RBI records are direct. It is medium on digital adoption because Raiffeisen and app-store pages show visible usage signals but not independently audited uptime. It is lower on product margin because the bank does not disclose the economics of the regulated transaction and account-continuity unit. The private facts that would change the view are clear: poor uptime, slow compliance decisions, low RBO usage, declining operational deposits, high business-customer churn, weak branch fallback during power events, or evidence that customers can migrate full account workflows to competitors without material delay. Until such evidence appears, Raiffeisen Bank JSC matters because it turns payment continuity into a cost customers may prefer not to test.