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 for payment creation, payment statuses, receipts, payment webhooks, and testing flows.
Go to Payment Scenarios for non-happy-path payment outcomes such as underpaid, overpaid, reclaim, and refund or return guidance.
Go to Onboarding for merchant application submission, signing, status tracking, and onboarding webhooks.
What you’ll find here
Supplemental reference for event payloads, signature verification, retry behavior, idempotency, and webhook consumer design.
Wallets to validate during QA, expected wallet capabilities, and practical caveats for testing and launch readiness.
How to use this section
Start in Payments to implement payment creation, hosted checkout, status handling, and primary payment webhook configuration.
Use Webhook Event Reference when hardening your webhook listener for production, especially around verification, retries, logging, and idempotency.
Use Compatible Crypto Wallets when planning QA, demos, and support expectations across wallet types.
Use 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
Core payment API flows, hosted checkout, status checks, receipts, and payment webhooks
Outcome-specific handling for non-happy-path payment states
Merchant application flows and onboarding event handling
Cross-cutting concepts such as authentication, environments, and rate limits
Last updated