# Revolut Published articles for Revolut. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Revolut phishing texts appear days after data breach DevFeed: [Revolut phishing texts appear days after data breach]() Original publisher: [Read original article]() Author: Pieter Arntz Published: 2026-09-17T14:07:15Z Content type: news Language: en Sources: [Malwarebytes]() Topics: [Social engineering](), [passwords](), [VirusTotal]() Tags: [account](), [breach](), [password](), [phishing](), [revolut](), [scam](), [scams](), [social-engineering](), [threat-intel]() ### AI overview Revolut customers received phishing texts days after the bank disclosed customer data to a government impostor. The report says the campaign's connection to the breach is not yet known and describes a fake identity check designed to obtain passwords. ### Source excerpt Revolut customers received phishing texts only days after the digital bank acknowledged disclosing customer data to a government impostor. ## Announcing Upvest as Confluent's 2026 EMEA Data Streaming Startup of the Year DevFeed: [Announcing Upvest as Confluent's 2026 EMEA Data Streaming Startup of the Year]() Original publisher: [Read original article]() Author: Tim Graczewski Published: 2026-07-16T00:07:01Z Content type: article Language: en Sources: [Confluent: Data in motion]() Topics: [Streaming](), [real-time](), [Resilience](), [event driven](), [Scalability](), [Cloud](), [data-governance](), [Microservices](), [Architecture & Design](), [Disaster Recovery]() Tags: [2026](), [cloud](), [cloud-native](), [compliance](), [confluent](), [confluent-cloud](), [data](), [data-governance](), [disaster-recovery](), [emea](), [event-driven](), [fintech](), [infrastructure](), [microservices](), [real-time](), [resilience](), [revolut](), [scalability](), [startup](), [streaming]() ### AI overview Confluent recognizes Berlin-based Upvest as its inaugural EMEA Data Streaming Startup of the Year. The article describes Upvest's real-time, event-driven fintech infrastructure, which supports embedded investments, client onboarding, data governance, disaster recovery, scalability, and regulatory resilience for major financial institutions. ### Source excerpt Confluent for Startups provides an easy on-ramp to Confluent Cloud for early stage startups with great data streaming use cases. ## Building the Web that Moves Money: inside Web engineering at Revolut DevFeed: [Building the Web that Moves Money: inside Web engineering at Revolut]() Original publisher: [Read original article]() Author: Revolut Published: 2025-10-16T09:45:59Z Content type: article Language: en Sources: [Revolut Engineering]() Topics: [Web Development](), [modern web development](), [web applications](), [Low-Code / Internal Tools](), [Agile]() Tags: [agile](), [applications](), [building](), [engineering](), [fintech](), [internal-tools](), [modern-web-development](), [revolut](), [web](), [web-applications](), [web-development](), [web-engineering]() ### AI overview Revolut describes its web engineering approach across customer-facing products and roughly a hundred internal web applications. The article discusses secure financial experiences, modern development practices, small empowered teams, and agile principles inspired by Extreme Programming. ### Source excerpt Building the Web that moves money: inside Web engineering at RevolutIntroduction In today's digital-first economy, the web is the critical touchpoint between people and their money. At Revolut, we embrace this reality in our approach to web engineering: focusing on not just building interfaces, but on creating seamless, secure, and future-proof financial experiences. Our mission at Revolut is to redefine the global standard for digital finance. Every line of code, design decision, and feature we release serves this goal: to make finance more accessible and beautifully engineered. These principles shape our culture, set a high standard for excellence, and require constant attention to detail. They also drive us to rethink modern web development tools and practices. This article focuses on the principles that help us deliver secure, beautiful financial products worldwide, and explains how engineers are building their careers along the way. The scope of Revolut web products Two independent but complementary pillars represent the current stage of the Revolut web ecosystem. Customer-facing applications These are the digital gateways through which our customers and partners experience Revolut directly: Main website and brand hub Revolut Business platform Revolut crypto exchange platform Human Resources Management Systems (HRMS) by Revolut Each of these touchpoints is an individual part of a unified ecosystem offering a consistent product experience that is closely aligned with our mobile platform. Internal web products Alongside our external platforms, Revolut operates around a hundred internal web applications. These provide our employees, operations, and partners with tools for: Back-office management Compliance and risk monitoring Customer support services Data and reporting systems Operational efficiency at scale These internal tools are the driving force behind Revolut, ensuring customer-facing products remain fast, secure, and globally scalable Core principles of we ## Reinventing Risk at Revolut DevFeed: [Reinventing Risk at Revolut]() Original publisher: [Read original article]() Author: Konstantin Vasilev Published: 2024-12-10T07:46:23Z Content type: opinion Language: en Sources: [Revolut Engineering]() Topics: [Finance](), [Artificial Intelligence](), [Software]() Tags: [ai](), [banking](), [fake-accounts](), [finance](), [financial](), [fraud](), [knowledge-graph](), [operations](), [outage](), [revolut](), [risk-management](), [services]() ### AI overview Revolut describes how its Risk function approaches financial and operational risk in a financial-services business. The article explains that risks can overlap, such as fraud involving fake accounts leading to unpaid loans, and discusses the limitations of segregating risks into separate departments. ### Source excerpt Using probability, reasoning and AI Revolut is known for its innovation in delivering "super-app" financial services to its customers. The success is evident not only through the rocketing user growth, but also via the ripple effects caused across the banking industry -- traditional finance has to reinvent and evolve, or remain part of history, just like the internet search replaced the paper phonebook. Behind this success stands a complex and impressive machinery, which is still piloted by the same founders, who also engineered the very first components and set the Revolut rocketship in motion. This machine is mostly known for its software excellence, however, with any financial services comes the responsibility of navigating a complex net of regulations and risks. True to the company values, the Risk function at Revolut also innovates, leveraging the decades of banking experience of its leadership and adding the challenger way of thinking with the latest technology. What is Risk? One can find many definitions of risk, ranging from explanations suitable for children, "The possibility of something bad happening", to advanced statistical definitions used in finance: Uncertainty of the return on investment, characterised by standard deviation, asymmetry and tails of the return distribution and the generic ISO 31000 definition: "The effect of uncertainty on objectives" In addition, both graduate textbooks and banking regulations define two general types of risk: Financial: related to financial positions, such as: user deposits, lending, and investments in market instruments. Operational: related to failure of operations, such as: system outage, fraud and natural disasters. Some of you might already sense the inevitable challenges in distinguishing the above definitions and risks. Events seldom happen in isolation and independently: a natural disaster can lead to system outages and market crashes, similarly fraudsters might use fake accounts to withdraw loans which would ## The fundamentals of iOS at Revolut DevFeed: [The fundamentals of iOS at Revolut]() Original publisher: [Read original article]() Author: Illia Kucheriavyi Published: 2024-05-14T11:41:25Z Content type: tutorial Language: en Sources: [Revolut Engineering]() Topics: [iOS](), [iOS development](), [feature flags](), [Mobile](), [SDKs](), [CI/CD](), [experiments](), [Development](), [Agile](), [Testing](), [releases]() Tags: [agile](), [continuous-delivery](), [continuous-integration](), [development](), [development-process](), [experiments](), [feature-flags](), [fundamentals](), [ios](), [ios-development](), [releases](), [revolut](), [sdks](), [software-engineering](), [testing]() ### AI overview This article describes Revolut's iOS development practices, covering its applications and SDKs, weekly App Store updates, continuous integration and delivery, feature flags, gradual rollouts, rollback procedures, and experimentation with statistical measurement. ### Source excerpt Let's take a look behind the scenes of the iOS development at Revolut, where we strive to provide exceptional financial services and seamless customer experiences for the customers who rely on our iOS apps to manage their financial lives. We believe that it's possible to deliver high-quality software, fast. To achieve this we follow a set of important principles and apply a number of modern agile practices, mainly inspired by XP (eXtreme Programming). Deliver fast Currently, on the iOS platform, we have both applications and SDKs. Here's a list of what's live: Revolut, Revolut <18, Revolut Business, Revolut POS and Revolut Pay SDK. All iOS applications are updated in the App Store on a weekly basis. We operate on the principles of continuous integration and continuous delivery to swiftly deliver new functionality to customers -- as soon as a feature or part of it is ready. We've built our own in-house framework for feature-based releases. According to our process, the Product Owner specifies a feature to be enabled starting from a selected version of the application. Then both the application version and its features are rolled out gradually, starting with a small percentage of our customer base. These two approaches -- feature flagging and gradual version and feature rollout -- enable delivering value to customers with the minimum amount of risk. If anything goes wrong, the flag will be turned off or the older version will be re-submitted as rollback, to remove the problematic change. Moreover, feature flags allow team members to easily switch between different user experiences, compare them, or turn them on and off for testing. We've also developed an in-house experimentation platform that allows teams to experiment with new features and measure their impact using predefined metrics in a statistically significant way. This platform guarantees that experiments are properly set up, and that results are produced using a robust statistical framework. All ideas are teste ## iOS Screen Navigation Engine at Revolut DevFeed: [iOS Screen Navigation Engine at Revolut]() Original publisher: [Read original article]() Author: Vincent Berihuete Published: 2022-08-17T11:35:30Z Content type: tutorial Language: en Sources: [Revolut Engineering]() Topics: [iOS](), [navigation](), [Code](), [Dependency injection](), [implementation]() Tags: [code](), [dependency-injection](), [engineering](), [fintech](), [ios](), [ios-app-development](), [ios-engineering](), [navigation](), [revolut]() ### AI overview This article describes Revolut's custom Flow Engine for iOS screen navigation. It compares storyboard- and view-controller-driven navigation with an abstraction that uses a state machine to manage flows, screens, dependencies, and actions. ### Source excerpt Ever heard about the Coordinator pattern? Good for you, this article isn't about it. I'm here to open your eyes to Custom Navigation Engines just like the one we created on our Revolut Flow Engine. First let's talk about some traditional approaches for navigation before we get into our Flow engine: Storyboard actions navigation The most traditional way of doing navigation with storyboards is the one that's triggered by an action. As you know, you can ctrl + drag from your button to reach the desired screen on your storyboard. Segue driven navigation Another traditional type of storyboard navigation are segues, by doing ctrl+drag from one view controller to another we create a connection of a certain type (push, modally, etc) and assign it an ID. https://medium.com/media/8976cef3dea76b0581556b979848d899/href ViewController code driven navigation The most traditional way outside storyboards, is to instantiate and push or present your view controllers programmatically. https://medium.com/media/efae70b3641c09ff15c404f46504a84e/hrefFlow Engine Now let's bring out the big guns: the abstraction of navigation outside view controllers. Why do we need to abstract navigation? Well, imagine you have a FoodDeliveryApp and in there you have a screen called ProductDetails that shows the information for a given product (Hamburger 🍔, fish and chips 🍟, etc) -- but you want to call this screen and its dependencies from anywhere. Will it be enough to just instantiate the screen everywhere, with its dependencies and its actions? 🤯 of course not! 😅 Wait, what? Don't worry, here's some code: https://medium.com/media/b24d2268c0b542848c5d8a6f05379a6e/href When we want to call our ProductDetail screen and pass its business actions through dependency injection, we end up doing this: https://medium.com/media/cb3e85b0c7ae83eb4080db9b221086f3/href Code looks clean to you? Well, kind of 😅. What happens when you need to show that product page from other view controllers and handle its actions? .sho