Card terminals in Teltow, Germany

Choose where the customer should pay

At a counter, keeping the terminal beside the till can make payment handover straightforward. Taking it to a table avoids sending customers to a separate checkout. On the move, portability matters, but so do charging, network access and a clear way to identify the correct sale.

For a software partner, the trade-off is not simply fixed versus portable hardware. Ask whether one staff member owns the sale throughout or another person collects payment. A shared terminal needs an unambiguous handover so staff do not charge the wrong order. Confirm which proposed devices support the intended use in Germany.

Separate connectivity from software connection

A terminal’s network connection and its connection to your software are different questions. Network access enables payment communication; a software connection may reduce manual amount entry and help match results to sales. Neither should be assumed from the terminal’s appearance or portability.

Compare a standalone workflow with a proposed connected workflow. Manual entry may involve fewer software dependencies, but staff must check amounts and reconcile records. A connected approach needs confirmed compatibility, agreed status handling and testing. NeroConnect is for connecting software/POS providers and their merchants to payment services; discuss your requirements with the team rather than assuming an existing integration.

• Describe where the terminal will be used and ask which connectivity options are supported.
• Confirm how the amount and sale reference would reach the terminal.
• Ask how completed, declined and uncertain outcomes would be represented in your software.

Worked example: a counter and collection handover

Hypothetical example: a software partner is assessing payments for a Teltow retailer with a sales counter and a separate collection point. Customers choose goods at the counter, but some pay when collecting them. The partner must decide whether each station needs its own terminal or whether a shared portable device fits the staff workflow.

A shared device means staff must locate it and select the right sale before each payment. Separate devices reduce that movement but introduce additional hardware and allocation questions. The partner should compare both options using realistic handovers, not just a successful payment at an empty counter.

• Create two test sales with different totals and collection references.
• Have a second staff member collect payment against the intended sale.
• Check that the correct sale is marked paid and the other remains unpaid.

Plan for uncertainty before repeating a payment

A lost connection or delayed software response can leave staff unsure whether payment completed. Repeating the charge immediately risks creating a second payment. Agree a procedure for checking the authoritative payment status before another attempt, including who staff should contact when they cannot resolve it.

An observable success check is that staff can distinguish a declined payment from an unknown outcome and explain the next step to the customer. Agree who investigates device or payment issues and who investigates the software record, so merchants are not left passing the same question between teams.

Confirm settlement and scope before choosing

A successful terminal payment is not the same event as settlement to the merchant. Ask about settlement timing, applicable charges, reporting references and how refunds or adjustments appear. For German merchants, confirm supported payment methods, EUR arrangements and account requirements directly; do not carry assumptions across from another market.

Your next action is to send NeroPay a short workflow description covering locations of use, staff handovers, existing software and reporting needs. Request confirmation of product availability, devices, connection options, commercial terms and support responsibilities before selecting hardware or promising a merchant a delivery date.