NAB Edge Credit Card
A live staff-pilot credit card on a micro-frontend platform in React Native — real accounts, real compliance, and a phased rollout that proved the architecture before whitelabel migration.
Product Snapshot
Partner / Brand: NAB (staff pilot)
Client: National Australia Bank
NAB's internal proof point for Project EDGE — a real credit card on a micro-frontend platform in React Native, shipped with Progressive Elaboration and a phased staff rollout.
Key Signals
- Program
- Project EDGE
- Product type
- Staff pilot
- Delivery model
- Progressive Elaboration
- Platform
- Micro-frontend · React Native
NAB Edge Credit Card fact sheet
Correct as at 11 April 2023
Product terms from NAB's published fact sheet. The staff pilot ran as a real credit card — standard rates, fees, and disclosures.
Minimum credit limit
$1,000
Purchase rate
12.99% p.a.
Interest-free period
Up to 44 days
Annual fee
$1
Minimum repayment
2% or $25
Cash advance rate
21.74% p.a.
Why micro-frontend — and why React Native
NAB needed more than a demo app. The staff pilot had to run as a live credit card — real accounts, real transactions, real compliance — on an architecture the bank could scale to partner brands. Micro-frontend was the principle: independently owned surfaces composing into one multi-tenant platform. React Native was the medium — one implementation path for those mobile surfaces on iOS and Android, with shared UI patterns and fast iteration inside a heavily regulated environment.
Cross-functional work in the domain model
The pilot was owned by the credit card domain — product owners, mobile engineers, DevOps, designers, QAs, and release engineers sharing one backlog. Mobile work tracked core banking changes, card servicing APIs, and what operations needed before go-live.
Progressive Elaboration in practice
Features were broken down Epic → Feature → Story so the organisation built what was needed when it was needed — not too early, not too late. Progressive Elaboration in an Agile setting let the team ship incrementally, refine scope as integration points became clear, and keep defect rates down by avoiding big-bang drops on untested paths.
Enterprise-wide rollout and feedback
The pilot reached NAB staff in stages. I coordinated with product, operations, support, and program leadership on each release — collecting feedback from real card usage and feeding it back into the backlog. Staff were the first production users before any external migration.
Production banking, not mocks
The app wired into live card and account services — digital card provisioning, statements, repayments, transaction history, authentication, and push notifications. Integration gaps, latency issues, and edge cases showed up early, with exposure limited to an internal staff cohort. Product fact sheets, consent flows, and disclosure timing were built into the journeys.
What the pilot unlocked
By the time whitelabel migration started, release governance, observability, security patterns, and shared micro-frontend components were already proven on a NAB-owned product. The architecture — and React Native as its mobile medium — was no longer a bet; it was the validated foundation for partner-branded apps on the same platform.
Explore Further
Need this kind of React Native delivery?
Book a strategy session to discuss enterprise architecture, product delivery, or mobile platform tooling.
Schedule an appointment