Source type
Paddle Source Configuration
Paddle sources receive billing, subscription, transaction, product, and customer webhooks with Paddle-Signature verification.
Paddle configuration
Create a Paddle source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Endpoint Secret Key values for provider signature. FastHook uses these settings to validate each Paddle delivery before it enters the routing workflow.
Source TypePADDLE
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsEndpoint Secret Key
{
"type": "PADDLE",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "PADDLE",
"webhook_signing_secret": "provider-secret"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}Paddle request contract
FastHook verifies paddle-signature by signing timestamp + ':' + raw body with HMAC-SHA256.
Paddle headers
Preserve paddle-signature when sending Paddle test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.
paddle-signatureSemicolon-separated ts and h1 signature values.
Paddle setup
- Create a Paddle notification destination with the FastHook Source URL.
- Paste the endpoint secret key into FastHook.
- Keep sandbox and production Paddle endpoints separate.