Alovio Payments · 8 pages
Alovio Payments Page 07 of 08 3 min read

Booknetic SaaS

Run Alovio Payments on a Booknetic SaaS platform: each business connects its own gateway account and writes its own manual methods, you allow them per plan, and businesses settle and refund from Transactions in their own panel.

On this page

On Booknetic SaaS the money never passes through the platform. Every business connects its own gateway account with its own keys, and customers pay that business directly. As the platform operator you decide which gateways exist on the platform and which plans get them — you never hold the businesses’ keys.

Site owner (regular Booknetic)SaaS operator
Gateway keysEntered once, in the hubEach business, in its Booknetic settings
Money goes toYour gateway accountEach business’s account
RefundsYou, from TransactionsThe business only
The hub’s gateway pageKeys, connection check, webhookMaster switch, plans, how many businesses are connected

Setting it up — the operator

  1. Keep the gateway switched on in Alovio Payments → Gateways. That switch is platform-wide: off hides the gateway from every business.

  2. Allow it in your plans. Each gateway adds a capability to Booknetic SaaS plans — Paystack (Alovio Payments), Xendit (Alovio Payments) and Tap Payments (Alovio Payments) — and Manual payment methods (Alovio Payments) lets businesses write their own bank transfer, cash or QR methods. A newly added capability starts switched off on existing plans, so switch it on for the plans that should have it. Nothing is switched on for you.

    Fig. 1The Alovio Payments capabilities in a Booknetic SaaS plan
  3. Businesses connect their own accounts. The gateway’s page in the hub counts how many have.

Fig. 2A gateway's page for the platform operator: switch, plans, businesses connected

Licence notices are shown to site administrators only, never to businesses.

Setting it up — a business

A business whose plan includes the gateway opens Booknetic → Settings → Payment methods in its own panel, enters its own keys (see Paystack, Xendit or Tap Payments) and switches the gateway on. Its Booknetic currency has to be one the gateway takes.

With Manual payment methods in its plan, a business also writes its own methods under Payments → Manual methods: its own bank details, instructions and QR code. See Manual methods.

Each business has its own webhook URL, shown in its payment settings (Tap needs none: every Tap payment carries its own). A webhook is checked with that business’s own keys, so a notification for another business’s payment is never applied to it.

Transactions, in the business’s panel

Each business sees its own payments under Payments → Transactions in its Booknetic panel — or as a menu item of its own when a staff role does not see Booknetic’s Payments. It lists only that business’s payments; another business’s payment simply does not exist there.

Fig. 3A business's Transactions: gateway and manual payments together

Each payment opens a page with Check now (or, for a manual method, Mark as received and Cancel booking), refunds, the timeline, and links to its appointments, which open in Booknetic’s own appointment view. Refunds work exactly as described in Transactions & refunds.

Fig. 4A paid payment's page in the business's panel

The screen appears while the plan includes an Alovio Payments gateway or manual methods, and it stays as long as the business has payments — so money already taken can still be refunded after a plan loses the gateway.

Two permissions let the business owner decide what each staff role can do:

  • Payment transactions — see the payments, use Check now, and retry a failed Booknetic update.
  • Refund and settle payments — send refunds, mark manual payments as received or cancel them, accept a mismatched payment by hand, and settle a refund whose answer was lost.

What the operator sees

Alovio Payments → Transactions shows every business’s payments, each marked with its business, for support. You can open any of them and re-check it with Check now. Refunds, marking manual payments as received, and accepting a mismatched payment stay with the business, because the money is in the business’s own account.

Switching a gateway off

Turning a gateway off — in a plan, or with the platform-wide switch — hides it at checkout from then on. Payments already started still finish: their returns, webhooks and background checks keep working.

Alovio Payments

$29 · Product page

Try it before you set it up.

A salon on Booknetic SaaS taking rand — book with a bank transfer, then mark it received as the salon. It resets every hour.

Open the sandbox