Paddle Sandbox
A stateful Paddle Billing sandbox with the full subscription lifecycle, 87 endpoints, 14 pre-seeded resource types, and webhook events. Test your Paddle integration without waiting for merchant approval, without touching real customer data, and without burning through Paddle's rate-limited test environment.
Test Scenarios
Run real subscription state transitions and webhook events without a Paddle merchant account.
Subscription Activated
trialing → active transition with subscription.activated event
Subscription Paused
active → paused with subscription.paused webhook
Subscription Resumed
paused → active with subscription.resumed webhook
Subscription Canceled
Cancel at period end with subscription.canceled webhook
Failed Payment
402 transaction.payment_failed lifecycle
Refund Issued
Adjustment created against a captured transaction
Product + Price Setup
Catalog creation flow with recurring billing cycles
Customer Provisioning
Customer created with address and tax data
Webhook Replay
Re-deliver any prior event for handler testing
Pre-seeded Resources
Every Paddle sandbox starts with realistic data across all 14 resource types so you can hit any endpoint immediately.
How It Works
- 1
Open the portal
A stateful Paddle environment is provisioned in under 2 seconds — no signup, no Paddle merchant account.
- 2
Point your app at the sandbox URL
Replace api.paddle.com with the sandbox base URL. Same routes, same payloads, no other code changes.
- 3
Run the full subscription lifecycle
Create products, prices, transactions, and subscriptions. Activate, pause, resume, cancel — every state transition fires the right webhook.
- 4
Verify your handlers
Replay any webhook event into your app and confirm your idempotency, signature verification, and retry logic actually work.
Why a Paddle sandbox?
Paddle's own developer sandbox requires merchant approval, has real rate limits, shares data with your team, and still depends on a network round trip to Paddle's servers. For most integration testing — especially webhook handler testing and subscription lifecycle simulation — that's heavier than you need.
FetchSandbox runs a fully stateful Paddle mock from Paddle's own OpenAPI spec. All 87 endpoints. The full subscription state machine. Real webhook events on every transition. No approval, no quotas, no shared environment, no flakiness.
Use the official Paddle sandbox for end-to-end checkout testing with real card flows. Use FetchSandbox for everything else: building integrations, testing webhook handlers, running CI checks, debugging idempotency, and onboarding new engineers.
FAQ
Do I need a Paddle merchant account?
No. FetchSandbox runs a fully local mock of the Paddle Billing API. No merchant approval, no test mode keys, no rate limits.
Is this different from Paddle's official sandbox?
Yes. Paddle's sandbox still requires a merchant account, calls Paddle's servers, and shares data across your team. FetchSandbox is local, stateful per session, and runs on your machine or in CI without any approval workflow.
Does it support the full subscription lifecycle?
Yes. Subscriptions transition through trialing → active → paused → canceled, and each transition fires the matching webhook event (subscription.activated, .paused, .resumed, .canceled).
Can I test my webhook handler with this?
Yes. Webhook events are emitted on every state change and can be replayed against your handler. This is ideal for testing signature verification, idempotency, and retry logic without waiting for real Paddle events.
Which Paddle API version is supported?
FetchSandbox uses Paddle's public OpenAPI spec for Paddle Billing. The bundled spec covers subscriptions, transactions, products, prices, customers, adjustments, and notifications.
Can I use this in CI?
Yes. Spin up a sandbox via the API, run your integration tests against it, then tear it down. No flakiness from a shared remote sandbox, no quota issues.
Ready to test your Paddle integration?
Free tier — 3 sandboxes, 10,000 requests/month. No credit card required.
Open Paddle Portal