DACH payments in Solidus: Kauf auf Rechnung, SEPA, Klarna, EPS and TWINT

TL;DR

Difficulty: Advanced

German online shoppers pay mostly by PayPal (28.7% of turnover), invoice (26.1%) and direct debit (14.4%), with cards fourth. Austria adds EPS, Switzerland runs on TWINT in francs. In Solidus, filter payment methods by the billing country, use Stripe for cards, SEPA, wallets, EPS and TWINT, and run invoice through a specialist or your own process. Invoice means shipping an unpaid order, so allow shipment for that method only, capture at dispatch and automate reminders. Complete redirect payments on the webhook, test partial refunds on every method, and store a settlement reference for the accountant.

A checkout built for Britain, with cards, Apple Pay and Google Pay, is the wrong checkout for Germany, Austria and Switzerland. In this article I go through which payment methods each of the three countries expects, with the shares from current studies, and how each one is wired into a Solidus store: per country method lists, Stripe for cards, SEPA, wallets, EPS and TWINT, pay on invoice through a specialist or your own process, the change invoice makes to the order flow, reminders under German law, fraud rules, refunds, reconciliation, and a worked example of what the wrong mix costs.

A checkout built for Britain is the wrong checkout for Germany

Picture Harbourside Leather, an invented Bristol shop selling belts, wallets and bags at harboursideleather.example. Its British checkout is cards, Apple Pay and Google Pay, and it works. The owner opens the shop to Germany, Austria and Switzerland with the same checkout and a translated product page, and the German orders do not come.

Nothing is broken. The checkout simply asks German shoppers to pay the way British shoppers pay. In German online retail, cards come fourth. PayPal, buying on invoice and direct debit carry most of the money, Austria has its own bank transfer method, and Switzerland has a different currency and its own payment app.

In an earlier article I covered how German shoppers pay online, and what the law asks of your price. That was the market and the law. This one is the build: which methods each of the three countries expects, and how each one is wired into a Solidus store, including the parts that break the order flow if nobody plans for them. I build on Solidus, so the implementation notes are Solidus specific. The market facts apply whatever platform you run.

Three countries, three different wallets

People lump DACH together as one market with one language. For payments it is three markets that happen to share a language and disagree about almost everything else.

Germany. The EHI Retail Institute asks online retailers for their turnover by payment method. In its 2026 study, PayPal comes first with 28.7% of turnover, buying on invoice (Kauf auf Rechnung) second with 26.1%, direct debit third with 14.4%, and credit and international debit cards fourth with 13.7%.1 A checkout that leads with cards leads with the method that carries the smallest share of the four.

A bar chart of the share of German online retail turnover by payment method in the EHI Online Payment study 2026: PayPal 28.7%, invoice 26.1%, direct debit 14.4%, credit and international debit cards 13.7%. Tap or click to open full screen and move around

Two names you may still find on old plugin lists are gone. Giropay, the German banks' online method, was shut down at the end of 2024.2 Sofort was folded into Klarna and discontinued as a standalone method.3 The banks' new answer is Wero, a wallet on instant SEPA transfers, which opened for online payments in Germany on 18 November 2025, starting with the savings banks and the cooperative banks, with Stripe and Unzer among the payment providers supporting the launch.4 It belongs on the list for later, not at the top of the checkout today.

Austria. The Austrian speciality is EPS, a bank redirect method. Stripe describes it as supported by all Austrian banks and accepted by most Austrian online retailers, and usable by customers in Austria only.5 PayPal, cards, invoice and Klarna are all expected as well. Wero is coming to Austria too: on 22 June 2026 Erste Bank Oesterreich and Raiffeisen Bank International announced they would become shareholders of the European Payments Initiative, the company behind Wero, but no Austrian launch date has been published.6 If you add one thing for Austria that you did not have for Germany, add EPS.

