testing-and-go-live

Test Dodo Payments integrations in test mode and validate production launch readiness.

6|1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/dodopayments/dodo-agent-plugin --skill testing-and-go-live-dodopayments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-and-go-live
Source: https://github.com/dodopayments/dodo-agent-plugin/tree/main/plugins/dodopayments/skills/testing-and-go-live
Command: npx skills add https://github.com/dodopayments/dodo-agent-plugin --skill testing-and-go-live-dodopayments

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about testing-and-go-live

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test Dodo Payments in test mode?

Set environment to 'test_mode' when creating the DodoPayments client and use a test API key prefixed dodo_test_ from the dashboard. Test mode uses https://test.dodopayments.com and is fully separate from live data.

What test card numbers work for Dodo Payments?

Use 4242 4242 4242 4242 for success, 4000 0000 0000 0002 for a generic decline, 4000 0000 0000 9995 for insufficient funds, and 4000 0000 0000 0069 to simulate a failed subscription renewal. Any future expiry and any CVC work in test mode.

How do I test Dodo Payments webhooks locally?

Install the dodopayments-cli, run dodo login with a test key, then use dodo wh listen http://localhost:3000/webhook to forward real signed test events. Use dodo wh trigger for mock events, but those payloads are unsigned and require unsafeUnwrap.

Why does my Dodo Payments test code hit production?

The SDK defaults to live_mode when the environment parameter is omitted. Always pass environment: 'test_mode' explicitly during development, otherwise test requests create real charges against the live API.

Can I reuse test product IDs in live mode?

No. Test and live environments are completely separate, so a product ID from test mode does not exist in live mode. Recreate the product in live mode via the API or dashboard and update your code to the new live product ID.