Integrations

Fits the tools you already pay for

Aura is the till, the back office and the code on the table. Your accountant keeps their ledger, your guests keep WhatsApp, your card machine keeps working — and anything not on this list can be built against the API.

Accounting

Your bookkeeper gets a balanced journal, not a sales report

Every settled sale posts a balanced double-entry journal — cash, card and QR clearing accounts, revenue, VAT and tips. The export reproduces that ledger rather than reconstructing it.

Xero

A balanced journal CSV for any date range, in the layout Xero's manual journal import expects. Back office → Reports → Accounting.

Sage / Pastel

The same journal in the Sage/Pastel layout — the two formats South African bookkeepers actually ask for, chosen from a dropdown.

Ledgr

A direct link to Ledgr, the SA accounting platform — so takings, VAT and the journal land in the books without a CSV round-trip.

SARS VAT201

Not an integration so much as a built-in return: standard, zero-rated and exempt sales, output VAT at 15%, input VAT from received purchase orders, VAT payable — as CSV or PDF, for any period.

Input VAT from purchasing

Received purchase orders feed the input-VAT side of the return, so the VAT201 isn't only half the picture.

Everything else as CSV

Dashboard, sales, X and Z reports, register movements and closures, product and customer reports — all exportable, so nothing is trapped in the product.

Messaging

Reach guests where they actually reply

WhatsApp Cloud API

Receipts and booking confirmations

A paid sale sends the attached customer a WhatsApp receipt with a signed web link valid for 90 days — if they've opted in. Confirming a pending booking sends the guest a confirmation the moment a manager taps Confirm. Both quietly no-op when the credentials aren't set, so nothing errors or queues forever.

Mailjet

The checklist daily digest

With email configured, a daily summary of every checklist's completion state goes to the address (or addresses) you set — so an owner who wasn't there knows whether closing was actually done.

Payments

Three South African providers, natively

Yoco

Card-present on the terminal, pay-by-link the guest settles on their own phone, card pre-authorisation to hold a bar tab, refunds back through the original provider, and Tap to Pay where SoftPOS is enabled. On QR Ordering venues it also powers the guest's own hosted checkout. Webhook-confirmed and idempotent, so a retried delivery can't double-capture.

SnapScan

A QR tender at the till, and the fallback rail on guest self-service orders when Yoco isn't configured — a per-order QR for the exact amount, including any tip the guest added.

Zapper

QR payments at the till with webhook confirmation. Leaving the webhook secret blank disables the webhook without disabling the tender.

The full payments page

Coming from another POS

Aura imports your menu straight from a Lightspeed, Tebi or Pilot CSV export — pick the source, preview the mapping, commit. Barcodes and SKUs come across with it, so the scanner works on day one.

How switching works →

Build your own

A documented REST API over the whole product, JWT and API-key auth, idempotency keys, signed webhooks, and a realtime WebSocket stream of kitchen, table and payment events. There's a live Swagger sandbox with a one-click demo token.

Open the developer hub →

Two scheduled endpoints are designed to be hit daily by a scheduler: one issues the automatic birthday vouchers, the other emails the checklist digest. Your installer wires them to Cloud Scheduler or cron — see scheduled jobs.

Need something that isn't here?

Tell us what you're connecting to. If it isn't built in, the API almost certainly covers it — and we'll tell you honestly if it doesn't.