v1.8.8 - Inline validation for checkout fields #
Flopay SDK 1.8.8 shows an inline error against the email and billing address fields as soon as a buyer leaves one incomplete, matching the postcode field.
25 Aug 2026
Flopay SDK v1.8.8 gives every required checkout field the feedback the postcode field already had. When a buyer leaves the email, street address, city or state field empty — or types an email the form cannot accept — the field is outlined in the theme's danger colour and an inline message appears beneath it, and the hosted card form's submit stays closed until it is fixed.
What changed
- The collected email and the AVS street, city and state fields now reveal an
inline
role="alert"message once the buyer leaves them, wired to the input througharia-invalidandaria-describedby. - Inline messages render in the theme's danger colour. Previously the postcode message inherited the regular input text colour, so it appeared in the body colour rather than red.
- An invalid city no longer draws a box that is open on its right-hand edge, where it meets the state field.
- Fields are only flagged once the buyer has actually been in them. Focus moves the page makes itself — including the card form's own load-time autofocus — no longer mark a field as visited.
- The cursor is no longer pulled back to the top of the form when the buyer tabs from the last billing field into the card fields.
- The card form renders in the order it is painted, so tab moves through it from top-left to bottom-right.
Why it matters
A buyer who left a required field blank previously saw a submit button that would not proceed, with nothing indicating which field was at fault. Each field now explains itself at the moment the buyer leaves it.
Developer notes
- Upgrade the
@flopay/*packages you use to1.8.8together. - No public exports, props, or API payloads have changed; the new messages use
the existing
appearance.variables.colorDangertoken and fall back to the default red when it is not set. - Existing integrations require no migration.