Integrations
The systems DonorCARE actually talks to
No rules engine, no if-this-then-that builder — DonorCARE doesn't have one yet. What it does have is a named set of real integrations: a payment gateway, LHDN e-invoicing, email delivery, forms, analytics, single sign-on, outbound webhooks, and an accounting export.
Named, not implied
- CHIP
- payment gateway
- MyInvois
- LHDN e-invoicing, auto-submit
- 9 events
- outbound webhook types
- SendGrid
- email delivery
Statutory e-invoicing
MyInvois submission, with TIN validation and an auto-submit cron
Every submission carries a real status — draft, pending, submitted, valid, invalid, or cancelled — with TIN validation tracked against it. For orgs that turn auto-submit on, a cron job files eligible invoices to LHDN twice a day, in batches, inside LHDN's own rate limit.
- TIN validation tracked per submission
- Auto-submit cron runs twice daily, batched and rate-limited to LHDN's cap
- Full status lifecycle: draft through valid or cancelled
Connected systems
CHIP, SendGrid, FormCARE, GA4, and JomCARE SSO
Each of these is a real, working connection an org can turn on from the Integrations screen — not a name dropped for effect.
- CHIP — the payment gateway behind every online donation
- SendGrid — email delivery, on by default
- FormCARE — the CARE-suite forms product, connected per org
- Google Analytics 4 — drop in a measurement ID, no bidirectional API
- JomCARE SSO — single sign-on into DonorCARE for the CARE product suite
React to your own events
Outbound webhooks — nine real event types
An org can subscribe an external system to DonorCARE events, HMAC-signed, with delivery failures tracked. This is the closest thing to 'automation' DonorCARE offers today: it fires the event reliably, but building what happens next is your own engineering work, not a DonorCARE-built workflow.
- donation.completed, donation.voided, donation.pending_review, donation.verification_uploaded
- myinvois.status_changed, receipt.generated, donor.tier_changed
- form.submission.created, form.archived
- HMAC-signed deliveries with failure-count tracking
Accounting, honestly described
SQL Accounting export — a file you import, not a live sync
For orgs with it enabled, DonorCARE generates an XML export formatted for SQL Account desktop software. It's a one-way, on-demand file an admin downloads and imports by hand — there's no continuous, two-way accounting sync.
- One-way XML export, gated per org
- Downloaded and imported manually into SQL Account
- Not a live or continuously-synced integration
Frequently asked questions
What happens if a submission to LHDN fails or is rejected?
It doesn't disappear into a black hole. Every submission carries a real status — draft, pending, submitted, valid, invalid, or cancelled — so a rejection shows up as invalid, not silence. Rejected and stuck submissions surface twice: as a 'Needs Attention' item on your dashboard, deep-linking straight to the record, and on the Compliance analytics page, which tracks rejection reasons and a running validation rate so your finance lead can see the pattern, not just one red badge.
Can I build a rule like 'when a donation completes, do X'?
Not inside DonorCARE — there's no automation or rules-engine builder. What you can do is subscribe an outbound webhook to that event and have your own system react to it.
Do you integrate with Stripe, a CRM, or a ticketing system?
Not yet. Those appear as coming-soon in our own admin, and we're not going to market them as shipped before they are.
Does the SQL Accounting export sync automatically?
No. It's a file you generate and import into SQL Account desktop software yourself — not a continuous sync.
We already use an accounting system. Does DonorCARE replace it?
No, and it isn't trying to. DonorCARE is built as a donor sub-ledger, not a general ledger — it doesn't hold a chart of accounts, a trial balance, or a fiscal-year configuration. It records donations, dates, and receipts, then feeds that into your accounting system through the SQL Accounting export or a CSV/JSON export, rather than replacing the books you already keep.
Can we get our donation and donor data out if we ever need to switch systems?
Yes. Exports cover donation CSV, receipt batches as a ZIP, and a full data export in JSON, alongside the LHDN and SQL Accounting formats above — so your records aren't locked into a format only DonorCARE can read.
Connect the systems you already run on
MyInvois e-invoicing and API & webhook access are Enterprise features; CHIP and SendGrid are available from Free.