Terminal ID

Learn how to create, edit and order terminal

The terminal ID is a unique identifier that is assigned to each POS terminal being registered under the desired MID. Several TIDs can be registered and maintained under a single MID. For physical POS terminals, the most common case is when a single point of sale, treated as a Merchant at DECTA systems, has multiple cash registers, each supplied with a POS terminal.

The request POST/v1/api/merchant/{merchantID}/addTerminal creates a new Terminal object. Upon successful registration, DECTA will issue a TID that will be used for setting up POS terminal configuration by either the TSP (Terminal Service Provider) or relevant service company.

In response, the requester receives a Terminal ID (TID).

The POS terminal record and TID can only be created after the relevant Legal Entity and Merchant entries have been created, and all contractual terms and conditions have been signed off on, met and set up. A POS terminal can only be created for a Merchant that is assigned the relevant parameters in DECTA systems that allow treating a Merchant as classified for physical POS transaction processing to avoid registering TIDs to e-commerce Merchants.

The POS terminal model should correspond to models specified in the agreements between DECTA/Acquirer/Merchants to ensure that only models that are Level 3 certified at payment institutions (Mastercard and Visa) are operating within the scope of the solution.

A request to create a POS terminal must contain information about the:

  • Terminal type: QCash, Retail, UCAT
  • Terminal service provider (TSP)
A Terminal ID (TID) is created in DECTA systems based on a pre-defined structure where prefixes specifying TSP and terminal type are assigned automatically while the suffix for the POS terminal number can be generated either by DECTA during the TID creation process or by the party that sends the TID creation request.

The request GET/v1/api/merchant/{merchantID}/terminals is used to retrieve information about TID objects previously registered for a particular MID. It is required to submit a valid MID. In response, the requester will receive a list of all TIDs under the given MID.

The request PATCH/v1/api/merchant/{merchantID}/terminals is used to manage the status of TIDs registered under MIDs. It is required to submit a valid TID and the desired status value. In response, the requester receives confirmation of a status change with an updated status value.

The following statuses are supported:

    ACTIVE(0): means that the POS terminal associated with the desired TID is in working status and ready for operations. Is assigned by default when a new TID is created. Can be changed to STOPPED or REMOVED.
    STOPPED(1): is used when it is necessary to temporarily suspend the operations of the POS terminal associated with a TID. Can be changed to ACTIVE or REMOVED.
    REMOVED(2): is used when a POS Terminal under the TID has been terminated or removed completely. Can be changed to ACTIVE or STOPPED.

POS terminal ordering at Terminal Service Provider

After the Merchant and POS terminal data are transferred to DECTA via Acquiring endpoints, a task will be generated in DECTA systems that enables POS terminal registration and ordering at TSP systems. After that:

    A physical POS terminal can be ordered from TSP:
  • • A physical POS terminal order is processed within standard EET (UTC/GMT +2 hours) working hours on business days
    The physical POS terminal is delivered to the merchant’s point of sale specified in the data transferred via API:
  • The physical POS terminal delivery to the merchant’s specified location takes place within standard EET (UTC/GMT +2 hours) working hours on business days. Depending on the contractual conditions of the Terminal Service Agreement:
    • POS terminal delivery takes place within a specified period of time: it usually depends on the number of POS terminals being ordered per specified period
    • o A TSP representative contacts the Merchant using the credentials specified in the data transferred via API to agree upon the time and date of the TSP representative’s visit to the Merchant’s point of sale
  • Any issues/incidents the Merchant might have with the installed POS terminal can be resolved by calling the contact numbers specified on each Terminal and accordingly in the Agreement between TSP and the Merchant
  • If any further actions with the physical POS terminal are needed, such as dismounting, replacement or a location change, are processed in accordance with the Merchant’s agreement with the relevant TSP
Jump to
  • Create a Terminal ID
  • Get a Terminal List
  • Change Terminal ID Status
  • POS terminal ordering at Terminal Service Provider