FloPay Backend Changelog

v1.7.28 - Flo-owned opening invoices linked to subscriptions #

Successful and failed opening charges for Flo-owned subscriptions now stay tied to the correct subscription and opening billing cycle across payment retries.

Opening invoices for Flo-owned subscriptions now remain associated with the correct subscription and original billing cycle throughout payment recovery. This keeps subscription invoice history consistent from the first positive-charge attempt onward.

What changed

• Successful and failed opening charges are associated with the corresponding Flo-owned subscription and its original opening billing cycle.
• Retries across payment providers converge on the same opening invoice. A later failed result cannot replace an invoice that has already been paid.
• When a retry succeeds through another provider, future renewals use the successful provider and payment method while retaining the original billing-cycle boundary.
• Existing opening invoices that can be matched unambiguously are corrected automatically. This reporting correction does not alter subscription schedules or initiate charges.

Developer notes

• No public API, SDK, webhook payload, status-code, or configuration contract has changed.
• No SDK update, payload migration, configuration change, or merchant action is required. This release contains no breaking changes or removed public APIs.