We’ve been able to replicate this issue in prior plugin versions so that means it’s likely an internal Stripe error. We’ve reported the issue to their engineers and are waiting for a response.
Stripe has confirmed the issue appears to be internal to their API. They are currently investigating and I will update this ticket once we have a new response from their engineers.
This support request has been set to resolved. Per the response I provided 2 days ago the issue was caused by an internal update that Stripe released on April 9th. It has since been resolved by Stripe.