# Fintech Published articles for Fintech. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Ninth Wave built AI-powered open finance onboarding on Amazon Bedrock DevFeed: [How Ninth Wave built AI-powered open finance onboarding on Amazon Bedrock]() Original publisher: [Read original article]() Author: Shawn Kelly Published: 2026-09-14T15:58:57Z Content type: article Language: en Sources: [Artificial Intelligence]() Topics: [Amazon Bedrock AgentCore](), [Artificial Intelligence](), [API](), [Architecture & Design](), [Security](), [Finance](), [Amazon Web Services](), [data]() Tags: [advanced-300](), [ai](), [amazon-bedrock](), [amazon-bedrock-agentcore](), [apis](), [customer-solutions](), [fintech](), [onboarding](), [pci-dss](), [security](), [soc-2]() ### AI overview The article describes how Ninth Wave built Compass, a multi-agent AI onboarding assistant powered by Amazon Bedrock AgentCore. Compass helps financial institutions validate bank APIs, map fields to Financial Data Exchange standards, and score production readiness while supporting secure, compliant open finance connectivity. ### Source excerpt Learn how Ninth Wave built Compass, a multi-agent AI onboarding assistant on Amazon Bedrock AgentCore that validates bank APIs against Financial Data Exchange (FDX) standards, scores compliance, and compresses open finance onboarding from weeks to minutes while meeting SOC 2 and PCI DSS requirements. ## Presentation: How To Run on Three Clouds at Once, and When Not To DevFeed: [Presentation: How To Run on Three Clouds at Once, and When Not To]() Original publisher: [Read original article]() Author: Ross McFarlane, Kevin Holditch Published: 2026-09-11T11:00:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [networking](), [Databases](), [Kubernetes]() Tags: [amazon](), [architecture](), [architecture-design](), [availability](), [aws](), [cloud](), [cloud-architecture](), [cloud-computing](), [cloud-networking](), [cockroach-labs](), [cockroachdb](), [containers](), [databases](), [devops](), [disaster-recovery](), [engineering](), [europe](), [financial-applications](), [fintech](), [form3-multicloud-architecture](), [infoq](), [kubernetes](), [microservices](), [networking](), [presentation](), [qcon-london-2026](), [qcon-software-development-conference](), [resilience](), [transcripts](), [us]() ### AI overview A presentation on Form3's move from one cloud to a triple-active multi-cloud architecture, covering cross-cloud networking, distributed databases, Kubernetes operators, and regional disaster-recovery expectations. ### Source excerpt Ross McFarlane and Kevin Holditch discuss Form3's evolution from a single-cloud setup to a triple active multi-cloud architecture. They share key engineering strategies for cross-cloud networking, distributed databases with CockroachDB and NATS, custom Kubernetes operators, and navigating distinct regional disaster recovery expectations across the UK, Europe, and US financial markets. By Ross McFarlane, Kevin Holditch ## A Developer's Guide to API Access Policies in Auth0 DevFeed: [A Developer's Guide to API Access Policies in Auth0]() Original publisher: [Read original article]() Author: Madhuri Ravindra Mohan Published: 2026-09-11T00:00:00Z Content type: tutorial Language: en Sources: [Auth0 Blog]() Topics: [Auth0](), [API](), [Authorization](), [Security](), [Back end](), [Web app]() Tags: [api](), [auth0](), [authorization](), [backend](), [fintech](), [security](), [web-app]() ### AI overview A developer guide to Auth0 API Access Policies for Applications. It explains how to configure per-API policies through the Auth0 Dashboard or Management API, and how to distinguish machine-to-machine client access from user-delegated access. ### Source excerpt Explore how to properly configure Auth0 API Access Policies and client grants to draw a hard line between strict M2M security and user-delegated access. ## Report: Stablecoins Are Reshaping Remittances DevFeed: [Report: Stablecoins Are Reshaping Remittances]() Original publisher: [Read original article]() Author: Solana Foundation Published: 2026-09-08T13:14:00Z Content type: news Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Finance]() Tags: [blockchain](), [blockchain-technology](), [cross-border-payments](), [crypto-news](), [cryptocurrency](), [defi](), [fintech](), [implementation](), [money-transfer-operators](), [nfts](), [payments](), [podcasts](), [regulatory](), [remittances](), [report](), [solana](), [solana-ecosystem](), [stablecoins](), [web3]() ### AI overview Solana Foundation published a report on how stablecoins could change remittances. It examines implementation paths, business models, regional corridors, existing projects, and regulatory risks for money transfer operators and fintech startups. ### Source excerpt New report on stablecoin remittances covering four implementation paths for money transfer operators, corridor overviews, and case studies. ## Finding three-way API drift with the AI Engineer DevFeed: [Finding three-way API drift with the AI Engineer]() Original publisher: [Read original article]() Author: Talia Kohan Published: 2026-09-01T16:00:00Z Content type: article Language: en Sources: [Postman Blog]() Topics: [API](), [Postman](), [OpenAPI Specification](), [Claude](), [Tooling](), [client](), [servers]() Tags: [ai-engineer](), [api](), [api-drift](), [apis](), [ci](), [fintech](), [general](), [openapi](), [postman-ai-engineer](), [production](), [qa]() ### AI overview The article explains how to detect three-way API drift by comparing an OpenAPI specification, the requests in Postman Collections, and the responses returned by a running server. It argues that pairwise checks can miss cases where all three sources disagree, and describes using Postman AI Engineer and the Context Graph to identify these inconsistencies. ### Source excerpt Find three-way API drift with Postman AI Engineer and the Context Graph. Compares your OpenAPI spec, collection requests, and live server responses. The post Finding three-way API drift with the AI Engineer appeared first on Postman Blog. ## Why Ramp built its own in-house coding agent, Inspect DevFeed: [Why Ramp built its own in-house coding agent, Inspect]() Original publisher: [Read original article]() Author: Gergely Orosz Published: 2026-08-25T15:20:23Z Content type: article Language: en Sources: [The Pragmatic Engineer]() Topics: [AI-assisted coding](), [coding]() Tags: [ai](), [coding-agents](), [company](), [fintech]() ### AI overview An in-depth look at why fintech company Ramp built its own in-house coding agent, Inspect, instead of taking an easier route, and how it compares with coding agents from frontier AI labs. ### Source excerpt A fintech company rejected the easy route and homebrewed its own coding agent - and is now a step ahead of coding agents from frontier AI labs. An in-depth look ## 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. ## Plaid vs Stripe: Why They Solve Different Problems (Not Competitors) DevFeed: [Plaid vs Stripe: Why They Solve Different Problems (Not Competitors)]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-06-11T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [stripe](), [App](), [data]() Tags: [ach](), [bank-transfers](), [banking](), [card](), [comparisons](), [developer-tools](), [fintech](), [integration](), [payments](), [stripe]() ### AI overview This guide compares Plaid and Stripe, explaining that Plaid connects bank accounts and provides account data and verification, while Stripe primarily processes card payments and offers related financial products. It identifies ACH transfers as their main area of overlap and explains how the platforms can be used together. ### Source excerpt Plaid vs Stripe compared. Why they are not really competitors, where each one fits, and how they can be used together for ACH, banking, and card payments. ## Top Tap Payments Alternatives for GCC and MENA SaaS in 2026 DevFeed: [Top Tap Payments Alternatives for GCC and MENA SaaS in 2026]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-05-19T00:00:00Z Content type: comparison Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Shopify]() Tags: [2026](), [alternatives](), [compliance](), [cross-border](), [e-commerce](), [fintech](), [gcc](), [mena](), [merchant-of-record](), [payments](), [saas](), [vat]() ### AI overview A comparison of Tap Payments alternatives for SaaS businesses operating across the GCC and MENA in 2026. It discusses regional payment coverage, local payment methods, pricing, VAT and e-invoicing obligations, and when a Merchant of Record may be preferable for cross-border operations. ### Source excerpt Compare the best Tap Payments alternatives for SaaS founders across Kuwait, KSA, UAE, Bahrain, Oman and Qatar in 2026. Verified pricing, ZATCA e-invoicing context, and a clear take on Merchant of Record for cross-border GCC SaaS. ## Top Paymob Alternatives for MENA SaaS and Online Businesses in 2026 DevFeed: [Top Paymob Alternatives for MENA SaaS and Online Businesses in 2026]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-05-19T00:00:00Z Content type: comparison Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Shared Responsibility Model]() Tags: [2026](), [alternatives](), [compare](), [compliance](), [cross-border](), [fintech](), [mena](), [merchant-of-record](), [pakistan](), [payment](), [pricing](), [saas](), [vat]() ### AI overview A comparison guide for MENA SaaS and online businesses evaluating alternatives to Paymob in 2026. It discusses regional payment coverage, local-currency settlement, cross-border USD billing, VAT compliance, and the distinction between Payment Facilitators and Merchants of Record. ### Source excerpt Compare the best Paymob alternatives for SaaS founders across Egypt, KSA, UAE, Oman and Pakistan in 2026. Verified pricing, ZATCA and e-invoicing context, and a clear take on Merchant of Record for cross-border MENA SaaS. ## Top Flutterwave Alternatives for African SaaS and Online Businesses in 2026 DevFeed: [Top Flutterwave Alternatives for African SaaS and Online Businesses in 2026]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-05-17T00:00:00Z Content type: comparison Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Shared Responsibility Model]() Tags: [2026](), [africa](), [alternatives](), [compare](), [cross-border](), [fintech](), [merchant-of-record](), [payments](), [pricing](), [saas]() ### AI overview A comparison of Flutterwave alternatives for African SaaS and online businesses in 2026. It examines regional payment coverage, pricing, settlement, compliance, chargeback liability, and the Merchant of Record model for businesses serving international customers. ### Source excerpt Compare the best Flutterwave alternatives for African SaaS founders in 2026. Verified pricing across Nigeria, Kenya, South Africa, Ghana and beyond, plus a clear take on the Merchant of Record model for cross-border African businesses. ## Top Paystack Alternatives for African SaaS and Online Businesses in 2026 DevFeed: [Top Paystack Alternatives for African SaaS and Online Businesses in 2026]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-05-11T00:00:00Z Content type: comparison Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service]() Tags: [2026](), [account](), [africa](), [alternatives](), [compare](), [compliance](), [cross-border](), [e-commerce](), [fintech](), [global](), [merchant-of-record](), [payment](), [pricing](), [regulatory](), [saas]() ### AI overview A comparison guide to Paystack alternatives for African SaaS and online businesses in 2026. It discusses cross-border billing, tax and regulatory compliance, settlement delays, account holds, pricing, and when a Merchant of Record may be preferable to a local payment processor. ### Source excerpt Compare the best Paystack alternatives for African SaaS founders in 2026. Real pricing across Nigeria, Kenya, South Africa, Ghana and Egypt, plus a clear take on when an MoR beats a local processor. ## "A generational leap": How Trio unified payment analytics and cut storage by 88% with ClickHouse Cloud DevFeed: ["A generational leap": How Trio unified payment analytics and cut storage by 88% with ClickHouse Cloud]() Original publisher: [Read original article]() Author: ClickHouse Published: 2026-04-17T08:23:49Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Cloud](), [cloud-infrastructure](), [data](), [dashboards](), [Database]() Tags: [analytics](), [clickhouse](), [cloud](), [compliance](), [dashboards](), [data](), [database](), [fintech](), [legal](), [logs](), [operations](), [payment](), [performance](), [systems](), [transactions]() ### AI overview Trio, a Brazilian fintech, uses ClickHouse Cloud as a unified source of truth for payment analytics. The platform handles more than 243 million payments in the first half of 2025 and over 1 billion daily events, while supporting reconciliation, compliance reporting, and operational, customer, and financial dashboards. Trio reports an 88% reduction in storage and major speed improvements using sliding windows, refreshable materialized views, and ReplacingMergeTree to manage late, duplicate, and out-of-order events. ### Source excerpt Brazilian fintech Trio cut storage by 88% and achieved a "generational leap" in speed by building a unified payment analytics platform on ClickHouse Cloud, handling 243M+ payments and 1B+ daily events with a sliding window approach for late and duplicate ## Razorpay's Linked Payments Architecture for Combining Payment Methods DevFeed: [Razorpay's Linked Payments Architecture for Combining Payment Methods]() Original publisher: [Read original article]() Author: Vatsal Mehta Published: 2026-04-08T09:56:17Z Content type: article Language: en Sources: [Razorpay Engineering - Medium]() Topics: [Architecture & Design](), [Microservices](), [Transactions](), [Database]() Tags: [architectures](), [authorization](), [fintech](), [microservices](), [monolithic-architecture](), [payment](), [payment-gateway](), [payment-processing](), [payments](), [razorpay](), [recovery](), [technical](), [transactions]() ### AI overview Razorpay describes Linked Payments, an architecture that lets customers combine a gift card with card, UPI, or another payment method for one order. The article explains the resulting challenges around authorization sequencing, failure recovery, and split settlement across payment-method microservices. ### Source excerpt You have a $50 gift card. Your cart is $75. The checkout says "pick one payment method." This is a solvable problem. If you've ever tried to use a gift card for an online purchase, you know this frustration intimately. The gift card covers most of it, but not quite all. The checkout forces you to choose: use the gift card and abandon some items, or ignore the gift card and pay the full amount another way. Either choice feels wrong. This isn't a technical limitation of payment processing. It's an architectural one. Most payment systems treat each method as an isolated, complete transaction. You pay with a card OR UPI OR a gift card. The concept of composing multiple methods to fulfill a single order simply doesn't exist in traditional payment gateway architectures. At Razorpay, this limitation was costing merchants real money. Gift card redemption rates suffered because customers abandoned partial-value cards. Average order values stayed lower because customers couldn't combine store credit with additional payment. The business case for solving this was clear. That's why we built Linked Payments, a system that treats payment methods as composable building blocks. Customers can now use a gift card for $50, then cover the remaining $25 via card, UPI, or any other method. The system handles authorization sequencing, failure recovery, and settlement splitting automatically. The Complexity Hidden in "Just Combine Them" The challenge sounds simple until you consider what payment systems actually do. Traditional payment flows are beautifully simple. Customer initiates payment. System authorizes the full amount from one method. If authorization succeeds, capture the funds. Settle to the merchant. Either the payment worked or it didn't. One authorization, one capture, one settlement. Linked payments shatter this simplicity. Now you have multiple authorizations for a single order. Sequential dependencies where the second payment only happens if the first succeeds. Partial fail ## Building Resilient Fintech Infrastructure for Scale DevFeed: [Building Resilient Fintech Infrastructure for Scale]() Original publisher: [Read original article]() Author: David Weiss Published: 2026-04-02T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [Resilience](), [Data Infrastructure](), [Database](), [CockroachDB](), [legacy]() Tags: [cockroach-labs](), [cockroachdb](), [compliance](), [fintech](), [fraud-detection](), [infrastructure](), [legacy](), [outages](), [postgresql](), [resilience](), [uptime]() ### AI overview The article argues that fintech and quant firms need resilient data infrastructure to handle growth, real-time payments, instant settlement, AI-driven fraud detection, and cross-border compliance. It describes the limits of legacy database architectures and presents SumUp's migration from PostgreSQL to CockroachDB as an example of improved resilience and near-zero downtime. ### Source excerpt The fintech companies and quant firms that define the next decade aren't just building better products. They're succeeding with more resilient fintech infrastructure. ## Rill and ClickHouse: real-time operational BI for a metered world DevFeed: [Rill and ClickHouse: real-time operational BI for a metered world]() Original publisher: [Read original article]() Author: ClickHouse Published: 2026-04-01T17:42:05Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [real-time](), [DLT](), [dashboards](), [data](), [Amazon Web Services](), [Cloud](), [stripe]() Tags: [analytics](), [aws](), [clickhouse](), [cloud](), [data](), [datasets](), [ecommerce](), [events](), [fintech](), [google](), [observability](), [real-time](), [scale](), [snap](), [streaming](), [stripe](), [systems]() ### AI overview Rill uses ClickHouse to power real-time operational BI for more than 100 billion daily events. Its declarative ingestion, high-performance aggregation, and metrics-first BI workflow brings cloud costs, payments, and product usage together for analysis against live data. ### Source excerpt Rill uses ClickHouse to power real-time operational BI for 100B+ daily events, enabling instant exploration and conversational analytics directly against live datasets through a declarative, BI-as-code workflow. ## How to Sell Software from Nigeria: A Complete Guide DevFeed: [How to Sell Software from Nigeria: A Complete Guide]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-03-28T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software](), [Software as a service](), [Finance](), [stripe]() Tags: [developers](), [fintech](), [global](), [guide](), [how-to](), [merchant-of-record](), [payment-processing](), [payments](), [paypal](), [software](), [stripe]() ### AI overview A guide for Nigerian developers on selling software and digital products globally. It discusses international payment processing, local and global processor limitations, compliance, currency challenges, and how a Merchant of Record can help manage payments and taxes. ### Source excerpt Guide for Nigerian developers to sell software and digital products globally. Covers payment processing, MoR platforms, international compliance, and receiving payouts. ## Scaling Payments in the Age of Real-Time Fraud: Building a Resilient Foundation for Fintech DevFeed: [Scaling Payments in the Age of Real-Time Fraud: Building a Resilient Foundation for Fintech]() Original publisher: [Read original article]() Author: Becca Weng Published: 2026-02-25T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [systems](), [Architecture & Design](), [Resilience](), [Availability](), [consistency](), [Low Latency](), [data]() Tags: [fintech](), [high-availability](), [latency](), [outages](), [payments](), [pci-dss](), [real-time](), [security](), [sensitive-data]() ### AI overview This article explains why fintech payment systems require resilient architectures that preserve atomic data updates, maintain low latency during demand spikes, support global regulatory and data-residency requirements, and provide high availability and security. It also introduces real-time fraud detection as an added source of complexity. ### Source excerpt Fintech is one of the most competitive and highly regulated industries in the world. Whether you're a payment processor, digital-first bank, trading platform, or wallet provider, your infrastructure is directly tied to customer trust. In this environment, outages aren't just technical incidents; a single missed transaction, delayed authorization, or moment of downtime can erode customer confidence instantly. ## Why these three fintech companies scaled with distributed SQL DevFeed: [Why these three fintech companies scaled with distributed SQL]() Original publisher: [Read original article]() Author: Becca Weng Published: 2026-02-02T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Scalability](), [SQL](), [Microservices](), [migration](), [Architecture & Design](), [MySQL](), [PostgreSQL]() Tags: [architecture](), [backend](), [caching](), [cloud](), [clusters](), [cockroachdb](), [compatibility](), [compliance](), [databases](), [distributed](), [financial](), [fintech](), [growth](), [india](), [migration](), [multi-cloud](), [mysql](), [payments](), [scale](), [sql]() ### AI overview This article describes how fintech platforms face growing transaction volumes, tighter regulations, and demanding financial workloads. Leaders from Groww, Global Payments, and Yubi explain their experiences, while the detailed case study of Groww covers its move from MySQL to CockroachDB to support horizontal scalability, multi-region resiliency, transactional guarantees, compliance, and growth with minimal application changes. ### Source excerpt From retail investing and global card payments to large-scale lending, fintech platforms are being pushed to their limits. User expectations are rising, regulations are tightening, and transaction volumes are growing faster and more unpredictably than ever before. Across these domains, one theme is emerging clearly: traditional databases struggle to keep up with modern financial workloads at scale. ## Why FinTech Is Moving to Distributed SQL Databases DevFeed: [Why FinTech Is Moving to Distributed SQL Databases]() Original publisher: [Read original article]() Author: David Weiss Published: 2025-12-12T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [Databases](), [SQL](), [systems](), [Transactions](), [consistency](), [Resilience](), [Availability]() Tags: [acid](), [availability](), [compliance](), [consistency](), [databases](), [distributed](), [fintech](), [global](), [legacy](), [nosql](), [payments](), [resilience](), [sql](), [trading](), [transactions]() ### AI overview This article explains why FinTech organizations are considering distributed SQL databases as they scale financial workloads across regions and clouds. It emphasizes correctness, consistent ACID transactions, resilience, availability, regulatory compliance, and the limitations of legacy relational and patchwork NoSQL systems. ### Source excerpt FinTech teams are operating under more pressure than ever. As digital financial services become the default for consumers and enterprises alike, the margin for error has all but disappeared. Users expect every interaction to be instantaneous, accurate, and always available, with very little patience for anything less. ## 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 ## Wahed Accelerates React Native Mobile Testing with Maestro DevFeed: [Wahed Accelerates React Native Mobile Testing with Maestro]() Original publisher: [Read original article]() Author: Jake Krupski Published: 2025-05-28T10:24:00Z Content type: article Language: en Sources: [mobile.dev - Medium]() Topics: [Mobile Testing](), [Test automation](), [React Native](), [Testing](), [Open Source]() Tags: [appium](), [case-study](), [fintech](), [maestro](), [mobile-test-automation](), [mobile-testing](), [react-native]() ### AI overview This case study describes how Wahed adopted Maestro for automated testing of its React Native mobile app. Test writing time fell from 3-4 hours per test with Appium to 10-15 minutes, releases shifted from biweekly to weekly, and automated test coverage grew from 50 manual smoke tests to approximately 250 tests. ### Source excerpt The world of mobile app development is fast-paced, demanding rapid iterations and flawless user experiences. But what happens when your mobile app testing process cannot keep up... ## Learnings from a Klarna Engineer on feature development DevFeed: [Learnings from a Klarna Engineer on feature development]() Original publisher: [Read original article]() Author: Julien Avezou Published: 2025-04-14T09:05:53Z Content type: article Language: en Sources: [Klarna Engineering]() Topics: [Development](), [Usability](), [Security](), [Scalability](), [Slack](), [Testing](), [Architecture & Design]() Tags: [bug](), [collaboration](), [communication](), [development](), [documentation](), [engineering](), [fintech](), [klarna](), [learning-to-code](), [scalability](), [security](), [slack](), [software-development](), [software-engineer](), [technical](), [testing]() ### AI overview A Klarna engineer shares lessons from developing a feature that helps users recover access to Klarna Card and Klarna balance accounts. The article emphasizes early and ongoing documentation, open communication through dedicated Slack channels, and collaborative Bug Bashes to support feature development. ### Source excerpt In the world of FinTech, where regulations and innovation collide, my team at Klarna implemented new ways for users to recover access to their Klarna Card and Klarna balance accounts on their device. This posed a series of challenges with a whole range of aspects to consider from product, usability, security, scalability and regulatory. With the feature now released, I would like to share key learnings from working on this complex feature. Documentation is Key Starting to document early on in the project is crucial. We generated documents at all stages of our project in order to gather feedback at a technical, product and design level. This helped in aligning with teams, enabling smooth collaboration, and setting a solid foundation for feature development and delivery. These documents allow close and continuous collaboration between stakeholders from both product, technical and design perspectives from the early stages of feature discovery to the start of implementation. However documentation doesn't stop there, once the implementation is done, it is equally as important to capture in writing your feature from both product and technical aspects, supported by architectural diagrams and swimlanes, so that stakeholders within the company have a clear reference when interacting with the feature in the future. Always communicate Establishing open communication channels, such as dedicated Slack channels for internal stakeholders, and providing regular updates in order to foster collaboration. Promptly raising blockers and organizing group discussions with colleagues from various competences ensures transparency and helps in addressing challenges effectively. Having an open channel to discuss and update on progress also helped streamline our communication and avoid unnecessary meetings. Having an open channel also serves as an accountability mechanism and a great way to keep track of the conversations and topics over time. The dedicated channel also provides an easy way to ## Designing high-performance financial ledgers with Temporal DevFeed: [Designing high-performance financial ledgers with Temporal]() Original publisher: [Read original article]() Author: Tim Imkin Published: 2025-03-18T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Architecture & Design](), [Scalability](), [Transactions](), [Resilience](), [integrity]() Tags: [accounting](), [compliance](), [crashes](), [design](), [financial](), [fintech](), [high-performance](), [ledger](), [payment](), [performance](), [reconciliation](), [resilience](), [temporal-concepts]() ### AI overview The article discusses designing high-performance financial ledgers around scalable transaction handling, double-entry bookkeeping, flexible metadata, and resilient workflow coordination. It presents Temporal's durable execution as a way to address failures caused by network issues, service downtime, and process crashes. ### Source excerpt Learn how Temporal's durable execution solves core challenges -- scalability, reconciliation, and compliance -- to create reliable, future-proof ledger systems. [Next page]()