> 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/feature-references/features-and-products-references/mobile-payments/troubleshooting-mobile-payments/site-doesnt-display-on-mobile-payment-application.md).

# Site Doesn't Display on Mobile Payment Application

{% stepper %}
{% step %}
Verify that site has Mobile Host connectivity.

* Ping the host from: POS Main Menu > Maintenance > Ping Test (site level)
* Ping the host from Verifone Commander as the VASC-level user MAINT using: Ping `<Mobile Host IP Address>`.
  {% endstep %}

{% step %}
If the site has connectivity, but does not appear on the mobile application, verify connectivity to the Mobile Host.

* Check the logs (/var/log/messages) to verify a site update request from Verifone Commander to the Mobile Host was successful
* If needed, contact mobile host provider.
  {% endstep %}

{% step %}
Confirm the Mobile Host Provide onboarding details were configured properly.
{% endstep %}
{% endstepper %}


---

# 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/feature-references/features-and-products-references/mobile-payments/troubleshooting-mobile-payments/site-doesnt-display-on-mobile-payment-application.md?ask=<question>&goal=<user_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.
