Skip to content
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

Settings API: New API Key Field Needed #1540

Closed
3 tasks done
DevinWalker opened this issue Feb 23, 2017 · 0 comments
Closed
3 tasks done

Settings API: New API Key Field Needed #1540

DevinWalker opened this issue Feb 23, 2017 · 0 comments
Assignees
Milestone

Comments

@DevinWalker
Copy link
Member

DevinWalker commented Feb 23, 2017

Issue Overview

Give payment gateways require a field that is first a text field when not completed with customizable placeholder text. When the field has a value saved, it is turned into a password field.

This has been brought up by our customers a number of times and the most common scenario is that they don't want sensitive information freely viewable by other site admins. As well, we can suggest Lockr if they want super secure protection once that integration is released.

Todos

  • Develop new Settings API field
  • Test with individual plugins
  • Integrate with each payment gateway
@DevinWalker DevinWalker added this to the 1.8.3 milestone Feb 23, 2017
@DevinWalker DevinWalker self-assigned this Feb 23, 2017
DevinWalker pushed a commit that referenced this issue Feb 23, 2017
DevinWalker pushed a commit that referenced this issue Feb 23, 2017
DevinWalker pushed a commit that referenced this issue Feb 23, 2017
@DevinWalker DevinWalker mentioned this issue Feb 23, 2017
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant