> 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-failure-notification.md). # Sending a payment failure notification When processing transactions, it's crucial to promptly notify customers about any issues that may arise, such as payment failures, to ensure transparency and maintain customer trust. The payment failure notification in our system is an automated response designed to alert the customer whenever a transaction does not go through successfully. ## Notification trigger This notification is primarily triggered by the `submitOrder` method within the `SubscriptionOrderHelper.java` class, ensuring that customers are quickly informed and can take necessary action to rectify the issue. --- # 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-failure-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.