Assign a payment terminal to a merchant
PUT/partner/partner/:partnerId/terminal/:terminalType/:serialnumber
Takes an already created terminal (part of the pool of unassigned terminals) and assigns it to an already existing merchant. A terminal can only be assigned to one merchant at a time. If it is already assigned to another merchant you will receive an error. It is necessary to publish the terminal configuration to the Handpoint gateway after this operation.
Request
Path Parameters
Possible values: non-empty
and <= 50 characters
ID of the partner who owns the terminal.
Possible values: [MPED400
, MPED800
, HILITE
, HIPLUS
, HIPRO
, HIFIVE
, BP50PLUS
, PAXA920
, PAXA80
, PAXA77
, PAXA50
, PAX30
, PAXA35
, PAXA60
, PAXA910
, PAXA920PRO
, PAXA930
, PAXARIES6
, PAXARIES8
, PAXE500
, PAXE700
, PAXE800
, PAXA800
, PAXIM30
, TELPOTPS900
, TELPOTPS988
, TELPOTPS989
, TELPOTPS328
, TELPOTPS300
, TELPOTPS
, VT
]
Type of terminal to be assigned.
Possible values: <= 20 characters
Serial number of the terminal to be assigned.
- application/json
Body
required
The assigment data to be used.
- Array [
- Array [
- ]
- ]
Possible values: [MPED400
, MPED800
, HILITE
, HIPLUS
, HIPRO
, HIFIVE
, BP50PLUS
, PAXA920
, PAXA80
, PAXA77
, PAXA50
, PAX30
, PAXA35
, PAXA60
, PAXA910
, PAXA920PRO
, PAXA930
, PAXARIES6
, PAXARIES8
, PAXE500
, PAXE700
, PAXE800
, PAXA800
, PAXIM30
, TELPOTPS900
, TELPOTPS988
, TELPOTPS989
, TELPOTPS328
, TELPOTPS300
, TELPOTPS
, VT
]
Terminal type supported by the TMS. They may belong to different brands: Pax, Telpo, Datecs or Virtual Terminals.
Possible values: <= 20 characters
The serial number of the terminal.
Possible values: [U
]
The status of the terminal, for assign operation the previous status should be UNASSIGNED.
Possible values: non-empty
and <= 50 characters
ID of your partner profile (provided by Handpoint)
Possible values: non-empty
and <= 20 characters
It is a unique Handpoint ID for the merchant, it must be unique across ALL TMS merchants. Handpoint will provide a range of IDs that can be used for this purpose.
Location of the payment terminal If empty, the merchant's location address will be used.
Address line 1 of the payment terminal If empty, the merchant's address will be used.
Zip code of the payment terminal If empty, the merchant's zip code will be used.
City of the payment terminal If empty, the merchant's city will be used.
Country code Alpha 2 of the payment terminal If empty, the merchant's country code will be used.
Phone number of the merchant associated with the payment terminal If empty, the merchant's phone number will be used.
E-mail associated with the payment terminal If empty, the merchant's email will be used.
Default value: false
Enable the tip functionality for the payment terminals. Only relevant for setting up Datecs terminals, not relevant for PAX or Telpo. This will override the merchant's tip flag value.
Default value: false
Show tip adjustment line in the receipt. Only relevant for setting up Datecs terminals, not relevant for PAX or Telpo. It is only used if tipFlag is true. This will override the merchant's tip flag value.
Use this software version instead of the default one.
Default value: false
Uses the default account selection (checking) on the payment terminal. Only relevant for setting up Datecs terminals in South Africa, not relevant for PAX or Telpo.
customFieldsByProtocol object[]
Custom fields to be used for the terminal configuration. Ask Handpoint about which acquirer custom fields need to be used for your partner profile. If empty, the merchant's custom fields will be used.
Protocol applied to the custom fields.
customFields object[]
Acquirer terminal id customized.
Responses
- 200
- 400
- 401
- 403
- 409
- 500
OK
Bad Request
- application/json
- Schema
- Example (from schema)
Schema
Error code.
Reason of the error.
Message guid of the error.
{
"code": "string",
"reason": "string",
"messageGuid": "string"
}
Unauthorized
- application/json
- Schema
- Example (from schema)
Schema
Error code.
Reason of the error.
Message guid of the error.
{
"code": "string",
"reason": "string",
"messageGuid": "string"
}
Forbidden
- application/json
- Schema
- Example (from schema)
Schema
Error code.
Reason of the error.
Message guid of the error.
{
"code": "string",
"reason": "string",
"messageGuid": "string"
}
Conflict
- application/json
- Schema
- Example (from schema)
Schema
Error code.
Reason of the error.
Message guid of the error.
{
"code": "string",
"reason": "string",
"messageGuid": "string"
}
Internal Server Error
- application/json
- Schema
- Example (from schema)
Schema
Error code.
Reason of the error.
Message guid of the error.
{
"code": "string",
"reason": "string",
"messageGuid": "string"
}