> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/customer-documentation/petro-and-c-store/commander-central/commander-central-user-guide/connect-device-to-cloud.md). # Connect Device to Cloud The Connect Device to Cloud section will provide details on how to enable the Cloud Connect feature in Verifone Configuration Client. Each Verifone Commander must be onboarded to the cloud within Verifone Configuration Client and added to Verifone Commander Central. {% hint style="info" %} If the site's information was not added to Verifone Commander Central prior to completing the Verifone Configuration Client onboarding steps, the site will automatically be added to Sites within Verifone Commander Central. The site name will be the site's Service ID and the hierarchy will need to be modified. {% endhint %} ### Requirements * The site where the device is located is set up within Verifone Commander Central within Administration > Sites. * The Verifone Commander onboarder must have credentials for Verifone Commander Central. * DNS must be enabled within Verifone Configuration Client (Local Area Network Configuration) for the connection to be successful. ### Pre-Release 54.02 - Connecting Device to Verifone Commander Central {% stepper %} {% step %} **Cloud Connect** Log in as Manager in Verifone Configuration Client and navigate to Initial Setup > Cloud Connect.
{% endstep %} {% step %} **Cloud Connect Button** Select the Cloud Connect button from the screen.
{% endstep %} {% step %} **URL and User Code** A URL and a user code are generated. Copy the User Code that was generated on your Configuration Client and then select the URL on your screen.
{% endstep %} {% step %} **Enter the Code** After the URL opens, enter the user code from Configuration Client into the ‘Enter your code here’ field and click Submit.
{% endstep %} {% step %} **New Site** Click Yes, log into the new site. A page will open that will prompt you to log into Verifone Commander Central. {% endstep %} {% step %} **Log in** Login with the credentials for Verifone Commander Central.
{% endstep %} {% step %} **Sharing the Information** The next prompt will prompt you to allow sharing the information from the Verifone Commander. Select **Allow**. A message will display ‘DONE!’.
{% endstep %} {% step %} **Configuration Client** Return to the Configuration Client page. Select Confirm Verification from the Cloud Connect window.
{% endstep %} {% step %} **Registration Completed**
{% endstep %} {% endstepper %} {% hint style="info" %} There is a 5-minute delay from when the site will show Active within Verifone Commander Central after it is registered. {% endhint %} {% hint style="warning" %} **If DNS is not enabled in Configuration Client > Initial Setup > Local Area Network Connection, then the Verifone Commander will not be able to resolve the IP from the URL and onboarding will fail.** {% endhint %} {% hint style="info" %} **T-Log data after onboarding** \ Transactions run before a Commander is onboarded to Verifone Commander Central will not appear in the T-Log Viewer, even after onboarding completes. T-Log data begins flowing to the cloud starting with the first period close after onboarding — transactions from the period in progress at the time of onboarding, and any period before it, are not included. This is expected behavior: T-Log and reporting data are organized by period boundary, and pre-onboarding activity is not backfilled. {% endhint %} ### Troubleshooting #### Error response ‘User Code has Expired. Please start the registration again.’
Make sure the user trying to onboard the Verifone Commander has the ‘Commander Onboarder Role’ assigned within Verifone C-Site. If the role has been assigned to the user, then contact the Verifone Helpdesk. The expiration time for the user code is 14 minutes, but the role assignment issue will appear immediately. #### Error response ‘Communication error, please check network settings.’
For the following payment networks, no routes need to be added into Initial setup > LAN Configuration as the MNSP will make the changes needed: BP, Sunoco, and Chevron\*. Chevron is making the changes to the MNSP with the assumption that the Payment NIC is configured for the default route. If the Payment NIC is not the default route, then it needs to be changed to the default route, saved, and the Verifone Commander must be rebooted. See the Chevron Playbook for more details. For Shell, Generic Buypass, etc. where the Payment NIC is NOT the default route, then DNS routes are required. DNS 1 8.8.8.8 and DNS 2 8.8.4.4 – Unless other DNS routes are required by the site’s network administrator. Site such as Exxon, Generic Buypass (Gulf, Sinclair, etc.) and others who do not have their own IP scheme and has the Payment NIC set as the default route would need to add the following Host Routes and DNS settings into Initial Setup > LAN Configuration: **Host Routes**
Host Route DescriptionIP AddressGatewaySubnet
C-Site VAM 123.23.135.174192.168.31.31255.255.255.255
C-Site VAM 218.213.229.217192.168.31.31255.255.255.255
C-Site VIC 134.117.16.222192.168.31.31255.255.255.255
C-Site GSC 1184.72.129.214192.168.31.31255.255.255.255
C-Site GSC 254.221.203.197192.168.31.31255.255.255.255
C-Site GSC 352.72.155.235192.168.31.31255.255.255.255
C-Site MQTT 1184.73.231.196192.168.31.31255.255.255.255
C-Site MQTT 23.212.149.223192.168.31.31255.255.255.255
C-Site MQTT352.6.28.56192.168.31.31255.255.255.255
DNS 18.8.8.8192.168.31.31255.255.255.255
DNS 28.8.4.4192.168.31.31255.255.255.255
**DNS Settings** * DNS 1: 8.8.8.8 * DNS 2: 8.8.4.4 ## Release 54.02+ - Connecting Device to Verifone Commander Central In Verifone Commander software release 54.02 and higher, there have been enhancements made to onboard the Verifone Commander. The steps have been simplified from previous releases. {% hint style="info" %} Ensure that the instructions are followed for the correct software release installed on the Verifone Commander prior to beginning onboarding. {% endhint %} {% stepper %} {% step %} **Verifone Configuration Client** Log into Verifone Configuration Client and navigate to Initial Setup > Connect to Verifone Commander Central.
{% endstep %} {% step %} **Login Credentials** Enter the C-Site Email and Password to connect the Verifone Commander to C-Site. Do not use the Verifone Configuration Client Credentials – they will not work. If the site doesn’t have an account, selecting the ‘Don’t have an account?’ option will provide information for the site to sign up for Verifone Commander Central.
{% endstep %} {% step %} **Connection** When the correct credentials are entered, Verifone Configuration Client will display ‘Connecting to Verifone Commander Central in Progress’.
{% endstep %} {% step %} **Onboarding Complete** After the onboarding is complete, the message below displays.
{% endstep %} {% endstepper %} {% hint style="info" %} **T-Log data after onboarding** \ Transactions run before a Commander is onboarded to Verifone Commander Central will not appear in the T-Log Viewer, even after onboarding completes. T-Log data begins flowing to the cloud starting with the first period close after onboarding — transactions from the period in progress at the time of onboarding, and any period before it, are not included. This is expected behavior: T-Log and reporting data are organized by period boundary, and pre-onboarding activity is not backfilled. {% endhint %} ## Troubleshooting #### Error message ‘Invalid credentials, please try again. Please make sure you are using your Commander Central credentials to login’
Confirm the Verifone Commander Central Credentials are being used and not the Verifone Configuration Client Credentials. #### Error message ‘Wrong Serial Number – Service ID Mapping. Please contact helpdesk’
* The service ID may be incorrect in the Verifone Commander. Confirm the site’s service ID is entered in by navigating to Help > Support in Configuration client to verify it is correct. If the service ID entered is incorrect, contact the Verifone helpdesk to correct the service ID. * Verifone Commander serial number may not match what the site has registered. Reach out to the Verifone Helpdesk to correct the Verifone Commander Serial number and/or Service ID. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://commanderhelp.verifone.com/customer-documentation/petro-and-c-store/commander-central/commander-central-user-guide/connect-device-to-cloud.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.