Switzerland. A different country in every sense that matters here. The currency is the franc, Switzerland is outside the EU, and the dominant online method is TWINT, the Swiss banks' payment app. Figures from the Swiss Payment Monitor, published by PostFinance in June 2026, put mobile payment, mainly TWINT, at 37.7% of Swiss online payments by number, credit cards at 26.3%, invoice or bank transfer at 18.0% and debit cards at 9.5%.7 Through Stripe, TWINT is only available to customers in Switzerland, in francs, up to CHF 5,000 per payment, and Stripe requires you to show prices in CHF and offer Switzerland as a shipping destination before it activates the method.8 Switzerland also has its own VAT: a foreign seller whose small consignments into Switzerland reach CHF 100,000 a year must register for Swiss VAT.9 The shipping side is in my shipping and returns article. The payment side is simple: CHF prices, TWINT and an invoice option, or do not bother.

For a UK shop, all three are export markets with customs and import VAT, which I cover in the cross border setup for Germany. None of that stops the payment methods: Stripe accounts in the UK can accept SEPA direct debit, EPS and TWINT.5810

What the checkout should show, and to whom

A checkout that shows every payment method to every customer feels generous. It is a conversion problem and a fraud problem at once.

A German customer scrolling past TWINT and EPS to find Rechnung wonders whether this shop really sells to Germany. A Swiss customer offered SEPA direct debit is offered something built for euro accounts. And a fraudster likes nothing better than a shop that offers pay on invoice to an address in a country where the shop has no collections process.

Out of the box, Solidus decides which payment methods a checkout offers by store, by an active flag and by whether the method is available to customers, and sorts them by one global position.11 It does not filter by country. So I add one small rule to that list: look up the zone of the billing address the customer just entered (zones are the sets of countries Solidus already uses for tax and shipping) and return only the methods allowed for that zone, in that zone's order. The other route is a separate Solidus store per country, which also gives each country its own domain and currency. The setup I start from for a DACH store:

ZoneMethods, in this order on the page
GermanyPayPal, invoice, SEPA direct debit, cards and wallets, Klarna
AustriaEPS, PayPal, cards and wallets, invoice, Klarna
SwitzerlandTWINT, cards, invoice, PayPal (prices from a CHF price list)
Rest of the EUCards, PayPal, plus the local favourite if you add one
UK and rest of worldCards, Apple Pay, Google Pay, PayPal

The order is not decoration. Most customers pick the first method they recognise. Put the trusted local one first and the checkout gets faster.

Solidus lets you go further than zones. You can hide a method below or above a basket value, hide invoice from a customer with an unpaid order on file, show instalments only above a threshold, or show business customers a different set. Each of those is a few more lines in the same rule. The framework treats "which methods does this customer see" as your decision, so make it deliberately.

Cards, SEPA and wallets: Stripe as the rail

For cards, SEPA direct debit, Apple Pay, Google Pay, EPS and TWINT, I use Stripe through solidus_stripe, the extension maintained in the Solidus organisation on GitHub. It uses Stripe's payment intents and the Payment Element, handles the extra authentication step before the order is finalised, can save payment methods for returning customers, and receives Stripe's webhooks.12 Four things matter in a DACH context.

SEPA direct debit is slow and reversible. Stripe tells you to wait at least six business days before you treat a SEPA debit as successful, because the customer's bank can still reject it.10 After that, the customer can ask their bank for a refund without giving a reason for eight weeks from the debit, and for up to 13 months if the debit was not authorised.10 In German law those are BGB § 675x and § 676b Abs. 2,1314 and the scheme rules are in the SEPA Direct Debit Core rulebook.15 Your Solidus order has to respect that: do not ship on a debit that has not settled unless you have decided to extend credit. For a 30 euro belt that is usually fine. For a 900 euro bag it is a decision.

The creditor identifier. Every SEPA debit carries a creditor identifier. By default Stripe uses its own, and Stripe recommends that businesses based in the EU use their own to lower dispute rates.10 A UK shop can start on Stripe's.

Wallets need the domain registered. Apple Pay and Google Pay in the Payment Element only appear once your domain is registered with Stripe.16 Missing wallets fail silently, so the registration belongs on the launch checklist.

SCA is not optional. Under the second Payment Services Directive (PSD2), a customer's bank in the EU must apply strong customer authentication when the customer pays online, unless an exemption applies.1718 The checkout has to send the customer to that authentication step and bring them back without losing the order. solidus_stripe shows it before the final confirmation.12 A hand rolled integration often does not, and the failure is an order stuck half paid that nobody notices until the customer complains.

