We experienced the same issue starting 11/3 as well. Specifically it was
affecting our call to CreateCustomerPaymentProfile, where the
customPaymentProfileId in the response was appearing as empty, due to
their unannounced addition of the customerPro...