← Back to all sparks
Recurly logo

Recurly

FINANCE
Velocity1.7

Subscription management and recurring billing

Recurly is shipping payment-gateway maintenance — Vantiv, WorldPay, Adyen, ApplePay tweaks, no headline moves.

subscription-billingpayment-gatewaysfraud-and-decline-handlingwebhooksdeveloper-librariesfeed-quality
Current state
The captured window is dominated by narrow gateway-level updates: WorldPay now passes sales tax, Vantiv learned three additional response codes (142, 141, 378, plus reworked handling for 229 and 992), Check Commerce's sandbox endpoint moved, and the V3 client libraries gained payment_gateway_references parameters. Adyen got SEPA retry support and Apple Pay added MPAN tracking for merchant-derived tokens. The published_at dates are 2026 but the entry bodies are dated Jan–Feb 2025 — the changelog feed appears to be republishing year-old gateway notes on a new cadence.
Where it's heading
Recurly is in a maintenance posture for its payment-gateway integrations rather than reaching for new product surfaces. The work is real and matters for billing reliability — adding response codes prevents misclassified declines, SEPA retries recover EU subscription revenue, MPAN tracking improves tokenization reporting — but none of it expands what Recurly is or who buys it. Webhook auto-pause for unresponsive endpoints is the most operationally interesting item, hinting at a small reliability layer Recurly is willing to enforce on its merchants.
Prediction
Without fresher entries it's hard to call where the product is heading. The likeliest next move is more gateway breadth (Stripe response-code parity, additional EU gateways), and possibly a friendlier developer-facing release-notes feed since the current one is republishing year-old content. The team should consider fixing the changelog publishing date drift before commenting deeper on velocity.

Recent moves

  1. 2mo ago

    2/26/2025: WorldPay Gateway - Added support for passing Sales Tax to the gateway.

    WorldPay now accepts sales tax passed through from Recurly. Real win for merchants in tax-heavy jurisdictions who previously had to compute and remit outside the gateway, but narrow in audience.

  2. 2mo ago

    2/26/2025: Vantiv Gateway - Added support for two new response codes: 142 and 141.

    Vantiv now recognizes response codes 142 and 141, both tied to prepaid cards. Prevents legitimate prepaid declines from being treated as hard failures, recovering what would otherwise be lost subscription revenue.

  3. 2mo ago

    Changelog index header (feed artifact)

    Generic header text from the docs.recurly.com changelog index page, including stray Tailwind-CSS license boilerplate. Pure feed-source artifact, not a release.

    View source ↗
  4. 2mo ago

    2/18/2025: V3 Libraries - updated to support new payment_gateway_references parameters.

    V3 client libraries gained support for payment_gateway_references parameters, letting integrators pass gateway-side reference IDs through the SDK rather than hand-rolled HTTP. Useful for advanced reconciliation flows.

  5. 3mo ago

    2/18/2025: Vantiv Gateway - added support for response code 378 on the gateway.

    Vantiv response code 378 is now mapped on the Recurly side — same recovery-from-misclassified-decline pattern as the 141/142 work a few weeks later. Incremental but cumulatively meaningful for retention math.

  6. 3mo ago

    2/4/2025: Check Commerce gateway - updated endpoint for sandbox Check Commerce to support new gateway development endpoint.

    Check Commerce sandbox endpoint moved to a new development URL. Affects merchants integrating Check Commerce in test environments only — production behavior unchanged.