Immediate invalidation of keys after reconnection

[daledupreez]

Description

We have had one merchant report of a really confusing and frustrating situation. After reconnecting to Stripe, they have one or two successful API requests using the newly received key, whereafter Stripe API requests fail due to the secret key having been invalidated. The specific error code that gets returned is platform_api_key_expired.

Steps to reproduce

The merchant that can reproduce this issue triggered a reconnection from the Stripe Settings tab, and could never get the reconnection to "stick".

Expected behavior

The reconnection should complete and the key should remain valid.

Screenshots

System report

System report

Additional context

Original report:

• Persistent reconnection notice with v10.0.0 #4729
• STRIPE-745
  Internal issue: 10365825-zen

[daledupreez]

Note that the following changes in 10.1.0 may help with diagnosing and debugging this issue further:

• Log the masked secret key when making API calls #4761
• Add verbose debug mode for OAuth connect flow #4765

[daledupreez]

To be explicit, any sites that encounter this error should attempt to enable both standard logging AND the verbose logging implemented in #4765, which can be done via the following code snippet:

add_filter( 'wc_stripe_is_verbose_debug_mode_enabled', '__return_true' );