Go-Live Checklist

Use this checklist before taking your Fluid integration to production.

Session management

• session-id contains the actual current session identifier, not a placeholder
• Widget initialises once per session immediately after authentication
• session-id is updated when session IDs rotate
• Widget is removed from the DOM on logout
• Exactly one Fluid element is mounted at any time
• Behaviour verified across multiple browser tabs

Events

• Event listeners attached synchronously in the same script block that adds the element
• Opening is gated on the initialised event
• The close command sets open back to false
• fluid-error events are logged or surfaced, not swallowed
• If used, Bridge handlers registered within script.onload (Bridge API)

Data

• Object-valued attributes (user-data, bonuses, transaction-attributes, transaction-limits) are stringified as JSON
• locale, country, and currency follow documented formats (BCP 47, Alpha-3, ISO 4217)
• balance, withdrawable-balance, and transaction-limits are continuously updated via reactive attributes

Backend

• Payment orchestrator’s server-to-server result notification is set up and tested end-to-end — this is the authoritative channel for transaction outcomes

Back Office

• Payment methods appear in the cashier
• Error mapping reviewed for actionable messaging
• Theme, content and the final step buttons (success and failure screens) verified

Presentation

• z-index is sufficiently high for overlay visibility
• Parent elements supply the intended font-family

Optional features

• Quick Deposit widget tested (if applicable)
• Virtual/Sweepstakes widget tested (if applicable)
• Bonus code validation via Bridge API working (if applicable)
• Two-factor authentication flow verified (if applicable)
• KYC verification flow verified (if applicable)
• Withdrawal warning configured (if applicable)