- paymentMethodId, customerPaymentProfileId, and paymentMethodToken are now required in the customerPaymentMethodRemoteCreate mutation for Stripe, Authorize.net, and Braintree
- Integrations must include the appropriate identifier before upgrading to API version 2026-07 or remote payment methods will fail
- Optional fields have been made mandatory, making this a breaking schema change