Get notified when a customer's payment method changes

If your integration shows subscriptions and payment status in your own system, it can now receive a webhook when a customer’s payment method changes. It no longer needs to keep asking for the customer’s payment methods to notice.

There are three new events for the payment method itself:

• payment_method.created when a card or SEPA payment method is saved, for example at checkout, in the customer portal or through the API.
• payment_method.updated when the payment method becomes the customer’s default, gets a new expiry date or can no longer be used.
• payment_method.deleted when the payment method is removed.

Each event contains the payment method exactly as the API returns it: card brand, last four digits, expiry, and whether it is the default and usable. Card numbers are never included.

Subscriptions now also show which payment method they are charged with: payment_method_uuid in the API and in every subscription webhook. The new subscription.payment_method_changed event tells your integration when that changes, for example when the customer replaces the card after a failed payment.

Turn the events on in the webhook settings when the API app is enabled, and send a test sample of them to your receiver first. Installed integrations can subscribe to them as well.

No event is sent just because a card passes its expiry date. Read is_expired and is_usable on the payment method instead.