--- title: "Releases CW33-2026" slug: "releases-cw33-2026" description: "Enhance your subscription management with customizable pause settings, improved SEPA error messages, and better checkout tracking for failed payments." updated: 2026-08-10T14:08:06Z published: 2026-08-10T14:08:06Z canonical: "help.frisbii.com/releases-cw33-2026" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.frisbii.com/llms.txt > Use this file to discover all available pages before exploring further. # Releases CW33-2026 ## B.260812-MINOR ### šŸ”§ Improved #### Customizable pause settings Separate maximum pause durations can now be set for time-based and issue-based subscriptions, for both the self-service portal and the Merchant Backend. You can define these durations in days, weeks, months, or years. For example, you can grant customers with a time-based subscription a longer pause period than customers with issue-based subscriptions. In addition, you can give your support agents a longer allowable pause period, so they can pause a customer's subscription as a goodwill gesture when needed. ![](https://cdn.document360.io/b84e1b5d-2ba6-4465-8c62-fb45a2f31314/Images/Documentation/image-TRUTNDU5.png) --- #### New SEPA error messages added With [API.260812-MINOR](/frisbii-media/docs/api-260812-minor#more-detailed-error-messages-for-failed-sepa-payments) we have added more SEPA error messages which will be displayed in Frisbii Mediaā€™s Transaction Log in case of failed payment. ****Find all SEPA error messages and what to to here**:** | Failure code | Explanation | Next steps | | --- | --- | --- | | `invalid_account_number` | The transaction canā€™t be processed because the IBAN that your customer provided is incorrect. | Contact your customer for correct account details, then retry the transaction. | | `account_closed` | The payment canā€™t be processed because your customerā€™s bank account is closed. | Contact your customer for new account details, then retry the transaction. | | `generic_could_not_process` | Stripe canā€™t identify a specific reason for the payment failure. | Contact Support for more information. | | `insufficient_funds` | The payment process canā€™t be completed because your customerā€™s bank account lacks the necessary funds. | Contact your customer to verify that they have the required funds, then retry the transaction. | | `debit_not_authorized` | The payment doesnā€™t have an authorised mandate. | Collect a new mandate, then retry the transaction. | | `debit_authorization_not_match` | The transaction canā€™t be processed due to missing or incorrect mandate information. | Collect a new mandate from your customer, then retry the transaction. | | `debit_disputed` | Your customer requested that their bank refund this payment. | Contact your customer to resolve any dispute, then retry the transaction. | | `recipient_deceased` | The mandate was set up on the account of a potentially deceased individual. | Verify your customerā€™s status before retrying the transaction. | | `branch_does_not_exist` | The payment canā€™t be processed because the bank branch associated with your customerā€™s IBAN doesnā€™t exist. | Contact your customer to provide new account details, then retry the transaction. | | `incorrect_account_holder_name` | The transaction canā€™t be processed because your customerā€™s account information is missing or incorrect. | Collect a new mandate and ask your customer to provide their name and address exactly as it appears on their bank account. Then, retry the transaction. | | `refer_to_customer` | We donā€™t have detailed information about the payment failure because your customerā€™s bank didnā€™t provide a reason code. | Contact your customer for more information. | --- ### šŸ› Bug Fixes **PLEN-11399**: The delivery log in the subscription view could fail to display if a stored delivery address could no longer be found. The delivery log now displays correctly in this case and marks the affected address as "deleted." --- ## S.260812-MINOR ### šŸ› Bug Fixes **PLEN-11451:** The self-service portal had several accessibility issues, including missing labels, unclear error messages, and unmarked required fields. These issues have been fixed: screen readers and password managers now work correctly, and required fields are clearly marked. **PLEN-11115:** In certain cases involving an age-based rule on the offer, the user management area of the self-service portal sometimes displayed the wrong multi-user subscription as active. The actually active subscription is now displayed reliably. --- ## C.260812-MINOR ### šŸ”§ Improved #### Checkout tracking now reports failed payment attempts Until now a failed payment was not visible in the checkout tracking data. From a tracking point of view, a customer switching the payment method and a customer entering a wrong IBAN looked nearly the same. The checkout tracking data now reports whether the page a customer sees is the result of a failed action, together with the cause of that failure: - `failed `- true if the page is the result of a failed action, otherwise false - `failureType `- the cause of the failure: - `USER_ERROR `- caused by the customer and usually correctable, e.g. a declined card, a wrong IBAN, or an abort at the payment provider - `CONFIGURATION_ERROR `- caused by the merchant configuration - `TECHNICAL_ERROR `- caused by Frisbii Media or the payment service provider - `UNKNOWN `- a failure happened, but the cause cannot be determined - `NONE `- no failure - `errorCode `- the API error code of the failure, 0 if unknown The new values are available in the [WebAnalyticsLoad](/frisbii-media/docs/web-analytics-integration) event and in the action / Statistic tracking payload, and additionally as data-failed, data-failure-type and data-error-code attributes on the checkout body element. No action is required. Existing tracking callbacks and events keep working unchanged - the new values are added on top. Applies to the V3 checkout.