> 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/why-did-my-payment-expire-and-what-happens-next.md). # Why Did My Payment Expire, and What Happens Next? A Bead payment expires when the payment quote window closes before any funds are detected. This page explains what causes expiry, what the customer experiences, and how integrators should handle it. #### Why does a payment expire? Each Bead payment is backed by a crypto quote — a fixed conversion rate valid for a limited window. The quote window starts when the payment is created. If the customer does not complete the wallet transfer before the quote window closes, the payment moves to `expired`. Expiry is triggered by the quote window timing out, not by any action from the merchant or integrator. #### What happens in the hosted UI? When the quote is about to expire, the hosted payment page gives the customer a short window to request a new quote. If the customer does not act within that window, the payment session ends and the status moves to `expired` automatically. #### What if funds arrive after the payment expires? Any funds that arrive after a payment has expired are not converted. Bead routes those funds to the reclaim flow and returns them to the payer. * If a `refundEmail` was provided in the original payment request, Bead emails reclaim instructions to that address automatically. * If no email was provided, the hosted payment page prompts the customer to enter an email so reclaim can proceed. Integrators do not need to implement the return flow directly. See [Reclaiming Unconverted Crypto](/reference-guide/payment-scenarios/reclaiming-unconverted-crypto.md) for full details on timing, windows, and customer experience. #### What should the integrator do? * Treat `expired` as a terminal non-success state. Do not fulfill the order. * Do not reuse the expired payment URL. It cannot be restarted. * If the customer still wants to pay, create a new payment and direct them to the new hosted payment URL. * Surface clear messaging so the customer understands what happened and what to do next. Suggested UI message: ``` Your payment session expired before a payment was detected. If you sent funds after the session ended, they will be returned to you through the reclaim process. To try again, please start a new payment. ``` #### What if the customer sent funds just before or just after expiry? If funds arrived before the quote expired but were not detected in time, or arrived shortly after expiry, they are treated the same as any other post-expiry funds — not converted, and returned through the reclaim process. The customer should be directed to start a new payment if they still want to complete their purchase. #### Can the customer fix an expired payment without starting over? No. Once a payment reaches `expired`, the session cannot be resumed or extended. The integrator must create a new payment and provide the customer with the new hosted payment URL. #### Related pages * [Payment Statuses](/payments/payment-statuses.md) * [Reclaiming Unconverted Crypto](/reference-guide/payment-scenarios/reclaiming-unconverted-crypto.md) * [Payment Scenarios](/reference-guide/payment-scenarios.md) * [Payment Webhooks](/payments/payment-webhooks.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 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://developers.bead.xyz/faqs-and-troubleshooting/payments-faqs/why-did-my-payment-expire-and-what-happens-next.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.