Skip to content
GatewayChanger

Marketplaces · Franchises · Groups

Three shapes of network. One checkout each.

One storefront. Several legal entities. A rule decides which one charges — and the money never leaves the entity that earned it.

Start in the free sandbox See how it works
  • Money goes shop to shop. Never through us.
  • No card numbers reach our servers. Ever.
  • Every entity keeps its own processor and its own books.

Who this is for

Built for networks, not for one big shop.

Marketplace payments without becoming the merchant of record — and the same mechanism for franchise networks and cross-border groups. Pick the shape that looks like yours.

Multi-vendor marketplaces

Each vendor charges under their own name.

  • You invoice commission, not payouts.
  • No wallet, no KYC queue, no float.
  • One order goes to one charging shop.

Werkhalle

Franchise networks

One national shop. Each location charges its own customers.

  • Route by delivery postcode or country.
  • Every location keeps its own merchant account.
  • The brand fee comes out of the settlement report.

Kaffeekern

Multi-entity and cross-border groups

French orders charge on the French entity.

  • Route by billing country.
  • Each entity charges through its own local acquirer.
  • If one entity is unreachable, the next takes the order.

Lumenta

Multi-vendor marketplace Werkhalle

How Werkhalle pays 112 workshops without touching a cent.

Illustrative example. Werkhalle is not a real company.

A furniture marketplace with 112 independent workshops.

  1. The problem.

    Werkhalle sells handmade furniture from 112 independent workshops in 9 countries. Every euro lands in Werkhalle's own account.

  2. What that costs.

    Refunds, chargebacks and VAT questions all arrive at Werkhalle first. Two people spend month-end paying 112 workshops out by hand.

  3. The setup.

    Each workshop installs the plugin on its own shop and connects its own Stripe. Werkhalle writes four routing rules in the dashboard.

  4. An order arrives.

    A customer in Lyon buys a €2,480 oak table from Atelier Brun in Nantes. She checks out on werkhalle.eu, exactly as before.

  5. The rule that fires.

    Rule 2: items from a workshop with a live shop → that workshop charges. The signed answer comes back before the payment form renders.

  6. Who charges.

    The card form inside Werkhalle's checkout is served by Atelier Brun. The €2,480 settles into Atelier Brun's French account.

  7. What each party gets.

    Werkhalle invoices its 11% commission from one settlement report. Atelier Brun owns the refund, the VAT invoice and any chargeback.

What the customer ticks at checkout

“I agree that my payment of €2,480.00 is processed by Atelier Brun SARL on behalf of Werkhalle GmbH.”

consent · version 2026-09-16 · required checkbox · hash, timestamp and IP stored on both orders

Franchise network Kaffeekern

One national webshop. Each location charges its own customers.

Illustrative example. Kaffeekern is not a real company.

38 coffee shops in Germany and Austria.

  1. One national webshop for beans and subscriptions; each location is its own GmbH with its own Stripe.

  2. Rule: delivery postcode → nearest location charges. A €54.90 subscription from 80331 München charges on the München franchisee.

  3. The franchisor invoices a 6% brand fee from the settlement report. No money parks in the franchisor’s account, no payout run, no franchisee waiting 14 days.

Cross-border EU group Lumenta

French orders charge on the French entity.

Illustrative example. Lumenta is not a real company.

One storefront, three legal entities.

  1. Rules by billing country: FR/BE/LU → the Paris entity, DE/AT → the Berlin entity, everything else → the Amsterdam entity.

  2. Each entity charges through its own local acquirer, so the payment is domestic rather than cross-border.

  3. If the Berlin shop is unreachable, the order routes to the next candidate. A card decline never fails over — that would just try a dead card twice.

Qualify yourself

Who this is for — and who it is not.

We would rather you leave on this section than in month three. Here is the whole of both lists.

This is for you if…

  • You run one storefront and several legal entities — vendors, franchisees, group companies, workshops, partner shops.
  • Each of those entities already has, or wants, its own payment processor.
  • You do not want to be the merchant of record for other people’s sales.
  • You want commission invoiced, not payouts administered.
  • You want to route by amount, currency, country, items, caps and availability — and read the rules out loud to your CFO.
  • You can tell your acquirer or PSP what each shop processes, and for whom.
  • You are on a self-hosted platform, where a shop can serve its own card form.

Store plugins

Plugins marked “In build” are published here only once a real test store has routed a real order end to end.

This is not for you if…

Seven ways to be a bad fit, and what fits instead.

  1. You are one shop with one entity, chasing higher approval rates across many PSPs.

    That is classic payment orchestration. Spreedly, Primer, Gr4vy or Corefy fit that job better than we do.

  2. You want a platform to hold the funds, run KYC and pay your vendors out.

    That is Stripe Connect, Adyen for Platforms, Mangopay or Mollie Connect. We hold no money and run no payouts.

  3. Your vendors must not be visible to the customer, or you need your own name on every statement.

    The charging entity is named at checkout, on the receipt and on the descriptor. That is the whole model.

  4. You are on a closed, hosted platform.

    Self-hosted platforms only, for now — the charging shop has to be able to serve its own payment page.

  5. You need a PCI attestation of compliance from your vendor today, or a signed enterprise SLA.

    We hold no PCI certification and we have no SLA to sign. We say so on the compliance page rather than pretend.

  6. You want one checkout with a single card charge split across several vendors.

    We route an order to one charging shop. We do not split one authorisation.

  7. Your model depends on processing for entities whose acquirers are not told what is happening.

    Not a fit, and we will say no. Disclosure to the acquirer is something each charging shop attests to.

Where we stand on certification, liability and disclosure is written out on the compliance page.

Route your first test order today.

Free sandbox. No card, no call, no expiry.

Start in the free sandbox Read the docs
  1. 1

    Create an organization. Register two shops.

  2. 2

    Install the plugin. Paste the shop key.

  3. 3

    Write one rule and check out.

  4. 4

    Watch a decision, a signature and a ledger entry appear.