> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/commerce-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/commerce-api/admin-apis/subscription-management/subscription-notifications/sending-a-payment-information-change-notification.md). # Sending a payment information change notification You will immediately receive a notification when a shopper changes their payment method or credit card detail information, billing address, or email address. ## Notification trigger In our commitment to maintaining transparency and enhancing user experience, we've implemented a notification system to inform you and shoppers about critical account changes. Specifically, this system sends alerts whenever a shopper's payment method or related account details are modified. These notifications ensure that all parties are immediately aware of updates that could affect transaction processing or account security. Below, we list the various activities that trigger these important notifications. The following activities trigger this notification. * Digital River receives updated stored credit card information from a [Card Account Updater](/commerce-api/admin-apis/subscription-management/subscription-notifications/card-account-updater.md). * The shopper [changes the quantity of the subscription product](/commerce-api/admin-apis/subscription-management/immediately-apply-a-midterm-subscription-change/reducing-the-subscription-renewal-quantity.md) while placing an order and while [placing an order and creating a new billing option](/commerce-api/admin-apis/subscription-management/update-the-subscription-at-the-next-renewal/changing-the-subscriptions-payment-source.md). * The shopper [manually renews their subscription by changing the renewal date](/commerce-api/admin-apis/subscription-management/immediately-change-the-subscription/updating-the-subscriptions-expiration-date.md) and [creating a new billing option](/commerce-api/admin-apis/subscription-management/update-the-subscription-at-the-next-renewal/changing-the-subscriptions-payment-option.md). * The shopper [associates a new payment source](/commerce-api/admin-apis/subscription-management/update-the-subscription-at-the-next-renewal/changing-the-subscriptions-payment-source.md) or [option ](/commerce-api/admin-apis/subscription-management/update-the-subscription-at-the-next-renewal/changing-the-subscriptions-payment-option.md)for an existing subscription. * The shopper [places an order for a mid-term change](/commerce-api/admin-apis/subscription-management/immediately-change-the-subscription/updating-the-subscriptions-expiration-date.md) and [creates a new billing option](/commerce-api/shopper-apis/subscriptions/update-subscription-at-the-next-renewal/changing-the-subscriptions-payment-option.md). * The shopper updates their billing option from the Self-Service section of your online store. The shopper can use the Self-Service section of your online store to edit the existing payment method or add a new payment method. * You submit an `AddUpdateShopperRequest` through the [User Management service](/commerce-api/shopper-apis/shoppers/managing-shoppers/user-management.md) to add or modify a shopper, including the shopper's default billing method. * The shopper goes to your custom page that contains the `displayUpdateAddressPaymentInfoPage` attribute. * You [change the subscription renewal product](/commerce-api/admin-apis/subscription-management/update-the-subscription-at-the-next-renewal/changing-the-subscription-renewal-product.md). * You [change the subscription renewal quantity](/commerce-api/shopper-apis/subscriptions/update-subscription-at-the-next-renewal/changing-the-subscription-renewal-quantity.md). * You update the subscription's payment option with or without the `expand=all` query parameter to create a shopper's billing option for a subscription. * You [update the subscription's payment source](/commerce-api/shopper-apis/subscriptions/update-subscription-at-the-next-renewal/changing-the-subscriptions-payment-source.md). * You [update the subscriber's ship-to and bill-to email addresses for all subscriptions](/commerce-api/admin-apis/subscription-management/subscription-notifications/updating-the-subscribers-email-address.md#changing-the-billing-and-shipping-email-addresses-in-the-cart-before-placing-the-order) so they can receive notifications. * You [create ](/commerce-api/shopper-apis/shoppers/managing-payment-options.md#creating-the-shopper-payment-options)or update a shopper's payment option. * You [get a specific subscription by identifier](/commerce-api/shopper-apis/subscriptions/retrieve-the-subscription/getting-a-subscription-by-identifier.md). The following classes trigger a payment information change notification: #### Payment Information Change Notification Trigger Classes The following classes trigger a payment information change notification: * `RetryAccountUpdateDataProcessor` * `UpdateEmailAddressRequestProcessor` * `PaymentSourceRequestProcessor` * `SubscriptionTask` * `SubscriptionImpl` * `AddEditPaymentForm` * `SubscriptionInfoEditPaymentInfoCommand` * `DisplayUpdateAddressPaymentInfoPage` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.digitalriver.com/commerce-api/admin-apis/subscription-management/subscription-notifications/sending-a-payment-information-change-notification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.