> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qonto.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment links

> Create shareable checkout pages and track the payments made against them

Payment links are shareable checkout pages for collecting payments from customers: the link opens a secure Qonto payment page where the customer pays by card, Apple Pay, PayPal, or iDEAL. The MCP server lets you create links, enumerate them, and read one back together with the payments it has collected.

Creating links requires the organization to have set up payment links first: [activate them in the Qonto web app](https://app.qonto.com/deeplinks?action=payment_links.activate). Managing that connection is not an MCP tool.

## Tools

| Tool                  | What it does                                                                                                                                                                                                                                                                                                                                                                      | Upstream                                                                                                                                                                                                  |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `list_payment_links`  | Paginated list of the organization's payment links. Read-only. Use it to resolve a link's UUID before fetching it with `get_payment_link`.                                                                                                                                                                                                                                        | [List payment links](/api-reference/business-api/payments-transfers/payment-links/index)                                                                                                                  |
| `create_payment_link` | Create a link from one of two body shapes: a **basket** (one or more `items` with quantity, unit price, and VAT rate, plus an optional `reusable` flag) or an **invoice** (`invoice_id`, `invoice_number`, `debitor_name`, `amount`). Both shapes accept `potential_payment_methods` (`credit_card`, `apple_pay`, `paypal`, `ideal`). Returns the new link with its public `url`. | [Create a payment link](/api-reference/business-api/payments-transfers/payment-links/create)                                                                                                              |
| `get_payment_link`    | Fetch one link by UUID together with the payments made against it, in a single payload: `payment_link`, `payments`, and `payments_meta`. Use it to see a link's status and who has paid it.                                                                                                                                                                                       | [Get a payment link](/api-reference/business-api/payments-transfers/payment-links/show) · [List payments for a payment link](/api-reference/business-api/payments-transfers/payment-links/index-payments) |

## Basket or invoice

A basket link itemizes what is being paid for and can be marked `reusable`, so one URL collects any number of payments (a ticket page, a fixed-price service). An invoice link references an existing client invoice (see [Invoices and billing](/mcp/tools/invoices)) and carries the customer's name and the invoice total, so the payment reconciles against that document. Pick the shape by passing either `items` or `invoice_id`; the tool's input schema documents each variant's fields.

`get_payment_link` merges two upstream operations so the link and what has been paid on it come back as one payload. A link with no payments returns an empty `payments` list; for a busy reusable link, `payments` holds the first 100 and `payments_meta.total_count` tells you when there are more.

**Try it**

> Create a reusable payment link for a €50 "Workshop ticket" and give me the URL.
>
> Create a payment link for invoice INV-2026-042 so the client can pay by card.
>
> List my payment links.
>
> Has anyone paid the link for invoice INV-2026-042 yet?