Payment method identifier now required for customerPaymentMethodRemoteCreate

As of API version 2026-07, the payment method identifier field is now required when using the customerPaymentMethodRemoteCreate mutation with Stripe, Authorize.net, or Braintree inputs.

The affected fields are:

• paymentMethodId on RemoteStripePaymentMethodInput
• customerPaymentProfileId on RemoteAuthorizeNetCustomerPaymentProfileInput
• paymentMethodToken on RemoteBraintreePaymentMethodInput

These fields were previously optional at the schema level but are required for the payment method to be functional. Without a payment method identifier, remotely created payment methods cannot be used for payment processing. This change aligns the API schema with existing runtime requirements.

If you are already passing a payment method identifier when calling this mutation, no changes are needed. If you are not, update your integration to include the appropriate identifier for your gateway before adopting API version 2026-07.