Kauf auf Rechnung: the one you cannot skip

Pay on invoice means the customer places the order, you ship it, the parcel arrives with an invoice, and the customer pays within the stated term, typically 14 days, by bank transfer. For the customer it is ideal: no card details, inspect the goods first. For the shop it means shipping goods to a stranger on the promise of a bank transfer.

There are two ways to run it, and you pick one before you touch the code.

Run it yourself. You carry the risk, issue the invoice and chase the payment. Shops that do this usually add a credit check at the checkout and limits on basket size and delivery address. It costs nothing in provider fees and a lot in operations: someone reconciles the bank account against open orders, sends reminders and hands the stubborn ones to a collections agency. Some invoices will be late, a few will never be paid, and that loss is the real cost of the method.

Hand it to a specialist. Klarna, Unzer, Mollie's partners and others run the credit check in the background, approve or decline in the checkout, and pay you whether or not the customer pays them. The fees are higher than for cards. In exchange you never chase anyone and your cash flow looks like card cash flow.

Which one costs less is a sum, not a feeling. The expected loss on self run invoice is the number of invoice orders times the share that is never paid times the basket (expected value):

L=n×p×bL = n \times p \times b

where LL is the expected monthly loss, nn the number of invoice orders a month, pp the share of invoices never paid, and bb the average basket.

A specialist's cost is a percentage of each basket plus a fixed fee per order (percentages):

F=n×(f×b+k)F = n \times (f \times b + k)

where FF is the monthly provider cost, ff the percentage fee, and kk the fixed fee per transaction.

A worked example with invented numbers you should replace with your own: Harbourside Leather expects 300 invoice orders a month from Germany at 80 euros each. If 2% are never paid, L=300×0.02×80=480L = 300 \times 0.02 \times 80 = 480, which is 480 euros a month, before the cost of the person who does the reconciling and chasing. If a provider quoted 3% plus 0.35 euros per order, F=300×(0.03×80+0.35)=825F = 300 \times (0.03 \times 80 + 0.35) = 825, which is 825 euros a month with no chasing at all. On these numbers the specialist costs 345 euros more a month and buys back the operations work and the cash flow. If the default rate were 4%, the loss would be 960 euros and the specialist would be the lower cost outright. Run the sum with your own contract and your own default history before you decide.

For business customers the picture changes. You know them, the baskets are large, and a consumer risk engine will decline exactly the orders you want. Klarna's pay later products are for consumers, so for business customers you run invoice yourself, on account, with your own credit limits.

In Solidus the specialist route is a payment method that talks to the provider's API during checkout, gets an approval, and creates a payment that is captured at shipment. The self run route is a payment method with no gateway at all, which Solidus ships as the check payment method,19 plus your own logic on top: the credit check, the limits, the invoice document and the reminder schedule.

What pay on invoice does to your order flow

Solidus orders move through a checkout flow of address, delivery, payment and confirm before they complete. Payments have their own states: checkout, pending, processing, completed, failed, void and invalid.20 Shipments wait as pending until they are ready, then are shipped. By default a shipment only becomes ready once the order is paid, controlled by the require_payment_to_ship setting, and Solidus does not capture card payments automatically unless you switch on auto_capture.21 That default suits cards: authorise at checkout, capture when you ship.

Invoice breaks it in one specific way. The order is complete and the parcel must ship while nothing has been paid. You ship an unpaid order by design.

Tap or click to open full screen and move around

The way I handle it:

Auto capture is off for the invoice method, and its payment goes to pending at checkout. Nothing is owed yet.

Shipments may become ready when the order's payment is a pending invoice payment. require_payment_to_ship is a single setting for the whole store,21 so switching it off would let unpaid card orders ship too. The fix is a small override of the shipment readiness check that makes the exception for the invoice method only. It is the single most important piece of code in the integration: wrong one way and invoice orders never ship, wrong the other way and unpaid card orders do.

Capture happens at shipment. When the warehouse marks the parcel shipped, the invoice payment is captured. For a specialist that means "we shipped, start the clock". For self run invoice it means "create the invoice with today's date, attach it to the order, send it and set a due date".

