Payment accounts

Ενημερώθηκε 27 Οκτ 2026

A payment account is a Stripe account connected to Cloomba. Every payment account belongs to a community or to your personal calendar. Card payments for an event go into one of the accounts of its community or personal calendar, and membership payments into the default account of that community.

A community or personal calendar can have more than one account — for a club and a company, or for each bank account you want money in — and each of its events can be paid into a different one.


Where the money goes

  • An event is paid into the account chosen for it, which is always one of the accounts of its community or personal calendar. If none is chosen, it uses the default account there at the moment of each sale.
  • A community's memberships are paid into the community's default account.

The account's holder is the seller: the payout, the Stripe receipts, refunds and disputes all belong to that account.


Adding an account

  • Your personal calendar: on cloomba.com, open Communities in the top bar, select Personal — the first card under Your communities — and open its Payments tab.
  • A community: open the community's Manage page and its Payments tab. The community's owners add and manage its accounts; its admins can see them.

Select Connect Stripe for the first account, or Add for another one, and finish Stripe's onboarding — your business details and a bank account. The first account becomes the default. A community or personal calendar can have up to 10, set up one at a time: while one is unfinished, its row shows Continue setup in place of Add.

Select an account's row to give it a name you will recognise or make it the default. An account becomes the default once it is ready to take payments. Manage on Stripe opens the Stripe dashboard for the person who connected the account — Stripe sends its login code to them.


Choosing the account for an event

Open Manage → Registration → Getting paid on a paid event and pick one under Payment account. The list shows the accounts of the event's community or personal calendar, the default marked (Default). An account still in onboarding is shown as Onboarding incomplete and can be picked once it is ready. The community's owners and admins choose; the organizer is notified when someone else makes the change. When there is only one account, its name is shown in place of the list.

The choice applies from the next sale. Tickets already sold stay on the account that took them. An event moved to another community is paid into that community's accounts from then on — see Moving an event to another community.


A community's default

The community's owners choose its default. Members who pay by subscription stay on the account they subscribed through, so the default can't change while any of their subscriptions run. It can change again once the last one has ended.

A community keeps its accounts and its default when its owners change.


Refunds and past sales

A refund always goes back through the account that took the payment — also after the event switched accounts or moved to another community. Switching an account moves future sales only. See Issuing refunds.


Questions

Can two events in the same community be paid into different accounts?
Yes. Connect both accounts to the community and choose one on each event.

I run a club and a company. How do I keep the money apart?
Give each its own community with its own account, or connect both accounts to one community and choose the right one on each event.

My co-organizer should receive the money for our event. How?
Put the event in a community where their account is connected — one they own.

What happens to tickets already sold when I switch accounts?
They stay on the account that took them, and so do their refunds.

Why can't I change my community's default?
Members pay into it by subscription. It can change again once the last subscription has ended.

Do extra accounts cost anything?
No. Adding an account is free, and the fee on each sale is the one described in How Cloomba fees work.