> For the complete documentation index, see [llms.txt](https://docs.barte.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.barte.com/guias/passo-a-passo-do-vendedor/2o-criando-pedidos-or-links-de-pagamento-or-assinaturas/links-de-pagamento.md).

# Links de Pagamento

Links de pagamento permitem criar **cobranças prontas para uso**, sem a necessidade de um checkout próprio ou integração complexa.

Ao gerar um link, a Barte se encarrega da experiência de pagamento, enquanto você acompanha o status da cobrança via API e webhooks.

Eles são ideais para:

* vendas manuais
* cobranças via WhatsApp, e-mail ou redes sociais
* operações sem frontend próprio
* testes rápidos de cobrança

***

### Tipos de links de pagamento

#### <i class="fa-diamond">:diamond:</i> Link de Pagamento Pontual

Indicado para **cobranças únicas**, com valor e vencimento definidos.

Acessar [Link de Pagamento Pontual](https://docs.barte.com/guias/passo-a-passo-do-vendedor/2o-criando-pedidos-or-links-de-pagamento-or-assinaturas/links-de-pagamento/link-de-pagamento-pontual.md)

***

#### <i class="fa-diamond">:diamond:</i> Link de Pagamento Recorrente

Utilizado para **cobranças recorrentes**, geralmente associado a um plano de assinatura.

Acessar [Link de Pagamento Recorrente](https://docs.barte.com/guias/passo-a-passo-do-vendedor/2o-criando-pedidos-or-links-de-pagamento-or-assinaturas/links-de-pagamento/link-de-pagamento-recorrente.md)


---

# 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.barte.com/guias/passo-a-passo-do-vendedor/2o-criando-pedidos-or-links-de-pagamento-or-assinaturas/links-de-pagamento.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.