Settlement is a separate event. For a specialist the payment completes when the provider confirms it will pay you. For self run invoice the payment stays open until a bank transfer arrives and is matched to the order. I model that as a custom state and a daily job that reads the bank feed and matches on the invoice number printed on the invoice.

Reminders are a scheduled job, not a person. Under German law a consumer is in default 30 days after the due date and receipt of the invoice, but only if the invoice points this out.22 From default, interest runs at 5 percentage points above the base rate for consumers, and the flat 40 euro fee applies to business customers only.23 So the schedule is roughly: a friendly reminder a few days after the due date, a second one a week later, a formal Mahnung once the customer is in default, then collections, with the account flagged so invoice never shows again. Every step is logged on the order. It is a background worker with a schedule, tested with time travel in the specs.

Returns on unpaid invoices reduce the invoice, they do not refund. If the customer sends half the order back before paying, you issue a credit note and the amount due drops. If they have already paid, you refund by bank transfer, which needs their IBAN, which means your return form asks for it. Card refunds go back to the card on their own. Invoice refunds go nowhere on their own.

Klarna, Unzer, Mollie: picking the specialist

Three providers cover most of what DACH shops ask for, and they differ in how much Solidus code already exists.

Klarna is the consumer brand German shoppers know, with invoice, instalments and pay now in one widget, and it now also carries what used to be Sofort.3 There is a Solidus extension, solidus_klarna_payments, in the Solidus community organisation on GitHub.24 Check its recent commits against your Solidus version before you rely on it.

Unzer, formerly Heidelpay, is the German specialist with invoice, instalments, direct debit and cards under one contract. Its older invoice product, Flexipay, the former Heidelpay invoice purchase, stopped taking new transactions on 31 May 2026 and was fully discontinued on 1 November 2026, with merchants moved to Unzer's newer pay later platform.25 If an old integration still points at it, it is time to rebuild. There is no maintained Solidus extension for Unzer, so this is a bespoke payment method.

Mollie is the Dutch aggregator that bundles EPS, TWINT, iDEAL, Bancontact, SEPA direct debit, cards, PayPal, Klarna, Billie and others behind one API and one settlement.26 For a shop selling across the EU and Switzerland at modest volume, Mollie is a sensible second rail next to Stripe. The Solidus gems for Mollie on GitHub are community projects of varying age, so I treat it as a bespoke payment method too.

PayPal has its own Solidus extension, solidus_paypal_commerce_platform, maintained in the Solidus organisation.27

Whichever you pick, read the contract for two things: the approval rate the provider will commit to, and what happens to a disputed order. Then wire it in as one Solidus payment method class per provider, with the provider's SDK behind an adapter, so that a later switch is configuration and not a rewrite. Bespoke Solidus code I write for this becomes yours on full payment, so the adapter stays with the shop if the provider changes. Before you ever switch, read the hidden dangers of switching payment gateways.

EPS for Austria, TWINT for Switzerland

Both are bank driven redirect methods, and both are handled the same way in Solidus. The customer picks the method, is sent to their bank or the TWINT app, approves there, and comes back with a success or failure. Stripe reports the result of both immediately.58

The Solidus side is a payment method that creates the payment in processing, stores the reference, sends the customer away, and completes or fails the payment when the webhook arrives. The order should not complete on the redirect back. A customer who closes the bank tab and reopens your site would otherwise get an order confirmation for a payment that never happened. The webhook is the truth. The redirect is a hint.

For TWINT, Stripe is now enough for most shops, including UK ones, as long as prices show in francs.8 A shop with serious Swiss volume may still prefer a Swiss acquirer that settles in francs into a Swiss account, which avoids converting every payment back.

One Swiss detail: prices. Your CHF price list should carry prices that already look Swiss, 49.90 or 50.00, not 49.37 from a conversion. In Solidus that is a separate price per variant in the CHF currency, which is how it should be anyway.

Fraud and risk, per method

Every method fails in its own way, and the risk rules should match.

Cards. Stolen card numbers. Stripe Radar catches much of it, strong customer authentication more, and the rest arrives as chargebacks. Useful rules: block mismatched billing and shipping countries above a basket value, and flag orders from a mail domain registered last week.

