> Markdown version of [/videos/100640-the-little-iframe-that-wanted-to-become-the-biggest-payment-platform](https://www.wearedevelopers.com/videos/100640-the-little-iframe-that-wanted-to-become-the-biggest-payment-platform). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # The Little iFrame That Wanted to Become the Biggest Payment Platform Scaling an isolated payment iframe to 1.6 million daily transactions exposed painful bottlenecks. See how shifting to trunk-based development, network-level mocking, and edge rendering slashed lead times to 15 minutes. - **Speakers:** Eduardo Aparicio Cardenes - **Event:** HalfStack Vienna 2026 - **Published:** November 19, 2026 - **Duration:** 28:08 - **URL:** https://www.wearedevelopers.com/videos/100640-the-little-iframe-that-wanted-to-become-the-biggest-payment-platform - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/f995e0de29571226042e9681072db0ed/thumbnails/thumbnail.jpg?time=664500ms ## Summary Extracting a payment platform into an independent iframe to handle 1.6 million daily transactions across four channels initially exposed severe delivery bottlenecks. Inheriting a legacy release process meant merging into a single shared staging environment, resulting in massive 100-commit release candidates, a huge blast radius, and deployments occurring only once or twice a month. To eliminate this bottleneck, the team implemented isolated feature branch deployments using GitHub Actions and AWS S3, utilizing browser cookies to route preview links for independent QA validation. This stability enabled a transition to trunk-based development with squash merges, Sentry version tracking, and automated feature flag rollouts via LaunchDarkly. Moving to continuous deployment reduced lead times from six days to under 15 minutes and scaled delivery to 40 releases a month. However, this 20x increase in deployment velocity overwhelmed manual QA, exposing an anti-pattern of "melted ice cream" testing—relying heavily on manual checks with only 61 automated tests. Because "confidence is the byproduct of understanding the customer's reality and the boundaries between the system," the team adopted an outside-in testing strategy inspired by the testing trophy. They mapped four critical boundaries: backend APIs, feature flags, PCI-compliant payment provider redirects, and parent-window `postMessage` contracts. By intercepting network requests using Mock Service Worker (MSW) and mocking the LaunchDarkly SDK at the network layer, they validated end-to-end customer journeys without the flakiness of full E2E environments. Scaling to over 1,700 automated tests—split evenly between low-level logic and user journeys like 3DS and MFA—drove PR check coverage to 100% and eliminated a 15.8% weekly hotfix rate. With velocity and testing solved, two new hurdles emerged: cross-repository coordination and international performance. Updating `postMessage` contracts across separate repositories for the cashier, shared types, and platform SDKs wasted 300 hours over 20 months; consolidating into an Nx monorepo saved 14 hours per engineer monthly. Finally, expanding into Brazil—which accounts for 65% of €300 million in deposits—revealed a 16-second p90 load time due to low-end devices and high network latency. Applying a "critical path principle," the team removed blocking client-side feature flag checks in favor of backend fallbacks, prefetched user eligibility data in the parent application immediately after login ("we didn't make the API faster, we changed when we paid the cost"), and wrapped the single-page application in static site generation (SSG) resolved at the edge. These optimizations dropped p90 load times under three seconds, proving that "the right solution is to start understanding the right problem." **Keywords:** iframe payment platform architecture, feature branch deployments, trunk-based development, continuous deployment pipeline, github actions workflow automation, launchdarkly feature flags, outside-in testing strategy, mock service worker integration testing, nx monorepo migration, cross-window postmessage contract, critical path performance optimization, edge static site generation, network latency optimization, automated qa validation, pci compliance payment redirects, testing trophy methodology ## Chapters 1. **Extracting the payment platform into an independent iframe** (00:00) — Extracting the payment experience into an iframe improved modularity, but inheriting a legacy shared staging workflow created severe release bottlenecks and large blast radiuses. 1. **Accelerating releases with feature branch deployments and continuous deployment** (03:57) — Implementing isolated S3 preview builds via GitHub Actions, adopting trunk-based development, and automating LaunchDarkly rollouts reduced deployment lead times from six days to fifteen minutes. 1. **Overcoming manual QA bottlenecks with outside-in integration testing** (09:55) — Faster delivery overwhelmed manual QA, prompting an outside-in integration testing strategy using Mock Service Worker to simulate system boundaries and eliminate post-release rollbacks. 1. **Consolidating fragmented SDK and type repositories into an Nx monorepo** (17:46) — Maintaining separate repositories for the cashier app, mobile and web SDKs, and shared types caused massive coordination overhead that was resolved by migrating into an Nx monorepo. 1. **Optimizing critical path performance for high-latency networks in Brazil** (20:40) — High network latency and low-end devices in Brazil caused sixteen-second load times, which were reduced to under three seconds by removing runtime feature flag checks, prefetching data after login, and pre-rendering static assets. ## Related Moments - [Building a developer-centric infrastructure for financial services](https://www.wearedevelopers.com/videos/608-throwing-off-the-burdens-of-scale-in-engineering) (from "Throwing off the burdens of scale in engineering") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/ef7e59aa66aaeb8b0dbbb292ca0f0f40/thumbnails/thumbnail.jpg?time=1842105ms - [Bridging early consumer fintech with traditional banking rails](https://www.wearedevelopers.com/videos/100371-acquired-live-interview-sri-shivananda-cio-jpmorganchase-with-ben-david-from-acquired) (from "Acquired Live Interview: Sri Shivananda (CIO, JPMorganChase) with Ben & David from Acquired") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/6670b2f6ba62979bea433748e9fa4809/thumbnails/thumbnail.jpg?time=163689ms - [Evolving payment architecture from legacy to cloud stacks](https://www.wearedevelopers.com/videos/90-apis-and-architecture-for-scaling-omnichannel-payments) (from "APIs and Architecture for scaling omnichannel payments") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/a57590b6ceec0af774b8daa9ef031da9/thumbnails/thumbnail.jpg?time=410415ms - [Navigating legacy systems and unconventional software testing practices](https://www.wearedevelopers.com/videos/557-iot-the-road-to-sustainability) (from "IoT: The road to sustainability") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/b54b0250ab9b8a49edfa887dd538f0c3/thumbnails/thumbnail.jpg?time=198600ms - [Accelerating development through integrated full-stack native platform primitives](https://www.wearedevelopers.com/videos/100032-under-the-hood-of-building-on-lovable) (from "Under the Hood of Building on Lovable") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/938ad01fcf12aa00515a43075be1a319/thumbnails/thumbnail.jpg?time=66750ms - [Overcoming challenges of scaling legacy monolithic frontend applications](https://www.wearedevelopers.com/videos/236-microfrontends-at-scale) (from "Microfrontends at Scale") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/f514752c459759def5ee668f157efd3f/thumbnails/thumbnail.jpg?time=313285ms ## Related Articles - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 103 - Superb Owl Trafficking](https://www.wearedevelopers.com/magazine/388-dev-digest-103-superb-owl-trafficking) - [Dev Digest 104 - Fight for your right to 3rd party](https://www.wearedevelopers.com/magazine/390-dev-digest-104-fight-for-your-right-to-3rd-party) ## Related Jobs - [Staff Fullstack Engineer, Retail](https://www.wearedevelopers.com/jobs/ext/4117773-staff-fullstack-engineer-retail) at **Redcare Pharmacy** - [Staff Fullstack Engineer, Retail](https://www.wearedevelopers.com/jobs/ext/3902063-staff-fullstack-engineer-retail) at **Redcare Pharmacy** - [Software Development Engineer 3](https://www.wearedevelopers.com/jobs/48595-software-development-engineer-3) at **WEX** - [Software Development Engineer 1](https://www.wearedevelopers.com/jobs/48594-software-development-engineer-1) at **WEX** - [Staff Fullstack Engineer, Retail (m/f/d)](https://www.wearedevelopers.com/jobs/48606-staff-fullstack-engineer-retail-m-f-d) at **Redcare Pharmacy** - [SDE3](https://www.wearedevelopers.com/jobs/48596-sde3) at **WEX**