FloPay SDK Changelog

v1.11.6 - An unavailable card-form security check is reported as a vault load failure #

When the secure card form reports that its security check is unavailable before the buyer submits, the SDK now records a vault load failure instead of a buyer-side state change, so outage monitoring can see it.

When the card-form security check is on, the secure card form can report an error before the buyer submits. Until now, the SDK recorded every such error as a lifecycle state change, whether the buyer's own check had failed or the check itself was unavailable. An unavailable check therefore never appeared as a vault load failure, so monitoring could not tell a buyer retrying from an outage. This release uses the cause the card form reports to tell the two apart.

What changed

• The card form's reported cause decides the classification. For an error the card form reports before the buyer submits, while the security check is on, the SDK reads the optional failureOutcome on the card form's error message and matches it exactly:
  • verification_failed or verification_expired: the buyer's own check failed or expired. It is still recorded as operation.state_transition at vault_mount.
  • No failureOutcome: recorded as operation.state_transition at vault_mount, exactly as before.
  • verification_unavailable, or any other value: recorded as a technical_error with code VAULT_LOAD_FAILED at vault_mount, so outage alerting counts it.
• Nothing changes for buyers. For every cause, the error still appears in the card form's error area and through onError, the buyer's other entries stay in place, and nothing reloads or submits on its own.
• Other errors are unchanged. Errors after the buyer submits keep VAULT_SUBMIT_FAILED, and card forms without the security check keep VAULT_LOAD_FAILED whatever the cause.
• No new telemetry field. The cause only selects the classification. It is never sent to telemetry or added to Sentry breadcrumbs, and VAULT_LOAD_FAILED still carries no reason.

Developer notes

No change is required for checkout integrations, and public types are unchanged.