eBrigade Payment methods module
Payment methods: one hub to enable Stripe, PayPal and HelloAsso by use
Configure your payment providers in one place and decide exactly where each one is offered: donation, membership, ticketing, membership dues or CRM invoice. Each connector can be switched on or off independently, with a real-time connection status.
These buttons are about the full eBrigade subscription: this module is included at no extra cost in every plan.
Settings hub that turns on Stripe, PayPal and HelloAsso independently for each use: donation, membership, dues and CRM invoice. Ticketing takes payment online through HelloAsso.
What is the eBrigade Payment methods module?
A configuration hub that enables Stripe, PayPal and HelloAsso independently for each use: donation, membership, membership dues and CRM invoice. Ticketing takes online payments via HelloAsso. It is included at no extra cost in every eBrigade plan.
Why use the Payment methods hub?
Stripe, PayPal and HelloAsso (a French online payment platform for associations) are three separate connectors, each with its own keys and its own settings screen. Without a central point, you lose track of which provider is active for which use, or whether it is properly connected — and a payment button can stay visible to members even though the keys have not even been entered.
What the Payment methods hub changes in eBrigade
A single tab brings together Stripe, PayPal and HelloAsso. For each provider, you see its connection status and tick the uses where it is offered: donation, membership, ticketing, membership dues, CRM invoice. The hub does not process payments — it is the configuration router that decides which connector appears in which form. Accounting consolidation is handled by the Accounting module.
What you can do with Payment methods
Each provider (PayPal, Stripe, HelloAsso) is enabled independently for five uses — donation, membership, ticketing, membership dues and CRM invoice. For example, you offer Stripe for membership dues and HelloAsso only for donations.
An Enabled/Disabled toggle turns an entire provider off or back on without reloading the page. When disabled, it disappears from every payment form, whatever uses are ticked.
Each provider shows a Connected or Not configured badge, updated automatically as soon as you save keys or reconnect an account. You see at a glance what is actually working.
The CRM invoice use can only be enabled if the provider’s keys are configured. If a key is removed, the toggle switches off and the database is cleaned up — no dead payment button is shown to the client.
The HelloAsso connection card (OAuth2, access/refresh tokens) is shown directly in the hub, next to the other providers, so you can link the association’s account without changing screens.
The hub creates and repairs its tables idempotently: it works even if PayPal, Stripe or HelloAsso have never been installed separately, and automatically takes over the historical payment settings for membership dues and donations.
Step by step
Enter the Stripe and PayPal keys, or link your HelloAsso account via OAuth2, from the Payment methods tab. Each provider’s badge switches to Connected as soon as the connection is valid.
For each provider, tick the uses where it should be offered: donation, membership, ticketing, membership dues, CRM invoice. The master switch lets you turn off an entire provider in one click.
Based on what you have enabled, each payment form (donation, membership dues, ticket, client invoice) offers the member only the providers you have allowed for that use. No configuration needs to be re-entered.
Where this module really pays off
Charities: HelloAsso enabled for donations and Stripe for membership dues, configured from a single tab.
Federated organisations: global HelloAsso settings applied to all sub-organisations, or an independent account per sub-organisation.
Events & ticketing: Stripe or PayPal enabled only for paid registrations, without affecting other uses.
CRM & client invoicing: card payment of invoices and quotes, with the toggle enabled only once the keys are configured.
Memberships: choice of the provider offered when a new member joins, separate from the annual membership dues.
v7.0 migration: automatic transfer of the old payment settings for membership dues and donations into the unified matrix.
Frequently asked questions
Are PayPal, Stripe and HelloAsso still separate modules?
Each keeps its own keys and payment logic, but their configuration is brought together in the Payment methods hub. You connect them and decide their scope from a single tab, and the member chooses their payment method in the relevant form.
Can a provider be enabled for certain uses only?
Yes, that is the core of the module. Each provider is enabled independently for five uses — donation, membership, ticketing, membership dues and CRM invoice — via a matrix of checkboxes. For example, you can allow HelloAsso for donations only.
Does the module consolidate payments and generate receipts?
No. The hub configures which provider is offered in which context; it does not consolidate payments and issues no receipts of any kind. Accounting follow-up is done in the Accounting module, and tax or membership dues receipts in the Donations and Membership dues modules.
What happens if I haven’t entered a provider’s keys yet?
The provider stays marked as Not configured and cannot be offered. For CRM invoices in particular, the toggle is locked until the keys are valid, to avoid showing the client a payment button that does not work.
Is this module included in the subscription?
Yes, at no extra cost from eBrigade. Only the fees charged by Stripe, PayPal or HelloAsso remain subject to their own pricing terms.