It is now possible for a POI to have a null merchant_id field. This is to allow use-cases where a POI is frequently used by different Merchants. A Merchant ID must be sent in the transaction messages if this option is used.

15/10/2025

The country_code field on addresses must now be a valid ISO 3166-1 alpha-3 code.

9/10/2025

Removed account_id from request bodies to create and update resources.

3/10/2025

GET query parameter on entities that can have configurations allows either a 'fragment' (config for that particular item) or 'coalesced' (config including details from parent POI Groups etc)

2/10/25

A second bug affecting transaction processing when a merchant did not have a configuration but the POI did

Address validation is now stricter; see Swagger for details

29/7/25

A bug affecting transaction processing when a merchant did not belong to a merchant group that resulted in the configuration being invalid

28/7/25

Added missing methods to /pois and /poi-groups swagger documentation

Allowed the creation/updating of Merchants and POIs with a nested Address without the `configurations_public` permissions

Added an `x-permissions` property to the swagger documentation to indicate the permissions required for each method

24/7/25

Removed unused account_id field from Users

16/7/25

Shift4 Dynamic Terminal Support

API Changelog

Introduction

Permitted POI Devices and Solutions

Diagnostic Exchange

Requests and Responses

Single Tap with Online PIN