Event ticketing
Via TicketCAREA gift with a name isn't the same as a ticket. DonorCARE does one.
DonorCARE registers a name to a memorial tablet or a blessing slot as part of a donation — no seat, no admission, no scan-in. Paid admission with seats and check-in is TicketCARE, a separate CARE Business App with its own sign-in and its own checkout.
Not a cold start
- 2
- sibling apps already wired: FormCARE, MyInvois
What DonorCARE actually does
Ceremony and ritual registration — a name tied to a gift
A donor sponsoring a memorial tablet or a blessing slot registers a name as part of their donation at checkout. The money is a gift, receipted under s44(6) where applicable — not a ticket sale. See /features/ceremony-registration for the full picture.
- Name registration happens inside the donation checkout
- Tracked from pending through to printed on a tablet
- Receipted as a gift, not a ticket
What DonorCARE doesn't do
No seats, no admission control, no check-in
Say the gap plainly: DonorCARE has no seat inventory, no admission control, no QR check-in at a door, no ticket transfer or resale, and no attendee list kept separate from its donor records. It was never built to run an event door.
The decision rule
Gift with a name, or paid admission with a seat — pick the product
If a supporter is giving and dedicating a name — to a memorial tablet, a blessing slot — that's a DonorCARE ceremony registration. If someone is paying for admission with a seat and a check-in at the door, that's TicketCARE. The two aren't the same feature wearing different names; they're different products for different transactions.
- Gift + dedicated name + tax receipt → DonorCARE ceremony registration
- Paid admission + seats + check-in → TicketCARE
Via a sibling app
TicketCARE — its own product, its own sign-in, no bridge yet
TicketCARE is the CARE Business Apps ticketing and events marketplace: its own sign-in, its own checkout, and CHIP payments under the organiser's own gateway keys. It runs alongside DonorCARE as a separate product, not a module inside it. DonorCARE's own Integrations screen lists TicketCARE as coming soon, and names the stated bridge plainly: donation sync from events. It doesn't exist yet — an organisation running both keeps two separate systems until that link is built.
- Separate product, separate checkout, separate login — deliberately, unlike the rest of the CARE suite
- CHIP payments under the organiser's own TicketCARE gateway keys
- Donation sync from events is the stated plan, not yet built
Design intent — not built yet
The real question isn't the sync — it's who owns the receipt
An attendee and a donor are different records that sometimes name the same person: someone buys a TicketCARE ticket, and separately — or at the same checkout — gives to the org's DonorCARE campaign. Donation sync from events, as named in our own Integrations screen, means a ticket-linked gift arriving in DonorCARE as its own record. The design question worth stating plainly: DonorCARE, not TicketCARE, would remain the one system that issues the s44(6) tax receipt, so the statutory logic stays in one place instead of being duplicated in two products. See /features/care-suite for how identity would resolve between the two records, and how this bridge compares to the others already planned across the CARE apps.
- An attendee record and a donor record are not automatically the same person's row, even when they are the same person
- A ticket sale is not a receiptable gift — only the donation portion, if any, would sync as one
- Intent: DonorCARE keeps sole ownership of the s44(6) receipt even for a ticket-linked gift
Registration is live. Ticketing is a different app. The bridge is ahead.
Ceremony and ritual registration, in DonorCARE
- Name registration at checkout
- Part of the donation itself, for memorial tablets and blessing slots.
- Tracked through to printing
- Every registration moves from pending to generated to printed.
Paid admission, seats, and check-in
A separate CARE Business App, with its own sign-in — not a feature inside DonorCARE.
- Seat inventory and admission control
- TicketCARE's job, not DonorCARE's.
- QR check-in at the door
- Lives in TicketCARE.
- Its own checkout and gateway keys
- TicketCARE takes payment through the organiser's own CHIP keys, separate from DonorCARE's.
A DonorCARE-to-TicketCARE data bridge
Also listed coming soon in DonorCARE's own Integrations screen. The design-intent rows above describe how we mean to build it — none of it exists today. No date implied.
- Donation sync from events
- The stated plan, named in our own Integrations screen — a ticket sale in TicketCARE showing up as a synced record in DonorCARE. Not built yet.
- Identity resolution across the two records
- Matching an attendee record to a donor record through the shared JomCARE identity. Not built yet.
- No shared attendee/donor data today
- Running both products today means keeping two separate records until the bridge exists.
Frequently asked questions
Does DonorCARE do event ticketing?
No. It does ceremony and ritual registration — a name registered as part of a gift, for a memorial tablet or blessing slot. There's no seat inventory, admission control, or check-in. Paid admission with seats is TicketCARE, a separate CARE Business App.
If I use both DonorCARE and TicketCARE, do they share donor data?
Not today. TicketCARE runs its own sign-in, checkout, and attendee records. There's no data bridge between the two products yet, so you'd be maintaining two separate systems until that link is built. The stated plan, named in our own Integrations screen, is donation sync from events — it isn't built yet.
Has DonorCARE connected a sibling CARE app like this before?
Yes, twice. FormCARE is wired into campaigns today — a checkout form step, fill-later reminder emails, and response sync. The BizCARE Books API files e-invoices to LHDN on a live schedule. TicketCARE follows the same pattern; it just isn't built yet. See /features/care-suite for the full picture across every CARE-app bridge.
Can I log into TicketCARE with my DonorCARE account?
No. Unlike the rest of the CARE Business Apps suite, TicketCARE deliberately runs its own sign-in door — there's no single sign-on between it and DonorCARE.
How do I know which one to use for an upcoming event?
Ask what the transaction actually is. A gift with a dedicated name and a tax receipt is a DonorCARE ceremony registration. Paid admission with a seat and check-in at the door is TicketCARE.
Is ceremony registration the same thing as a ticket, just named differently?
No — the underlying transaction is different. A ceremony registration is a donation; the money is a gift receipted under s44(6) where applicable. A ticket is a sale for admission. DonorCARE only does the former.
Is the identity-matching and receipt-ownership design above already built?
No. It's design intent — how we mean to resolve an attendee record against a donor record through the shared JomCARE identity, and keep DonorCARE as the sole issuer of the s44(6) receipt when a ticket includes a gift. None of it exists today; the status ledger above is the accurate, current picture.
Register names to a memorial tablet, the right way
Ceremony and ritual registration ships on Enterprise. For paid admission with seats and check-in, that's TicketCARE.