Sandbox

Setup and test your Paddle integration in Paddle’s Sandbox Environment. Use our test cards to test end-to-end workflows.

Paddle Sandbox is completely separate from the Paddle Production environment. This means products/plans and dashboard settings will need to be configured independently in each environment.

Launching the Paddle Checkout

To open checkouts, you will need to specify the sandbox environment in your front end JavaScript code. Without this, the Paddle checkout will not launch.

<script src="https://cdn.paddle.com/paddle/paddle.js"></script>
<script type="text/javascript">
  Paddle.Environment.set('sandbox');
  Paddle.Setup({ vendor: 1234567 });
</script>

Sandbox API calls

To make API calls to your Sandbox environment you must add the sandbox- prefix in the URL hostname. For example:

https://sandbox-checkout.paddle.com/api/

Test Cards

Real card information cannot be used in the Paddle Sandbox. For the test cards below, enter a valid expiration date in the future, and any random CVC number. Each test card’s billing country is set to U.S.

Card Type Card Number
Valid card without 3DS 4242 4242 4242 4242
Valid card with 3DS 4000 0038 0000 0446
Declined card 4000 0000 0000 0002

Testing PayPal

Paddle’s checkout supports payments via PayPal. To make test transactions using PayPal, you will need to first create a PayPal Sandbox account. You can then enter your PayPal sandbox credentials into the Paddle checkout to complete test transactions.

Moving to Production

When moving from Sandbox testing to Production there a few things to remember.

  1. Remove “sandbox-” prefix from the API endpoints
  2. Update Vendor ID
  3. Update API Auth key
  4. Update Product/Plan IDs
  5. Remove Paddle.Environment.set('sandbox') from front end JavaScript code
  6. Update Whitelisted webhook alert IPs (if used)

We recommend having two sets of application settings, one for Sandbox and one for Production to help avoid mistakes.