FloPay SDK Changelog

v1.8.3 - Optional checkout buyer identity #

Merchants can now start a checkout before the buyer's email is known, and the SDK collects identity during checkout only when the chosen payment method does not provide it.

Flopay SDK v1.8.3 makes the buyer's email optional when a checkout session is created. Checkout can begin before identity is known and gathers it in-flow only when the selected payment method does not already supply it. Existing sessions that carry complete buyer data keep their current behavior.

What changed

• FlopayCheckout can be rendered with a userId but no email. The session is created and the payment surface mounts before buyer identity exists.
• Buyer identity is captured automatically when the buyer pays with a wallet or PayPal flow that returns it. When the provider does not supply identity — for example on alternative payment methods — checkout shows a required panel that collects the buyer's email and name before payment is submitted.
• Card checkout collects the required email and name on the payment surface, validates them before submit, and attaches only complete, non-blank values.
• @flopay/shared now exports the isValidEmail helper for reusing the same email validation the SDK applies internally.

Why it matters

Merchants no longer need the buyer's email up front to start a checkout. This supports flows where identity is collected during, rather than before, payment, while sessions that already include full buyer details continue to work unchanged.

Developer notes

• Upgrade the @flopay/* packages you use to 1.8.3 together; this repository publishes the workspace at one shared version.
• When rendering FlopayCheckout, userId remains required; you may now omit the buyer email and let checkout collect it when needed.
• Use the exported isValidEmail from @flopay/shared if you want to pre-check buyer email with the same rules the SDK enforces.