PayPal. Account takeovers and "item not received" claims. Ship with tracking and keep the tracking number on the order.

SEPA direct debit. The eight week refund right.10 Limit it to returning customers or to baskets you can afford to lose, or accept the risk consciously.

Invoice. The big one. Someone orders to a parcel shop under a name that matches nobody, and never pays. If a specialist carries the risk, you accept their declines. If you carry it, you need address checks, a credit check, no parcel shops or forwarding addresses for invoice orders, a basket limit for first orders, and a check that notices the same address ordering five times in a day. All of it lives in that same rule plus a call before the order completes, and all of it is logged, so you can see why an order was declined when the customer phones.

TWINT and EPS. Very low fraud, because the customer authenticated at their bank, and EPS payments cannot be disputed through the bank at all.5 The risk is operational: a webhook that never arrives. Monitor for payments stuck in processing for more than an hour.

Refunds, partial refunds and the returns nobody planned for

Refunds are where payment integrations hide most of their bugs, because nobody tests them until a customer wants one.

Solidus has a proper refund model: a refund belongs to a payment, has an amount and a reason, and calls the gateway to move the money. The specialist providers vary. Some support partial refunds through their API, some need a credit note. Find out before launch.

The DACH wrinkle is that partial returns are common. A customer orders two sizes, keeps one and sends one back. On a card or PayPal that is a partial refund against the original payment. On invoice it is a credit note if unpaid, a bank transfer if paid. On SEPA, Stripe recommends refunding only after the original payment has settled, and warns that a customer who also disputes with the bank can end up credited twice.10 On EPS the refund arrives as a separate bank credit, not a reversal.5 On TWINT it goes back to the app or its funding source.8 Every one of those is a different code path, and every one needs a test.

I build the return flow so that the refund route is chosen by the payment method, not by the person processing the return. The warehouse marks items received, the system works out what is owed, and the right refund happens on the right rail. The only manual step is the IBAN when the original payment cannot receive a refund, and the return form collects that.

Reconciliation, or keeping your accountant on side

A shop with five payment methods has five settlement streams arriving on five schedules with five fee structures, and an accountant who needs to match every line to an invoice.

Stripe pays out in batches with a report of every payment and fee. PayPal holds a balance. Klarna, Unzer and Mollie settle net of fees on their own cycles with a settlement file. A Swiss acquirer settles in francs. Self run invoice payments arrive one transfer at a time with whatever reference the customer typed.

What the accountant needs from Solidus is an export per period with every order, the payment method, the gross amount, the fee, the net amount and the settlement batch. In Solidus that is a reporting query over payments, plus a settlement reference stored per payment from the provider's webhooks or settlement files. It is the difference between month end taking an afternoon and taking a week.

For self run invoice, reconciliation runs the other way: incoming transfers matched to open invoices. A daily import of the bank feed matches on the invoice number in the reference, then on amount and customer name for the creative references, and leaves a short queue of unmatched transfers for a human.

Saved payment methods and the returning customer

A returning customer should not have to type anything. solidus_stripe can save a card or a SEPA mandate against the customer and offer it on the next order.12 Stripe expects you to get the customer's permission before you save a payment method for later use.28 I put that behind an unticked box, and give the customer a way to delete saved methods from their account page. Invoice needs nothing saved, but your risk rules can relax for a customer with three paid invoices behind them, which is one query on their order history at checkout.

What the wrong mix costs

Put a number on Harbourside Leather's empty German checkout, because "conversion problem" does not get a budget approved. Revenue from a checkout is visitors times conversion rate times basket (ratios and rates):

R=V×c×bR = V \times c \times b

where RR is monthly checkout revenue, VV the visitors who reach the checkout, cc the share of them who complete an order, and bb the average basket.

Assume, purely for illustration, 10,000 German visitors a month reach the checkout with an 80 euro basket. With cards and PayPal only, say 2.0% complete: R=10000×0.020×80=16000R = 10000 \times 0.020 \times 80 = 16000 euros a month. If adding invoice and direct debit in front of cards lifts completion to 2.8%, then R=10000×0.028×80=22400R = 10000 \times 0.028 \times 80 = 22400 euros a month.

