> For the complete documentation index, see [llms.txt](https://help.alianhub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.alianhub.com/app-installation-and-start-guide/4.-installation-guide/4.7-payment-configuration/4.7.2-paddle-configuration.md).

# 4.7.2 Paddle Configuration

<figure><img src="/files/ZzJ2rIw9ORj49fWudxC2" alt=""><figcaption></figcaption></figure>

### 4.7.2.1 Add Domain

1. Go to <https://login.paddle.com/signup> and create a new account in Paddle.
2. Now go to Checkout > Website Approval

Here you need to add your domain for which you have generated the license, as provided in the below image

Note: you don’t have to include https\://, www, or specific web pages.

<figure><img src="/files/kahUSjQ5vNpPrTNetdcd" alt=""><figcaption></figcaption></figure>

### 4.7.2.2 Add Payment Link

Here you need to add a default payment link. You can use the below provided url by replacing YOUR\_WEB\_DOMAIN with your own web\_domain\_url

Example: [***https://YOUR\_WEB\_DOMAIN/#/checkout***](https://your_web_domain/#/checkout)

<figure><img src="/files/oN3LOWjOsKtHJnjW1P6J" alt=""><figcaption></figcaption></figure>

### 4.7.2.3 Get Tokens

Now for the further API requests to be handled by paddle, you need to generate an API\_KEY and a Client-side Token.

#### 4.7.2.3.1 Get API Key

For the API key, you can directly get the API key as provided in the below image, as a default API key is already generated. And you can copy and set it in the Paddle API key form field.

<figure><img src="/files/bsCUWeeurNlHomwrUXQU" alt=""><figcaption></figcaption></figure>

#### 4.7.2.3.2 Generate Client-side Token

For the Client-side token, you need to generate a token manually as per below-provided steps

1. Navigate to the Developer tools > Authentication. Now, click on generate a token.

<figure><img src="/files/HWLHfFFQGtVUHOrRsBqy" alt=""><figcaption></figcaption></figure>

2. Enter the name and description of the token.

<figure><img src="/files/447Dr30uv9zfueC8RUef" alt=""><figcaption></figcaption></figure>

3. Copy the generated token

<figure><img src="/files/OkCkSQiMFAyduB4yIXmP" alt=""><figcaption></figcaption></figure>

### 4.7.2.4 Add Webhook

For registering a webhook follow the below-provided steps.

1. Navigate to the Notifications tab, and click on New Destination

<figure><img src="/files/yReVXOzeFr9G5gcRwAZh" alt=""><figcaption></figcaption></figure>

2. Select the events as shown in the image below.

<figure><img src="/files/Fw8TDKaCH858WYSeQnQ9" alt=""><figcaption></figcaption></figure>

### 4.7.2.5 Customize Checkout page

You can customize your checkout page from Checkout > checkout settings tab and then click on Inline tab.

Note: The inline checkout is used in the app. So, in order to customize the checkout you need to make changes here only.

<figure><img src="/files/fontbSbx8AEDH2gqGT7F" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.alianhub.com/app-installation-and-start-guide/4.-installation-guide/4.7-payment-configuration/4.7.2-paddle-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
