Braintree: "Client token has expired" error - Token not regenerated automatically on checkout

[pratikkamani]

Preconditions and environment

-Magento 2 version: 2.4.7-p3
-PHP version: 8.2
-paypal/module-braintree-core version : 4.6.1-p3

-Braintree Payment Method configured with Merchant ID, Public Key, Private Key, and validated Credentials successfully.

Steps to reproduce

1. Configure Braintree payment in Magento Admin using valid credentials.
2. Leave the site idle for more than 24 hours (token expiry period).
3. Visit the checkout page.
4. Attempt to proceed with Braintree payment.

Expected result

• Braintree should regenerate the client token automatically if the previous one is expired.
• Checkout should load the payment method without errors.

Actual result

Checkout displays an error:
Either the client token has expired and a new one should be generated or the tokenization key has been deactivated or deleted.
Simply opening Stores > Configuration > Sales > Payment Methods in the admin temporarily resolves the issue.

Additional information

• We have a storefront built on VueJS, checkout and admin interfaces on Magento 2.
• This issue repeats every Sunday or after site inactivity.
• Admin config visit appears to refresh the token indirectly.
• This could be related to the token lifecycle not being managed properly in Magento’s Braintree module.

Braintree.mp4

Release note

Suggestion
Implement a mechanism to regenerate the client token automatically when expired, especially on the checkout load.

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @pratikkamani. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @pratikkamani ,

Thank you for your report and collaboration on this issue.

We attempted to reproduce the reported behavior on a Magento 2.4.8 instance, but were unable to replicate the issue. Please find the screen recordings attached for your reference.

40085.1.1.1.mov

Steps we followed:

• Configured Braintree payment in Magento Admin using valid credentials.
• Left the site idle for over 24 hours (token expiry period).
• Navigated to the checkout page.
• Attempted to proceed with Braintree payment.

Based on our testing, everything functioned as expected. Could you kindly recheck on your end and let us know if we might be missing any specific configuration or step?

As we await further input, we are moving this ticket to "Needs Update" status.

Thank you again!