Alovio Payments · 8 pages
Tap Payments for Booknetic: setup
Connect Tap Payments to Booknetic through Alovio Payments: Gulf currencies, the secret key, the optional merchant ID, and why there is no webhook to set up.
On this page
Tap Payments takes payments on its own hosted page, where the customer picks a method: KNET, mada, Benefit, cards, Apple Pay and others, whichever Tap has switched on for your account. Alovio Payments creates a Tap charge for each payment, sends the customer to Tap’s page, and marks the booking paid once Tap confirms the charge.
Countries and currencies
| Booknetic currency | Where it is used |
|---|---|
| KWD | Kuwait |
| SAR | Saudi Arabia |
| AED | United Arab Emirates |
| BHD | Bahrain |
| OMR | Oman |
| QAR | Qatar |
| USD | US dollars, where Tap accepts them for your account |
In any other currency, Tap is not offered at checkout. KWD, BHD and OMR have three decimals, and amounts are sent to Tap exactly as Booknetic calculated them.
Where the keys go
- A regular Booknetic site: Alovio Payments → Gateways → Tap Payments, under Set up Tap Payments → Enter your API key. The Tap tab in Booknetic → Settings → Payment methods edits the same values.
- Booknetic SaaS: every business enters its own keys in its own Booknetic → Settings → Payment methods. See Booknetic SaaS.
| Field | What goes in it |
|---|---|
| Mode | Test (no real money moves) or Live. |
| Test secret key | Starts with sk_test_. From your Tap dashboard. |
| Live secret key | Starts with sk_live_. |
| Merchant ID | Optional. Fill it in only when Tap gives you one to send with each charge, for example on a Tap platform account. |
A publishable key (pk_…) is refused: enter the secret key. A key that belongs to the other mode is
refused too. Save & check saves the keys and asks Tap whether they work.
No webhook to set up
Every Tap payment carries its own webhook address, so there is nothing to paste into the Tap dashboard: the Tap page in the hub has no webhook step. Tap signs each webhook with your secret key, and the plugin checks that signature before reading anything from it. A webhook only reaches your site when the site is reachable from the internet; without it, payments are still confirmed when the customer comes back and by the background checks.
What the customer sees
- Tap needs the customer’s e-mail address. When a customer books without one, the business’s own address is sent instead, and the payment’s timeline says so.
- Tap’s page stays open for 5 to 60 minutes: the booking’s payment time limit, kept within what Tap allows.
- If the customer closes Tap’s page, Tap reports the payment as cancelled and the booking panel offers to try again. A declined card is reported as failed, with the same offer.
Refunds
Full and partial refunds are sent through Tap from the payment’s page. Tap usually answers at once; when a refund is still pending at Tap, the background checks ask about it until it finishes. See Transactions & refunds.
$29 · Product page
A salon on Booknetic SaaS taking rand — book with a bank transfer, then mark it received as the salon. It resets every hour.