November 10, 2026 - Recurly Subscription Management
about 4 hours ago
| Release Date | Feature | Type | Potential Impact | Description / Overview |
|---|---|---|---|---|
| Nov 12 | Recurly Login | Enhancement | Low | Logging in to Recurly is changing slightly. The login page now asks for your email first, then takes you to the password prompt or, if you use SSO, sends you automatically to your identity provider. Password reset has an updated flow with new screens and built-in lockout protection, and a successful reset unlocks your account right away. Your password, SSO setup, and 2FA stay the same, so no action is needed. |
| Nov 10 | Revolv3 Gateway | Enhancement | Low | We'll be storing the target gateway used in Revolv3's orchestration to inform merchant reporting. No integration updates are necessary to receive this update. |
| Nov 10 | Ebanx Gateway | Bug fix | Low | A cosmetic issue was fixed that caused auth codes to not display for card transactions. No integration updates are necessary to receive this update. |
| Nov 10 | Vantiv Gateway | Bug fix | Low | We've updated handling of response format errors when non-Vantiv gateway tokens are sent to Vantiv via custom gateway routing. The response will not reflect invalid data, and no integration changes are necessary for integrators. |
| Nov 10 | Exports | Enhancement | New | Recurly now offers an Unprocessed Notifications - External export that lists App Management external subscriptions with notifications from Apple and Google that couldn’t be processed, along with the identifiers needed to resolve them. This new export will only be available to merchants who have enabled the connections to app stores feature. |
| Nov 10 | Supported Languages | Enhancement | Low | Recurly now supports traditional Chinese (zh-TW) for emails and invoices. This new option can be found in Email Templates -> Configure Languages -> Chinese (Taiwan). |
| Nov 5 | Ebanx Gateway | Bug fix | High | An issue with status updates has been released early, addressing an issue where realtime status updates were not being reflected in reporting. No integration updates are necessary to receive this update. |