HomeProduct DocsAPI ReferenceChangelog
RecurlyAPI GuidesRecurly.jsWebhooksAPI ReferenceSupportBook demo
Changelog

October 06, 2026 - Recurly Subscription Management

October 6th brings meaningful improvements to card network compliance and checkout flexibility. Stripe merchants will now see Mastercard TLID support for recurring transactions automatically, and Cobadge card support (such as Cartes Bancaires) is now available in Recurly.js for Stripe, for merchants who wish to accept them. Adyen merchants will also benefit from a behind-the-scenes address handling improvement designed to boost authorization rates.

On the fixes side, a reporting issue that was incorrectly combining Apple Pay and credit card data in Analytics has been resolved, giving merchants accurate payment method reporting going forward. Worldpay ACH merchants processing business bank accounts will now see company names correctly carried through NACHA verification, and CyberSource migrations continue — reach out to Support if you have questions about your migration timeline.

Release DateFeatureTypePotential ImpactDescription / Overview
Oct 6Stripe GatewayEnhancementMedRecurly now stores and sends Mastercard Transaction Link IDs (TLIDs) on recurring transactions processed through the Stripe gateway, in alignment with Mastercard's mandate for subscription billing. No integration changes are required.
Oct 6Recurly.jsEnhancementLowRecurly.js now supports co-badge cards (such as Cartes Bancaires) for merchants using the Stripe gateway. This is opt-in and no changes are required if you do not wish to accept co-badge cards. See updated Recurly.js and Stripe integration documentation after release for setup details.
Oct 6Adyen GatewayEnhancementLowRecurly has made a behind-the-scenes update to how address data is sent to Adyen in the United States to improve authorization rates. No integration changes are required.
Oct 6Cybersource GatewayEnhancementLowRecurly is continuing its phased migration to enhance CyberSource processing. No integration changes are required. If you have questions about your migration status, contact Recurly Support.
Oct 6AnalyticsBug fixLowRecurly has resolved an issue where Apple Pay transaction data was being incorrectly combined with credit card data in reporting. Apple Pay and credit card transactions will now appear separately as intended. No action is required, but merchants relying on payment method reporting should expect their historical data split to reflect correctly after release.
Oct 6WorldPay GatewayBug fixLowRecurly has resolved an issue where the company name was not being passed to Worldpay during NACHA verification for business bank account ACH transactions. This is a behind-the-scenes fix and no changes are required.