Menu
Feedback
Start here
Tutorials
Developer portal

Known Issues
Support Rules
Troubleshooting

Frequently Asked Questions
Announcements
News
Announcements
Credentials in gateway affiliations must be provided by the payment provider
Photo of the author
PedroAntunesCosta
Published on 10/13/2022
Last update on 4/3/2023

When configuring gateway affiliations in the Admin to make payments available in your store, you must enter the following credentials to identify your store for the payment provider: Application Key and Application Token. These credentials have the same function as user and password and must be provided by the payment provider.

What has changed?

These credentials should not be mistaken for the Application Key and Application Token credentials used in VTEX APIs for integrations. In this case, credentials are generated in the Admin and used to identify external systems that access VTEX stores' services. You can identify an Application Key generated in the Admin by having vtexappkey- at its beginning.

If your store has any gateway affiliations configured with a pair of Application Key and Application Token generated in the Admin, you must replace them by April 30, 2023.

Why did we make this change?

Using the Application Key and Application Token generated in the Admin in gateway affiliations can pose a security risk, as keys are being shared to access services from a VTEX store. The role assigned to a credential defines which store resources a given user can access. Depending on the role, anyone with access to the credentials can access the allowed resources improperly. You can check the instructions in the Application Keys article to disable an Application Key if needed.

What needs to be done?

The payment provider must provide the credentials for the affiliation being configured. The keys must be replaced by April 30, 2023. You can find the instructions for configuring them in the Registering gateway affiliations article.

Was this helpful?
Yes
No
Suggest Edits (GitHub)
On this page
Still got questions?
Ask the community
Find solutions and share ideas in the VTEX community.
Join our community
Request support from VTEX
For personalized assistance, contact our experts.
Open a support ticket
GithubDeveloper portalCommunityFeedback