Platform & white-label
Your brand leads. The infrastructure holds.
fanhub. is membership and commerce rails your organisation runs under its own name: the page, the card, checkout and event operations carry your colours and logo, on one member database nobody has to retype.
What runs today
Everything below is built, not a plan. What waits for fan payments is marked where it appears; what is not built yet is in the next section.
Identity & database
One fan account works across every organisation, and each organisation holds its own member records, isolated at the database level.
- Sign in by email or Google, with no guest checkout
- Row-level isolation between organisations
- Per-purpose consent, service and marketing recorded separately
- CSV export of all member data, on every plan, unconditionally
- Import an existing list without creating fake accounts: members claim their own
Money and the books
Once fan payments are live: Buyer funds settle to the organisation's account through a payment-gateway sub-account. fanhub. never holds an organisation's money. Payouts follow the payment provider's settlement schedule.
- QRIS first, plus virtual account, e-wallet and cards
- Split settlement per organisation, with a swappable gateway
- Double-entry cash book reconciled daily against the gateway report
- Atomic refunds: money and points reversed in one journal
- A flat platform fee on its own line, never a percentage
Membership & cards
Seasonal tiers, a digital card, and member pricing that applies itself in the shop.
- Seasonal tiers with benefit lists and quotas
- Digital member card with a QR, one construction across four registers
- Automatic member pricing on merchandise
Events & check-in
Free or paid events, with check-in that keeps working when the signal does not.
- Event pages with OG cards that look right when shared on WhatsApp
- Once fan payments are live: Paid registration through the same checkout
- A check-in QR that rotates every 30 seconds, with anti-pass-back
- Offline mode: scans queue and sync themselves once there is signal
- Verified attendance records per event
Shop & drops
Once fan payments are live: A club shop with stock, variants, and limited drops that cannot oversell.
- Catalogue with variants and per-variant stock
- Limited drops with anti-oversell locks
Points & announcements
Points can only be earned, never bought, and are funded by the organisation.
- Points from check-in and purchases, valued in rupiah by the club, with scheduled expiry
- An auditable points ledger, with no transfers between clubs and no cash-out
- Announcements to members from the console
Integrations: what connects, what needs activation, what does not exist yet
Tell a link, an export, and an automatic connection apart before you decide. What does not exist is not shown here as a capability.
Available now
- Member CSV export by the account owner, on every plan
- A link to an external ticket page from an event
- Pages, member card, checkout and gate scanner in the browser
Needs activation
- Member payments (dues, paid tickets, merch)
- Shipping rates and parcel tracking through a courier
- Payment service fees shown separately, never fanhub. revenue
Not yet available
- Public API and webhooks
- Accounting connectors
- Automatic ticket sync across providers
- Attendance import from other providers
Platform & white-label
Your brand leads. The infrastructure holds.
Use your organisation's colours and logo on the page, the member card, checkout, and event operations. If a colour is hard to read, the system adjusts it slightly and tells you. Custom domains are available on Enterprise.
This primary has enough contrast. Used as is.
Derived from your colours
- --club-primary-safe#0E7C4A
- --club-deep#104430
- --club-on-primary#FFFFFF
- --club-focus#0E7C4A
- --club-selected#cfe2de
The "powered by fanhub." mark is always on every community page, exactly once, and is not part of the theme.
Member card
Sample view. Every community and member name here is fictional.
What legal usually asks
Your organisation is the data controller; fanhub. is the processor. That is not a slogan, it is the shape of the system.
- Member data can be exported at any time, on every plan, unconditionally
- Every reveal of a member's contact is written to an access log with the name of the person who opened it
- Service agreement and marketing permission are recorded separately, each with its document version and timestamp
- An umbrella structure sees aggregates by default; per-member data stays with the chapter that owns it unless that chapter agrees otherwise in writing
- Data handling follows the PDP Law and data processing agreements with our service providers.
What is not built yet, and when
We do not present plans as capabilities. None of the below can be used today.
Planned
Chapters & umbrella reporting
A parent and chapter structure, with a national view containing aggregates by default.
Planned
Dues billing
Dues cycles, per-chapter rates, arrears and reminders.
Next
GO Manager
Pooled orders with a proof timeline, deposits and settlement.
Next
Metered campaigns
Quota-based WhatsApp broadcasts on top of the announcements that already exist.
Next
Sponsor report
A seasonal report of verified attendance and tier mix.
Later
Official fanclub console
Artist-led theming, presales, and member-only content.
Parked
Seated ticketing
Not our plan. fanhub. keeps the model where a ticket is a product with capacity.
Want to see how this fits your organisation?
We can walk through it together, or you can create a free page and see the same rails from the organiser's side.