Would you mind also send me the shop id you are testing via private message so I can investigate further?
Topic summary
customerPaymentMethodRemoteCreate returns placeholder (“bogus”) instrument data on creation, e.g., brand “bogus”, expiryYear 1900, empty last digits, despite sometimes successfully creating a payment method.
After creation, querying the customer may later show correct brand, expiry, and last digits for the same CustomerPaymentMethod ID; other times, no payment method is created (empty array seen in a screenshot).
Context: This is a GraphQL mutation used to migrate Stripe payment methods via remoteReference.stripePaymentMethod with a Stripe customerId. “Async” here means the creation completes after the initial request and data may not be immediately available.
Explanation shared: The process is asynchronous; the initial response can contain placeholder values. Implement retry polling with backoff to fetch the real payment method data. If repeated pulls still return bogus data, the creation likely failed.
Actions/updates: Migration scripts were adjusted to account for async behavior. Shopify staff requested shop details via private message and plans to clarify documentation.
Status: Ongoing. No product fix or explicit “processing” status yet; recommended workaround is retry polling.