Contents
What PaddleSubs Stores in Paddle developer
PaddleSubs keeps its settings in the custom_data of Paddle entities, so a site
connected to the same Paddle account can rebuild them. Don't edit these keys in Paddle by hand unless you
mean to change the setting.
- Products
-
Category(the category and its parents, top first, as[{"title": …, "alias": …}]; an olderApps/Devalias path is still read),Access(the access level's title),Level(the level's name),Add groups,Remove groups,Purchase typeandLicense policy. Saving a product writes its custom data whole, so keys PaddleSubs no longer uses are dropped.Not verified: whether Paddle replaces a product's custom data on update or merges it with the keys already there. If it merges, old keys stay.
- Prices
-
Billing type,Period frequency,Period intervalandFixed end date: how long a one-time price's access lasts. - Discounts
-
Group key,Ordering,Scope,From,To,Same category,Eligible after expirationandNumber of products: the rules of relation and bundle discounts. A category scope uses the same structure as a product'sCategory. - Transactions
-
Access subscriptionson transactions saved from the administrator, which restores; andpaddlesubs_license_idon checkouts started from a renewal link.
Paddle's dashboard may not show nested custom data in full; use Paddle's API to inspect it. Category ids are never stored, only titles and aliases, so the web addresses of categories survive a rebuild while their ids don't.