FloPay SDK Changelog

v1.8.22 - Broader buyer identity and saved-payment coverage #

Flopay SDK 1.8.22 strengthens release validation for buyer identity, saved payment methods, 3D Secure, and pre-authorisation checkout journeys.

Flopay SDK v1.8.22 is a maintenance release that expands automated browser coverage for buyer identification, saved payment methods, and card pre-authorisation. Public SDK behavior and integration surfaces remain unchanged.

What changed

• Release validation now covers buyer identification during card, Google Pay, and Afterpay checkout journeys.
• Additional checks protect hosted card entry, 3D Secure challenges, retry after a declined payment, and reuse of a saved payment method.
• Pre-authorisation coverage now verifies successful, declined, and 3D Secure outcomes while continuing to distinguish authorised payments from captured payments.
• @flopay/js, @flopay/node, @flopay/react, and @flopay/shared are available together at version 1.8.22.

Why it matters

Broader validation helps protect the identity, authentication, and payment state handling that merchants and buyers rely on across checkout journeys.

Developer notes

• Upgrade the @flopay/* packages you use to 1.8.22 together.
• No public exports, API payloads, documented configuration, or runtime behavior have changed.
• Existing integrations require no migration or operational action.