FloPay Backend Changelog

v1.10.31 - Pre-dispute alerts link to the payment by card, amount and date #

When an alert network's references do not match a Flopay payment, Flopay now finds the payment by the card's last four digits, the amount and the transaction date, and confirms it with the authorization code where it can. Linked alerts carry the payment and customer in their webhooks. Ambiguous alerts stay unlinked. No integration change is needed.

Most pre-dispute alerts from alert networks arrived unlinked, with an empty paymentIds, because the references the network sends (such as the acquirer reference number) are not ones Flopay records for a payment. Merchants then had to find the order themselves inside the short response window.

What changed

• When an alert's references match no payment, Flopay searches the merchant's captured payments, refunded ones included, for the alert amount and currency (or the network's converted amount), made around the transaction date by a customer with a saved card ending in the alert's last four digits.
• When the alert carries an authorization code and the payment ran on Stripe, Flopay confirms the payment against the authorization code Stripe recorded for it.
• Flopay links only when exactly one payment remains. When several could match, the alert stays unlinked rather than guess.
• An alert delivered unlinked earlier is linked when the alert network sends it again or updates it: a pre_dispute_alert.updated event carries the same preDisputeAlert.id with paymentIds, linkStatus: "linked" and user.
• Once linked, an alert stays linked when a later notification matches nothing.

Why it matters

• More alerts arrive already tied to the payment and customer, so merchants can refund or respond inside the alert window without searching for the order.

Developer notes

• The webhook payload shape is unchanged. Treat paymentIds and user on pre_dispute_alert.updated as you already do.
• This release contains no breaking changes.