Payments sit too close to revenue for support ownership to be ambiguous. Behind every successful transaction are settlements, reconciliation, refunds, reporting, customer service, risk controls, and the flow of funds through the business. When any of these processes becomes unclear or inefficient, the consequences extend well beyond checkout.
We sat down with Tim Bruns, Head of Customer Support at Shopware, to explore what years of working closely with merchants have taught us about payments: where complexity emerges as businesses scale, how merchants can manage change without putting revenue at risk, and why the payment layer is becoming an increasingly strategic part of commerce infrastructure.
What are the biggest misconceptions merchants have about payments?
I think the biggest misconception is that payments are simply the final step of commerce. But payments sit much deeper in the business. Every transaction connects customer intent with revenue, financial operations, risk, and the systems required to execute commerce. In that sense, payments are part of the financial infrastructure on which commerce operates.
And I think that distinction will become increasingly important. Commerce is becoming more connected, more automated, and more intelligent. Payments can't remain an isolated transaction layer within that environment. They need to evolve as part of the broader commerce architecture. The question is no longer simply: “How can your customers pay?” But rather: “Is your payment infrastructure helping your business operate, connect, and evolve as effectively as it should?”
When does payment complexity become a business problem?
Complexity usually accumulates gradually. A merchant adds a provider to enter a new market, introduces another payment method to meet customer expectations, or connects another system to solve a reporting or operational requirement. Each decision can be perfectly rational in isolation. The problem emerges at the system level. Over time, the business can end up managing multiple contracts, integrations, dashboards, settlement schedules, support paths, and sources of truth.
The cost isn't always visible on a payment invoice. It appears in the time spent reconciling transactions, coordinating teams, maintaining integrations, investigating exceptions, and resolving discrepancies. Eventually, payment complexity becomes operational complexity – affecting efficiency, speed of execution, visibility, and the ability to scale without adding disproportionate overhead. That's the point where payments stop being a technical integration question and become an operating-model question.
How should Finance, Operations, and Ecommerce evaluate payments?
Each team sees a different part of the same system. Finance needs reliable transaction data, predictable settlements, transparent costs, and efficient reconciliation. Operations needs clear processes, dependable integrations, and defined ownership when issues arise. Ecommerce needs a payment portfolio that supports conversion across devices, markets, and purchasing situations.
The strongest payment setups connect these perspectives rather than optimizing one in isolation. A payment method that supports conversion but creates disproportionate operational effort may not improve the overall economics of the business. That's why leaders should evaluate payments across the entire transaction lifecycle – from customer choice at checkout to the point where funds are reconciled and available to the business.
How should merchants approach switching to a new payment setup?
The first question is almost always: “Will everything continue to work?” That's understandable. With many ecommerce capabilities, a temporary issue is inconvenient. With payments, an interruption can immediately affect revenue. I don't see that caution as resistance to change. It's good risk management. Merchants need confidence that checkout will work reliably, existing payment processes will be handled correctly, and they know where to turn if something goes wrong.
That's why I recommend treating migration as a controlled transition rather than a single switch. With Shopware Payments, that means connecting your PayPal Business account, configuring the relevant payment methods, and testing the checkout and payment flows thoroughly while your existing setup remains available. Finance, ecommerce, and support should also understand what's changing and what it means for their work.
Once the new setup has been validated, you can stop routing new payments through the previous setup while keeping the integration active until outstanding payment processes – such as authorized payments awaiting capture or pending refunds – are complete. Only then should the previous integration be deactivated. The best migration shouldn't feel like a leap of faith. By the time you go live, you should already know it works.
What's one piece of advice you give every merchant about payments?
Don't set up payments once and assume the job is done. Your customers change, your business grows, new payment methods emerge, and the economics of your setup evolve. What worked well a year ago may not be the right setup today.
I encourage merchants to review payments from two perspectives. First, the customer: are you offering the right payment methods for different preferences and purchasing situations? Second, the business: how much effort does it take to manage providers, integrations, payouts, refunds, and support?
A setup can work perfectly at checkout while creating unnecessary operational effort behind the scenes. That's why payment optimization goes beyond transaction fees. It includes customer choice, conversion, operational efficiency, and the overall economics of running payments. Don't just ask whether your payments work. Ask whether they're still working as hard as they could for your business.
Which metrics should leaders use to evaluate payments?
Transaction fees are important, but they don't tell the whole story. I would look at a balanced set of commercial, financial, and operational measures: payment success and authorization rates, conversion by payment method and device, average order value, settlement timing, refund and dispute handling, reconciliation effort, support volume, and the total internal and external cost of running the payment setup.
What matters is the value and effort created across the full transaction lifecycle. A payment setup can look inexpensive on a pricing sheet while becoming costly through failed transactions, slow access to funds, manual work, fragmented systems, or unnecessary complexity. The economics of payments are ultimately determined by what happens around the transaction as much as by the transaction itself. The cheapest transaction can still be an expensive way to run payments.
What payment methods belong to a strong checkout in Germany?
There isn't one perfect payment mix for every German merchant. It depends on your customer base, products, average order value, devices, and markets. But there are several methods I'd expect to see in a strong modern checkout. PayPal is an important foundation in Germany because of its familiarity and adoption. Cards provide broad acceptance, particularly for international customers. Apple Pay and Google Pay make mobile purchasing more convenient, while PayPal Pay Later and Klarna provide greater flexibility, particularly for higher-value purchases.
The important point is that these methods aren't simply competing for the same transaction. Each plays a different role in the payment portfolio and addresses different preferences and purchasing situations. If you're selling internationally, local payment preferences add another dimension. The goal isn't to offer everything. It's to build a deliberate payment mix that supports both the customer experience and the economics of your business.
What's the one capability leaders often overlook when comparing payment setups?
Settlement speed is something merchants don't always pay much attention to at first. Then payment volumes grow, and suddenly it becomes very tangible. Think about what happens after the customer clicks “Pay.” That revenue may need to fund inventory, suppliers, marketing, or simply the day-to-day operation of the business. The sooner it's available, the sooner you can put it back to work.
With Shopware Payments, 24-hour settlement helps shorten that cycle. At higher transaction volumes, even a day or two can represent a meaningful amount of working capital. That's why merchants should look beyond the headline transaction fee and consider the broader economics of their payment setup. For the customer, the payment journey ends when the purchase is complete. For the business, it ends when the money is available to put back to work.
Where are payments heading next?
At the beginning, we talked about the misconception that payments are simply the final step of commerce. I think the next few years will make that misconception impossible to maintain. AI is already changing how people discover products and how businesses serve them. Over time, intelligent systems and AI agents will take on more of the work – recommending, comparing, reordering, negotiating, and eventually executing parts of the purchasing process. That raises a fascinating question: what happens to payments when the customer isn't necessarily the one clicking the Pay button anymore?
The payment layer will need to become more connected to everything around the transaction – commerce data, customer context, financial operations, risk, and the systems making decisions. As commerce becomes more autonomous, the ability of these systems to exchange context and act together becomes increasingly important.
That's what makes embedded payments interesting beyond their immediate operational benefits. Bringing payments closer to the commerce platform creates a foundation where commerce, financial operations, and automation can evolve together.
At the same time, greater autonomy requires greater control. Merchants will need to understand and govern how money moves through increasingly intelligent systems. We don't know exactly what agentic commerce will look like in five years – and we don't need to. The goal is to build a payment foundation flexible enough to evolve with it. Payments will always move money. But as commerce becomes more connected and autonomous, the payment layer will increasingly become part of how commerce itself operates.
Beyond the transaction: My final thoughts
If there’s one thing I’ve learned from supporting merchants, it’s that payments are far more than a transaction layer. They influence customer experience, financial operations, organizational efficiency, and ultimately a company’s ability to adapt and scale. As commerce becomes more connected and intelligent, that role will only become more important. Payments increasingly sit at the intersection of commerce, capital, data, and technology – which makes the architecture and operating model behind them a strategic consideration.
My advice: treat payments with the same strategic discipline as the rest of your commerce infrastructure. Want to see how we’re approaching this at Shopware? Explore Shopware Payments.
