Next Action widget

Use Next Action when an existing order requires the customer to complete an additional step, such as a supported 3DS challenge or redirect. Reuse the original order token.

For 3DS, the returned experience may first collect browser and device signals, then continue without a challenge or display the issuer's challenge. A loading view does not mean the customer must authenticate manually. Keep the widget mounted while it manages the flow, and verify the original order after a callback or return. See the 3DS purchase flow for the stages and payment outcomes.

Decision flowAsk Athia about this#

See the customer experienceAsk Athia about this#

Next Action works with both DEUNA payment widgets and merchant-owned payment forms. After your backend submits the payment, open Next Action only when the response requires another customer step. The widget then presents the supported 3DS challenge or alternative payment method (APM) redirect and reports the outcome through its callbacks.

The following walkthrough shows how the experience continues from a merchant checkout into the required post-payment action:

The video illustrates the customer-facing transition. Your integration must still use the payment response, callbacks, and backend reconciliation described below; do not infer the final payment state from what the customer sees in the widget.

Open Next ActionAsk Athia about this#

await DeunaSDK.initNextAction({
  orderToken,
  callbacks: {
    onSuccess: () => verifyOriginalOrder(),
    onError: (error) => recoverAfterVerification(error),
    onClosed: () => recoverAfterVerification(),
  },
});

await deunaSDK.initNextAction({
  orderToken,
  mode: 'modal',
  callbacks: {
    onSuccess: verifyOriginalOrder,
    onError: recoverAfterVerification,
    onClosed: recoverAfterVerification,
  },
});

let callbacks = NextActionCallbacks()
callbacks.onSuccess = { _ in verifyOriginalOrder() }
callbacks.onError = { error in recoverAfterVerification(error) }
callbacks.onClosed = { _ in recoverAfterVerification(nil) }

deunaSDK.initNextAction(
    orderToken: orderToken,
    callbacks: callbacks,
    language: "en"
)

val callbacks = NextActionCallbacks().apply {
    onSuccess = { verifyOriginalOrder() }
    onError = { error -> recoverAfterVerification(error) }
    onClosed = { recoverAfterVerification(null) }
}

deunaSDK.initNextAction(
    context = this,
    orderToken = orderToken,
    callbacks = callbacks,
    language = "en"
)

ParametersAsk Athia about this#

Handle every outcomeAsk Athia about this#

Redirect and popup requirementsAsk Athia about this#

• Allow the SDK to open its supported external authentication surface.
• Preserve app lifecycle state while the customer leaves and returns.
• On Web, open from a customer gesture and do not sandbox the widget in a way that blocks popups or top-level navigation.
• On React Native, keep the SDK renderer mounted while its external redirect controller is active.
• On iOS and Android, use the maintained SDK modal or embedded component instead of recreating the internal WebView bridge.
• Test successful challenge, rejection, customer cancellation, issuer timeout, network loss, and returning from the background.

Embedded presentationAsk Athia about this#

The Web SDK supports mode: 'target' plus target; iOS and Android expose embedded widget components; React Native uses its DeunaWidget renderer. Reserve enough initial height, respond to size changes, and ensure the host does not hide challenge controls behind a sticky footer or on-screen keyboard.

3DS iframe loading fallbackAsk Athia about this#

When DEUNA presents a 3DS challenge inside an iframe, Next Action monitors the loading state of the issuer view.

• If the iframe loads successfully within the first 5 seconds, the flow continues normally and no additional recovery actions are displayed.
• If the view does not finish loading after 5 seconds, the Did the view fail to load? option appears.

When expanded, the shopper can:

• Reload view: retries loading the 3DS challenge.
• Change payment method: allows the shopper to leave the current challenge and select another payment method, after confirming the action.

If the iframe finishes loading while the fallback is visible, the recovery options are automatically hidden and the shopper can continue with the challenge.

Expand

Integration behavior

The merchant should continue using the Next Action callbacks and the authoritative order status to determine the final payment outcome.

Related referencesAsk Athia about this#