Flutter 3.17.0

onDataRequest can now answer Transact. The handler previously only announced that Transact needed data, with no way to supply it.

Impact

onDataRequest can now answer Transact. The handler previously only announced that Transact needed data, with no way to supply it. It is now request/response: the handler returns an AtomicTransactDataResponse (or null to send nothing) and may be async, so the data can be gathered from the user or a backend first. New types AtomicTransactDataResponse, AtomicTransactCardData, AtomicTransactIdentity, and AtomicTransactCardType match the native TransactDataResponse field for field. Integrators already implementing onDataRequest must update their handler's signature.
Deferred payment methods. New deferredPaymentMethodStrategy config (sdk / api) lets an app have Transact request the payment method through onDataRequest instead of reading it from the Atomic API. Leaving it unset keeps the API default.

onDataRequest was unusable before this release. fields was decoded into the wrong type and threw before the handler ever ran, and taskId, userId, and identifier were never sent by either platform.

Okta Verify handoff. Users authenticating through Okta can now be redirected into the Okta Verify app during the auth flow.
iOS 26+ login pages. Fixed the bottom button on some login pages being hidden below the toolbar.
Crash fix for mixed Swift configurations. Prevented a crash during WebKit operations when the SDK is linked alongside Swift 5 language-mode code.

Okta Verify handoff. Users authenticating through Okta can now be redirected into the Okta Verify app during the auth flow.

onDataRequest now returns a response to Transact — the handler may be async and returns an AtomicTransactDataResponse or null (#100)
Added deferredPaymentMethodStrategy to AtomicConfig, so Transact can request the payment method through onDataRequest rather than the Atomic API (#100)
Fixed onDataRequest throwing on fields decoding, and taskId/userId/identifier never being sent (#100)