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 in the running product, not a plan. What is not built yet is in the next section and marked as such.
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 phone number 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
Buyer funds settle to the organisation's account through a payment-gateway sub-account. FanHub never holds an organisation's money.
- 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
- Paid registration through the same checkout
- A check-in QR that rotates every minute, with anti-pass-back
- Offline mode: scans queue and sync themselves once there is signal
- Verified attendance records per event
Shop & drops
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
- Shipping rates and tracking through a courier integration
Points & announcements
Points can only be earned, never bought, and are funded by the organisation.
- Points from check-in and purchases, 1 point = Rp1, with scheduled expiry
- An auditable points ledger, with no transfers between clubs and no cash-out
- Announcements to members from the console
White-label that behaves
Your colours and logo map onto the whole presentation layer, and when a colour cannot carry text the system darkens it just enough and tells you, rather than quietly substituting one. Custom domains are available on Enterprise.
Try it with your own colours on the home page →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 only; per-member data stays with the chapter that owns it
- The database sits in Indonesia, as UU PDP requires
What is not built yet, and when
We do not present plans as capabilities. None of the below can be used today.
Q4 2026
Chapters & umbrella reporting
A parent and chapter structure, with a national view containing aggregates only.
Q4 2026
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.