---
title: >-
  Payment method identifier now required for customerPaymentMethodRemoteCreate -
  Shopify developer changelog
description: >-
  Shopify’s developer changelog documents all changes to Shopify’s platform.
  Find the latest news and learn about new platform opportunities.
source_url:
  html: >-
    https://shopify.dev/changelog/posts/payment-method-identifier-now-required-for-customerpaymentmethodremotecreate
  md: >-
    https://shopify.dev/changelog/posts/payment-method-identifier-now-required-for-customerpaymentmethodremotecreate.md
metadata:
  effectiveApiVersion: 2026-07
  affectedApi:
    - displayName: Admin GraphQL API
      handle: admin-graphql
  primaryTag:
    displayName: API
    handle: api
  secondaryTag:
    displayName: Breaking API Change
    handle: breaking-api-change
  indicatesActionRequired: false
  createdAt: '2026-03-18T11:40:22-04:00'
  postedAt: '2026-04-01T08:00:00-04:00'
  updatedAt: '2026-03-18T12:26:54-04:00'
  effectiveAt: '2026-07-01T08:00:00-04:00'
---

April 1, 2026

# Payment method identifier now required for customerPaymentMethodRemoteCreate

DateApril 1, 2026

Version[2026-07](https://shopify.dev/changelog?api_version=2026-07)

Flags[Breaking API Change](https://shopify.dev/changelog?filter=breaking-api-change)

SurfacesAPI

Affected APIs[Admin GraphQL API](https://shopify.dev/changelog?api_type=admin-graphql)

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.