---
updatedAt: 2026-03-18T14:39:26.000Z
agentTools:
  projectIndex: https://pinpad.docs.netevia.com/llms.txt
---

# Global connection

Your client application will connect to the backend Mediator. And then it will send requests addressed to a certain PIN Pad connected to the Mediator. The PIN Pad, after processing your request, will respond back to the Mediator – and in turn – your app will receive the response.

# Client credentials

In order to connect to the PIN Pad Mediator, you need to have the following credentials (*provided by Netevia*):

* **Client ID**
* **Client Secret**

<br />

# Endpoints

These are the endpoints for the remote Mediator API:

* dev environment: <https://pinpad.netevia.dev>
* production environment: *Coming soon*

<br />

# Connection and communication flow

The following is the general flow for connecting and communicating with the Mediator.\
Detailed information about Mediator's API methods are provided in the [Mediator API](https://pinpad.docs.netevia.com/reference/mediator-api) section.

1. Get the [Access Token](https://pinpad.docs.netevia.com/reference/mediator-api#access-token) using your client credentials. Include that token in each subsequent request.
2. Get the list of [available PIN Pads](https://pinpad.docs.netevia.com/reference/mediator-api#available-pin-pads) currently connected to the Mediator, and their serial numbers.
3. Build a [request message](https://pinpad.docs.netevia.com/reference/message-format) for the PIN Pad and [send it](https://pinpad.docs.netevia.com/reference/mediator-api#pin-pad-request) to the Mediator, specifying the target PIN Pad's serial number. You will receive a request ID from the Mediator as a response.
4. Poll the Mediator to [check if there is a response](https://pinpad.docs.netevia.com/reference/mediator-api#pin-pad-response-check) from the PIN Pad. If there is, [parse it](https://pinpad.docs.netevia.com/reference/message-format) accordingly.

<br />