Knowledge Base
Deviking Paddle Gateway for Woocommerce

Setting Up Your Paddle Live Account

Before configuring Deviking Paddle Gateway, you need a Paddle account and the required credentials.

Paddle provides two completely separate environments:

  • Sandbox — for testing without real payments
  • Live — for accepting real customer payments

Sandbox and Live use separate API keys, client-side tokens, webhook destinations and transaction data. Credentials from one environment cannot be used in the other.

1.1 Start with Paddle Sandbox

We strongly recommend completing your integration in Sandbox before switching to Live.

Create or sign in to your Paddle Sandbox account.

In Sandbox:

  • No real money is charged
  • Test cards can be used
  • Checkout displays a Test Mode indicator
  • Live website approval is not required
  • Sandbox credentials are completely separate from Live credentials

1.2 Set the Default Payment Link

Paddle requires a Default Payment Link before transactions can be created.

Go to:

Paddle Dashboard → Checkout → Checkout settings

Find:

Default payment link

Enter your website URL, for example:

https://example.com/

In Sandbox, Paddle also allows test domains or localhost.

Click Save.

A Default Payment Link is required even when the checkout itself is opened dynamically by Deviking Paddle Gateway.


1.3 Create the Sandbox API Key

Go to:

Paddle → Developer tools → Authentication → API keys

Click:

New API key

Use a recognizable name, for example:

Deviking Paddle Gateway

The API key is used by your WooCommerce server to securely communicate with Paddle.

After creating it, copy the key immediately.

A Sandbox API key normally starts with:

pdl_sdbx_apikey_

Paddle only displays the full API key when it is created, so store it securely.


1.4 Create the Sandbox Client-side Token

On the same Authentication page, open:

Client-side tokens

Click:

New client-side token

For example, name it:

Deviking Paddle Checkout

Copy the generated token.

Sandbox client-side tokens start with:

test_

The client-side token is used by Paddle.js to securely open the Paddle Checkout in the customer’s browser.


1.5 Create the Sandbox Webhook

First install Deviking Paddle Gateway in WordPress because the plugin will display the exact webhook URL that you need.

After installation, go to:

WooCommerce → Settings → Payments → Paddle

You will see:

Paddle Webhook URL

It will normally look similar to:

https://example.com/?wc-api=deviking_paddle

Copy this URL.

Now go to:

Paddle → Developer tools → Notifications

Click:

New destination

Set:

Notification type: URL

Paste the Paddle Webhook URL from WooCommerce.

Subscribe at least to the following events:

  • transaction.paid
  • transaction.completed
  • transaction.payment_failed
  • transaction.canceled

Save the destination.

Then open the destination again and copy its:

Secret key

Each Paddle notification destination has its own secret key, which is used to verify that incoming webhooks genuinely came from Paddle.

You will enter this value later into:

Sandbox Webhook Secret

inside Deviking Paddle Gateway.