> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/release-notes/new-rn.md). # New RN ## June 2026 {% updates format="full" %} {% update date="2026-07-09" tags="new,enhancement,fix" %} ## If a SEPA Direct Debit payment fails, shoppers can now retry it directly from the retry page, just as they can at checkout. This gives customers a straightforward second chance to complete their purchase, helping you recover orders that would otherwise be abandoned after a single failed attempt. If a SEPA Direct Debit payment fails, shoppers can now retry it directly from the retry page, just as they can at checkout. This gives customers a straightforward second chance to complete their purchase, helping you recover orders that would otherwise be abandoned after a single failed attempt. {% endupdate %} {% update date="2026-07-09" tags="new,fix,enhancement" %} ## {% endupdate %} {% update date="2026-07-09" tags="new,fix" %} ## test {% endupdate %} {% endupdates %} ## May 2026 #### Retry SEPA Direct Debit payments from the retry page * If a SEPA Direct Debit payment fails, shoppers can now retry it directly from the retry page, just as they can at checkout. This gives customers a straightforward second chance to complete their purchase, helping you recover orders that would otherwise be abandoned after a single failed attempt. #### More flexible scheduled subscription changes (API) * The Schedule Subscription Changes API now treats Product Code, Pricing Options, and Quantity as independent, optional fields. You can schedule a product change without sending pricing options (or vice versa); any field you leave out keeps its current value at renewal. Previously these fields had to be sent together, which forced extra work and risked overwriting values unintentionally; now integrations are simpler, and changes are more predictable. #### Test Google Pay end-to-end in the sandbox * You can now run structured Google Pay test orders in the sandbox, covering scenarios such as declines, network errors, and wallet issues. This lets you confirm how Google Pay behaves across real-world situations before going live, reducing the risk of payment problems reaching your shoppers.
Improved * Auto-renewal reminder emails can now show the gross and net price the shopper actually paid in their last billing cycle, instead of the catalogue list price. Add the new variables from the Email Template Manager. Customers who received a promotional discount previously saw an incorrect amount in these reminders; now they see what they were really charged, which reduces confusion and pricing-related support queries. * Shoppers checking out with a free product or a 100% discount coupon in ConvertPlus are no longer asked for payment details - the checkout recognises zero-value orders and skips the payment step. Removing an unnecessary step for orders that cost nothing cuts checkout friction and drop-off, so more free sign-ups and promotions convert. * The American Express logo in ConvertPlus and 2pay.js has been updated to the latest brand guidelines. This keeps your checkout compliant with Amex's branding requirements and shows shoppers a current, familiar logo they recognise and trust.
Fixed * Fixed the iDeal payment flow in the default flows cart when it is loaded inside an iframe, including correct handling of the redirects iDeal requires. Merchants who embed the cart in an iframe can now offer iDeal reliably, so shoppers in the Netherlands can pay with their preferred method. * Fixed an issue that caused an incorrect number of devices to be sent in the LCN for certain subscriptions. * Fixed an issue where certain refund emails were sent with no recipient. * Fixed an issue where subscriptions would not be disabled automatically after canceling an order. * Fixed an issue where trying to access the Lead management section in the Merchant Control Panel would display a 500 error.
--- # 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.2checkout.com/release-notes/new-rn.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.