FloPay Backend Changelog

Client-facing updates for FloPay backend and API releases.

v1.7.30 - Invoices from unlinked provider customers now book under their client #

Completes the v1.7.29 fix for invoices - provider invoices whose customer was never attached to a Flo user were recorded without a client and hidden from client views; they now adopt the owning gateway's client.

28 Aug 2026

Fix
Invoices
Reliability

v1.7.29 made purchases from provider customers that Flo has never linked to a user book under the client that owns the gateway. Invoices for the same customers still arrived without a client, so they were missing from client-scoped invoice lists and exports. The invoice ledger now applies the same rule.

What changed

  • Provider invoices (including pending one-time invoices created before the gateway invoice exists) that reach the ledger without a client adopt the client of the gateway they were issued through. A client supplied by the caller, or already on the row, is never overridden.

Developer notes

  • Applies to every invoice ledger path (Stripe and PayPal webhooks, API checkout, scheduler renewals).
  • Invoices recorded before this release keep their previous client value.
  • No schema change and no change to any SDK-facing contract.