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

Swiss umbrella organisations can provide their sections with a central payment platform through which each section independently collects membership fees, event tickets, and course fees – with its own branding and payouts directly to the section's account. The association maintains an overview via an aggregated Dashboard and can automatically deduct an association share (e.g. licence fee or umbrella organisation contribution) per transaction via split payments before the remainder is transferred to the section.
This guide explains how such a platform solution works, which architecture variants exist, and shows three concrete scenarios for Swiss associations.
1. The Problem: Why Decentralised 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 management software, and the section in Lausanne collects cash. The umbrella organisation has no overview of payment flows, cannot provide aggregated figures for the delegates' assembly, and has no way to automatically collect the association share.
This scenario leads to three specific problems. First: The association must manually request and track the contribution of each section – a considerable administrative burden with 40–500 sections. Second: The sections offer their members an inconsistent payment experience – some accept TWINT, others only bank transfers. Third: For training programmes, licences, or events offered centrally by the association, a standardised processing method is lacking.
2. The Solution: Central Platform with Decentralised Accounts
An association platform refers to a central payment infrastructure through which all sections of an association process payments – without the association accepting the payments itself. Each section has its own sub-account (sub-merchant account) with its own branding, its own products, and its own payouts to the section's IBAN.
The association acts as the platform operator and manages the onboarding of the sections. In the background, payment processing is handled by a Payment Service Provider (PSP), which, as a technical partner, covers the regulatory requirements (KYC checks, Anti-Money Laundering Act) for each section. The association itself generally does not require its own financial market licence 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 the Association Share
Split payment means that an incoming payment is automatically split into two or more parts. For associations, this is the crucial mechanism: With every transaction of a section, a predefined share (e.g. 5% or a fixed amount of EUR 2) is remitted to the association, and the remainder goes to the section. This way, the association does not need to request its contribution separately – it is automatically deducted with each payment.
Example: A member of the Bern section pays their annual membership fee of EUR 120 via TWINT. The PSP automatically deducts EUR 6 (5%) as the association share and transfers EUR 114 minus transaction fees to the IBAN of the Bern section. The association share is collected and paid out periodically to the umbrella organisation. No manual effort, no invoices, no follow-ups.
2.2 Reporting: Two Levels, One Dashboard
A platform solution typically provides two levels of reporting. The association sees aggregated figures: total transaction volume of all sections, association shares, number of active sections, top sections by turnover. Each section exclusively sees its own transactions: incoming payments, payouts, open items. The sections have no access to the data of other sections.
3. Architecture Variants: Which Model Suits Your Association?
Depending on the size of the association, technical expertise, and budget, three architecture variants are available.
Criterion | Model A: Manual Redirection | Model B: Platform Solution (PSP) | Model C: White-Label Payment |
Principle | Association redirects sections to a PSP, each section opens Una cuenta itself | Association operates a central platform, onboards sections via API or Dashboard | Association offers payment solution under its own brand (white-label PSP) |
Section Onboarding | Each section independently | Association onboards centrally (incl. KYC) | Association onboards centrally |
Split Payment | No (manual collection of association share) | Yes (automatically 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 | EUR 0 (sections pay themselves) | Platform fee or revenue share | Licence fee + integration costs |
Ideal for | Small associations (5–20 sections) | Medium–large associations (20–500 sections) | Large associations with dedicated 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 with a platform solution 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 membership fee (EUR 80–150 per member). The association charges a licence share of EUR 5 per member. Previously, each local club had to transfer the licence share separately to the association – 20% forgot to do so, 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 fee of EUR 120 via TWINT, EUR 5 automatically goes to the association, and EUR 115 (minus the transaction fee) goes to TV Aarau. The association sees in real time which local clubs have settled accounts for how many members.
4.2 Professional Association with Further Training Offerings
A professional association offers central further training courses (EUR 350–800 per course) and has 12 regional sections that organise their own networking events (EUR 25–50 per event). Via 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 its sections a standardised solution for ticket sales at concerts. Each section receives its own sales page with club logo and colour scheme. Tickets are sold via the section's mini-webshop, and the proceeds flow directly into the section's account. The association receives a fixed amount of EUR 0.50 per ticket sold as a contribution to platform financing.
5. Regulatory Aspects: Does the Association Need a Licence?
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 intermediary under the Banking Act (BankA). The short answer: generally not, if the association uses a licensed PSP as a technical partner and the funds do not flow through the association's 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's share), the association does not accept customer funds and does not engage in payment services activities. The regulatory responsibility (KYC, AMLA compliance) lies with the PSP. The association acts merely as an intermediary that connects its sections to the PSP.
Important: If, on the other hand, the association collects the payments itself, pools them in its own account, and subsequently forwards them to the sections, it may be considered a financial intermediary and will require SRO affiliation (Self-Regulatory Organisation) or even a Fintech licence pursuant to Art. 1b BankA. This model is not recommended for associations. The platform solution via a licensed PSP avoids this problem.
Note: This section does not constitute legal advice. Regulatory requirements depend on the specific business model. If in doubt, consult a lawyer specialised 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 indicative values for an association with 40 sections and an annual total volume of EUR 500,000.
Cost Factor | Model A: Decentralised | Model B: Platform (PSP) | Model C: White-Label |
Setup Costs Association | EUR 0 | EUR 0–2,000 (depending on PSP) | EUR 5,000–20,000 (integration) |
Running Costs Association | EUR 0 (sections pay themselves) | Revenue share or platform fee | Licence fee from approx. EUR 200–500/month |
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) |
Admin Effort Association | High (manual fee collection) | Low (Dashboard, automatic) | Low (Dashboard, API) |
Admin Effort per Section | Medium (manage 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 could achieve individually. With a total volume of EUR 500,000+, negotiations for customised terms are possible with most PSPs.
7. Checklist: Setting Up an Association Platform for Payments
Determine requirements: How many sections? Which payment occasions (fees, events, courses)?
Select architecture model: Decentralised (A), platform (B), or white-label (C)?
Evaluate PSP with platform solution and request a quote (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 need (articles of association, IBAN, board members)?
Launch pilot with 3–5 sections and test the process
Clarify reporting requirements: Which figures does the association need, which does the section need?
Prepare communication to sections: Explain benefits, create instructions
Clarify regulatory question: Do funds flow through the association or directly via the PSP?
Plan rollout: Phased onboarding (e.g. 10 sections per month)
8. How to Build an Association Platform with Payrexx
With its platform solution, Payrexx offers a model specifically designed for associations with multiple sections. The association receives a central Dashboard through which it onboards sections as sub-merchants – including KYC verification, which Payrexx handles as a licensed Payment Facilitator. Each section receives its own account with its own branding, its own products (fees, events, shop), and its own payouts to its IBAN account.
Split payments can be configured per section or per product: The association defines which share is automatically deducted. Reporting provides the association with aggregated metrics and each section with its individual transactions. The sections pay transaction fees – the association can obtain these at a buy rate and determine for itself which fees to pass on to the sections. For an individual assessment, contact the Payrexx platform team for a non-binding consultation.
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-Comerciante account, where logo, colors and association name are configured individually. Members see the branding of their local section when paying, not that of the umbrella association.
View detailed response
Does the association need a FINMA licence to operate a payment platform?
Generally not, 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.
View detailed response
How does the onboarding of association members work?
The association initiates onboarding: It invites the section to the platform, the section provides statutes, IBAN, and board identification. The PSP carries out the KYC check. Depending on the provider, this takes 1–5 working days per section.
View detailed response
Can the association set the split-payment share differently for each section?
Yes, with most platform solutions, the split payment share can be configured individually per section or even per product category. For example, the association can charge 5% for membership fees and a flat EUR 0.50 for event tickets.
View detailed response
How many sections are needed for a platform solution to be worthwhile?
A platform solution is generally 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.
View detailed response
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 association can use the difference between the buy rate and the pass-through price as an additional source of revenue.
View detailed response

