FloPay Backend Changelog

Client-facing updates for FloPay backend and API releases.

v1.10.30 - Pre-dispute alert webhooks describe the card transaction behind the alert #

Pre-dispute alert webhooks now carry the transaction date, card brand, card issuer country and the alert network's converted amount when they are known, so merchants can find the payment an alert is about even before Flopay links it. The new fields are optional and nullable. Existing fields and integrations are unchanged.

19 Oct 2026

Improvement
Webhooks
Disputes

A pre-dispute alert is delivered as soon as Flopay can attribute it to a merchant, often before it is linked to a Flopay payment. Until now the alert told the merchant the amount, currency, card digits and descriptor, but not when the payment was made or which card network it ran on, which made the order harder to find inside the short response window.

What changed

  • pre_dispute_alert.created and pre_dispute_alert.updated carry five new fields on preDisputeAlert: transactionAt, cardBrand, cardCountry, convertedAmount and convertedCurrency.
  • transactionAt is when the card transaction took place. Alert networks usually report only the date, which is delivered as midnight UTC. When the network gives no date, it comes from the acquirer reference number's processing date, which is the transaction date or the day after it.
  • cardBrand is the lower-case card network, such as visa or mastercard, and cardCountry is the two-letter country of the card issuer.
  • convertedAmount and convertedCurrency are the alert amount as converted by the alert network, when it supplied a conversion. They are always present or null together.
  • Stripe inquiries and early fraud warnings fill transactionAt, cardBrand and cardCountry from the charge.

Why it matters

  • Merchants can locate the payment an alert is about, by date and card, while the alert is still unlinked.

Developer notes

  • Every new field is optional and nullable. Alerts first delivered before this release report them as null.
  • The fields are descriptive: learning them for an alert already delivered does not send a new pre_dispute_alert.updated event.
  • Card BIN is still never part of the payload.
  • This release contains no breaking changes.