create_client_side_token
Generate client-side tokens to authenticate Paddle.js integrations for specific applications or environments, enabling secure payment processing.
Instructions
This tool will create a new client-side token in Paddle.
Client-side tokens are needed to authenticate with Paddle.js. A token is provided when initializing Paddle.js.
When creating a client-side token, provide a descriptive name to help identify its purpose. Usually created for each application or environment that needs to authenticate with Paddle.js.
If successful, the response includes a copy of the new client-side token entity. The returned token field is the client-side token that needs to be provided when initializing Paddle.js. Can be exposed client-side safely. If it starts with:
test_: The token is a test token for a sandbox environment and shouldn't be used in production.
live_: The token is a live token for a production environment. It can be used to test too but Paddle.js checkouts require real cards.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>"
},
"name": "create_client_side_token"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name of this client-side token. | |
| description | No | Short description for this client-side token. |