0/ We've highlighted FinTech infrastructure co's like BR, FIS, JKHY, MA, V, ICE, NDAQ, etc. as companies w/ a variety of moats that have led to dominant mkt share & outperformance despite being 50+ years old on avg.
$FISV had their investor day yesterday and laid out the why.
All while being #1 as a core account processor, merchant acquirer, bill pay, P2P payments, etc...
They highlight the progress on the deal & new goals post integration.
M&A is a skill & FISV has it financially; tech integration leaves something to be desired
(i) Merchant Solutions
(ii) Integrated Banking
(iii) Digital Payments
(iv) Card Payments
They conduct more than 12,000 financial tx / second & reach nearly ~100% of US households
(i) Flexible API Service Architecture
(ii) Security & Fraud Tools
(iii) Third Party Integrations
(iv) Data & Analytics
This is a slide I imagine a number of BaaS companies look to emulate in future decks.
They believe $90B was spent in '20 by Financial Institution on IT which is projected to grow at a 6.3% CAGR through '24.
For those that believe FinTech B2B infrastructure is saturated thats a portion of the pie
With talks of @Marqeta going public next year this will be an interesting comp for this business line.
This is part of the oppty co's like Marqeta & Galileo saw $FISV won't entertain the startup.
(i) Omnichannel Capabilities
(ii) Horizontal Commerce Solutions
(iii) Leading Technology
(iv) Payments Innovation
(v) Local Execution
(vi) Integration Advantages
More from Trading
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.