That is 6,400 euros a month more from the same traffic. These conversion rates are assumptions, not measurements. The point of the sum is the break even: with 10,000 visitors and an 80 euro basket, every tenth of a percentage point of conversion is 800 euros a month, and the extra fees on the invoice orders are a small share of that. Measure your own before and after, per country.

The same sum applies to Switzerland with TWINT and to Austria with EPS. The markets are smaller, so the euros are smaller. The logic is the same.

The launch checklist

  1. Payment methods filtered by the billing address's zone, so each customer sees only what fits their country.
  2. The local method first in each zone: PayPal or invoice for Germany, EPS for Austria, TWINT for Switzerland.
  3. A CHF price list for Switzerland with Swiss looking prices.
  4. Invoice method with shipment allowed on a pending invoice payment only, capture at shipment, a reminder schedule that runs itself, and IBAN collection in the return form.
  5. Your domain registered with Stripe, so Apple Pay and Google Pay actually appear.
  6. The authentication redirect and return tested with Stripe's test cards.
  7. Every redirect method completing the order on the webhook, never on the redirect.
  8. A partial refund tested on every method, including SEPA before and after settlement.
  9. A settlement reference stored per payment and an export your accountant has approved.
  10. Fraud rules per method, logged, with a way to see why an order was declined.
  11. Saved payment methods behind an unticked box, deletable from the account page.
  12. An alert for payments stuck in processing for more than an hour.
  13. No giropay, no standalone Sofort module, no Heidelpay Flexipay left in the code.

Where this fits

Payments are one part of selling into DACH, and the part with the fastest payoff. Get the mix right and the checkout converts. Get the order flow right and invoice orders ship, get paid and reconcile without a person in the loop. Get the fraud rules right and the invoice orders that ship are the ones that get paid.

If you are still choosing a platform, I compared the options in Solidus versus Shopify, Shopware, Magento and WooCommerce for a DACH SME. On Solidus, everything in this article is a handful of tested Ruby classes in your own code base, and the bespoke code becomes yours on full payment. If you want a second pair of eyes on your DACH checkout, I run a free workshop, and the first two weeks of work are on me.

If your checkout is losing German, Austrian or Swiss customers at the payment step, or you are planning a Solidus build and want the payment methods right the first time, I run a free workshop and the first two weeks of work are on me. Bring the checkout, I will bring the list of methods your markets actually expect.

