Alovio Payments · 8 pages
Alovio Payments Page 02 of 08 4 min read

Paystack for Booknetic: setup

Connect Paystack to Booknetic through Alovio Payments: currencies, test and live keys, the webhook URL, the optional signing secret and payment channels.

On this page

Paystack takes payments on its own hosted checkout. Alovio Payments starts the payment, sends the customer there, and marks the booking paid once Paystack confirms it.

Fig. 1The customer picks Paystack at Booknetic's confirm step
Fig. 2Paystack's checkout (test mode)

While the customer pays, the booking panel waits for the answer, and shows its own finish screen once Paystack confirms the payment.

Fig. 3The booking panel while the customer pays in Paystack's window

Currencies

Paystack is offered for NGN, GHS, KES, ZAR and USD. Your Booknetic currency has to be one of them: in any other currency, Paystack is not offered at checkout. XOF is not supported.

Where the keys go

  • A regular Booknetic site: Alovio Payments → Gateways → Paystack, under Set up Paystack → Enter your API key. The Paystack tab in Booknetic → Settings → Payment methods edits the same values, so either place works.
  • Booknetic SaaS: every business enters its own keys in its own Booknetic → Settings → Payment methods. See Booknetic SaaS.
FieldWhat goes in it
ModeTest (no real money moves; customers see Paystack’s test checkout) or Live.
Test secret or restricted keyStarts with sk_test_ or rk_test_. Paystack recommends a restricted key.
Live secret or restricted keyStarts with sk_live_ or rk_live_.
Test / Live webhook signing secretOptional. Starts with whsec_. Needed for webhooks when you use a restricted key (below).
Payment channelsOptional: card, bank account, bank transfer, USSD, QR code, mobile money, EFT, Apple Pay, Capitec Pay, PayAttitude. Leave it empty to offer everything your Paystack account supports.
Fig. 4Paystack's keys in Booknetic's payment settings

Booknetic’s new React admin (the preview Booknetic 6.2 opens with &ui=new) shows the same fields:

Fig. 5Paystack's keys in Booknetic's new React settings

Use the secret or restricted key, never the public one (pk_): a public key is refused. A key that belongs to the other mode is refused too — a live key while Test is selected, or the other way round.

Save & check saves the keys and then asks Paystack whether they work. If Paystack refuses a restricted key, the message says the key is missing the permission to verify transactions.

The webhook

The webhook lets Paystack tell your site the moment a payment succeeds. It is optional but recommended — it matters most for bank transfers and mobile money, which can confirm minutes or hours later. Without it, payments are still confirmed when the customer comes back and by the background checks, just more slowly.

  1. Copy the Webhook URL from the Paystack page in the hub (or from the Paystack tab in Booknetic’s payment settings). On a regular site it looks like https://your-site.example/wp-json/alovio-payments/v1/notify/paystack. On Booknetic SaaS each business has its own URL, shown in its own payment settings.
  2. In the Paystack dashboard, open Settings → API Keys & Webhooks.
  3. Paste the URL into Test Webhook URL — and into Live Webhook URL when you go live.
  4. Optional but recommended: create a webhook signing secret (whsec_…) there and enter it in the form.

The hub’s Paystack page shows Notifications are being received once the first one arrives.

One URL for both modes. You can put the same URL in Paystack’s test and live settings. Each event says which mode it comes from and is checked with that mode’s keys; an event from the mode you are not using is acknowledged and ignored.

How webhooks are verified.

  • With a signing secret (whsec_), only Paystack’s newer signature is accepted, and an event more than five minutes old is refused.
  • Without one, the classic signature made with your secret key (sk_) is checked.
  • A restricted key without a signing secret means no webhooks at all: Paystack never signs with a restricted key. That is a supported setup — payments are confirmed by the customer’s return and the background checks.

Paystack’s dashboard has one webhook URL per mode. If you already use that Paystack account for another site, you may not be able to point it here — the webhook is optional for exactly that reason.

What the customer sees

The customer picks Paystack at the confirm step and pays on Paystack’s checkout. A declined card keeps them on Paystack’s page to try again; if they cancel there, the payment is marked failed and they can try again in Booknetic.

Paystack needs an e-mail address for every payment. If the customer did not give one, the business’s address is used instead (on a regular site, the site’s admin e-mail), so Paystack’s receipt goes there; the payment’s timeline notes it.

“Pass charges to customers”. If your Paystack account adds Paystack’s fee on top of the price, the payment still matches — it is compared with the amount that was asked for. A payment of less than was asked for is held under Needs a look.

Refunds on Paystack

Paystack refunds in full or in part, and its refunds are not instant: a refund shows Processing until Paystack completes it, which can take several minutes, then the booking is updated. If Paystack needs the customer’s bank details to finish a refund, it stays Processing until you complete it in the Paystack dashboard. See Transactions & refunds.

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