Registration and payments
Fees that look like an academic meeting, not a festival checkout
Societies and universities sell places by membership, career stage, workshops and invited status. Eventumbot registration is built around those tables, with invoices that finance teams can recognise.
Categories first, then payment
Define who may register, at which rate, and which extras attach. Early-bird windows, member verification and complementary places for chairs are rules, not footnotes in an email.
Academic fee tables
Member, student, low-income country and accompanying categories without a consumer-ticket hack.
Invoices
Institutional billing, purchase orders and receipts that match the registrant record.
Payments
Collect card or invoice payment according to the methods you enable for the meeting.
Registration should know who presented
Presenting authors are not anonymous ticket buyers. When abstract records exist in Eventumbot, registration can recognise people the programme already knows. That matters for speaker fees, complementary places and on-site badges.
The checkout lives next to the public story
Rates belong on the event website with the same categories the till uses. Societies often pair registration with member-facing annual meetings rather than a generic ticket shop.
Frequently asked questions
Yes. Institutional invoices are a normal path for campus and society meetings. We confirm the methods during scoping.
Sometimes registration stays with the PCO. Eventumbot can still own abstracts and the programme. We map that split before kickoff.
Solutions
Book a demo
Eventumbot registration: member and non-member categories, early-bird windows, invoices and payments that match how scholarly meetings sell places.