Mollie Connect with Shopware 6

[near valve]

Hi! We're building a B2B marketplace on Shopware 6 where a single cart can contain products from multiple dealers. After checkout, we split the order into per-dealer orders.

We want to use Mollie Connect (Marketplace model) to split the payment so each dealer receives their share automatically.

Our planned approach:

• Each dealer has their own Mollie connected account (onboarded via OAuth / Client Links API)
• We use the Mollie Shopware 6 plugin for payment processing
• After checkout, we split the order into per-dealer orders and want to route the corresponding payment amounts to each dealer

This follows the split payments approach from the docs:
https://docs.mollie.com/docs/connect-marketplaces-processing-payments
https://docs.mollie.com/docs/connect-marketplaces-split-payments-with-delayed-routing

Questions:

1. Does the Mollie Shopware 6 plugin expose any event or extension point to add a routing array to the payment creation call? Or should we call the Mollie API directly for the routing part?

2. For our use case (multi-dealer cart, amounts known at checkout time), would you recommend upfront or delayed routing?

3. Are there any known limitations with split payments + the Shopware 6 plugin we should be aware of?

4. How should refunds be handled for split payments? Since the original payment is split across multiple dealers, would we need to manage routingReversals manually per dealer, or does the Shopware plugin handle this when a refund is triggered on a per-dealer order?

Thanks!

[near valve]

Follow-up question: since delayed routing seems to be the only viable approach in Shopware (the plugin doesn't support injecting routing at payment creation), the payment would first land in our Mollie account before being routed to the dealers. Our agency raised the concern that this might require a banking license on our side. Is that the case, or does Mollie Connect cover the regulatory side?

[lofty vale]

Hi, thanks for your patience. Let me ping @dull heron to look into this 🙏

[dull heron]

Hi @near valve the Shopware plugin is mainly built for traditional single-merchant use cases, so you'll have to make use of delayed routing here. Based on the info you gave, I'd suggest letting the plugin only handle the payment and offloading all other backend processes to a custom plugin or marketplace backend. As for the legal implications I have pinged our solution management team - the colleagues can give you more insights into the implications of the various marketplace use cases.

[near valve]

Hey Hannes, thanks for your reply. That was our though aswell, the only troubling part I haven't solved yet is how the refunds would work in my custom plugin. We are still in the early stages and might actually pivot to a more customizeable Framework instead of fighting the traditional B2C nature of Shopware. We were thinking of MedusaJS + MercurJS for the Marketplace. Do you have any expirience or are you aware of the limits of this potential stack? Also for the legal question, we are from Germany if that helps 🙂 . Thanks

[inner swallow]

hi @near valve , I think Hannes's advise to keep the payment itself as-is and handle the routes afterwards further downstream (with Delayed Routing) makes sense. For refunds you have 2 options:

• Submit refunds with routingReversals for the clawback of the dealers (so a debit on their balance, making up for the refund that is initially funded with yours). But that's not supported in the Shopware plugin, so it would require a customzation.
• Submit the refunds as-is and periodically (daily / weekly) carry out the debits on the dealers using Balance Transfers. This could be handled completely outside Shopware (would have to be implemented), so you can rely on the supported regular refund flow in Shopware itself. See https://docs.mollie.com/reference/create-connect-balance-transfer