Connect a payment terminal

1. Choose the provider and supported installation

Select the terminal provider used by this shop. PolCard and eService keep separate configuration. Confirm the supplied terminal model, integration method and provider requirements before rollout; a connected terminal alone does not establish certification.

2. Enter the local connection details

For a network connection, keep the register and terminal on a network that allows them to reach one another. Enter the terminal’s local IP, provider-supplied ECR port and required register identifier. Authorization-host addresses are not the terminal’s local endpoint. Reserve the IP with your network administrator where appropriate.

3. Test the connection and the payment separately

Test the connection and compare the returned device identity with the physical terminal. Save the intended configuration. Use a low-value provider-approved test only when authorized, and follow the physical terminal prompts. The isolated payment tool does not create a normal POS sale or fiscal receipt.

4. Handle an uncertain outcome using the original attempt

Read the final status in POS and the terminal, not just the amount or a communication acknowledgment. Check status before collecting the same amount again. Cancellation, signature decisions and lost communication need a final correlated result; reconnecting must not start another charge.

eService installation note

The eService implementation uses the vendor’s native Android library. Device architecture and the installed build must support it; a JavaScript refresh cannot add a missing native library. Unattended kiosk devices and payment-slip printing have separate provider requirements.