> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/payment-link/checkout-links-and-options/order-confirmation-documents.md).

# Order confirmation documents

## Overview

Shoppers can access order confirmations when they place orders. The PDF download link is displayed in:

* The Thank You pages
* myAccount
* The confirmation email that they receive after placing the order

This applies to orders paid for through the following payment methods:

* Purchase orders
* Wire transfers
* Checks

## Availability

All 2Checkout accounts.

## Example

### **Shopping cart**

1. Your shoppers need to select Purchase order, Wire Transfer or Check as their payment option and select any preferred billing currency and/or other required payment details. Then, they need to click **Continue**.
2. Once they've reached the Thank You page, they need to click the **Download order confirmation** in order to download their partner invoice in PDF format.

### myAccount

Your shoppers can also download the PDF from **myAccount** by visiting the **Order details** section for their order and clicking the **Download order confirmation** link.

### Email

The confirmation email that the shoppers receive after placing the order also contains the PDF download link.


---

# 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.2checkout.com/payment-link/checkout-links-and-options/order-confirmation-documents.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.