Integrations
What connects today — and what does not
An integrations page is only useful if it is complete in both directions. Here is everything Aced connects to in production, followed by the things it does not, so nothing surfaces as a surprise during implementation.
Production
Supported today
| Connection | Type | What it does |
|---|---|---|
| Stripe | Native | Card processing under your own Stripe account, Terminal readers, hosted payment surfaces, cards on file and payouts to your bank. |
| Gusto | Formatted export | A Gusto-formatted payroll file that imports directly, generated from the time clock. |
| ADP, QuickBooks & other payroll | Universal CSV | Per-employee summary and day-by-day detail with the over-40 overtime split calculated. |
| Bookkeeping systems | Accountant CSV pack | Sales, tenders, tax by category, refunds and deposits for a period, with documented definitions. |
| Customer, product & gift-card import | CSV import | Bring an existing list in during migration, with presets for common source formats. |
| Calendar | ICS files | Event and booking details that open in a normal calendar application. |
| Receipt & kitchen printers | Star WebPRNT over your network | Silent ticket printing for the grill; see the hardware page for models. |
Accurate as of August 2026. If a row here is load-bearing for you, confirm it with us before you sign anything.
Honestly, no
Not available today
This table exists because a page that only lists what works is impossible to evaluate. If one of these is a requirement, it is better to know now.
| Not available | Status | What to do instead |
|---|---|---|
| Public REST API | Not published | Data movement is by CSV import and export. Raise it in discovery if you need programmatic access. |
| Third-party webhooks | Not published | There is no developer webhook catalogue today. |
| Live accounting sync | Not available | The accountant pack is a CSV export, not a two-way sync with a ledger system. |
| Tee-time marketplace distribution | Deliberately not offered | Aced is the course's own booking system. Marketplace reach is not part of it. |
| Third-party tournament platforms | Not integrated | Tournaments and leagues are native to Aced rather than connected to an external scoring product. |
| Handicap authority sync | Not available | Handicaps are held on the golfer record and used for net scoring; there is no automatic feed to or from a governing body. |
Why publish the second table at all
Integration questions
Is there a public API?
Not today. There is no published REST API and no webhook catalogue for third-party developers. Data movement happens through CSV import and export, which is unglamorous but real. We would rather say that than list an API that is not documented or supported.
Does Aced connect to QuickBooks or Xero?
Not directly. The accountant pack is a set of CSV exports designed to import cleanly into a bookkeeping system — including QuickBooks — but it is an export rather than a live two-way sync, and calling it an integration would overstate it.
What about payroll?
Payroll exports as a per-employee summary and a day-by-day detail file in universal CSV, which imports into ADP, QuickBooks and the rest, plus an optional Gusto-formatted file that imports directly into Gusto.
Can I get my data out?
Yes, whenever you want it while the account is active — customers, sales, timesheets and reports as CSV. Export is treated as a feature rather than a retention lever.
Will you build an integration we need?
Tell us during discovery. If an integration is load-bearing for your operation, it belongs in the scoping conversation and in the written proposal, not in a hopeful conversation after go-live.
Name the system you cannot give up
Every course has one — an accounting package, a payroll provider, a handicap workflow. Tell us in the first conversation and we will say plainly whether it fits.