Card terminals in Eberswalde, Germany

Match the terminal to where orders are completed

A counter terminal gives staff a consistent place to finish an order and check the result. Taking payment at a table avoids asking customers to leave their seats, but staff need a reliable way to select the correct bill. Mobile use adds questions about coverage, power and finding an order away from the main workstation.

For software partners serving businesses in Eberswalde and the wider Berlin and Brandenburg area, begin with the merchant’s actual service pattern. Ask which connection options each proposed device supports and test them where payments will happen. Do not assume that a working connection beside the till proves coverage elsewhere.

Choose how order amounts reach the terminal

With a separate terminal workflow, staff may enter the payment amount manually and then update the order. This can keep responsibilities simple, but creates opportunities for incorrect amounts or payments attached to the wrong order. A connected workflow can reduce repeated entry where supported, although its references, status updates and recovery behaviour need checking.

NeroConnect is for connecting software/POS providers and their merchants to payment services. Discuss the proposed order-to-payment journey with the team rather than assuming an existing integration is available. Confirm supported devices, integration scope and what staff will see when a payment succeeds, fails or remains uncertain.

Worked example: an interrupted table payment

Hypothetical example: an Eberswalde café uses a software partner’s ordering system. A customer pays a €42 table bill, but the connection drops before the ordering screen receives a final result. The order still looks unpaid. Asking the customer to pay again immediately could create a duplicate payment.

The agreed procedure should be to check the available transaction record and match the amount, time and order reference before retrying. If the result cannot be established, staff should follow the provider’s escalation procedure and explain the uncertainty to the customer. The software partner should define how the confirmed result will later be attached to the original order.

• Record the order reference and the payment attempt.
• Check the transaction outcome through the agreed source.
• Resolve the original attempt before starting another payment.

Separate completed orders from settled funds

An order marked paid, a successful payment transaction and funds reaching the business’s account are different records. Reconciliation should connect them without treating them as interchangeable. Ask which references appear in transaction reports and settlement records, and how fees, refunds and reporting periods are represented.

Before choosing a service for a German business, confirm settlement timing, payout currency, applicable charges and account requirements with the team. Decide who reviews unmatched items: the merchant, software partner or payment support team. Staff should know what information to collect without copying customers’ card details into support messages.

Prove the workflow before committing

Run agreed tests covering a successful payment, a declined attempt, an interruption and a refund where supported. An observable success check is that each completed test payment matches one intended order, uncertain attempts remain visible for review, and the available reporting lets the merchant trace the outcome. Check staff permissions and handover between shifts too.

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. Existing software partners should confirm whether their proposed arrangement fits rather than assuming a software change is necessary.