INTEGRATIONS
Paddle
How to connect Paddle to NoChurn: what to paste, what NoChurn does in Paddle and what it reads.
Connect
In NoChurn, test mode first, open Integrations, pick Paddle and paste the fields below (or send them to POST /v1/billing_connections with provider: "paddle"). Use the provider’s test or sandbox credentials in test mode. Secrets are stored encrypted and never returned by the API.
| Field | Where to find it |
|---|---|
api_keySECRET | Developer tools › Authentication (sandbox key in Test mode), with the Customer portal session permission (card update links) |
The connection returns a webhook_url. Create a webhook endpoint on that URL in Paddle, then paste the signing secret Paddle gives you in NoChurn (webhook_secret on PATCH /v1/billing_connections/{id}).
What NoChurn does
| Retries | Paddle retries the payment (its own retry settings). NoChurn sends the recovery emails. |
|---|---|
| Card update | The recovery emails link to Paddle’s own page where the customer updates the payment method. |
| Cancel flow offers | Applied in Paddle: discount, pause. An offer the provider cannot apply reaches your backend as a billing.*_requested webhook. |
| Cancellation | A cancellation requested in the cancel flow is carried out in Paddle. |
| Disputes | Paddle handles disputes. NoChurn shows them on the customer’s timeline. |
| Events | NoChurn follows Paddle’s webhooks. |
| Import | The last 12 months are imported when you connect (POST /v1/billing_connections/{id}/backfill imports again). |
Fixed by Paddle, not by a setting: retries, disputes. The rest can be changed per connection with PATCH /v1/billing_connections/{id}.
What NoChurn reads
- Customers and subscriptions
- Transactions and failures
- Discounts and prices, to build offers
- Disputes, read only
What stays with Paddle: checkout, payments and payment recovery; sales tax and invoices, as the merchant of record; disputes and refunds. More on the Paddle integration page.