> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/canada-doc-center/applications/secure-payment/payment-standalone-mode/terminal-configuration/test-network-connection.md).

# Test Network Connection

### Test Network Connection

The Secure Payment application's payment module works with counter-top and mobile payment terminals. Many counter-top terminals use a wired (Ethernet) network connection but many also use a wireless (Wi-Fi) as a backup connection. Mobile terminals will connect to Wi-Fi and/or mobile (cellular) networks.

If the terminal is taking longer than expected to process transactions, you may want to check the terminal's network connection to ensure that everything is working correctly.

#### **To test your network connection:**

1. From the main screen, touch **Network**.

\
![Network button](https://documentation.payfacto.com/SecurePayment/Pay/UG/CA-EN/assets/images/Pay/MainSaleScreen_NetworkButton.png)

2. The *Connection test* screen appears and displays the results of the connection test.
3. If the *Connection Test* screen displays a **Failure** message, touch the **Continue** button and check the terminal's Wi-Fi settings as well as your router and then repeat the network connection test.

\
![Network connection test failure](https://documentation.payfacto.com/SecurePayment/Pay/UG/CA-EN/assets/images/Pay/NetworkConnectionTest_Failure.png)

4. If the *Connection Test* screen displays a **Success** message, touch the **Continue** button to return to the Secure Payment application.

\
![Network connection test success](https://documentation.payfacto.com/SecurePayment/Pay/UG/CA-EN/assets/images/Pay/NetworkConnectionTest_Success.png)


---

# 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://docs.payfacto.com/payfacto-knowledge/canada-doc-center/applications/secure-payment/payment-standalone-mode/terminal-configuration/test-network-connection.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.