SHIFT4 Commerce Engine for Cloud Troubleshooting Guide

Some Shift4 properties do not use the UTG at all. They run on Commerce Engine for Cloud — Shift4’s cloud middleware, which reaches the card terminal directly over the internet. There is no gateway software on a property PC, no certificate, and no local IP address to maintain. This guide explains how to recognise a Commerce Engine property, how to support it, and the one setting that must never be filled in.

1. What Commerce Engine for Cloud is

Commerce Engine for Cloud (often shortened to CE or Commerce Engine) is Shift4’s modern, hosted alternative to the UTG. Instead of installing gateway software on a Windows PC at the property, Shift4 talks to the card terminal over the internet from their own cloud.

Front desk browser
Stayflexi PMS

▼ charge request

Stayflexi servers
the transaction is sent from our backend, not from the browser

▼
HTTPS to Shift4’s cloud API
identified by terminal serial number and manufacturer

Shift4 Commerce Engine cloud
locates the terminal and authorises the card

▼ over the property’s internet connection

Card terminal at the property
for example a PAX device — shows the EMV prompt and amount

What this changes for support

	UTG properties	Commerce Engine properties
Gateway software	UTG installed on a property Windows PC	None — nothing to install, start or restart
Who sends the transaction	The front desk browser, to a PC on the same local network	Stayflexi’s servers, to Shift4’s cloud
Static IP address	Required. IP drift is the top cause of outages.	Not required. Nothing breaks when an IP changes.
SSL certificate	Self-signed cert must be generated and trusted on each PC	None to manage
Terminal identified by	API Terminal ID, routed by the local UTG	Terminal serial number + manufacturer
If the property PC is off	Card payments stop	No effect — the PC is not in the path
If the terminal loses internet	Local network may still work	Card payments stop until it reconnects
Front desk can fix it?	Often — restart the UTG service	Usually only power and internet on the terminal itself

Commerce Engine properties are far less fragile. Most of the classic Shift4 escalations — “lane closed after a reboot”, certificate errors, UTG service not running — simply cannot happen on Commerce Engine. If a property is on CE, do not go looking for a UTG.

2. Which mode is this property on?

Open Meta → Configure Custom Payment Gateway Information for the hotel and look at three fields.

Shift4 Utg Url	Terminal Serial number	Terminal Manufacturer	Verdict
blank	filled, e.g. `2210184124`	filled, e.g. `PAX`	Commerce Engine for Cloud. Correct and expected. This guide applies.
filled, e.g. `https://192.168.1.14:277/`	blank	blank	UTG property. Use the UTG troubleshooting guide instead.
blank	blank	blank	Not configured. Card terminal payments cannot work. Escalate to Stayflexi Ops.
filled	filled	filled	Ambiguous — raise it. When a UTG URL is present it wins, and the property runs in UTG mode regardless of the serial number. Ask Ops to confirm which mode is intended and clear the other field.

The single most important rule in this guide: never put an address into “Shift4 Utg Url” on a Commerce Engine property.

The UTG URL field is what decides the mode. If it is blank, Stayflexi sends the transaction to Shift4’s cloud. The moment anything is typed into it, the property silently switches to UTG mode and starts trying to reach gateway software that does not exist. A blank UTG URL on a Commerce Engine property is not a missing setting — it is the setting.

3. The configuration fields

For a Commerce Engine property, Meta → Configure Custom Payment Gateway Information should look like this.

Field	Value	Notes
Choose Active Payment Gateway	`SHIFT4`	Same for both modes
Auth token	from the Shift4 partner portal	Used once, to generate the access token
Shift4 Utg Url	leave blank	Blank is what selects Commerce Engine. See the rule above.
Shift4 Access Token	generated value	Produced by Generate access token from the Auth token
Shift4 API Terminal Id	e.g. `0002`	Supplied by Shift4
Shift4 Terminal Serial number	e.g. `2210184124`	Printed on the terminal, usually on a label on the underside or back. This is how Shift4’s cloud finds the device.
Shift4 Terminal Manufacturer	e.g. `PAX`	The device maker. Must match what Shift4 registered.

Generating the access token

This step is identical for both modes. Confirm the merchant is visible on the Shift4 partner portal, paste the Auth token into Meta, and click Generate access token, then Save.

If you see AuthToken not valid ENGINE27S7, the auth token is not valid. Use the Reissue token button in the partner portal to generate a fresh one and retry. If reissuing also fails, escalate to Shift4.

The serial number and manufacturer must match Shift4’s own records exactly. Stayflexi does not discover or register terminals — these values are typed in by hand and sent to Shift4’s cloud as-is. A single wrong digit means Shift4 cannot find the device, and the charge fails with a “device not connected” error.

4. Front desk: the three-minute check Front desk

On a Commerce Engine property there is no gateway software to restart, so the checklist is short. Almost every failure is the terminal’s power or internet connection.

Step 1 — Look at the terminal

Is it powered on and showing its normal idle or Shift4 screen? If the screen is blank, check the power cable and the outlet.

Step 2 — Check the terminal’s internet connection

This is the critical one. The terminal talks to Shift4 over the internet directly, so it needs a working connection of its own.

Wi-Fi terminal: confirm it still shows a Wi-Fi signal and is joined to the right network. A changed Wi-Fi password will silently drop it.
Ethernet terminal: reseat the cable at both the terminal and the switch, and confirm a link light.
Mobile/LTE terminal: check the signal indicator.

Confirm the property’s internet is up generally — if staff cannot load a website, the terminal cannot reach Shift4 either.

