> For the complete documentation index, see [llms.txt](https://docs.sensepass.com/sensepay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sensepass.com/sensepay/merchants/merchant-dashboard/payment-requests.md).

# Payment requests

A payment request sends your customer a payment link by SMS and/or email.

**Types of request**

| Menu item                      | Tab              | Customer | Amount    |
| ------------------------------ | ---------------- | -------- | --------- |
| Create payment request         | Payment          | Optional | Yes       |
| Create payment + Token request | Capture+Tokenize | Required | Yes       |
| Create Token request           | Tokenization     | Required | No amount |
| Create authorization request   | Authorization    | Required | Yes       |

**Create a payment request**

1. In the menu, open **Payment Request** and click **Create payment request**, or click another tab at the top of the form.
2. Check the Business, Location and Terminal at the top of the page.
3. Select a customer in the **Customer** field, or click the button next to it to add a new one. The customer's phone number and email are filled in for you. A customer is required for Capture+Tokenize, Tokenization and Authorization.
4. Check the **Request Expiration**. A date is filled in for you; change it if needed.
5. Select **Amount**, choose the **Currency** and enter the amount. You can select **Products** instead.
6. Optionally, enter a **Reason**, **Order ID** and **Invoice ID**.
7. Select the **Country** and enter the customer's **Phone Number** and/or **Email**. The link is sent to what you enter.
8. Optionally, enter a **Custom SMS Text** and a **Comment** (shown to the customer). Under **Optional Details** you can add a **Customer ID** and an attachment (**Add Attachment**).
9. Click **Request Payment**. A Success message shows the transaction number.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FzYBlYxODI90yroXvt47C%2Fm-pr-filled.png?alt=media" alt="Create payment request (example data)"><figcaption><p>Create payment request (example data)</p></figcaption></figure>

**Send many requests at once (Bulk Upload)**

1. On the payment request screen, click **Bulk Upload**.
2. Click **Download Template** and fill in the Excel template, one request per row.
3. Click **Load xlsx file**, select your file and click **Upload**.

The file must be an .xlsx file of up to 1 MB. The template (paymentRequestsTemplate.xlsx) has one header row and one example row. After the upload, a result file (paymentRequestsUploadResult.xlsx) is downloaded with the outcome of each row.

| Column                                  | Example value in the template  |
| --------------------------------------- | ------------------------------ |
| Currency                                | currency iso (for example USD) |
| Amount                                  | decimal amount                 |
| Installments                            | maximum installments           |
| Request Expiration                      | YYYY-MM-DD HH:mm               |
| Location                                | location name                  |
| Custom Sms Text, Comments, Phone Number | -                              |
| Email                                   | <name@domain.com>              |
| Customer Id, Product Name               | -                              |
| Product SKU                             | Item Number                    |
| Product Description, Product Quantity   | -                              |
| Product Amount                          | decimal amount                 |
| Product VAT                             | vat decimal amount             |

**Track your requests**

In the menu, open **Payment Request** and click **Payment request transactions**. The **Payment Requests History** screen lists your requests with their status (for example Pending), amount and **Expires At** date. Each request shows the transaction number, email, branch, who initiated it, the device, the reason and a QR code. From here you can:

* **Copy Link**: copy the payment link to share it yourself. The customer can also scan the QR code.
* **Cancel Request**: cancel the request.
* **More Details**: open the transaction details.
* **Resend Reminder**: send the customer a reminder.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2Fk783YXf6KSxYZ5Cd0st8%2Fm-pr-history.png?alt=media" alt="Payment Requests History"><figcaption><p>Payment Requests History</p></figcaption></figure>


---

# 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.sensepass.com/sensepay/merchants/merchant-dashboard/payment-requests.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.
