What problem does it solve? Moving a payment integration from development to production is risky: test and live environments are fully separate, the SDK defaults to live mode, and unsigned webhook test payloads can silently break verification logic. This Skill guides you through test-mode payment scenarios, webhook testing, and a complete go-live checklist so nothing is missed before launch. ## Core Features & Use Cases - Test payment scenarios: Simulate card success, declines, insufficient funds, subscription renewal failures, and UPI outcomes using documented test card numbers and VPAs. - Webhook testing: Forward real test-mode events to localhost with dodo wh listen, or trigger mock events with dodo wh trigger while understanding which payloads are unsigned. - Environment migration and launch checks: Recreate products in live mode, rotate keys, reconfigure webhook URLs and secrets, and verify KYC, monitoring, and checkout settings. - Use Case: Before launching a SaaS billing flow, you simulate a failed subscription renewal with card 4000 0000 0000 0069, confirm payment.failed and subscription.on_hold webhooks arrive locally, then walk the go-live checklist to switch to live keys and product IDs. ## Quick Start Ask the agent to walk you through testing a Dodo Payments checkout in test mode and then run the go-live checklist before switching to production.