Hey @brett_single,
We can take a look at that change in behavior. I’m assuming you’re using the subscriptionBillingAttemptCreate mutation?
Can you share the API version you are using and if possible, the request id from the response that returned the error?
UPDATE: Looks like another developer has reported this here. If you can, keep an eye on that thread for updates