> For the complete documentation index, see [llms.txt](https://docs.vapinetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vapinetwork.ai/call/for-buyers-and-agents/receipts-and-retries.md). # Receipts and retries Local receipts record paid API calls; settlement checks and x402 payment identifiers help prevent duplicate payments. {% hint style="info" %} Call is launching. The console does not serve Call yet; this page describes the launch flow. {% endhint %} Use receipts to record paid calls and to check an uncertain settlement before you try again. Call supports safe retries when the API advertises the x402 `payment-identifier` extension. ## Receipts In the console, the quote dialog shows receipt status and the paid result includes a settlement reference. The `vapi` client writes a local receipt for each paid call. List CLI receipts with: ```bash vapi receipts ``` The local ledger records the quote, settlement, and latency for each paid call. ## Safe retries When an API advertises `payment-identifier`, the same identifier and request fingerprint can return a cached response without a second settlement. Reusing an identifier for a different request fingerprint is rejected. See [x402 extensions](/call/reference/x402-extensions.md) for the payment wire fields and discovery metadata. ## Check an uncertain payment If a paid call loses its response, use the receipt ID with: ```bash vapi pay --resume ``` The client reads the chain for that receipt's authorization state. It does not open a wallet, sign, or pay again.
Two ways to recover a paid call. Response lost: a paid call returned no response, so the payment may or may not have settled; vapi receipts lists every paid call with its ID; vapi pay --resume with that receipt ID reads the authorization's state onchain. No wallet is opened, nothing is signed, and nothing is paid again. Safe retry, when the API advertises payment-identifier: retry the request with the same payment-identifier as the first attempt. With the same request fingerprint you get the cached response and no second settlement. With a different fingerprint the retry is rejected, because the identifier was already used for another request. One identifier means one settlement.

Reconcile with the receipt, or retry with the same payment-identifier. Neither pays twice.

Checked on 2026-10-02. --- # 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.vapinetwork.ai/call/for-buyers-and-agents/receipts-and-retries.md?ask=&goal= ``` `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.