Step 3 — Reboot the terminal

Power the terminal off and on, and wait for it to return to its idle screen and reconnect. Give it a full minute before testing.

Step 4 — Run a $1 test

From the Stayflexi folio, run a $1 card transaction. The terminal should light up and display the amount. If it does, void or refund the test and you are done.

If it still fails, note the exact on-screen error message and raise a ticket. Include the terminal’s serial number.

What you do not need to check on a Commerce Engine property: the back-office PC, any “Shift4 UTG2” service, Windows services, certificates, or the PC’s IP address. None of them are in the payment path. If someone asks you to restart the UTG on a CE property, they have the wrong guide.

5. Error decoder

What you see	What it means	What to do
“Commerce Engine For Cloud device not connected. Please contact Support.”	Shift4’s cloud cannot reach the terminal. The card was not charged. Either the terminal is offline, or the serial number and manufacturer in Meta do not match a device Shift4 knows about.	Front desk: work through the three-minute check above. If the terminal is definitely powered and online, escalate — the configured serial number may be wrong.
“The card terminal could not be reached”	The same condition, shown in Stayflexi’s own wording.	Check the terminal is powered on, awake and connected to the internet, then try again.
The charge takes a very long time and then fails	The request to Shift4’s cloud timed out. Charges are given a long window before being abandoned.	Do not retry repeatedly. Check the terminal, then escalate with the time of the attempt.
A declined or card-specific message	Shift4’s own response, passed through unchanged — this is the card or the issuer, not the integration.	Ask the guest for another card. No escalation needed.
Errors mentioning a UTG URL, a gateway address, or `ERR_CONNECTION_*` / certificate problems	The property is being treated as a UTG property when it should be on Commerce Engine.	Do not add a UTG URL. Escalate to Stayflexi Ops and say the property is on Commerce Engine.

6. Ops procedures Stayflexi Ops

Procedure A — Confirm the property really is on Commerce Engine

Check Meta against the table in section 2 before anything else. The most common mistake is treating a CE property as a broken UTG property because the UTG URL is blank.

Procedure B — Verify the terminal identity

Ask the property to read the serial number printed on the physical terminal, usually on a label on the underside or back.
Compare it character by character with Shift4 Terminal Serial number in Meta.
Confirm Shift4 Terminal Manufacturer matches the device (for example PAX).
Confirm the Shift4 API Terminal Id is populated and matches what Shift4 supplied.

A mismatch in any of these produces “device not connected” even though the terminal is perfectly healthy.

Procedure C — Confirm the access token is present

If Shift4 Access Token is blank, regenerate it from the Auth token and save. Without it, no Shift4 transaction can be authorised in either mode.

Procedure D — Escalate to Shift4

If the terminal is powered, online, and the serial and manufacturer match what is printed on the device, the remaining possibilities are on Shift4’s side: the terminal may not be enrolled for Commerce Engine, or may be registered against a different merchant. Escalate.

Never “fix” a Commerce Engine property by filling in the UTG URL. It will appear to change something, and it will make things worse: the property leaves cloud mode and starts trying to reach gateway software that was never installed.

7. Known limitations

Commerce Engine support is newer than the UTG integration. A few things behave differently, and knowing them prevents wasted troubleshooting.

The terminal status panel does not appear for Commerce Engine properties. Its absence is expected and is not a fault.
One terminal per property. Multi-terminal setups are supported for UTG properties but not for Commerce Engine — the serial number and manufacturer are held once, at property level.
No offline mode. If the property’s internet is down, card terminal payments are unavailable. There is no local fallback, because there is no local gateway.
Charges are sent from Stayflexi’s servers, not the browser. A slow or flaky front desk PC will not cause a card failure, and browser developer tools will not show the Shift4 call the way they do for UTG properties.

If a front desk agent reports terminal behaviour that these notes do not cover, raise it with Stayflexi Ops rather than improvising — Commerce Engine properties are a small part of the estate and their failure patterns are still being catalogued.

8. Escalating to Shift4

Have this ready before you call

Item	Where to get it
Merchant name and Shift4 merchant ID	Partner portal / property record
Terminal serial number	The label on the physical terminal, and Meta
Terminal manufacturer and model	The device itself, e.g. PAX
The exact error message	The PMS screen at the time of the failure
Date and time of the failed attempt	Front desk
Confirmation the terminal is online	Section 4, steps 1–3

State clearly that the property is on Commerce Engine for Cloud, not the UTG. This saves a long detour into gateway software that is not installed.

Shift4 support contacts

Go to shift4.com/support and choose Chat Support, Phone Support, or Email Support. Selecting phone support prompts you to pick a region. Stayflexi properties on Shift4 are in the United States and Canada only — use the matching line below.

Region	Phone	Use for
United States	+1 888.276.2108	Terminal down, live outage affecting check-ins/check-outs
Canada	+1 855.894.7996	Same, for Canadian properties

Use phone support when the terminal is down. A property that cannot take card payments is a live revenue outage — chat and email queues are not the right channel for it. Shift4 support operates 24/7/365.

Who owns what: Shift4 own the terminal hardware, its enrolment for Commerce Engine, and the cloud service that reaches it. Stayflexi own the Meta configuration — the terminal serial number, manufacturer, API Terminal ID and access token. The property owns the terminal’s power and internet connection.

Shift4 UTG troubleshooting guide — for properties that run the Universal Transaction Gateway on a local PC. Check section 2 above first to confirm which guide applies.
Shift4 Support
Shift4 Knowledge Base

Did You Know?