FloPay SDK Changelog

v1.8.1 - Leaner checkout SDK #

Checkout integrations load less unused JavaScript after the retired Flopay Elements and legacy PayPalButton APIs were removed.

Flopay SDK v1.8.1 reduces the merchant checkout bundle by removing public APIs from earlier Elements-based integrations. Supported checkout experiences remain available through FlopayCheckout and SplitCardForm, with standalone direct PayPal available through DirectPayPalButton.

This is an intentional breaking change for integrations that import the removed APIs. Integrations already using the maintained checkout components do not need to change their checkout flow.

What changed

• @flopay/react no longer exports PayPalButton, PaymentElement, AddressElement, useElements, or their associated prop types. FlopayProvider also no longer exposes a Flopay Elements group.
• @flopay/js no longer exports FlopayElements. The Flopay class no longer provides elements(), submitElements(), confirmPayment(), confirmPayPalPayment(), or resumePayPalPayment().
• @flopay/shared no longer exports the matching Elements constants, types, or legacy payment-provider adapter methods.
• Hosted card capture, wallet and alternative payment methods, and supported direct PayPal checkout flows remain available through the maintained SDK surfaces.

Why it matters

In a like-for-like comparison with v1.7.0, the merchant checkout bundle is 18,137 bytes smaller raw, 3,747 bytes smaller when gzip-compressed, and 2,562 bytes smaller when Brotli-compressed.

Developer notes

• Upgrade the @flopay/js, @flopay/node, @flopay/react, and @flopay/shared packages you use to 1.8.1 together.
• Replace legacy Elements usage with FlopayCheckout or SplitCardForm. Replace the removed PayPalButton with DirectPayPalButton when you need a standalone PayPal control.
• There is no deprecation bridge for the removed exports. Update direct imports and any affected TypeScript types before upgrading.