Terminals

Introduction

Our SDKs are not the only way a payment can be completed using Sticitt. An alternative option is to post the PaymentID to one of our Sticitt terminals, thereby enabling card present, tap- or scan to pay transactions to complete the payment.

Retrieve terminals

Should you not have the terminalIDs required to push a payment to a terminal, or you would like to provide the user the option to select a terminal, a list of all available terminals per merchant can be retrieved:


GET	/v1/terminals/merchantID


merchantID	Required: Your unique MerchantID will be provided separately

Successful response body

[
  {
    "terminalID": "5ad56279-654d-4568-be03-172a0fdad34e",
    "defaultReference": "Terminal 1",
    "terminalName": "External Tuckshop Blue Terminal"
  },
  {
    "terminalID": "4ad56279-654d-4568-be03-172a0fdad34e",
    "defaultReference": "Terminal 2",
    "terminalName": "External Tuckshop Red Terminal"
  }
]

Submit payment to terminal


POST	/v1/terminal/submit-payment

Post body

{
  "terminalID": "4ad56279-654d-4568-be03-172a0fdad34e",
  "paymentID": "968a5051-5b6a-4ef1-8c9a-87e236a6a877"
}

Possible responses

Status Code	Description	Reason
200	Success
400	Bad Request	At least one of the arguments are invalid
401	Unauthorized	Token invalid, expired or missing
404	Not found	The TerminalID/PaymentID provided could not be found
409	Conflict	The terminal is offline or busy processing another payment

Payment completion

Notification of payment completion will occur using the Webhooks.

Last modified: 20 February 2025