
As technology businesses expand globally, their payments infrastructure often struggles to keep pace. PayDo CEO Serhii Zakharov explores why.
Technology businesses can go international almost from day one, but their payments infrastructure doesn’t always keep pace. Serhii Zakharov, CEO of PayDo, explores why payments need to scale alongside the businesses they support.
Technology companies can become international remarkably quickly. A SaaS business can sign customers in 20 countries in its first year, while an AI or digital services company can build a distributed workforce across several continents almost from day one.
But the payments infrastructure supporting those businesses does not always develop at the same pace.
It usually starts when a technology company stops being local, which happens very early now. Its payments setup may have been chosen when it had one market and one currency. As the business grows, it adds providers one at a time: one for card acquiring, another for payouts and a third for currency conversion.
Each decision makes sense on the day. Stacked together, they create a stack no one sees.
The businesses most affected are often those with money moving in both directions: a marketplace or platform paying sellers and creators, a SaaS company with global subscriptions and distributed teams, or an AI or digital services firm paying contractors across multiple jurisdictions.
The resulting problems are practical ones: slow or failed cross-border payouts, reconciliation spread across several systems, and onboarding that must be repeated with every new provider.
For technology businesses looking to scale globally, payments can’t be treated as an add-on. The payments infrastructure needs to be able to scale with the company.
The international nature of technology businesses has also changed what they require from payments.
Ten years ago, a technology company’s payments were mostly inbound, with customers paying for a product. Today, outbound flows matter just as much.
A company may have developers in Poland, designers in Georgia, support staff in Southeast Asia and contractors in Latin America, all expecting to be paid on time and in their own currency.
That changes what the infrastructure needs to do. It requires multi-currency accounts so funds aren’t converted twice, mass payouts that can handle hundreds of recipients at once, and clear visibility into where each payment is at any moment.
Regulatory and compliance requirements also need to be considered market by market, including whether local authorisation or regulatory standing is required. The companies that struggle are often those trying to run a global workforce on payment tools designed for a domestic business.
Payments are usually the last part of the business to be designed, and the first thing to break when it goes international.
Recipient expectations are changing at the same time.
This shows up most clearly with freelance developers and creators, who work for several international companies at once and have strong preferences about how and where they are paid. Some want payment to a local account in their own currency, some want a card, while others want faster options for smaller amounts.
For businesses, payout flexibility is consequently becoming part of how they attract and retain talent. A company that pays late, or can only pay in one way, risks losing good contractors to one that does not.
Some of the most interesting markets for technology companies today are emerging economies with strong technical talent and rapidly growing digital sectors. That is precisely why international businesses want to hire or sell there.
The difficulty is not necessarily the markets themselves, but how payments get there.
Routes can involve long correspondent banking chains, local currency rules can add steps, and providers may apply broad country-level risk settings rather than assessing the specific business and payment flow.
Companies expanding into these markets should ask a few practical questions. Which corridors does your provider actually support directly? How long do payments take to settle? What documentation will recipients need? How are currency conversions handled?
One practical step is to try a small payout run before committing an entire payroll to a new corridor.
More broadly, the mistake is to choose a provider for the first market and assume it will work for the tenth.
Management teams should understand whether a provider has direct access to the payment networks it relies upon or routes through intermediaries. The difference is not cosmetic. PayDo has direct access to major payment networks, including Visa, Mastercard, SWIFT and SEPA, helping reduce the number of intermediaries involved in processing payments and, in turn, potential points of friction. They should ask whether it can collect payments and pay out in multiple currencies under one relationship, and what happens to onboarding when the business adds another market or product line.
Finance teams also need to understand what visibility they will have over settlement and reconciliation, and businesses need to know who they can speak to when something goes wrong and how quickly they can expect a response.
The underlying question is whether the provider absorbs complexity as you grow or passes it back to your operations team.
Onboarding presents another challenge for newer digital business models.
Automated onboarding is very good at assessing businesses that fit an established pattern. But newer models do not always fit those patterns. A platform might split settlements across 30 countries, for example, while a SaaS company can have refund patterns that look different from those of a conventional business.
The result is that complexity gets read as risk.
A system built on category averages reads complexity as risk.
Less automation and looser standards are not the answer. Instead, providers need to define what normal looks like for each business from the start, with experienced people asking the right questions, then let automation monitor activity against that baseline.
This front-loaded work requires more effort during onboarding, but can lead to faster, better decisions and fewer disruptions later.
I have seen an application sit for weeks over a refund rate that turned out to be a free trial policy. A reviewer who works with software companies would have recognised that on the first read. Front-loading that work is why our own onboarding at PayDo typically takes one to three days from application to a live account.
Compliance and commercial teams should work from the same understanding of the client so the decision is better, not softer or slower.
The effect of payments infrastructure on a growing digital business is perhaps clearest at an operational level.
One digital business working with PayDo was collecting steady flows of customer payments but repeatedly encountered a problem with the time between a payment being confirmed and the money actually arriving.
Previous providers would indicate that an incoming payment was successful when it was initiated, but the funds had not yet settled. On every transaction, the business therefore had to choose between delaying service to its customers or fulfilling orders against money it could not yet see, effectively financing the gap itself.
As the company scaled, cash flow became increasingly difficult to forecast and plan around.
PayDo set the business up with a dedicated C2B IBAN for open banking collections. Customers could pay account-to-account into the client’s own account, with the client receiving real-time notifications when funds had been received rather than simply initiated.
Settlement used Faster Payments and SEPA Instant, while the client’s technical team had direct API access to transaction data, enabling automated reconciliation. PayDo worked alongside the client’s team to bring the system into production without disrupting its operations.
The company now receives real-time confirmation of funds received, and reconciliation that previously took time from its team is now automated. The cash-flow gaps have been removed, and the business can forecast and plan its payment operations in ways it could not before.
These requirements will continue to evolve.
Three developments are particularly important. First, account-to-account payments through open banking will likely take a bigger share of collections, particularly for recurring and high-value payments where cards can add cost without adding equivalent value.
Second, as open finance develops, businesses will be able to work with a much fuller picture of financial data.
Third, technology companies are likely to continue consolidating their payment stacks.
Running one business through many providers is expensive and operationally complex, and more companies will look towards fewer, deeper infrastructure relationships.
These are questions I will explore further at Web Summit in Lisbon on 11 November, when I will speak on the MoneyConf stage about how technology businesses can tackle payments complexity as they grow.
PayDo CEO Serhii Zakharov
Drawing on my experience as a founder, the session will follow a company through five stages of international expansion, examining how payment decisions that make sense early on can create operational challenges later. The aim is to help founders and operators recognise where their businesses stand and what they need to consider before entering their next market.
For technology businesses, the important question is therefore not simply whether their payments setup works today. It is whether it will continue to work as they enter the next market, hire the next international team and add the next group of customers.

