Skip to content

From the form to the payment, in one step

Online registration for your event, payment included

Collecting registrations usually means three tools that do not talk to each other: a form for the data, a spreadsheet to keep count, and the bank to work out who has paid. DanceMatik makes them one. People register, pay and get their confirmation; you see a registration that is already settled, with nothing to tick off by hand.

The form is built from your event's rules

This is not a generic form you add fields to: you set the rules when you create the event, and the form applies them to whoever registers.

Automatic checks

Age, category, level, how many people per registration: the conditions you set are checked while the person fills the form, not afterwards. Anyone who does not qualify finds out immediately, and you do not receive registrations that need fixing.

Your own questions

Add the fields you need — shirt size, dietary requirements, school name — and find them in the export alongside everything else.

Files collected at registration

If your event needs an attachment (a music track, a certificate), the person uploads it while registering. It arrives attached to their registration, not in an inbox.

The account comes last

The whole form can be filled in without signing in: the account is only needed to confirm, so registrations, dancers and receipts stay tied to a person.

Payment is part of registering, not a later step

The platform works out the price from the rules you wrote, and collects the money while the person is still there.

Four ways to pay

Card, PayPal, bank transfer and internal credit. A transfer stays pending until you confirm it, and the registration knows that.

Prices that change by themselves

Date-based tiers, different prices per competition, coupons with an expiry: the total is calculated, not typed.

Fees are your call

Absorb them yourself or pass them to the person registering. Either way, the total shown is the total charged.

Money lands in your account

Card payments go to the account you connect, not to a platform account you then have to wait on.

Registrations become the rest of the event

Data entered once carries through to the end: that is the difference between a form and a management tool.

The schedule builds itself

Registrations feed the running order for the day, which you can rearrange and publish.

The public page is automatic

Your event gets its own page with dates, venue, prices and a registration button, without you setting up a separate site.

Export whenever you want

Participant list, takings and the answers to your own questions, in a spreadsheet any program can open.

The rest of the platform

Frequently asked questions

Can I use it if my event is not a competition?
Yes. The platform handles competitions, workshops, masterclasses, showcases and multi-day festivals. Registration works the same way: what changes is the rules you set, not the tool.
Do people have to create an account?
To confirm, yes: the form can be filled in without signing in, and the account is needed at confirmation. With it, they find registrations, dancers and documents in one place.
How do I get paid?
You connect your own account and card payments land there. You can also accept PayPal, bank transfer and internal credit; a transfer stays pending until you confirm it.
Can I close registrations on a date?
Yes, and they can also close early once you hit the cap you set. From that moment the public page says so, instead of accepting registrations you would have to turn down.
What if I need to refund someone?
The refund is recorded from the event management: the registration changes state, and the accounting export reflects it.

Open registrations before you print the poster

Create the event, set the rules, and the form is online. Nothing to install.

Cookies and third-party content

We only use technical cookies, needed to browse, buy and stay signed in. We do no profiling and use no analytics or marketing tools. Google Maps, if you enable it, sets Google cookies. Continuing to browse does not count as acceptance. Cookie policy