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

# Accept Payments

- [Create Payment Link](https://docs.braidpay.com/braidpay/accept-payments/create-payment-link.md): Payment Links make it easy to sell online without the need for a website. Choose between a fixed amount or let the customer decide the amount.
- [Creating an Invoice ](https://docs.braidpay.com/braidpay/accept-payments/creating-an-invoice.md): Create and send professional invoices to your clients, enabling them to easily pay you in stablecoins such as USDC and USDT.
- [Get Paid by BraidPay Users](https://docs.braidpay.com/braidpay/accept-payments/get-paid-by-braidpay-users.md): This feature allows other BraidPay users to send you payments directly to your BraidPay account, making it easy to receive funds within the platform.
- [Email Receipts](https://docs.braidpay.com/braidpay/accept-payments/email-receipts.md): With BraidPay, both the sender and receiver will get automatic email receipts after a transaction, ensuring transparency and providing a clear record of each payment.


---

# 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.braidpay.com/braidpay/accept-payments.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.