# Operational Guides

### Purpose

Operational Guides contains supplemental implementation guidance for running a payments integration in production.

Use this section for practical topics that support the core Payments documentation, such as webhook consumption, operational hardening, and end-to-end wallet testing.

This section is not the primary home for core API usage, payment status behavior, or onboarding workflows.

* Go to [Payments ](/payments.md)for payment creation, payment statuses, receipts, payment webhooks, and testing flows.
* Go to [Payment Scenarios](/reference-guide/payment-scenarios.md) for non-happy-path payment outcomes such as underpaid, overpaid, reclaim, and refund or return guidance.
* Go to [Onboarding](/onboarding.md) for merchant application submission, signing, status tracking, and onboarding webhooks.

### What you’ll find here

| Page                                                                                          | What it covers                                                                                                               |
| --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| [Webhook Event Reference](/reference-guide/operational-guides/webhook-event-reference.md)     | Supplemental reference for event payloads, signature verification, retry behavior, idempotency, and webhook consumer design. |
| [Compatible Crypto Wallets](/reference-guide/operational-guides/compatible-crypto-wallets.md) | Wallets to validate during QA, expected wallet capabilities, and practical caveats for testing and launch readiness.         |

### How to use this section

1. Start in [Payments](/payments.md) to implement payment creation, hosted checkout, status handling, and primary payment webhook configuration.
2. Use [Webhook Event Reference](/reference-guide/operational-guides/webhook-event-reference.md) when hardening your webhook listener for production, especially around verification, retries, logging, and idempotency.
3. Use [Compatible Crypto Wallets](/reference-guide/operational-guides/compatible-crypto-wallets.md) when planning QA, demos, and support expectations across wallet types.
4. Use [Payment Scenarios](/reference-guide/payment-scenarios.md) when the question is outcome-driven, such as what to do when a payment is underpaid, overpaid, expired, invalid, cancelled, or requires reclaim handling.

### Related sections

| Section                                                    | Use it for                                                                             |
| ---------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| [Payments](/payments.md)                                   | Core payment API flows, hosted checkout, status checks, receipts, and payment webhooks |
| [Payment Scenarios](/reference-guide/payment-scenarios.md) | Outcome-specific handling for non-happy-path payment states                            |
| [Onboarding](/onboarding.md)                               | Merchant application flows and onboarding event handling                               |
| [Core Concepts](/reference-guide/core-concepts.md)         | Cross-cutting concepts such as authentication, environments, and rate limits           |


---

# Agent Instructions: 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:

```
GET https://developers.bead.xyz/reference-guide/operational-guides.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.