FloPay SDK Changelog

v1.12.1 - Telemetry and compatibility guides name the first release with the security check cause split #

The SDK telemetry guide and vault verification compatibility guide now say that v1.11.6 is the first release that can report an unavailable card-form security check as a vault load failure. SDK behavior is unchanged.

The SDK vault verification compatibility guide described telling a buyer's failed card-form security check apart from an unavailable check as coming in a future release, and the SDK telemetry guide did not say which release it applies from. That split shipped in v1.11.6, and both guides now say so. This change does not affect SDK behavior.

What changed

• Telemetry guide. When the card-form security check is on, an error the card form reports before the buyer submits is classified by the card form's optional failureOutcome from v1.11.6 onwards. The guide now also says that v1.11.5 records every such error as operation.state_transition at vault_mount.
• Vault verification compatibility guide. The guide names v1.11.6 as the first release with the cause split, next to v1.11.5 as the first release with the protected card-entry path. Which SDK versions have a protected card-entry path is unchanged.

Integration notes

No code changes are needed. An unavailable security check is recorded as technical_error with code VAULT_LOAD_FAILED only on v1.11.6 or later, and only when the card form reports the cause in failureOutcome. Otherwise it is recorded as operation.state_transition at vault_mount.