# 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 ](https://developers.bead.xyz/payments)for payment creation, payment statuses, receipts, payment webhooks, and testing flows.
* Go to [Payment Scenarios](https://developers.bead.xyz/reference-guide/payment-scenarios) for non-happy-path payment outcomes such as underpaid, overpaid, reclaim, and refund or return guidance.
* Go to [Onboarding](https://developers.bead.xyz/onboarding) for merchant application submission, signing, status tracking, and onboarding webhooks.

### What you’ll find here

| Page                                                                                                                  | What it covers                                                                                                               |
| --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| [Webhook Event Reference](https://developers.bead.xyz/reference-guide/operational-guides/webhook-event-reference)     | Supplemental reference for event payloads, signature verification, retry behavior, idempotency, and webhook consumer design. |
| [Compatible Crypto Wallets](https://developers.bead.xyz/reference-guide/operational-guides/compatible-crypto-wallets) | 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](https://developers.bead.xyz/payments) to implement payment creation, hosted checkout, status handling, and primary payment webhook configuration.
2. Use [Webhook Event Reference](https://developers.bead.xyz/reference-guide/operational-guides/webhook-event-reference) when hardening your webhook listener for production, especially around verification, retries, logging, and idempotency.
3. Use [Compatible Crypto Wallets](https://developers.bead.xyz/reference-guide/operational-guides/compatible-crypto-wallets) when planning QA, demos, and support expectations across wallet types.
4. Use [Payment Scenarios](https://developers.bead.xyz/reference-guide/payment-scenarios) 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](https://developers.bead.xyz/payments)                                   | Core payment API flows, hosted checkout, status checks, receipts, and payment webhooks |
| [Payment Scenarios](https://developers.bead.xyz/reference-guide/payment-scenarios) | Outcome-specific handling for non-happy-path payment states                            |
| [Onboarding](https://developers.bead.xyz/onboarding)                               | Merchant application flows and onboarding event handling                               |
| [Core Concepts](https://developers.bead.xyz/reference-guide/core-concepts)         | Cross-cutting concepts such as authentication, environments, and rate limits           |