> For the complete documentation index, see [llms.txt](https://hollow-peak.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hollow-peak.gitbook.io/docs/payments/payment-links.md).

# Payment Links

Requesting payment from someone without an order.

A payment link asks someone to pay a specific amount, without a product or a customer account. Useful for invoices, deposits, custom work and anything quoted individually.

## Creating one

**Payments → Payment Links → New**

| Field       | Notes                                                       |
| ----------- | ----------------------------------------------------------- |
| Title       | What the payer sees — e.g. “Website deposit — Acme Digital” |
| Amount      | In your store currency                                      |
| Description | Optional detail                                             |
| Client      | Optionally attach it to a client record                     |
| Expiry      | Optional                                                    |

You get a link with a long random token:

```
https://your-domain.com/pay/2f8a1c4e9b7d3a6f
```

## How the payer uses it

They open the link, see the title, amount and description, choose a payment method, and pay. No account, no sign-in.

{% hint style="info" %}
**The token is the authorisation.** Anyone holding the link can open it. Send it directly to the person who should pay — do not post it publicly.

The token is long and random, so it cannot be guessed or counted through.
{% endhint %}

## Tracking

The list shows each link's status — unpaid, paid, expired — with the amount and date. Paid links produce a payment record like any other, and can be refunded the same way.

## Good practice

* Put the invoice number or client name in the title, so your records reconcile
* Set an expiry on quotes, so an old price cannot be paid months later
* Attach the client, so it appears on their record
* Send one link per payment, rather than reusing one


---

# 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://hollow-peak.gitbook.io/docs/payments/payment-links.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.
