Payments
Paddle
Connect Paddle for Customers, the revenue of Analytics and the chargebacks of Disputes.
Connect Paddle so that Customers shows who pays you, what each one pays and who is about to leave. Analytics then ties transactions and renewals to the visits behind them, and shows MRR. Disputes shows each chargeback of Paddle and how it ended. Troopy never changes anything in Paddle.
Before you begin
Owners and admins connect, replace and disconnect a service.
What Troopy reads, and for what
| Product | What it reads |
|---|---|
| Customers | Each subscription with its customer, and the transactions. A read each hour. |
| Analytics | New transactions and renewals every 5 minutes, and MRR. |
| Disputes | The chargebacks. Paddle answers them itself, so Troopy prepares no evidence. |
Connect Paddle
- Open Settings > Apps, and select the tile of Paddle. Its card opens.
- Select Create the key in Paddle. For a test account, select Or in the sandbox.
- Under Developer tools > Authentication, create an API key named Troopy.
- Give it Read on Transactions, Subscriptions and Customers only, and copy it.
- Paste it into the card, and select Connect Paddle. The key starts with
pdl_live_apikey_orpdl_sdbx_apikey_.
Chargebacks
To read the chargebacks for Disputes, the key also needs Read on Adjustments. A key with no such access reads no chargeback, and the rest works.
How Troopy reads chargebacks
- A chargeback of Paddle is an adjustment. Paddle says a win, and never a loss.
- A chargeback with no win after 120 days counts as lost.
- An early warning and its chargeback are one dispute.
- The troop chat hears of a chargeback only when it is 2 days old at most.
Replace or disconnect
- Replace key puts a new key in the place of the old one.
- Disconnect removes the key. Customers takes the subscriptions of Paddle off its customers.
Paddle keeps a refund as an adjustment. Customers does not read it there, so that payment still counts.