メインコンテンツへスキップ
このページで

The following settings allow you to customize the checkout behavior and appearance to suit each merchant's specific needs.

Language#

The checkout interface language is automatically configured based on the country in which your business operates.

This setting aims to ensure a localized experience for shoppers, reducing friction and improving conversion rates.

  • The language is defined through the tokenization of orders.
  • Language can be dynamically specified for each order.

Base URL#

If you'd like to customize a specific base URL for your payment links, then you can request it from our support team. This customization allows you to tailor the experience to your brand identity.

Example: https://payhere.yourbrand.deuna.com

Enable user authentication#

DEUNA lets you configure whether your shoppers complete checkout as guests or as authenticated users, with access to their saved cards and previous purchase data. This behavior is controlled by two variables:

VariableTypeDescription
user_authentication_flowbooleanEnables the authenticated user flow (login, OTP, saved cards).
init_with_guest_userbooleanEnables the guest user flow (no login).

Both variables are configured inside widgets_general_config.user_experience when creating or updating your merchant configuration:

JSON
{
  "widgets_general_config": {
    "user_experience": {
      "user_authentication_flow": true,
      "init_with_guest_user": false
    }
  }
}

How is it decided whether a user sees the authenticated flow?

If you set user_authentication_flow: true, DEUNA determines which user to show (and therefore, which saved cards) following a priority order. A value defined at a higher level always overrides the levels below it:

PrioritySourceDescription
1(highest)Query param userTokenIf the merchant explicitly sends a userToken when initializing the widget, that user is used regardless of any other configuration.
2Merchant configurationIf no userToken is sent, the configuration defined in widgets_general_config.user_experience is used.
3 (lowest)Order / billing emailIf there's no userToken and no applicable configuration, the decision is based solely on the email received in the order or billing data.

Example — initializing with an explicit userToken:

JavaScript
deunaSDK.initElements({
  orderToken: "YOUR_ORDER_TOKEN",
  userToken: "YOUR_USER_TOKEN", // overrides merchant config and order email
  // ...other initialization parameters
});

Overriding at initialization: onlyCardEnrollment

Parameters sent inside behavior when initializing the WebSDK let you override certain flows defined in your merchant configuration, without changing that configuration itself.

onlyCardEnrollment hides an authenticated user's saved cards, allowing only the enrollment of a new card. This is recommended when the merchant manages the display of the user's saved cards from their own UI, and only needs DEUNA to handle the card-enrollment form.

onlyCardEnrollment overrides the outcome of the priority table above: even if a userToken or an active user_authentication_flow would normally show saved cards, this flag forces them to stay hidden for that session.

External authorizer (userToken)OTP (user_authentication_flow)onlyCardEnrollmentSaved cards visible?
✅❌❌✅
✅❌✅❌
❌✅❌✅
❌✅✅❌

Example — Vault Widget WebSDK configuration:

JavaScript
await DeunaSDK.initElements({
  orderToken: "<ORDER_TOKEN>",
  userToken: "<AUTHENTICATION_TOKEN>",
  userInfo: { /* ... */ },
  behavior: {
    onlyCardEnrollment: true,
    // ...other behavior overrides
  },
  callbacks: { /* ... */ },
  },
});

OTP channels#

When a shopper logs in at checkout, DEUNA sends a one-time password (OTP) by email or SMS. Both channels are enabled by default. Use the otp_channels setting to disable SMS for your merchant account; email always remains available.

Contact your DEUNA account manager to apply this setting.

Choose a configuration mode

Modesms_enabledAvailable channelsReturning shopper behavior
Defaulttrue or omittedEmail and SMSDEUNA uses the channel from the shopper's last successful login.
Email onlyfalseEmailDEUNA ignores an SMS preference and sends the OTP by email.

The sms_enabled variable is configured inside widgets_general_config.otp_channels. Select an example to disable SMS or restore the default behavior:

curl --request PATCH \
  --url https://api.sandbox.deuna.io/api/v1/merchants/{merchant_id}/checkout/configurations \
  --header 'Authorization: Bearer YOUR_MERCHANT_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
    "widgets_general_config": {
      "otp_channels": {
        "sms_enabled": false
      }
    }
  }'

For production, replace https://api.sandbox.deuna.io with https://api.deuna.io. Test the change in sandbox before applying it in production.

Understand shopper behavior

DEUNA remembers the channel each shopper used for their last successful login and uses it for the next OTP. This gives returning shoppers the code through the channel they previously selected, unless your merchant configuration disables that channel.

  • Default configuration: DEUNA sends the OTP through the shopper's preferred channel.
  • SMS disabled: DEUNA sends the OTP by email, even when the shopper's preferred channel is SMS.
  • The restriction applies to authenticated OTP flows in Payment Widget, Payment Link, and Payment Vault. Guest flows aren't affected.
  • When SMS is disabled, the SMS option doesn't appear in the OTP view.
  • Resend code uses the channel currently in use.

Frequently asked questions

Does this apply to all my shoppers?

Yes. The setting applies to the merchant account, not to individual shoppers.

Do I need to change my integration?

No. The widget reads the setting during initialization. You don't need to change the SDK configuration or order-creation request.

What happens if I don't configure otp_channels?

Both email and SMS remain enabled, and the shopper flow doesn't change.

Enable card saving#

Besides deciding whether a user checks out as a guest or as an authenticated user, you can configure how card-saving behaves during payment.

VariableTypeDescription
show_saved_cards_flowbooleanDisplays a checkbox that lets the shopper decide whether to save their card during payment. When disabled (false, the default), the card is saved automatically without asking, which improves conversion on future purchases.
default_card_flowbooleanDisplays an additional checkbox letting the user decide whether that card should be marked as the default for future purchases. Disabled by default.

Both variables are also configured inside widgets_general_config.user_experience:

JSON
{
  "widgets_general_config": {
    "user_experience": {
      "show_saved_cards_flow": true,
      "default_card_flow": true
    }
  }
}

Enable card saving#

It is possible to display a checkbox that allows the shopper to decide whether to save their card at checkout. This option is useful in guest flows.

The default behavior is not to display the checkbox and automatically save the card to improve conversion.

Allow card deletion#

Controls whether shoppers can delete saved cards in the Vault Widget. Recommended for subscription and recurring billing models to prevent accidental payment method removal and involuntary churn.

VariableTypeDefaultDescription
allow_card_deletionbooleantrueDetermines if shoppers can delete cards. When false, all deletion actions are hidden.

Configure inside widgets_general_config.user_experience:

JSON
{
  "widgets_general_config": {
    "user_experience": {
      "allow_card_deletion": false
    }
  }
}

UI behavior

StateActive cardsExpired cardsDefault cardSingle card view
false (Disabled)Hides "Delete" from the menu (only "Set as default" is shown).Hides the trash icon.Hides the actions menu entirely to avoid empty popovers.Hides the delete button.
true or omitted (Default)Standard deletion available in menu.Trash icon visible and active.Standard deletion available in menu.Delete button visible and active.

Visual styles#

Customize your widget using CustomStyle.

Adapt your customers' visual experience to your brand guidelines.