FloPay Backend Changelog

v1.7.19 - Subscription recovery history #

Subscription recovery campaigns, retry rounds, and the next scheduled recovery retry are now visible through public read APIs and timeline projections.

Flo-managed subscription recovery is now easier to inspect from merchant dashboards, admin tools, and operational workflows. Teams can review the recovery campaigns and retry rounds attached to a subscription, and timelines now show the next scheduled recovery retry when one is already planned.

What changed

• GET /v1/subscriptions/:id/recovery returns the authenticated client's recovery history for a subscription.
• GET /v1/admin/subscriptions/:id/recovery?clientId= gives administrators the same recovery view for a selected client.
• Timeline future events can now include subscription.recovery_retry for the next scheduled recovery retry, using the active recovery schedule instead of projecting an ordinary rebill while recovery is still in progress.
• Recovery reads are paginated and client-scoped, so consumers can safely build dashboard and support views without fetching unbounded history.

Why it matters

• Merchants and support teams can explain where a failed renewal is in recovery without inferring state from separate events.
• Buyer-facing and operator-facing timelines no longer suggest a normal upcoming rebill when the subscription is actively waiting for a recovery retry.

Developer notes

• This is an additive, read-only API change. Existing subscription, timeline, webhook, and SDK-facing behavior remains compatible.
• Clients with strict timeline event validation should accept the new subscription.recovery_retry future event code.
• The new recovery endpoints use the standard paginated list response shape: data, page, limit, pages, and total.