> For the complete documentation index, see [llms.txt](https://docs.bird.com/applications/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/applications/payments/bird-pay-beta/concepts/payment-link.md).

# Payment Link

A payment link is a simple tool that allows businesses to accept payments online without a website. By generating a unique URL, customers can pay instantly via any payment method supported by Bird Pay. This flexibility boosts sales, simplifies transactions, and enhances customer convenience.

{% hint style="info" %}
Sample Payment Link: <https://pay.bird.com/nusuybvPLhiFEh7fNw1>
{% endhint %}

Payment links can be created manually in the Bird Pay UX or automatically through flows.\
Each payment link includes the following configurable fields:

* **Type** - Decide whether you or the customer will enter the amount. For most situations, you’ll enter the amount yourself. However, for cases like fundraising, you can select **My customer will enter the amount**.
* **Amount** - Choose the amount and currencies
* **Title** - Enter the title for your payment link
* **Description** - Provide details about your payment link
* **Customer** - If your customer is already a known contact available in BirdCRM, you can use the same. It's an optional field
* **Information to collect from customer**
  * **Phone**
  * **Shipping address**
  * **Reference**
  * **Message**
* **Link configuration**
  * **One time** - These can be used multiple times until they expire
  * **Reusable** - These expire after a single successful payment
* **Active until** - Expiry date & time of your payment link

<figure><img src="/files/colR25khCAtkkOzt2Eih" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
Payment links can be shared with your customers on any messaging channel.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bird.com/applications/payments/bird-pay-beta/concepts/payment-link.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.