Alovio Payments · 8 pages
Alovio Payments Page 06 of 08 5 min read

Transactions & refunds

The Transactions list, what each status means, the payments that need a look, and how full, partial, pending and lost refunds work.

On this page

Alovio Payments → Transactions lists every payment from every connected plugin: the online gateways and your manual methods. Filter by status or gateway, or search by reference, e-mail or a manual payment’s code. Test payments carry a Test mark, and a payment whose booking has since been canceled carries Booking canceled.

Fig. 1Transactions in the hub: one payment needs a look, filters by status and gateway

A business on Booknetic SaaS sees the same list for its own payments under Payments → Transactions in its Booknetic panel.

Fig. 2Transactions in a business's Booknetic panel

Statuses

StatusWhat it means
StartedThe payment exists; the gateway’s checkout has not been opened yet.
WaitingThe checkout is open, or a slow method (a bank transfer, say) has not confirmed yet. Background checks keep asking — don’t ask the customer to pay again. For a manual method: the money has not been marked as received yet.
PaidThe gateway confirmed the amount, the currency and the reference.
FailedThe gateway says the payment failed.
CanceledThe customer backed out and the gateway confirmed that nothing was paid.
ExpiredThe time ran out with nothing paid. A late payment can still turn it into Paid.
Check amountThe gateway says paid, but the amount, currency or reference does not match — or, for a manual method, the amount marked as received is not what the booking costs. Never marked paid on its own.
Paid too latePaid after the purchase it was for had already been dropped.
Partly refunded / RefundedSome, or all, of the money went back to the customer.

The filters group these: Paid, Waiting, Needs a look, Not paid (failed, canceled or expired) and Refunded.

Needs a look

Three different problems land here, and each has its own action:

  • Amount did not match → accept or refund. Look at the payment in the gateway’s dashboard first (for a manual method, at what actually arrived). If you accept what was received, Accept and mark paid marks what it paid for as paid, and the timeline records that it was accepted by hand. Otherwise refund it.
Fig. 3A payment held because the amount received differs
  • Paid too late → refund, or set it up by hand. The customer paid after the waiting time ran out, so nothing holds this money.
  • Paid, booking canceled → rebook or refund. The money was kept for a booking that is now canceled in Booknetic.

A payment can also show Booknetic was not updated when Booknetic reported an error while being told about it. Alovio Payments retries by itself; Try now retries straight away.

A payment’s page

Each payment opens a page of its own: what was received and refunded, what confirmed it, when the next automatic check runs, the reference and the gateway’s transaction id, the payment window, and a What happened timeline of everything the gateway, the webhook, the checks and the people involved reported. Check now asks the gateway about the payment immediately.

Fig. 4A Paystack payment's page in the hub, with its refund and timeline

A manual payment’s page shows its payment code instead, with Mark as received and Cancel booking; there is no gateway to check. See Manual methods.

Refunds

Refunds go through the gateway, from the payment’s page: Refund…, then the amount, an optional note (kept here and sent to the gateway), and Also cancel the booking. Review, then send — a refund cannot be undone.

Fig. 5The refund form: amount, note and Also cancel the booking
  • Full or partial. Lower the amount for a partial refund. You can refund up to what has not been refunded yet; refunds still in progress count against that, so a double click or a second person cannot send the same money twice.
  • The booking follows once the gateway confirms. Its paid amount goes down by the refund (spread over the appointments the payment covered). After a full refund Booknetic shows it as not paid; after a partial one it stays paid with the smaller amount, which Booknetic shows as a deposit.
  • Also cancel the booking is on for a full refund and off for a partial one. When it is on, the booking moves to the status your Booknetic settings use for failed payments — or to canceled, if none is set — once the gateway confirms the refund.
  • Booknetic’s own workflows run. The change goes through Booknetic like any other booking change, and Alovio Payments adds a Payment refunded workflow event of its own.
  • Packages and gift cards are refunded as money only: the package or gift card stays with the customer. Adjust it by hand if needed.
  • Manual methods have nothing to send the money back through: their refund is a record. The booking follows at once, and you pay the money back yourself.

Pending refunds

Gateways often take a while to finish a refund. Until they do, it shows Processing: “Refund sent. The gateway is processing it; the booking is updated once it completes.” The gateway’s webhook or the background checks close it, and only then do the payment and the booking change.

Fig. 6A partial Paystack refund still processing

When the gateway does not answer

If the gateway does not answer while a refund is being sent — a timeout, a server error — the refund may or may not have been made. It is marked Answer lost: it is not counted as failed (sending it again could pay twice), it is not booked, and its amount stays reserved. Check the payment in the gateway’s dashboard, then choose It was refunded or It was not.

If the gateway refuses a refund outright, the refund is marked failed, the gateway’s message is shown, and nothing else changes.

Refunds made in the gateway’s dashboard

A refund you make directly in the gateway’s own dashboard is not booked here: the payment and the booking stay as they were (on Paystack, with the webhook set up, the refund is noted in the payment’s timeline). Refund from Alovio Payments so the booking follows.

Who can refund

On a regular site, refunds are made in the hub by site administrators. On Booknetic SaaS the money is in each business’s own gateway account, so the business refunds it from Payments → Transactions in its own Booknetic panel; the platform operator can see every payment and re-check it, but the refund is the business’s. Staff roles can be allowed to view payments, or also to refund and settle them. See Booknetic SaaS.

How long records are kept

The payment records are always kept. The gateways’ raw answers — already stripped of keys and card data — help when you investigate a payment and are deleted after the number of days set under Alovio Payments → Settings (90 by default). Deleting the plugin keeps everything, unless you turn on Delete everything when the plugin is deleted.

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