It is very interesting to see Stripe decoupling embedded fintech from its core payments stack. This shows that Stripe's embedded suite is mature enough to stand on its own. This flexibility is very important to larger companies, which may want to use some elements of the platform but not all. Here at Tint, we also believe in flexibility, which is why we built our embedded insurance platform to be modularized. We offer the tech, services, and access to insurers that brands need to launch their solutions and let them choose from a plug-and-play solution to a bespoke combination of modules. In the end, flexibility will win in embedded insurance in the same way it won in embedded payments!
Matheus Riolfi’s Post
More Relevant Posts
-
CEO @Nationwide Payment Systems, Providing customized payment and Advisory Services to businesses! 18K+ followers
UNDERSTANDING THE STRIPE DEBANKING CONTROVERSY Stripe, a leading online payment processing platform, recently emerged amidst controversy and backlash. This article aims to provide an in-depth analysis of the situation, shedding light on the intricacies and implications of the debanking controversy faced by Silicon Valley’s financial giant. This is my take on the recent article in Daily Mail UK. Nationwide Payment Systems provides a reliable alternative to STRIPE. https://lnkd.in/egR3veFR Nationwide Payment Systems
Understanding the Stripe Debanking Controversy
https://nationwidepaymentsystems.com
-
CMO @adstrong, Google Shopping Ads Solutions for Agencies, Brands and Shops | Helping B2B SaaS Marketing Teams Deliver Results ツ | Founder
Bold move by Stripe. Decoupling payments from their services stack 🤯 A big shift towards greater flexibility and customization in the fintech space, and I am looking forward to see how this all plays out in the next couple of months... Especially for B2B that haven't integrated Stripe and their services so far. Standalone verifications? Yes. Standalone risk/fraud detection? Yes Standalone in-person payments? Yes 100+ payment methods? Hell yes https://lnkd.in/d7cvwvQ3
Stripe, doubling down on embedded finance, de-couples payments from the rest of its stack | TechCrunch
https://techcrunch.com
-
BaaS is here to stay, what matters is the implementation model being selected by the individual players.
Leadership | FinTech | Payments | Banking | Innovation |
Is Banking-as-a-Service (#BaaS) the future of financial services (FS) or a business model increasingly in trouble? Looking at last week’s events, both could be true. Let’s take a look. The need for open, scalable, flexible, efficient and fast set-ups in FS – together with the decoupling of the back-end from the front-end - have brought to the fore the SaaS principle, which in #banking we call BaaS (banking instead of software). The majority of fintechs were built on the back of a BaaS model, i.e. using the infrastructure and licensing of partners while they focus on the customer relationship. US-based Synapse was one of the first and leading BaaS players. What we would call a full-stack platform provider, i.e. an end-to-end BaaS player that would take care of all the back-end stuff on a modular basis and rely on partner banks for the licensing piece. The model worked well until BaaS players like Synapse were challenged by increased regulatory scrutiny. Railsr is a characteristic example going from being one of the most successful BaaS players to bankruptcy and a revoking of their license in Lithuania due to compliance failings. As a result, many of the BaaS providers’ (fintech) clients left and sought direct relationships with the banks, to mitigate the risk of their BaaS provider going out of business. Last week Synapse filed for Chapter 11 bankruptcy with its assets being acquired by TabaPay, in a play that was some time in the making following Evolve Bank & Trust, Synapses’s primary banking partner, ending the relationship last summer. At the same time, Stripe, a #fintech that helps merchants and platforms to accept payments has used the BaaS model to enable its customers embed a range of FS: — Stripe Connect allows business to embed multiparty payments and offer a variety of FS, like collecting payments from customers and paying out third parties. — Stripe Capital enables businesses to access financing based on their cash-flow. — Stripe Issuing allows businesses to instantly create and issue white-label virtual and physical cards. — Stripe Treasury enables businesses to offer accounts to their customers. Up to now Stripe required businesses to be #payments customers to be able to use the embedded finance offerings. Last week it announced a significant strategic shift by: — de-coupling payments from the rest of its FS stack — broadening embedded finance functionality Essentially, it's a doubling down on Stripe’s BaaS #strategy that now becomes independent in order to be able to expand scope and grow faster. My take-aways: — Embedded Finance will continue to take FS by storm and BaaS will remain the enabling infrastructure behind. — The failure of providers such as Synapse or Railsr is not a failure of BaaS but of a specific implementation approach that failed to adapt. — Scale is critical. — E2E, integrated business models will win. Opinions: my own, Graphic sources: Stripe, WhiteSight
-
-
Synergies are awaited!!! I believe BaaS (Banking-as-a-Service) will be a game changer, especially in emerging markets 💹. From #fintechs bringing more fronts 📳 to #banks capacity to handing over unwarranted market 🎯 segments to #fintechs, BaaS partnerships🏦 can exponentially increase financial inclusion 💵.
Leadership | FinTech | Payments | Banking | Innovation |
Is Banking-as-a-Service (#BaaS) the future of financial services (FS) or a business model increasingly in trouble? Looking at last week’s events, both could be true. Let’s take a look. The need for open, scalable, flexible, efficient and fast set-ups in FS – together with the decoupling of the back-end from the front-end - have brought to the fore the SaaS principle, which in #banking we call BaaS (banking instead of software). The majority of fintechs were built on the back of a BaaS model, i.e. using the infrastructure and licensing of partners while they focus on the customer relationship. US-based Synapse was one of the first and leading BaaS players. What we would call a full-stack platform provider, i.e. an end-to-end BaaS player that would take care of all the back-end stuff on a modular basis and rely on partner banks for the licensing piece. The model worked well until BaaS players like Synapse were challenged by increased regulatory scrutiny. Railsr is a characteristic example going from being one of the most successful BaaS players to bankruptcy and a revoking of their license in Lithuania due to compliance failings. As a result, many of the BaaS providers’ (fintech) clients left and sought direct relationships with the banks, to mitigate the risk of their BaaS provider going out of business. Last week Synapse filed for Chapter 11 bankruptcy with its assets being acquired by TabaPay, in a play that was some time in the making following Evolve Bank & Trust, Synapses’s primary banking partner, ending the relationship last summer. At the same time, Stripe, a #fintech that helps merchants and platforms to accept payments has used the BaaS model to enable its customers embed a range of FS: — Stripe Connect allows business to embed multiparty payments and offer a variety of FS, like collecting payments from customers and paying out third parties. — Stripe Capital enables businesses to access financing based on their cash-flow. — Stripe Issuing allows businesses to instantly create and issue white-label virtual and physical cards. — Stripe Treasury enables businesses to offer accounts to their customers. Up to now Stripe required businesses to be #payments customers to be able to use the embedded finance offerings. Last week it announced a significant strategic shift by: — de-coupling payments from the rest of its FS stack — broadening embedded finance functionality Essentially, it's a doubling down on Stripe’s BaaS #strategy that now becomes independent in order to be able to expand scope and grow faster. My take-aways: — Embedded Finance will continue to take FS by storm and BaaS will remain the enabling infrastructure behind. — The failure of providers such as Synapse or Railsr is not a failure of BaaS but of a specific implementation approach that failed to adapt. — Scale is critical. — E2E, integrated business models will win. Opinions: my own, Graphic sources: Stripe, WhiteSight
-
-
baas: banking: as a service: others fail some succeed why
Leadership | FinTech | Payments | Banking | Innovation |
Is Banking-as-a-Service (#BaaS) the future of financial services (FS) or a business model increasingly in trouble? Looking at last week’s events, both could be true. Let’s take a look. The need for open, scalable, flexible, efficient and fast set-ups in FS – together with the decoupling of the back-end from the front-end - have brought to the fore the SaaS principle, which in #banking we call BaaS (banking instead of software). The majority of fintechs were built on the back of a BaaS model, i.e. using the infrastructure and licensing of partners while they focus on the customer relationship. US-based Synapse was one of the first and leading BaaS players. What we would call a full-stack platform provider, i.e. an end-to-end BaaS player that would take care of all the back-end stuff on a modular basis and rely on partner banks for the licensing piece. The model worked well until BaaS players like Synapse were challenged by increased regulatory scrutiny. Railsr is a characteristic example going from being one of the most successful BaaS players to bankruptcy and a revoking of their license in Lithuania due to compliance failings. As a result, many of the BaaS providers’ (fintech) clients left and sought direct relationships with the banks, to mitigate the risk of their BaaS provider going out of business. Last week Synapse filed for Chapter 11 bankruptcy with its assets being acquired by TabaPay, in a play that was some time in the making following Evolve Bank & Trust, Synapses’s primary banking partner, ending the relationship last summer. At the same time, Stripe, a #fintech that helps merchants and platforms to accept payments has used the BaaS model to enable its customers embed a range of FS: — Stripe Connect allows business to embed multiparty payments and offer a variety of FS, like collecting payments from customers and paying out third parties. — Stripe Capital enables businesses to access financing based on their cash-flow. — Stripe Issuing allows businesses to instantly create and issue white-label virtual and physical cards. — Stripe Treasury enables businesses to offer accounts to their customers. Up to now Stripe required businesses to be #payments customers to be able to use the embedded finance offerings. Last week it announced a significant strategic shift by: — de-coupling payments from the rest of its FS stack — broadening embedded finance functionality Essentially, it's a doubling down on Stripe’s BaaS #strategy that now becomes independent in order to be able to expand scope and grow faster. My take-aways: — Embedded Finance will continue to take FS by storm and BaaS will remain the enabling infrastructure behind. — The failure of providers such as Synapse or Railsr is not a failure of BaaS but of a specific implementation approach that failed to adapt. — Scale is critical. — E2E, integrated business models will win. Opinions: my own, Graphic sources: Stripe, WhiteSight
-
-
Professional in Financial Services |IFIC (Certified) |Residential and Commercial Loans |Customer Service Experience|Retail Banking |Financial Account Analysis |Digital Banking |QBO|Microsoft Office 365
❇️Future of Financial Services ❇️ #banking #service #bank #financialcompany #business #BaaS #future #bankingservices #banks
Leadership | FinTech | Payments | Banking | Innovation |
Is Banking-as-a-Service (#BaaS) the future of financial services (FS) or a business model increasingly in trouble? Looking at last week’s events, both could be true. Let’s take a look. The need for open, scalable, flexible, efficient and fast set-ups in FS – together with the decoupling of the back-end from the front-end - have brought to the fore the SaaS principle, which in #banking we call BaaS (banking instead of software). The majority of fintechs were built on the back of a BaaS model, i.e. using the infrastructure and licensing of partners while they focus on the customer relationship. US-based Synapse was one of the first and leading BaaS players. What we would call a full-stack platform provider, i.e. an end-to-end BaaS player that would take care of all the back-end stuff on a modular basis and rely on partner banks for the licensing piece. The model worked well until BaaS players like Synapse were challenged by increased regulatory scrutiny. Railsr is a characteristic example going from being one of the most successful BaaS players to bankruptcy and a revoking of their license in Lithuania due to compliance failings. As a result, many of the BaaS providers’ (fintech) clients left and sought direct relationships with the banks, to mitigate the risk of their BaaS provider going out of business. Last week Synapse filed for Chapter 11 bankruptcy with its assets being acquired by TabaPay, in a play that was some time in the making following Evolve Bank & Trust, Synapses’s primary banking partner, ending the relationship last summer. At the same time, Stripe, a #fintech that helps merchants and platforms to accept payments has used the BaaS model to enable its customers embed a range of FS: — Stripe Connect allows business to embed multiparty payments and offer a variety of FS, like collecting payments from customers and paying out third parties. — Stripe Capital enables businesses to access financing based on their cash-flow. — Stripe Issuing allows businesses to instantly create and issue white-label virtual and physical cards. — Stripe Treasury enables businesses to offer accounts to their customers. Up to now Stripe required businesses to be #payments customers to be able to use the embedded finance offerings. Last week it announced a significant strategic shift by: — de-coupling payments from the rest of its FS stack — broadening embedded finance functionality Essentially, it's a doubling down on Stripe’s BaaS #strategy that now becomes independent in order to be able to expand scope and grow faster. My take-aways: — Embedded Finance will continue to take FS by storm and BaaS will remain the enabling infrastructure behind. — The failure of providers such as Synapse or Railsr is not a failure of BaaS but of a specific implementation approach that failed to adapt. — Scale is critical. — E2E, integrated business models will win. Opinions: my own, Graphic sources: Stripe, WhiteSight
-
-
Head of Strategy & Content @ Sardine / Writer FintechBrainfood 🧠
Stripe Issuing is at 200m cards. Fiserv is 1.6bn, Global Payments has 800m. That makes Stripe a MAJOR issuer processor. They also doubled the cards issued in the last 12 months. There's a view in the market that the payments companies aren't doing that well in embedded finance. This would suggest that's not true. This nugget isn't widely discussed in 1. Payments. We talk about Marqeta and Galileo but not Stripe or Adyen. 2. Banking as a Service. The talk is all about Synapse, Evolve and then Lithic etc as modern issuer processors. 3. Tech. We still see Stripe as the acquirer / PSP but the jury was out on the ability to do more. I'd hear lots of rumors that "Stripe's embedded finance isn't going so well" but no hard data. Open to contrary opinions. William Gaybrick (Source: Stripe, GPN Q1 results)
-
-
Is Banking-as-a-Service (#BaaS) the future of financial services (FS) or a business model increasingly in trouble? Looking at last week’s events, both could be true. Let’s take a look. The need for open, scalable, flexible, efficient and fast set-ups in FS – together with the decoupling of the back-end from the front-end - have brought to the fore the SaaS principle, which in #banking we call BaaS (banking instead of software). The majority of fintechs were built on the back of a BaaS model, i.e. using the infrastructure and licensing of partners while they focus on the customer relationship. US-based Synapse was one of the first and leading BaaS players. What we would call a full-stack platform provider, i.e. an end-to-end BaaS player that would take care of all the back-end stuff on a modular basis and rely on partner banks for the licensing piece. The model worked well until BaaS players like Synapse were challenged by increased regulatory scrutiny. Railsr is a characteristic example going from being one of the most successful BaaS players to bankruptcy and a revoking of their license in Lithuania due to compliance failings. As a result, many of the BaaS providers’ (fintech) clients left and sought direct relationships with the banks, to mitigate the risk of their BaaS provider going out of business. Last week Synapse filed for Chapter 11 bankruptcy with its assets being acquired by TabaPay, in a play that was some time in the making following Evolve Bank & Trust, Synapses’s primary banking partner, ending the relationship last summer. At the same time, Stripe, a #fintech that helps merchants and platforms to accept payments has used the BaaS model to enable its customers embed a range of FS: — Stripe Connect allows business to embed multiparty payments and offer a variety of FS, like collecting payments from customers and paying out third parties. — Stripe Capital enables businesses to access financing based on their cash-flow. — Stripe Issuing allows businesses to instantly create and issue white-label virtual and physical cards. — Stripe Treasury enables businesses to offer accounts to their customers. Up to now Stripe required businesses to be #payments customers to be able to use the embedded finance offerings. Last week it announced a significant strategic shift by: — de-coupling payments from the rest of its FS stack — broadening embedded finance functionality Essentially, it's a doubling down on Stripe’s BaaS #strategy that now becomes independent in order to be able to expand scope and grow faster. My take-aways: — Embedded Finance will continue to take FS by storm and BaaS will remain the enabling infrastructure behind. — The failure of providers such as Synapse or Railsr is not a failure of BaaS but of a specific implementation approach that failed to adapt. — Scale is critical. — E2E, integrated business models will win. Opinions: my own, Graphic sources: Stripe, WhiteSight
Leadership | FinTech | Payments | Banking | Innovation |
Is Banking-as-a-Service (#BaaS) the future of financial services (FS) or a business model increasingly in trouble? Looking at last week’s events, both could be true. Let’s take a look. The need for open, scalable, flexible, efficient and fast set-ups in FS – together with the decoupling of the back-end from the front-end - have brought to the fore the SaaS principle, which in #banking we call BaaS (banking instead of software). The majority of fintechs were built on the back of a BaaS model, i.e. using the infrastructure and licensing of partners while they focus on the customer relationship. US-based Synapse was one of the first and leading BaaS players. What we would call a full-stack platform provider, i.e. an end-to-end BaaS player that would take care of all the back-end stuff on a modular basis and rely on partner banks for the licensing piece. The model worked well until BaaS players like Synapse were challenged by increased regulatory scrutiny. Railsr is a characteristic example going from being one of the most successful BaaS players to bankruptcy and a revoking of their license in Lithuania due to compliance failings. As a result, many of the BaaS providers’ (fintech) clients left and sought direct relationships with the banks, to mitigate the risk of their BaaS provider going out of business. Last week Synapse filed for Chapter 11 bankruptcy with its assets being acquired by TabaPay, in a play that was some time in the making following Evolve Bank & Trust, Synapses’s primary banking partner, ending the relationship last summer. At the same time, Stripe, a #fintech that helps merchants and platforms to accept payments has used the BaaS model to enable its customers embed a range of FS: — Stripe Connect allows business to embed multiparty payments and offer a variety of FS, like collecting payments from customers and paying out third parties. — Stripe Capital enables businesses to access financing based on their cash-flow. — Stripe Issuing allows businesses to instantly create and issue white-label virtual and physical cards. — Stripe Treasury enables businesses to offer accounts to their customers. Up to now Stripe required businesses to be #payments customers to be able to use the embedded finance offerings. Last week it announced a significant strategic shift by: — de-coupling payments from the rest of its FS stack — broadening embedded finance functionality Essentially, it's a doubling down on Stripe’s BaaS #strategy that now becomes independent in order to be able to expand scope and grow faster. My take-aways: — Embedded Finance will continue to take FS by storm and BaaS will remain the enabling infrastructure behind. — The failure of providers such as Synapse or Railsr is not a failure of BaaS but of a specific implementation approach that failed to adapt. — Scale is critical. — E2E, integrated business models will win. Opinions: my own, Graphic sources: Stripe, WhiteSight
-
-
Leadership | FinTech | Payments | Banking | Innovation |
Is Banking-as-a-Service (#BaaS) the future of financial services (FS) or a business model increasingly in trouble? Looking at last week’s events, both could be true. Let’s take a look. The need for open, scalable, flexible, efficient and fast set-ups in FS – together with the decoupling of the back-end from the front-end - have brought to the fore the SaaS principle, which in #banking we call BaaS (banking instead of software). The majority of fintechs were built on the back of a BaaS model, i.e. using the infrastructure and licensing of partners while they focus on the customer relationship. US-based Synapse was one of the first and leading BaaS players. What we would call a full-stack platform provider, i.e. an end-to-end BaaS player that would take care of all the back-end stuff on a modular basis and rely on partner banks for the licensing piece. The model worked well until BaaS players like Synapse were challenged by increased regulatory scrutiny. Railsr is a characteristic example going from being one of the most successful BaaS players to bankruptcy and a revoking of their license in Lithuania due to compliance failings. As a result, many of the BaaS providers’ (fintech) clients left and sought direct relationships with the banks, to mitigate the risk of their BaaS provider going out of business. Last week Synapse filed for Chapter 11 bankruptcy with its assets being acquired by TabaPay, in a play that was some time in the making following Evolve Bank & Trust, Synapses’s primary banking partner, ending the relationship last summer. At the same time, Stripe, a #fintech that helps merchants and platforms to accept payments has used the BaaS model to enable its customers embed a range of FS: — Stripe Connect allows business to embed multiparty payments and offer a variety of FS, like collecting payments from customers and paying out third parties. — Stripe Capital enables businesses to access financing based on their cash-flow. — Stripe Issuing allows businesses to instantly create and issue white-label virtual and physical cards. — Stripe Treasury enables businesses to offer accounts to their customers. Up to now Stripe required businesses to be #payments customers to be able to use the embedded finance offerings. Last week it announced a significant strategic shift by: — de-coupling payments from the rest of its FS stack — broadening embedded finance functionality Essentially, it's a doubling down on Stripe’s BaaS #strategy that now becomes independent in order to be able to expand scope and grow faster. My take-aways: — Embedded Finance will continue to take FS by storm and BaaS will remain the enabling infrastructure behind. — The failure of providers such as Synapse or Railsr is not a failure of BaaS but of a specific implementation approach that failed to adapt. — Scale is critical. — E2E, integrated business models will win. Opinions: my own, Graphic sources: Stripe, WhiteSight
-
-
Senior SAP Finance Control Consultant bei ISAP Solutions FZE. Blockchain | Wallet | NFT | DeFi | Metaverse |
Is Banking-as-a-Service (#BaaS) the future of financial services (FS) or a business model increasingly in trouble? Looking at last week’s events, both could be true. Let’s take a look. The need for open, scalable, flexible, efficient and fast set-ups in FS – together with the decoupling of the back-end from the front-end - have brought to the fore the SaaS principle, which in #banking we call BaaS (banking instead of software). The majority of fintechs were built on the back of a BaaS model, i.e. using the infrastructure and licensing of partners while they focus on the customer relationship. US-based Synapse was one of the first and leading BaaS players. What we would call a full-stack platform provider, i.e. an end-to-end BaaS player that would take care of all the back-end stuff on a modular basis and rely on partner banks for the licensing piece. The model worked well until BaaS players like Synapse were challenged by increased regulatory scrutiny. Railsr is a characteristic example going from being one of the most successful BaaS players to bankruptcy and a revoking of their license in Lithuania due to compliance failings. As a result, many of the BaaS providers’ (fintech) clients left and sought direct relationships with the banks, to mitigate the risk of their BaaS provider going out of business. Last week Synapse filed for Chapter 11 bankruptcy with its assets being acquired by TabaPay, in a play that was some time in the making following Evolve Bank & Trust, Synapses’s primary banking partner, ending the relationship last summer. At the same time, Stripe, a #fintech that helps merchants and platforms to accept payments has used the BaaS model to enable its customers embed a range of FS: — Stripe Connect allows business to embed multiparty payments and offer a variety of FS, like collecting payments from customers and paying out third parties. — Stripe Capital enables businesses to access financing based on their cash-flow. — Stripe Issuing allows businesses to instantly create and issue white-label virtual and physical cards. — Stripe Treasury enables businesses to offer accounts to their customers. Up to now Stripe required businesses to be #payments customers to be able to use the embedded finance offerings. Last week it announced a significant strategic shift by: — de-coupling payments from the rest of its FS stack — broadening embedded finance functionality Essentially, it's a doubling down on Stripe’s BaaS #strategy that now becomes independent in order to be able to expand scope and grow faster. My take-aways: — Embedded Finance will continue to take FS by storm and BaaS will remain the enabling infrastructure behind. — The failure of providers such as Synapse or Railsr is not a failure of BaaS but of a specific implementation approach that failed to adapt. — Scale is critical. — E2E, integrated business models will win. Opinions: my own, Graphic sources: Stripe, WhiteSight
Leadership | FinTech | Payments | Banking | Innovation |
Is Banking-as-a-Service (#BaaS) the future of financial services (FS) or a business model increasingly in trouble? Looking at last week’s events, both could be true. Let’s take a look. The need for open, scalable, flexible, efficient and fast set-ups in FS – together with the decoupling of the back-end from the front-end - have brought to the fore the SaaS principle, which in #banking we call BaaS (banking instead of software). The majority of fintechs were built on the back of a BaaS model, i.e. using the infrastructure and licensing of partners while they focus on the customer relationship. US-based Synapse was one of the first and leading BaaS players. What we would call a full-stack platform provider, i.e. an end-to-end BaaS player that would take care of all the back-end stuff on a modular basis and rely on partner banks for the licensing piece. The model worked well until BaaS players like Synapse were challenged by increased regulatory scrutiny. Railsr is a characteristic example going from being one of the most successful BaaS players to bankruptcy and a revoking of their license in Lithuania due to compliance failings. As a result, many of the BaaS providers’ (fintech) clients left and sought direct relationships with the banks, to mitigate the risk of their BaaS provider going out of business. Last week Synapse filed for Chapter 11 bankruptcy with its assets being acquired by TabaPay, in a play that was some time in the making following Evolve Bank & Trust, Synapses’s primary banking partner, ending the relationship last summer. At the same time, Stripe, a #fintech that helps merchants and platforms to accept payments has used the BaaS model to enable its customers embed a range of FS: — Stripe Connect allows business to embed multiparty payments and offer a variety of FS, like collecting payments from customers and paying out third parties. — Stripe Capital enables businesses to access financing based on their cash-flow. — Stripe Issuing allows businesses to instantly create and issue white-label virtual and physical cards. — Stripe Treasury enables businesses to offer accounts to their customers. Up to now Stripe required businesses to be #payments customers to be able to use the embedded finance offerings. Last week it announced a significant strategic shift by: — de-coupling payments from the rest of its FS stack — broadening embedded finance functionality Essentially, it's a doubling down on Stripe’s BaaS #strategy that now becomes independent in order to be able to expand scope and grow faster. My take-aways: — Embedded Finance will continue to take FS by storm and BaaS will remain the enabling infrastructure behind. — The failure of providers such as Synapse or Railsr is not a failure of BaaS but of a specific implementation approach that failed to adapt. — Scale is critical. — E2E, integrated business models will win. Opinions: my own, Graphic sources: Stripe, WhiteSight
-
