-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding considerations for tokenization #354
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should add the same comment to React / React Native (if we do it in both)?
Basis Theory {{ language }} SDK uses camel case for most methods and converts these properties to snake case when sending requests to the API.
Co-authored-by: Davi Aquino <djejaquino@users.noreply.github.com>
## Before You Begin | ||
|
||
This SDK requires the use of an API Key associated with a **Public Application**, which only allows `token:create` or `token:update` | ||
permissions to mitigate the risk that these API keys may be publicly exposed within your frontend applications. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You probably don't want to hear this, but this is no longer true - for all these client SDKs. We use Public Apps with no permissions for invoking Proxies and Reactors via Sessions.
I don't expect you to fix in this PR though, we should review the SDKs pages.
🎉 This PR is included in version 1.141.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
tokenize
in js projects.Testing required outside of automated testing?
Screenshots (if appropriate):
Rollback / Rollforward Procedure
Reviewer Checklist