Pairing
Pairing is the process by which we connect the physical terminals (E.g. A920) to our backend.

We consider pairing to be step 2 of your integration, after Authentication. If you have not yet authenticated it is recommended that you complete that first.

You must pair a terminal before you can send it any transactions.

There are two ways to pair to our system: non-legacy and legacy. We strongly recommend that new integrations use the non-legacy pairing, but we have included the legacy pairing flow for those who have already implemented it or are maintaining an existing integration. You can find both flows below.

Pairing a New Terminal (Non-Legacy Api V2)
This is the new preferred pairing flow.
Pre‑Requisites
  1. Token: This is required to call the API. (Obtained: You will request this using the application Authentication flow.)
  2. A920 Terminal (Obtained: During on boarding)
Summarised Flow
  1. The terminal connects to the back-end.
  2. The terminal requests a pairing code.
  3. The API receives the pairing request via an HTTP call.
  4. The API validates the pairing code.
  5. If the code is valid, the terminal disconnects from the pairing server.
  6. The terminal connects to the transaction server.
  7. The terminal is now successfully paired.
Step By Step
For a deeper description or understanding of what your actions are doing click the step to expand.

You have now successfully paired your first terminal.