Skip to content

Events, registration and gates for organisers

Linked events at every level, QR tickets, and gates that keep scanning through a signal drop, with every booth selling through asasii pos. Bought once and owned outright.

Visitors registering at a table at an outdoor event
Scans offline
Gates keep checking tickets when the signal drops.
Every level linked
State and district events roll up to the parent.
Booths on asasii pos
Cash, card and DuitNow QR at every booth.
Owned outright
No fee per ticket and no share of sales.

An event on asasii events

From the approved proposal to the close-out report.

  1. Weeks before

    Approved and listed

    The proposal is approved at the right level and the event goes on the event website.

  2. Registration open

    Attendees register

    They sign in, choose their days, agree to the privacy notice and get a QR ticket.

  3. Before the event

    Booths approved

    Each approved vendor gets a booth and an asasii pos outlet with its own menu.

  4. Gates open

    The first scans

    Door staff scan QR tickets, and walk-ins register at the gate.

  5. Mid-morning

    A gate loses signal

    Scanners keep checking tickets on the device and upload when the network is back.

  6. Afternoon

    A session moves

    The change goes to the app by push, and by SMS to those without it.

  7. Every night

    Settlement

    Card and DuitNow QR sales settle to each vendor's account. Cash stays with the vendor.

  8. After the event

    Close-out

    Late offline sales settle, finance reconciles fees and payouts, and the close-out report goes up for approval.

A licence, not a fee on every ticket

The organiser buys an events platform and keeps everything it produces. idataraya is paid to build, customise and maintain it.

TopicA ticketing platformasasii events
Who owns the softwareThe platform; access ends with the contractThe organiser, outright
Where attendee data livesThe platform's cloudThe organiser's own environment
Ticket and booth fee paymentsThe platform's gateway and its rateFPX and DuitNow QR into the organiser's own account
Booth salesA separate system, or noneEvery booth on asasii pos, settled to the vendor
What it costsA fee per ticket or per attendeeA system, plus a yearly fee with defined response times

Security and Malaysian compliance

The questions procurement and audit ask, answered in the platform.

Security and data overview
PDPA 2010
Consent is recorded at registration, with the notice version and each choice.
MyKad masked
MyKad numbers are masked on screen and in exports.
Single sign-on and MFA
On every console, with the organiser's identity provider.
Roles by level
Each office sees its own events and those below, and door staff cannot open attendee records.
Audit trail
Every change and every view of personal data, kept for seven years.
Your own environment
Attendee data stays in the organiser's own data centre or cloud account.
Two members of the team on calls at their desks

Installed and maintained by idataraya

asasii events runs in the organiser's own data centre or cloud account, under the organiser's own IT team. idataraya installs it and keeps it current, and the organiser holds the keys, the backups and the data.

  • Response times by severity, measured monthly
  • Monitoring from within the organiser's environment
  • A drilled backup and restore
  • Software updates and the customisations made for you
Our services

Questions organisers ask

About linked events, the gate, the booths and where it runs.

Can state and district events link to a national event?

Yes. A state, district or kampung event links to a parent event and keeps its own date, venue, programme and budget. It takes the theme, branding, reporting codes and core registration fields from the parent. Every registration and booth sale rolls up to every level above it.

Do attendees need the app?

No. Attendees can register on the event website, and the ticket goes to My tickets and their email. The QR works on the phone or printed, and announcements reach those without the app by SMS.

What happens at the gate when the signal drops?

Scanners keep checking tickets on the device against the last ticket list and hold the scans. They upload when the network is back, and duplicate tickets are flagged on upload. Walk-ins registered at the gate are saved on the phone until the signal returns.

How do vendors take payment at the booths?

Every approved booth sells through asasii pos, on a terminal lent by the organiser or on the vendor's own Android tablet. Vendors take cash, card and DuitNow QR. Card and DuitNow QR settle nightly to the vendor's own bank account, and cash stays with the vendor.

How is attendee data protected?

Consent is recorded at registration with the privacy notice version, and MyKad numbers are masked on screen and in exports. Each office sees its own events and those below it, and door staff cannot open attendee records. Every change and every view of personal data is in the audit trail.

Where does it run, and can our other systems talk to it?

In the organiser's own data centre or cloud account. idataraya installs it, hardens it and keeps it current, and the organiser's team holds the keys, the backups and the data. A documented API with scoped keys lets the finance system, dashboards, the organiser's website or a third party read events, reports, payments and budgets.

What does the yearly agreement cover?

Software updates, the customisations made for you, monitoring, and severity-based response and restoration targets. Hosting stays with you. It is a fee, not a share of ticket or booth sales.