FloPay SDK Changelog

v1.3.2 - Clear billing address errors on vault card checkout #

On the vault card path, an invalid billing postcode is now caught before the card is charged and shown with the billing provider's exact, country-specific message. Buyers correct the field and resubmit without re-entering card details, and postcode rules match the billing API exactly so a code accepted in the browser is accepted server-side.

FloPay SDK v1.3.2 fixes a case on the vault card checkout where an invalid billing address could leave the buyer waiting until a generic "Timed out waiting for payment confirmation." message. When the billing address is rejected, the SDK now blocks the charge, surfaces the specific reason immediately, and lets the buyer correct the field and resubmit — without re-entering their card.

What changed

• On the vault card path, the billing address is confirmed before the card is submitted for charge. If the address is rejected, the submit is held and the card is never charged, so the checkout no longer hangs on a generic timeout.
• The exact, country-specific reason is now shown inline and reported through onError — for example "Postal/ZIP code is not valid for the selected country. Expected format: e.g. A1A 1A1" — instead of being silently dropped.
• After a rejected address, the vault widget keeps the entered card, so the buyer fixes the postcode and resubmits without re-typing card details.
• A transient network or server blip while saving the address no longer hard-fails checkout: the flow falls back to best-effort so a recoverable session can still complete.
• The client-side postcode rules in @flopay/shared (isValidPostalCode, isPostalCodeSupported, getPostalCodeExample) now mirror the billing API's validation exactly, so a postcode accepted in the browser is accepted server-side and the inline hint matches the server's message.

Developer notes

• No API changes are required to adopt this release. If you consume the @flopay/shared postcode helpers directly, their results and country-specific examples now align 1:1 with the billing API — review any places where you previously worked around client/server differences.