Release testing instructions for WC Payments 5.1.0

Client secret encryption toggle

We added a new setting in Payments > Settings page, in the Advanced section, named Enable public key encryption, which is encryption the public_secret exposed in the network request made to our server.

Run these tests with the setting enabled, and check if the checkout works as expected.

Before switching the toggle on

Note: No need to test this every time, just seeing this once will be enough before activating the toggle

• Open network tab on chrome developer tools before you switch to the Checkout page.
• Switch to checkout page
• On the response to the wc-ajax=create_payment_intent or wc-ajax=create_setup_intent calls, you should see a data.client_secret key with this pattern: pi_xxx_secret_yyy

After switching the toggle:

• The data.client_secret should be seen as encrypted.

Flows that need testing after enabling the toggle

• Checkout with normal credit card
• Blocks: Checkout with normal credit card
• UPE - Regular Checkout
• UPE - Manage Payment Methods
• UPE - Checkout with blocks
• Renew subscription