Published:
Last updated (content):
Last updated (prices):

Swiss umbrella organizations can provide their sections with a central payment platform through which each section independently collects membership fees, event tickets, and course fees – with their own branding and their own payout to the section's bank account. The organization maintains an overview via an aggregated Dashboard and can automatically deduct an association share (e.g. license fee or umbrella organization contribution) per transaction via split payments before the rest flows to the section.
This guide explains how such a platform solution works, what architectural variants exist, and shows three concrete scenarios for Swiss associations.
1. The Problem: Why decentralized payment solutions slow down associations
In many Swiss associations, each section has its own payment solution – or none at all. The gymnastics club in Zug uses PostFinance E-Finance and QR bills, the section in Bern works with club software, and the section in Lausanne collects in cash. The umbrella organization has no overview of the payment flows, cannot provide aggregated figures for the delegates' meeting, and has no way to automatically collect the association share.
This scenario leads to three concrete problems. First: The association must manually request and track the contribution of each section – with 40–500 sections, this is a significant administrative effort. Second: The sections offer their members an inconsistent payment experience – some accept TWINT, others only bank transfers. Third: For continuing education offers, licenses, or events offered centrally by the association, there is no uniform processing.
2. The Solution: Central platform with decentralized accounts
An association platform is a central payment infrastructure through which all sections of an association process payments – without the association itself receiving the payments. Each section has its own sub-account (sub-merchant account) with its own branding, its own products, and its own payout to the section's IBAN.
The association acts as the platform operator and handles the onboarding of the sections. In the background, payment processing runs via a Payment Service Provider (PSP) that, as a technical partner, covers the regulatory requirements (KYC check, Anti-Money Laundering Act) for each section. The association itself usually does not need its own financial market license because it does not act as a payment intermediary – the funds flow directly from the payer via the PSP to the section.
2.1 Split Payment: Automatically deduct association share
Split Payment means that an incoming payment is automatically divided into two or more parts. For associations, this is the crucial mechanism: With each transaction of a section, a predefined share (e.g. 5% or a fixed amount of CHF 2) is transferred to the association, and the rest goes to the section. Thus, the association does not have to request its contribution separately – it is automatically deducted with every payment.
Example: A member of the Bern section pays their annual fee of CHF 120 via TWINT. The PSP automatically deducts CHF 6 (5%) as the association share and transfers CHF 114 minus transaction fees to the IBAN of the Bern section. The association share is collected and periodically paid out to the umbrella organization. No manual effort, no invoices, no chasing up.
2.2 Reporting: Two levels, one dashboard
A platform solution typically offers two reporting levels. The association sees aggregated figures: total transaction volume of all sections, association shares, number of active sections, top sections by turnover. Each section sees exclusively its own transactions: incoming payments, payouts, outstanding items. The sections have no insight into the data of other sections.
3. Architectural Variants: Which model fits your association?
Depending on the size of the association, technical know-how, and budget, three architectural variants are possible.
Criterion | Model A: Manual referral | Model B: Platform Solution (PSP) | Model C: White-Label Payment |
Principle | The association forwards sections to a PSP; each section opens its own account | The association operates a central platform and onboards sections via API or Dashboard | The association offers a payment solution under its own brand (White-Label PSP) |
Section Onboarding | Each section independently | The association onboards centrally (incl. KYC) | The association onboards centrally |
Split Payment | No (manual collection of association share) | Yes (automatic per transaction) | Yes (automatic, full control) |
Branding per Section | Yes (own account) | Yes (sub-merchant with own logo) | Optional (White-Label = association brand) |
Aggregated Reporting | No | Yes (association Dashboard) | Yes (full control) |
Technical Effort | None | Low–Medium (Dashboard or API) | High (API integration, own frontend) |
Association Costs | CHF 0 (sections pay themselves) | Platform fee or revenue share | License fee + integration costs |
Ideal for | Small associations (5–20 sections) | Medium–large associations (20–500 sections) | Large associations with their own tech team |
Most Swiss associations fare best with Model B: A platform solution via a PSP that handles onboarding, KYC checks, and payment processing. The association configures the platform, onboards the sections, and defines the split-payment rules. Providers offering platform solutions in Switzerland include Payrexx, Stripe Connect, and wallee.
4. Three Scenarios: How Swiss associations use the platform solution
4.1 Cantonal sports association with 40 local clubs
A cantonal gymnastics association has 40 local clubs with a total of 6,000 members. Each local club collects its own annual fee (CHF 80–150 per member). The association charges a license share of CHF 5 per member. Previously, each local club had to transfer the license share separately to the association – 20% forgot it, 10% paid late.
With the platform solution: The association sets up a sub-merchant account for each local club. When a member of TV Aarau pays their contribution of CHF 120 via TWINT, CHF 5 automatically goes to the association, and CHF 115 (minus transaction fee) goes to TV Aarau. The association sees in real-time which local clubs have billed how many members.
4.2 Professional association with continuing education offers
A professional association offers central continuing education courses (CHF 350–800 per course) and has 12 regional sections that host their own networking events (CHF 25–50 per event). Through the platform, the association sells the courses centrally, while each section processes its events through its own sub-merchant account. The association has an overview of all bookings – central and regional – in one Dashboard.
4.3 Music association with regional sections
A Swiss music association with 80 regional sections (brass bands, choirs, orchestras) wants to offer sections a uniform solution for ticket sales at concerts. Each section gets its own sales page with its club logo and color scheme. Tickets are sold via the section's mini webshop, and the revenues flow directly to the section account. The association receives a fixed amount of CHF 0.50 per ticket sold as a contribution to platform financing.
5. Regulatory Aspects: Does the association need to have a license?
When an association processes payments via a platform, the question arises whether it qualifies as a financial intermediary under the Anti-Money Laundering Act (AMLA) or as a payment transmitter under the Banking Act (BA). The short answer: Usually not, provided the association uses a licensed PSP as its technical partner and the funds do not flow through the association's own account.
The crucial distinction: As long as the PSP forwards the payments directly from the payer to the section (with an automatic split for the association share), the association does not receive customer funds and does not engage in payment services. The regulatory responsibility (KYC, AMLA compliance) lies with the PSP. The association merely acts as an intermediary connecting its sections to the PSP.
Important: If, on the other hand, the association receives the payments itself, collects them in its own account, and then forwards them to the sections, it may qualify as a financial intermediary and will need to join an SRO (self-regulatory organization) or even obtain a Fintech license under Art. 1b of the Banking Act. This model is not recommended for associations. The platform solution via a licensed PSP avoids this problem.
Note: This section does not replace legal advice. Regulatory requirements depend on the specific business model. In case of doubt, consult a lawyer specializing in financial market law.
6. Costs: What an association platform costs
The costs for a platform solution depend on the model, the number of sections, and the transaction volume. The following table provides guidelines for an association with 40 sections and an annual total volume of CHF 500,000.
Cost Factor | Model A: Decentralized | Model B: Platform (PSP) | Model C: White-Label |
Association Setup Costs | CHF 0 | CHF 0–2,000 (depending on PSP) | CHF 5,000–20,000 (Integration) |
Ongoing Association Costs | CHF 0 (sections pay themselves) | Revenue share or platform fee | License fee from approx. CHF 200–500/mth. |
Transaction Fees (per section) | approx. 1.3–2.5% (own PSP account) | approx. 1.3–2.5% (centrally negotiated) | approx. 1.0–1.8% (volume discount) |
Association Admin Effort | High (manual fee collection) | Low (Dashboard, automatic) | Low (Dashboard, API) |
Admin Effort per Section | Medium (managing own account) | Low (onboarding by association) | Low (onboarding by association) |
Break-even (estimated) | Immediate | From approx. 10–15 sections | From approx. 50+ sections |
Additional advantage for the association: By centrally negotiating transaction fees, the association can often secure better conditions for its sections than each section would achieve individually. With a total volume of CHF 500,000+, negotiations for custom terms are possible with most PSPs.
7. Checklist: Setting up an association platform for payments
Identify needs: How many sections? Which payment occasions (fees, events, courses)?
Choose architectural model: Decentralized (A), Platform (B), or White-Label (C)?
Evaluate PSPs with platform solutions and obtain offers (Payrexx, Stripe Connect, wallee, etc.)
Define split-payment rules: Percentage share or fixed amount per transaction for the association
Define onboarding process for sections: What data does the PSP require (statutes, IBAN, board members)?
Start a pilot with 3–5 sections and test the process
Clarify reporting requirements: Which figures does the association need, and which does the section need?
Prepare communication for the sections: Explain the benefits, create instructions
Clarify regulatory questions: Do funds flow through the association or directly through the PSP?
Plan the rollout: Phased onboarding (e.g. 10 sections per month)
8. How you can build an association platform with Payrexx
With its platform solution, Payrexx offers a model specifically designed for associations with multiple sections. The association gets a central Dashboard through which it onboards sections as sub-merchants – including the KYC check, which Payrexx handles as a licensed Payment Facilitator. Each section gets its own account with its own branding, its own products (fees, events, shop), and its own payout to its IBAN account.
Split payments can be configured per section or per product: The association defines which share is automatically deducted. Reporting shows the association aggregated metrics and each section their individual transactions. Sections pay transaction fees – the association can purchase these at a buy-rate and define itself which fees it passes on to the sections. For an individual evaluation, contact the Payrexx platform team for a non-binding conversation.
Frequently asked questions about the payment platform for associations
Can each section use its own logo and branding on the payment page?
Yes. With a platform solution, each section receives its own sub-merchant account, where logo, colours and club name can be configured individually. When paying, members see the branding of their local section, not that of the umbrella association.
See detailed answer
Does the association need a FINMA licence to operate a payment platform?
As a rule, no, if the association uses a licensed PSP as a partner and the funds do not flow through the association account. The PSP assumes the regulatory responsibility (KYC, AML compliance) and forwards the payments directly to the sections.
See detailed answer
How does the onboarding of association members work?
The association initiates onboarding: It invites the section to the platform, the section provides bylaws, IBAN and board identification. The PSP carries out the KYC check. Depending on the provider, this takes 1–5 working days per section.
See detailed answer
Can the association set the split payment share differently for each section?
Yes, with most platform solutions, the split payment share can be individually configured per section or even per product category. For example, the association can charge a fixed fee of 5% for membership fees and CHF 0.50 for event tickets.
See detailed answer
How many sections are needed for a platform solution to be worthwhile?
A platform solution is usually worthwhile from around 10–15 sections. Below that, it is often sufficient to refer the sections to a PSP and collect the association share manually.
See detailed answer
Can I, as an association, set the transaction fees for my sections myself?
Yes, with many platform solutions, the association receives a buy rate (purchase price) and can define the transaction fees for the sections itself. The difference between the buy rate and the passed-on price can the association use as an additional source of income.
See detailed answer

