Paddle Billing Client Tokens & docs tweaks #895
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Paddle have recently added client side tokens as a way to interact with the Paddle API using Paddle.js without exposing your API tokens. Paddle recommend using these instead of passing the
seller
option, as new features may require it.The latest feature of Paddle.js is the ability to generate localised price previews on the fly, which is great for building pricing pages as it shows the customer's local currency (with taxes too). This was a feature I've been requesting since the start as the previous version had it too.
This PR adds
client_token
toPaddleBilling
, which is set by environment variables or in the credentials/secrets files.I've also updated the Paddle Billing subscription docs and renamed some
Pay::Paddle
examples toPay::PaddleClassic