FD SDK Error Handling and Recovery

Classify errors before displaying them

Customer messages should explain what happened, whether funds or an application may be affected, and the next safe action. Internal error details must remain in secured logs and support tooling.

• Correctable customer input or eligibility issue
• Temporary network or upstream availability issue
• Payment submitted with status pending confirmation
• Non-retryable issuer or policy outcome
• Support-assisted reconciliation or servicing case

Avoid duplicate financial actions

Retries must not create duplicate payment or booking attempts. When the final outcome is uncertain, show a pending state and reconcile against the authoritative status before asking the customer to act again.