> For the complete documentation index, see [llms.txt](https://developers.bead.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bead.xyz/faqs-and-troubleshooting/payments-faqs/crypto-conversion-timing-and-volatility-exposure.md).

# Crypto conversion timing and volatility exposure

#### When is crypto converted?

For a valid completed crypto payment, Bead converts the received crypto promptly after receipt and confirmation.

Bead does not hold completed crypto payments in crypto until settlement. Once the payment is completed and converted, the fiat proceeds are held for settlement and later deposited according to the applicable settlement schedule.

#### Is conversion real time, batched, or at settlement?

Conversion occurs as part of the payment completion flow, not at the later settlement deposit date.

Crypto is not held and converted in a settlement batch. The later settlement process is based on the converted fiat proceeds.

#### Does the merchant have crypto volatility exposure until settlement?

No. The merchant is not intended to have crypto price exposure through the settlement window.

The quoted payment amount is locked through the provider’s payment window and the crypto is converted as part of the payment completion flow. After conversion, settlement occurs from fiat proceeds rather than from crypto held until settlement.

#### What is the maximum exposure window?

The exposure window is tied to the payment quote window and conversion processing, not the settlement timing.

Once a valid payment is completed and converted, later settlement timing does not create additional crypto price exposure for the merchant.

#### What happens if crypto is sent after expiration or in the wrong amount?

If a payment is not completed successfully, the crypto may remain unconverted and be handled through Bead’s reclaim process.

Examples can include underpaid, expired, invalid, or cancelled payment outcomes. In those cases, the payment should not be treated the same as a completed 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.bead.xyz/faqs-and-troubleshooting/payments-faqs/crypto-conversion-timing-and-volatility-exposure.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.
