HairConnect Manual Log in

Buckaroo and the payment terminal

Updated on 2026-11-15

Buckaroo (betaalterminal) (payment terminal)

Leest elke nacht de kaartbetalingen van uw betaalterminal en de stortingen van Buckaroo, en legt ze per dag naast de bonnen in het kassaboek. Alleen lezen: er vertrekt geen bedrag naar de terminal. (Reads the card payments of your payment terminal and Buckaroo's payouts every night, and lays them next to the receipts in the cash journal, day by day. Read-only: no amount is sent to the terminal.)

Buckaroo processes the payments of a card terminal and then pays the money out to your bank account. If you got your terminal through Optios (Optios PAY), look at your bank statement: if the card money comes from Stichting Derdengelden Buckaroo, this is your integration.

What it does:

  • Every morning at 06:30 HairConnect reads the terminal's payments of the past seven days, and Buckaroo's payouts.
  • Every payment is laid next to a card payment on a receipt of the same register day. Per day, receipts, terminal and payout come together in the Kaartbetalingen (card payments) table of the cash journal. How that works and what the statuses mean is in Cash journal and transactions.
  • Buckaroo's payouts on your bank account are recognised. They disappear from Overschrijvingen → Niet gekoppeld (transfers → not matched): they are not customers paying a receipt.

What it does not do: no amount is sent to the terminal, no mail is sent, no receipt is created and no amount on a receipt changes.

A key that can only read

  1. Sign in to My Buckaroo (my.buckaroo.io).
  2. Create a new API key.
  3. Tick only the read rights for sales and payouts — in the Dutch-language portal Verkopen: Lezen and Uitbetaling: Lezen. Nothing more is needed, and a key that cannot change anything cannot change anything if it ever leaks either.
  4. Copy the key. It starts with apk_.

Which rights you can tick in My Buckaroo depends on your role there. If you do not see the two rights, ask whoever manages the Buckaroo account.

Setting up

Instellingen → Koppelingen → Betalen → Buckaroo (betaalterminal) → Instellen (Settings → Integrations → Payments → Buckaroo (payment terminal) → Set up). Only the owner can open this screen.

Field Required Explanation
API-sleutel (API key) yes The key from above. It is stored encrypted, for this salon only.
Rekening waarvan Buckaroo stort (account Buckaroo pays from) no After the first night HairConnect proposes an account here: the account that every morning pays out exactly what the terminal saw the day before, with how many payouts match to the cent. Click Voorstel overnemen (take over the proposal) and save. If you leave it empty, the receipts are still laid next to the terminal, but the payouts are not checked.
Betaalmiddelen die over de terminal lopen (payment methods that go through the terminal) no Bancontact and the credit card by default. Only what is paid by card at the counter: a payment with a QR code or online does not go through this terminal.
Geschiedenis ophalen vanaf (niet verplicht) (fetch history from, optional) no Once: the next night HairConnect reads the payments from this day, for instance the start of the financial year. After that every night looks back seven days. Empty: only the past seven days.
Winkel-id (niet verplicht) (store ID, optional) no Only if more than one business hangs under the same Buckaroo account: then HairConnect only reads the payments of this store ID.
TID van de terminal (niet verplicht) (terminal TID, optional) no Only if a second terminal that does not belong to this salon hangs under the same account. The TID is on the terminal's slip.

Verbinding testen (test connection) reads one payment from the past thirty days and requests the payouts. If it works, you read for instance De sleutel werkt. Laatste betaling: € 64,00 op 04/11/2026 om 14:58. De uitbetalingen lezen lukt ook. (The key works. Last payment: € 64.00 on 04/11/2026 at 14:58. Reading the payouts works too.) If Buckaroo refuses the key, the test says why: a key that was not pasted in full, or a key without the two rights. The test only reads, too.

The first time, and after a gap

The nightly round looks back seven days. If you want the card check further back, for instance from the start of the financial year, fill in Geschiedenis ophalen vanaf. The next night HairConnect fetches everything from that day, in chunks of a month; the nights after that, seven days again.

If no round ran for a while, because the module was off or the server was down, the next round automatically fetches those days too, from where the previous one stopped.

A day before the first fetch does not appear in the Kaartbetalingen table. Otherwise every card receipt of that day would look like a difference, while the terminal simply had not been read yet. Today is not in it yet either: a day that is still under way would show a terminal that saw too little.

While it is off

If the module is off, or on without a key, HairConnect asks nothing of Buckaroo. The Kaartbetalingen table disappears from the cash journal, so does the tile on the Overzicht (overview), and the Kaartcontrole (card check) says it is off. What was already fetched stays stored.

What someone confirmed in the Kaartcontrole stays as it was confirmed.