Go-live checklist

Run through this list before launching your integration. Every item is covered in detail elsewhere in the manual; this page is the final "am I done" pass.

Session

• session-id receives the real, current session ID of the authenticated user, never a placeholder (Session handling)
• The widget initialises once per session, right after authentication, not on every render
• When your platform rotates or refreshes the session ID, the new value is pushed onto the session-id attribute
• The widget is removed from the DOM on logout
• Exactly one Fluid element is mounted at any time
• Behaviour verified in a second browser tab

Events

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

Data

• Object valued attributes (user-data, bonuses, transaction-attributes) are passed as stringified JSON (Data objects)
• locale, country and currency use the documented formats (Attributes)
• balance, withdrawable-balance and deposit-limit are kept up to date through the reactive attributes

Backend

• The payment orchestrator's server to server result notification to your backend is set up and tested end to end; this is the authoritative channel for transaction outcomes

Back office

• Payment methods are configured and appear in the cashier
• Error mapping is reviewed so orchestrator failures show actionable messages
• Theme, content and the final step buttons are reviewed (How Fluid Works)

Presentation

• z-index is high enough for the overlay to sit above your UI (Styling)
• The parent element provides the intended font-family