Silverflow, a Dutch startup founded by Adyen alumni, is breaking cover and announcing seed funding.
The pre-launch company has spent the last two years building what it describes as a “cloud-native” online card processor that directly connects to card networks. The aim is to offer a modern replacement for the 20 to 40-year-old payments card processing tech that is mostly in use today.
Backing Silverflow’s €2.6 million seed round is U.K.-based VC Crane Venture Partners, with participation from Inkef Capital and unnamed angel investors and industry leaders from Pay.On, First Data, Booking.com and Adyen. It brings the fintech startup’s total funding to date to ~€3 million.
Bootstrapped while in development and launching in 2021, Silverflow’s founders are CEO Anne-Willem de Vries (who was focused on card acquiring and processing at Adyen), CBDO Robert Kraal (former Adyen COO and EVP global card acquiring & processing of Adyen) and CTO Paul Buying (founder of acquired translation startup Livewords).
“The payments tech stack needs an upgrade,” Kraal tells me. “Today’s card payment infrastructure based on 30 to 40-year-old technology is still in use across the global payment landscape. This legacy infrastructure is costing everyone time and money: consumers, merchants, payment-service-providers and banks. The legacy platforms require a lengthy on-boarding process and are expensive to maintain, [and] they also aren’t fit for purpose today because they don’t support data use”.
In addition, Kraal says that adding new functionality is a lengthy and expensive process, requiring the effort of specialised engineers which ultimately slows down innovation “for the whole card payments system”.
“Finally, every acquirer provides its customer with a different processing platform, which for a typical payment service provider (PSP) means they have to deal with multiple legacy platforms — and all the costs and specialised support each entails,” adds de Vries.
To solve this, Silverflow claims it has built the first payments processor with a “cloud-native platform” built for today’s technology stack. This includes offering simple APIs and “streamlined data flows” directly integrated into the card networks.
Continues de Vries: “Instead of managing a complex network of acquirers across markets with dozens of bank and card network connections to maintain, Silverflow provides card-acquiring processing as a service that connects to card networks directly through a simple API”.
Target customers are PSPs, acquirers and “global top-market merchants” that are seeing €500 million to 10 billion in annual transactions.
“As a managed service, Silverflow provides the maintenance for connections and new product innovation that users have typically had to support in-house or work on long-term product road maps with suppliers,” explains Kraal. “Based in the cloud, Silverflow is infinitely scalable for peak flows and also provides robust data insights that users haven’t previously been able to access”.
With regards to competitors, Kraal says there are no other companies at the moment doing something similar, “as far as we are aware”. Currently, acquirers use traditional third-party processors, such as SIA, Omnipay, Cybersource or MIGS. Some companies, like Adyen, have built their own in-house processing platform.
So, why hasn’t a cloud-native card processing platform like Silverflow been done before and why now? A lack of awareness of the problem might be one reason, says de Vries.
“Unless you have built several integrations to acquirers during your career, you are not aware that the 30 to 40-years-old infrastructure is still in use. This is not typically a problem some bright college graduates would tackle,” he posits.
“Second, to build this successfully, you need to have prior knowledge of the card payments industry to navigate all the legal, regulatory and technical requirements.
“Thirdly, any large corporate currently active in card payment processing will be aware of the problem and have the relevant industry knowledge. However, building a new processing platform would require them to allocate their most talented staff to this project for two-three years, taking away resources from their existing projects. In addition, they would also need to manage a complex migration project to move their existing customers from their current system to the new one and risk losing some of the customers along the way”.
