Update terminal settings

patch /stores/{storeId}/terminalSettings

Updates payment terminal settings for the store identified in the path. These settings apply to all terminals under the store, unless different values are configured for an individual terminal.

  • To change a parameter value, include the full object that contains the parameter, even if you don't want to change all parameters in the object.
  • To restore a parameter value inherited from a higher level, include the full object that contains the parameter, and specify an empty value for the parameter or omit the parameter.
  • Objects that are not included in the request are not updated.

To make this request, your API credential must have the following role:

  • Management API—Terminal settings read and write

Endpoint destination URL

https://management-test.adyen.com/v1/stores/{storeId}/terminalSettings
Click to copy

Path parameters

storeId string Required

The unique identifier of the store.

Request parameters

cardholderReceipt

Settings to define the header of the shopper receipt.

connectivity

Settings for terminal connectivity features.

gratuities [Gratuity] array

Settings for tipping with or without predefined options to choose from. The maximum number of predefined options is four, or three plus the option to enter a custom tip.

hardware

Settings for terminal hardware features.

nexo

Settings for a Terminal API integration.

offlineProcessing

Settings for offline payment features.

opi

Settings for an Oracle Payment Interface (OPI) integration.

receiptOptions

Generic receipt settings.

receiptPrinting

Transaction outcomes that you want the terminal to print a merchant receipt or a shopper receipt for.

signature

Settings to skip signature, sign on display, or sign on receipt.

surcharge

Settings for payment surcharge features.

timeouts

Settings for device time-outs.

wifiProfiles

Remote Wi-Fi profiles for WPA and WPA2 PSK and EAP Wi-Fi networks.

Response parameters

After submitting a call, you receive a response message to inform you that your request was received and processed.

Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.

HTTP Responses

  • 200 - OK

    The request has succeeded.

    Show more Show less
  • 400 - Bad Request

    A problem reading or understanding the request.

    Show more Show less
  • 401 - Unauthorized

    Authentication required.

    Show more Show less
  • 403 - Forbidden

    Insufficient permissions to process the request.

    Show more Show less
  • 422 - Unprocessable Entity

    A request validation error.

    Show more Show less
  • 500 - Internal Server Error

    The server could not process the request.

    Show more Show less
  • Request
  • Click to copy
  • Response
  • Click to copy