Payment methods in online shops: which ones your product range really needs
Related Posts
- Produktdaten pflegen: der unterschätzte Erfolgsfaktor im Onlineshop
- Xentral 2026: Diese Neuerungen sollten Sie als Shopware-Händler kennen
- Load Time and Core Web Vitals: Why Performance Directly Affects Revenue
- Aktuelle Shopware-Nachrichten: Dieser Beitrag wartet noch auf belastbare Fakten
- Shopware at a Glance: New Leadership, Fresh Releases and Agentic Commerce as the Key Theme
Most read
- Reducing returns: seven levers that really work
- Load Time and Core Web Vitals: Why Performance Directly Affects Revenue
- Produktdaten pflegen: der unterschätzte Erfolgsfaktor im Onlineshop
- Xentral 2026: Diese Neuerungen sollten Sie als Shopware-Händler kennen
- Shopware at a Glance: New Leadership, Fresh Releases and Agentic Commerce as the Key Theme
Latest posts
- Reducing returns: seven levers that really work
- Produktdaten pflegen: der unterschätzte Erfolgsfaktor im Onlineshop
- Aktuelle Shopware-Nachrichten: Dieser Beitrag wartet noch auf belastbare Fakten
- Xentral 2026: Diese Neuerungen sollten Sie als Shopware-Händler kennen
- Shopware at a Glance: New Leadership, Fresh Releases and Agentic Commerce as the Key Theme
At first glance, choosing payment methods seems like a purely technical decision. In fact, it is one of the few levers that simultaneously affects conversion, liquidity, payment default risk, and operating costs. Anyone who evaluates it only by fee rates is optimizing the wrong thing.
## The basic conflict: trust versus risk
Every payment method distributes risk differently between buyer and seller. With prepayment, the buyer bears the entire risk; with purchase on account, the merchant does. All other methods fall somewhere in between and differ mainly in who has the shorter end of the stick in case of a dispute.
This distribution leads to a simple rule: the less known your shop is, the more you have to advance in good faith. An established brand shop can afford to offer prepayment as the only option. A young shop that nobody knows cannot – purchase on account is simply the price for the lack of trust there.
## The basic set
For the German-speaking market, a set of four to six methods has proven practical.
Purchase on account is traditionally the most popular payment method in Germany and, for many product ranges, the one with the strongest conversion. Default risk can be mitigated through providers who take over the receivables default for a fee. The costs are higher than for other methods, but in most product ranges are more than offset by the additional orders.
Direct debit is inexpensive and well established with customers, but carries a chargeback risk for eight weeks. It makes the most sense for recurring payments and for existing customers.
Credit card is indispensable as soon as you ship abroad, and is a given for younger target groups anyway. Make sure strong customer authentication is implemented cleanly – a failed 3-D Secure step is one of the most common causes of checkout abandonment.
Digital wallets drastically shorten the checkout, because address and payment data are already stored. Their effect is especially clear on mobile devices, where every additional input field costs orders.
Instant bank transfer and comparable methods provide real-time payment confirmation and enable immediate shipping, without the merchant bearing the chargeback risk of direct debit.
Prepayment, finally, costs almost nothing and is actively desired by a small but loyal part of the customer base. It should be available, but should not remain the only option.
## How many payment methods make sense?
More choice is not automatically better. From about eight methods in the checkout onward, decision time measurably increases without the completion rate rising further. In addition, maintenance effort increases: every payment method needs an integration, a test concept, a rule for partial refunds, and a place in accounting.
A good approach is to design the offering contextually. Not every payment method needs to be shown to every customer. Sensible rules include, for example:
- Purchase on account only from the second purchase onward, or below a maximum cart value
- Certain methods only for selected delivery countries
- Exclusion of high-risk combinations with mismatched delivery and billing addresses
- Higher-value orders with additional review
These rules belong in a documented risk logic, not in case-by-case decisions that accumulate over time. Otherwise, after a year, nobody will know anymore why a particular customer doesn't see a particular option.
## The checkout also plays a role
The best selection of payment methods is of little use if the checkout process itself is clunky. Four details stand out in practice.
First: The order of the options acts like a recommendation. Put the method that is actually chosen most often in your shop at the top – not the one with the lowest fee.
Second: Logos instead of text lists. Payment methods are recognized visually. A plain radio button list with names is grasped significantly more slowly than a selection with familiar brand marks.
Third: Error messages must be actionable. "The payment could not be processed" helps no one. A note on what to do, along with an offer of an alternative payment method, is better – ideally without losing the shopping cart.
Fourth: Payment abandonments must be logged. A shop that doesn't know at which point and with which payment method orders fail is optimizing blind.
## Calculating fees correctly
Comparing payment service providers by percentage transaction rate alone falls short. A full cost calculation should also include: base fees, cost per transaction, costs for chargebacks and refunds, fees for credit checks, payout intervals, and the internal effort for payment reconciliation and dunning.
The last point in particular is regularly underestimated. A method with fees half a percentage point lower, but requiring twenty minutes of manual reconciliation daily, is the more expensive option in smaller shops.
Equally relevant is the payout interval. Anyone who needs to pre-finance goods as revenue grows will feel the difference between a daily and a fourteen-day payout very directly in liquidity planning.
## Don't forget legal obligations
Payment methods must not be surcharged without objective reason; for common cashless methods, extra fees are generally impermissible in consumer transactions. Price information must include the final price. Anyone granting discounts on individual payment methods should design them transparently and without discrimination. These are not minor details but typical grounds for warning letters – when in doubt, a brief legal review before going live is worthwhile.
## Testing is part of it
Payment methods are the only area of the shop where an error immediately costs money – either because an order doesn't go through, or because a payment doesn't arrive. A written test concept is therefore mandatory, not optional. It should cover at least the following cases per method: successful payment, abandonment by the customer, rejection by the provider, return from an external payment window, partial refund, full refund, and cancellation before shipping.
Add to this list a test after every major update of the shop system or a payment extension. In practice, payment methods rarely fail with a loud error, but quietly: the status change doesn't happen, orders hang in an intermediate state, and nobody notices until accounting asks two weeks later. Simple monitoring for orders that remain in the "open" payment status longer than a defined period reveals exactly these cases.
## Conclusion
A good payment method mix is not a maximum offering, but a deliberate selection: enough trust for the undecided first-time buyer, enough protection for the merchant, and a checkout that doesn't turn the selection into a mental exercise. Review the mix at least once a year based on real figures – share per method, abandonment rate per method, default rate, full costs. In most shops, this analysis reveals at least one method that no longer contributes anything, and one that is missing.
Comments
No comments yet.
Write a comment