> For the complete documentation index, see [llms.txt](https://help.starkbank.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.starkbank.com/pagamentos-e-transferencias/comprovantes/por-que-meu-comprovante-mostra-agendado-e-nao-pago.md).

# Por que meu comprovante mostra “agendado” e não “pago”?

Veja em quais casos o comprovante baixado ainda aparece como “agendado”.

Isso acontece porque a transação ainda não foi processada. O comprovante gerado nesse momento é de **agendamento**.

***

## Casos mais comuns

* **Boletos** → só processados no próximo dia útil
* **Impostos e concessionárias** → só processados no próximo dia útil
* **TED** → pode demorar algumas horas para compensar

Quando o valor for de fato creditado, o Stark Bank disponibiliza automaticamente o **comprovante de pagamento**.

***

## Artigos relacionados

[Como baixar um comprovante?](/pagamentos-e-transferencias/comprovantes/como-baixar-um-comprovante.md)

[Qual a diferença entre comprovante de pagamento e comprovante de agendamento?](/pagamentos-e-transferencias/comprovantes/qual-a-diferenca-entre-comprovante-de-pagamento-e-comprovante-de-agendamento.md)

[Quais são os tipos de pagamentos e transferências no Stark Bank?](/pagamentos-e-transferencias/tipos-de-pagamentos-e-transferencias/quais-sao-os-tipos-de-pagamentos-e-transferencias-no-stark-bank.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://help.starkbank.com/pagamentos-e-transferencias/comprovantes/por-que-meu-comprovante-mostra-agendado-e-nao-pago.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.