The agent plans in your time zone, and buyers download every e-book in an order

Improvements

• Improved The agent plans in your time zone. Times you give the agent for posts, sales, discount codes, bookings and access end dates are read in your account's time zone, and the agent names the zone when it isn't Polish time. A Polish account without its own zone stays on Polish time. You can change the zone in the account settings, which now show the zone in use.
• Improved Downloads for every product in an order. The thank-you page gives the buyer a download button for each e-book or file product in the order, also one bought as an order bump on an e-book or a course. A course keeps its login button next to the download. Learn more
• Improved Unsent replies stay in the community chat. A reply you started in a channel or a thread stays when you switch a tab, open another channel or reload the page, and it comes back when sending fails. Each channel and thread keeps its own. In the browser and in the mobile app.

Fixes

• Fixed Order bumps. A bump is granted with its own quantity, not the main product's, and a paid bump is never skipped: the purchase completes only once the bump's access is granted.
• Fixed The whole amount when archiving a subscriber with a refund. The refund of the last payment covers the whole invoice, also with an order bump, a quantity above one or a price with tax added on top. The order stays under its own product when you refund a bump's access.
• Fixed Renewal refunds settle. A renewal refund that Stripe confirms later, or a full refund of a renewal made in the Stripe dashboard, marks the order as refunded.
• Fixed The chat box keeps its place. Editing a line in the middle of a longer message in the community chat no longer makes the box jump and hide the lines below.
• Fixed Old test links say what to do. An old test link to a checkout says it's no longer valid and that you can create a new one in the checkout settings, instead of showing an error.

API, MCP and CLI

• API Refund state when archiving. Archiving a client with a refund through the API returns refund.state (confirmed, pending or failed) next to the status, so a refund that failed is visible.