FloPay SDK Changelog

v1.8.2 - Reliable session retries and Vite-ready payment logos #

Node session creation now honors caller-managed idempotency keys, while React payment logos load reliably in default Vite integrations.

FloPay SDK v1.8.2 makes checkout-session retries safer for server integrations and removes the bundler-specific asset resolution that broke alternative-payment method logos in Vite.

What changed

• @flopay/node sends a valid caller-supplied idempotencyKey unchanged as the Idempotency-Key header when creating a checkout session. Omitting the option keeps the request unkeyed, and empty or overlong values are safely ignored.
• @flopay/react loads its ten payment-brand SVGs from the versioned FloPay CDN instead of resolving package-relative assets with import.meta.url.
• A failed or CSP-blocked logo request now falls back to the existing inline method monogram instead of leaving the payment tile without a brand mark.
• The SVG sources remain in the repository for controlled CDN publishing, but no SVG files or bytes are emitted in the published React package.

Why it matters

Server callers can reuse one stable key after a lost response without risking a second logical checkout session. React consumers can render payment logos under Vite's default dependency optimizer without middleware or optimizeDeps changes, while other supported bundlers keep the same rendered behavior.

Developer notes

• Upgrade the @flopay/* packages you use to 1.8.2 together; this repository publishes the workspace at one shared version.
• Merchants with a strict Content Security Policy must allow https://cdn.flopay.com in img-src.
• The ten files under https://cdn.flopay.com/sdk-logos/v1/ must be live before publishing this release.