> For the complete documentation index, see [llms.txt](https://docs.lyzi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lyzi.io/en/merchant/backoffice/liens-de-paiement.md).

# Payment Links

Create a link, send it, your customer pays in crypto. No hardware and no integration: a message, an email or a text message is enough.

{% embed url="<https://youtu.be/aRVG_ZSQ6LY>" %}

## Create a payment link

{% stepper %}
{% step %}

### Open the form

In the menu, click Payment Links, then the create button. The Create a payment link form opens.
{% endstep %}

{% step %}

### Identify the sale

Fill in the Client reference, the Product reference and the Product type. This information lets you find the sale in your list and in your history.
{% endstep %}

{% step %}

### Choose the validity period

Enter a number and a unit. The duration must be between 10 minutes and 2 years. Without any specific setting, a link stays valid for 30 days, that is, 1 month.
{% endstep %}

{% step %}

### Set the price

Enter the Price and choose the Currency.
{% endstep %}

{% step %}

### Assign a cash register

Select the cash register in the Assign to a cash register field. This is what makes the link valid: once the cash register is chosen, its outline turns blue and the create button becomes clickable.
{% endstep %}

{% step %}

### Confirm and share

Click Create my payment link. The Cancel button closes the form. Then copy the link and send it to your customer.
{% endstep %}
{% endstepper %}

## Track your links

The list of your links shows, for each one: the Link name, its Status, the Sold item, the person who created it, the Amount, the creation date and the expiration date. A search bar, the refresh icon and the Columns button help you find and organize the information.

The status is INITIAL as long as the customer hasn't paid, PAID once the payment is completed and EXPIRED when the validity period has passed.

## Act on a link

The copy icon on each row copies the link to your clipboard. The three-dot menu offers three actions: Open link, Expire link to deactivate it immediately, and Attach document, for example an invoice or a quote.

## Send the link to your customer

Once created, the link appears in the list. Copy it with the dedicated icon, then send it by email, add it to an invoice or share it via WhatsApp. You can also open the link in a browser and send a screenshot of the payment page.

## What your customer sees

Your customer lands on a summary of the transaction. The link's validity period is shown at the top right. They choose their payment method, accept the terms and conditions of sale, then pay in crypto.

{% hint style="info" %}
An expired link can no longer be paid. Create a new one, or adjust the validity period when you create it to give your customer enough time.
{% endhint %}


---

# 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.lyzi.io/en/merchant/backoffice/liens-de-paiement.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.
