> 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/psdk-latest/psdk-user-guide-and-training/psdk-user-guide/logging.md).

# Logging

Logging is enabled by default. Depending on the platform standard logging facilities (like android.util.Log for Android) would be used if available.

Logging levels are modified using [PaymentSdk.configureLogLevel](https://docs.verifone.com/psdk-api-latest/android-java/index/paymentsdkbase#configureloglevel-psdkloglevel) call. Redirection to file can be set via [PaymentSdk.configureLogFile](https://docs.verifone.com/psdk-api-latest/android-java/index/paymentsdkbase#configurelogfile-string-long) and [PaymentSdk.configureLogFileWithRotation](https://docs.verifone.com/psdk-api-latest/android-java/index/paymentsdkbase#configurelogfilewithrotation-string-long-long) calls. Refer to API guide for more details.

## Logging levels <a href="#logging-levels" id="logging-levels"></a>

* LOG\_TRACE - adds logging of data being sent/received by PSDK interfaces unmasked, with encrypted communication between PSDK and terminal being logged after decrypting.
* LOG\_DEBUG - default level, logs messaging between PSDK and the terminal masking sensitive data fields plus any other info required to be delivered to Verifone for debugging.
* LOG\_INFO - logs various informational messages.
* LOG\_WARN - logs recoverable errors.
* LOG\_ERROR - logs unrecoverable errors that result in failure to process transaction/interaction with terminal
* LOG\_FATAL - logs unrecoverable errors that lead to PSDK termination.
* LOG\_NONE - turn logging off.

{% hint style="info" %}
**See Also**

[PsdkLogLevel](https://docs.verifone.com/psdk-api-latest/android-java/index/psdkloglevel)
{% endhint %}

## Masked fields <a href="#masked-fields" id="masked-fields"></a>

PSDK will mask following information when configured for LOG\_DEBUG level:

* Identification of the customer account for payment instruments (PAN or otherwise).
* Name of the cardholder.
* Card exiry date.
* Any track data if it is provided by the terminal in cleartext (possible for gift cards for example).

***

{% columns %}
{% column width="25%" %}

<figure><img src="/files/9ezXRridnCaI1awLr3X9" alt="" width="150"><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="25%" %}

{% endcolumn %}

{% column width="16.66666666666666%" %}
**Version:**\
**Date:**
{% endcolumn %}

{% column width="33.333333333333336%" %} <code class="expression">space.vars.psdk\_version</code>\ <code class="expression">space.vars.psdk\_date</code>
{% endcolumn %}
{% endcolumns %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.verifone.com/psdk-latest/psdk-user-guide-and-training/psdk-user-guide/logging.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.