FloPay Backend Changelog

Client-facing updates for FloPay backend and API releases.

v1.0.1 - Local product catalog foundation #

New gateway-independent APIs for managing products, prices, coupons, and collections directly on the platform.

14 May 2026

Feature
Catalog
Products
Coupons
Collections
API

Merchants can now manage their own products, prices, coupons, and collections through the platform API without relying on a payment gateway's catalog. This release adds the data layer and CRUD endpoints that future checkout and subscription flows will build on.

What changed

  • Products — Create, list, retrieve, update, and soft-delete products scoped to the authenticated client. Each product supports one-time or recurring pricing with multiple currencies via nested prices.
  • Coupons — Manage percentage or fixed-amount discounts with duration controls (once, repeating, forever), per-currency amounts, and optional product associations.
  • Collections — Group products into named collections for catalog organization, with associations managed in the same create or update request.
  • Consistent list queries — All new list endpoints (GET /products, GET /coupons, GET /collections) accept the standard page, limit, sort, filter, and relation-inclusion parameters introduced in v1.0.0.
  • Unique codes — Product, coupon, and collection code values are enforced as unique per client at the database level.

Why it matters

This is the catalog foundation that lets merchants define their offerings once and reuse them across checkout, subscriptions, and reporting — independent of which payment gateway ultimately processes a transaction. Soft-delete semantics preserve historical references on existing invoices and subscriptions even after a product or coupon is retired.

Developer notes

  • All catalog endpoints are guarded by client authentication; client_id is derived from the authenticated client and is never read from the request body.
  • Nested prices and product associations are upserted in the same request, so a single POST or PATCH call is sufficient to persist a product with its prices or a coupon with its applicable products.
  • No checkout or Stripe flows change in this release. Wiring the catalog into checkout and subscription creation will follow in subsequent releases.