FD SDK Events and Callback Planning

Model business outcomes, not screen transitions

The host application should react to meaningful journey outcomes and server-confirmed states. Do not treat a user reaching a particular screen as proof that a booking or payment has completed.

• Journey opened or resumed
• Customer action required
• Booking submitted for processing
• Confirmed success, failure, or cancellation
• Servicing request received or updated

Design callbacks to be resilient

Callback handling should be idempotent, observable, and safe to retry. The exact event catalogue and verification mechanism are supplied through approved technical onboarding.