> 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/online-payments/plugins/prestashop-plugin-integration/error-handling-and-troubleshooting.md).

# Error Handling and Troubleshooting

If you encounter any errors during the installation and configuration of the PrestaShop plugin, you can find a log of all errors under the *Advanced parameters → Logs* section.

<div data-with-frame="true"><figure><img src="https://3085512782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fyw34t0Oefjx0nEVMOjo2%2Fuploads%2F6TyUhe0wlQKxm4pIbR5E%2FOpenCart%203%20logs.png?alt=media&amp;token=20cd6536-3cf6-4388-9d45-3e44ff12540b" alt=""><figcaption></figcaption></figure></div>

If some errors are not logged, you can always view the Apache or Nginx logs.

## Common errors <a href="#common-errors" id="common-errors"></a>

* Not having the currency of PrestaShop set to the one that the payment contract supports;
* Not having created a public key for [Secure Card Capture](/online-payments/api-integration-methods-auth-and-endpoints/secure-card-capture-key.md);&#x20;
* Organization ID, Payment Contract ID, or 3DS Contract ID do not match the correct entity that they were created for;
* cURL verify host is enabled/disabled but the host server does not have proper TLS certificates;
* Not having the latest PrestaShop module version installed;
* Make sure that the credentials are correct: Payment Contract ID, User ID, API key, Organization ID, etc;

{% hint style="danger" %}
The Prestashop connector will only work for version 1.7 and above.
{% endhint %}

In most cases, the error may be caused by various PHP errors and/or warnings.

If the error is caused by a request to the Verifone server, then the error message received when the request fails is very informative. Here is an example:

```
{
    "code": 116,
    "details": {},
    "timestamp": 1608705038970,
    "message": "Access is restricted to authenticated users only. The query can't be made without a valid JWT (check the Authorization header of your request)."
}
```

The above request was denied because the user was not authorized. This is due to an invalid token being present in the Authorization bearer.

This kind of error format will be present on almost all requests that fail and will deliver a concrete error message along with it which in turn will pinpoint the problem precisely.


---

# 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/online-payments/plugins/prestashop-plugin-integration/error-handling-and-troubleshooting.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.