Sources

  1. 1.

    EHI Retail Institute, Smartphone statt Portemonnaie: Mobile Payment boomt, press release on the study Online Payment 2026, EHI, 5 May 2026, https://www.ehi.org/presse/smartphone-statt-portemonnaie-mobile-payment-boomt/

  2. 2.

    heise online, Giropay goes, Wero comes, heise, 14 June 2024, https://www.heise.de/en/news/Giropay-goes-Wero-comes-9764396.html

  3. 3.

    Stripe, SOFORT is being consolidated into Klarna and discontinued as a standalone payment method, Stripe Support, 2026, https://support.stripe.com/questions/sofort-is-being-consolidated-into-klarna-and-discontinued-as-a-standalone-payment-method

  4. 4.

    IT Finanzmagazin, EPI startet Wero im deutschen Onlinehandel und gewinnt erste große Händler, 18 November 2025, https://www.it-finanzmagazin.de/epi-startet-wero-im-deutschen-onlinehandel-und-gewinnt-erste-grosse-haendler-236442/

  5. 5.

    Stripe, EPS payments (eligibility, customer location, refunds, disputes), Stripe documentation, 2026, https://docs.stripe.com/payments/eps

  6. 6.

    Raiffeisen Bank International, press release on Erste Bank Oesterreich and RBI joining EPI as shareholders, 22 June 2026, https://www.rbinternational.com/en/raiffeisen/media-hub/press-releases/2026/epi.html

  7. 7.

    PostFinance, What payment methods should a Swiss online shop offer?, PostFinance developer blog, 15 June 2026, citing the Swiss Payment Monitor (University of St. Gallen and ZHAW), https://developer.postfinance.ch/en/blog/business-blog/key-payment-methods.html

  8. 8.

    Stripe, TWINT payments (eligibility, customer location, limits, refunds), Stripe documentation, 2026, https://docs.stripe.com/payments/twint

  9. 9.

    Swiss Federal Tax Administration, VAT registration for mail order companies, ESTV, 2026, https://www.estv.admin.ch/en/vat-registration-for-mail-order-companies

  10. 10.

    Stripe, SEPA Direct Debit payments (business locations, timing, failed payments, disputes, refunds, creditor identifiers), Stripe documentation, 2026, https://docs.stripe.com/payments/sepa-debit

  11. 11.

    Solidus, core/app/models/spree/order.rb (available_payment_methods), solidusio/solidus on GitHub, 2026, https://github.com/solidusio/solidus/blob/main/core/app/models/spree/order.rb

  12. 12.

    Solidus, solidus_stripe README, solidusio/solidus_stripe on GitHub, 2026, https://github.com/solidusio/solidus_stripe

  13. 13.

    Bürgerliches Gesetzbuch (BGB), § 675x Absätze 1, 2 und 4, Bundesministerium der Justiz, gesetze im internet, 2026, https://www.gesetze-im-internet.de/bgb/__675x.html

  14. 14.

    Bürgerliches Gesetzbuch (BGB), § 676b Absatz 2, Bundesministerium der Justiz, gesetze im internet, 2026, https://www.gesetze-im-internet.de/bgb/__676b.html

  15. 15.

    European Payments Council, SEPA Direct Debit Core Scheme Rulebook, EPC016-06, 2025 version 1.2, sections 4.3 and 4.8, EPC, 2026, https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2026-09/EPC016-06%202025%20SDD%20Core%20Rulebook%20version%201.2.pdf

  16. 16.

    Stripe, Register domains for payment methods, Stripe documentation, 2026, https://docs.stripe.com/payments/payment-methods/pmd-registration

  17. 17.

    European Parliament and Council, Directive (EU) 2015/2366 on payment services in the internal market (PSD2), Article 97, EUR-Lex, 2015, https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32015L2366

  18. 18.

    European Commission, Commission Delegated Regulation (EU) 2018/389, regulatory technical standards for strong customer authentication, EUR-Lex, 2018, https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32018R0389

  19. 19.

    Solidus, core/app/models/spree/payment_method/check.rb, solidusio/solidus on GitHub, 2026, https://github.com/solidusio/solidus/blob/main/core/app/models/spree/payment_method/check.rb

  20. 20.

    Solidus, core/app/models/spree/core/state_machines/payment.rb, solidusio/solidus on GitHub, 2026, https://github.com/solidusio/solidus/blob/main/core/app/models/spree/core/state_machines/payment.rb

  21. 21.

    Solidus, core/lib/spree/app_configuration.rb (preferences auto_capture and require_payment_to_ship), solidusio/solidus on GitHub, 2026, https://github.com/solidusio/solidus/blob/main/core/lib/spree/app_configuration.rb

  22. 22.

    Bürgerliches Gesetzbuch (BGB), § 286 Absatz 3, Bundesministerium der Justiz, gesetze im internet, 2026, https://www.gesetze-im-internet.de/bgb/__286.html

  23. 23.

    Bürgerliches Gesetzbuch (BGB), § 288 Absätze 1 und 5, Bundesministerium der Justiz, gesetze im internet, 2026, https://www.gesetze-im-internet.de/bgb/__288.html

  24. 24.

    Solidus community, solidus_klarna_payments, solidusio-contrib on GitHub, 2026, https://github.com/solidusio-contrib/solidus_klarna_payments

  25. 25.

    Unzer, Transition of Invoice Purchase (Heidelpay Invoice Purchase), Unzer help centre, 2026, https://help.unzer.com/en/support/solutions/articles/79000149747-transition-of-invoice-purchase-heidelpay-invoice-purchase-

  26. 26.

    Mollie, Payment methods, Mollie documentation, 2026, https://docs.mollie.com/docs/payment-methods

  27. 27.

    Solidus, solidus_paypal_commerce_platform, solidusio on GitHub, 2026, https://github.com/solidusio/solidus_paypal_commerce_platform

  28. 28.

    Stripe, Save payment details during payment, Stripe documentation, 2026, https://docs.stripe.com/payments/save-during-payment