FloPay SDK Changelog

v1.11.3 - Bounded cause for unusable wallet confirmation results #

When a wallet confirmation such as Apple Pay or Google Pay returns a result the SDK cannot use, the technical-error telemetry event now says what shape the result had.

When a wallet confirmation such as Apple Pay or Google Pay finishes with a result the SDK cannot use, the technical-error telemetry event now carries a bounded reason. Operators can tell a confirmation that returned nothing apart from one that returned an unexpected value, without collecting the provider's response or any payment details.

What changed

• Bounded cause for unusable wallet confirmation results. A wallet confirmation reported with errorCode CONFIGURATION_INVALID and failureCategory invalid_response now carries one reason, whether the result arrived on time or late:
  • confirmation_result_missing: the confirmation returned no result.
  • confirmation_result_not_object: the confirmation returned a value that is not a result object.
  • confirmation_result_unconfirmed: the confirmation returned an object with neither an error nor a confirmed payment or setup.
• Codes are unchanged. errorCode, failureCategory and the operation outcome stay the same. Rejected confirmations and provider error results never carry these three values, and any other reason value is still reported as unknown.

Developer notes

No change is required for checkout integrations. Telemetry consumers should accept the three new reason values on technical-error events.