> 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/payment-documents.md).

# Payment documents

Payment Documents(receipts) are defined as any document with the purpose of describing a payment acceptance and processing, containing details such as the payment amount, payment method, terminal ID, transaction ID, or the authorization number and not only limited to those. Verifone payment documents cover both in-store, MOTO, Pay By Link, Virtual Terminal and eComm solutions. This can also be integrated with third party payment documents providers like Invoice4U.

Payment documents can be generated, re-generated, shown, and provided through Verifone Central. They can be sent, at any time, to the merchant and shopper mailboxes from **Verifone Central** -> **Documents** tab. These can be customized as per merchant needs including here the possibility to add a merchant logo, a merchant address, and many other information.

## Payment documents through Verifone Central <a href="#payment-documents-through-verifone-central" id="payment-documents-through-verifone-central"></a>

To get started, the Merchant needs to be onboarded for this service with Verifone.  After enrolment, Merchants will be able to access the [Payment Documents](/online-payments/payment-documents/verifone-central.md) for eligible Transaction Types and Statuses through Verifone Central.

### Availability  <a href="#availability__00a0" id="availability__00a0"></a>

✅ Access

* Merchant Admin
  * view and edit Payment Documents
* Merchant Supervisor
  * view and edit Payment Documents
* Merchant Cashier
  * view Payment Documents

🚫 No access

* Merchant Reviewer
* Merchant User

### Payment document logo <a href="#payment-document-logo" id="payment-document-logo"></a>

The Merchant logo will have to respect the below requirements:

* Accepted file types: .png
* Maximum upload file size: 500 KB

{% hint style="info" %}
Depending on the country and the sale channel (In-Store or eComm) there are some specific types of receipts that can be used.
{% endhint %}

## Third party payment documents through Invoice4U <a href="#third-party-payment-documents-through-invoice4u" id="third-party-payment-documents-through-invoice4u"></a>

Verifone's third party payment documents service allows you to utilize payment document (also called as transaction receipts) providers outside of Verifone. Currently, Verifone offers third party payment documents functionality with one external provider, with [Invoice4U](/online-payments/payment-documents/invoice4u.md) in Israel.

Verifone's Third party Payment Documents generation - through Invoice4U feature is available as a value-added Verifone service for Merchants in Israel. To get started, the Merchant needs to be onboarded for this service with Verifone. The Merchant also needs to be enrolled with Invoice4U, which is a separate entity from Verifone. After enrolment to both services, Merchants will be able to access Invoice4U Payment Document IDs for eligible Transaction Types and Statuses.


---

# 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/online-payments/payment-documents.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.
