Card terminals in Quickborn, Germany

Start with the route from bill to payment

A counter terminal gives staff a fixed payment point, but guests may have to leave their table and queue. Taking a terminal to the table keeps payment close to the guest, but introduces battery, coverage and device-sharing decisions. For collection orders, consider whether a shared counter would obstruct table-service staff.

Map a busy service before choosing hardware. Who brings the bill, retrieves the terminal and checks the outcome? If several servers share one device, identify where it returns after each payment. Ask which terminal options are available for your German business rather than assuming every advertised device or feature is offered.

Test the connection where guests actually sit

Ask which connection methods the proposed terminal supports and what each requires. A working connection beside the router does not establish reliable operation at a rear table or outdoor seating area. If mobile connectivity is offered, confirm any associated charges and coverage requirements.

Agree a fallback for an unavailable connection. Staff should know how to check an uncertain transaction before asking the guest to pay again. Do not assume a terminal can accept payments without connectivity; ask the provider what happens during an interruption and how pending outcomes are resolved.

• Request a demonstration or agree how coverage will be checked before committing.
• Include the counter, furthest table and any outdoor payment location.
• Ask how connection failures and unresolved transactions appear to staff.

Make shared terminals work during a busy service

Hypothetical example: a Quickborn restaurant takes table payments while handling collection orders at its entrance. On a busy evening, the only terminal is carried to a rear table just as a collection customer arrives. The buying question is whether another device is justified or a clear handover routine would be sufficient.

Compare those choices against actual staff movement and likely queues, not just device count. A second terminal introduces another cost and charging responsibility. With one shared device, define priority and its return point. If guests want separate payments, ask how staff can track the remaining bill without assuming automatic POS synchronisation.

• Rehearse a table payment followed immediately by a collection payment.
• Check that another staff member can identify the payment outcome and remaining bill without guessing.

Separate payment confirmation from settlement

A successful terminal payment and money arriving in the business account are different stages. Ask about settlement timing, cut-off times, weekend or public-holiday handling and any circumstances that could delay funds. Request terms applicable to your business in Germany, including the settlement currency.

Also ask how transactions, refunds and charges appear in reports. Your closing routine should let staff match confirmed payments to restaurant bills and investigate differences. If a guest queries a payment, staff need a transaction reference and a clear escalation route, rather than relying only on the guest's banking screen.

Compare the full offer, not just the terminal

Request a written breakdown of terminal costs, processing charges, contract terms, support arrangements and replacement procedures. If you need the terminal to work with existing restaurant software, ask for confirmation of the specific supported setup. Do not assume a connection is available merely because both products handle payments.

NeroPay offers card terminals and payment services. With an eligible NeroPay card terminal, NeroPOS, NeroWeb and NeroBooking software can be included without an additional software subscription charge. Terminal costs, payment processing charges, eligibility and applicable terms still apply. Your next action is to send the team your service layout, current POS details and payment requirements so availability, supported devices, commercial terms and pricing can be confirmed.