> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-us/payware-connect/transaction-help/transaction-errors/all-transactions-declining.md).

# All Transactions Declining

Troubleshoot all transaction types declining on Verifone devices.

{% hint style="info" %}
**Use this when** every transaction type — Sale, Credit, Pre Auth, Voice Auth, and so on — is declining, not just one card or transaction type.
{% endhint %}

{% hint style="danger" %}
**Do NOT use this when** only certain transaction types, specific cards, or a single transaction are declining — this page covers a site-wide decline only.
{% endhint %}

## Symptoms

* Every transaction type is declining, across all cards and transaction methods.

**Most likely cause:** the location has lost its internet connection.

## Before you start

* Confirm the decline is affecting all transaction types, not an isolated one.

## Resolve the issue

{% stepper %}
{% step %}

### Verify the internet connection

Confirm the location has an active internet connection. If internet is unavailable, all transaction types can decline.

✅ **Issue fixed — stop here.** ❌ **Still not working — continue to escalation below.**
{% endstep %}
{% endstepper %}

## Still not working? Contact the Helpdesk

{% hint style="info" %}
If the issue persists, contact the level one help desk, your merchant services provider, or the Verifone Helpdesk for further assistance.

* Use our Chat platform
* Or call 1.800.VERIFONE (837.4366)
  {% endhint %}

<details>

<summary>Keywords</summary>

Also called: all transactions declining, every card declining, site-wide decline, no transactions processing. Search terms: transactions declining, internet connection, all cards declining.

</details>


---

# 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.verifone.com/support-us/payware-connect/transaction-help/transaction-errors/all-transactions-declining.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.