[cj]

[e-mail]

We're not actively having problems. It was a few months ago. Refreshing myself on the technical details of the payload inconsistency and its cause would take a couple hours. But I believe it was related to us using a 3rd party service (that integrates with Stripe) sending out emails to customers whose charges failed, with a form to collect updated credit card info. The form for updating cc info used payment intents (may be using the wrong term) which is delivered differently than the (old) payment sources type.

The edge case being now there exists 2 groups of customers, 1 group who have a payment method attached under the new payment method / payment intent architecture, and a 2nd group with payment methods attached using the original / old method.

Webhooks often include the payment method, and the data structure for the payment method differs depending on how the payment method was attached to the customer.