Widget Translation

Language Translation

The language translation feature is available for both Embedded and Hosted Experience, with support based on user type

This can be specified via POST Session Request

User Type	Embedded: Inline	Embedded: Modal	Embedded: Drawer	Hosted
Auth user, Guest user	✅	✅	✅	✅
Agent	❌	❌	❌	✅

Language Selector Dropdown

CCG provides additional ability to switch between languages using the "language selector dropdown" during their journey on the widget.

User Type	Embedded: Inline	Embedded: Modal	Embedded: Drawer	Hosted
Auth user, Guest user, Agent	❌	❌	❌	✅

tip

• There's no configuration provided to show/hide this dropdown
• This available only for Hosted experience
• Why is "Language Selector Dropdown" restriced to Hosted experience?
  • "Language Selector Dropdown" triggers reloading of widget to apply language translation, which would require reload of merchant's webpage and close the widget then relaunch it

How to Set Preferred Language

Preferred Language can be set via POST Session Request by passing the supported language value for the preferredLanguage prop.

To utilize the language translation feature, refer to the API documentation.

Example: Set Preferred Language

Here is the structure of Config object in POST Session Request including preferredLanguage:

  "config": {
    "modes": [
      "PAYMENT"
    ],
    "options": {
      "saveDisabled": false,
      "preferredLanguage": "es" 
    }
  }

Steps to Hide the Language Selector Dropdown for Hosted Widgets

The visibility of the language selector dropdown can be managed through the hideApplicationLanguageSelector flag, which is provided in the configuration via a POST Session Request.

This dropdown appears during agent sessions, customer sessions, and agent-initiated customer sessions.

However,the hideApplicationLanguageSelector flag only controls the visibility of the language selector dropdown in agent sessions. It does not affect the visibility of the dropdown in agent-initiated customer sessions.

For more details refer to the API documentation.

Example: Hide Language Selector Dropdown for Hosted Widget

{
  "appearance": {
    "visibility": {
      "hideApplicationLanguageSelector": true
    }
  }
}

Exceptions

• "Privacy Policy": translation is not applicable and is set to "https://www.optum.com/privacy-policy.html"
• You can override this via POST Session Request, by providing a link to your privacy policy url

Example: Override privacy policy

Here is the structure of Config object in POST Session Request including privacyPolicyUrl:

  "config": {
    "modes": [
      "PAYMENT"
    ],
    "privacyPolicyUrl": "url-to-your-privacy-policy-page"
  }

Things to Keep in Mind

The following items are not included within the scope of the language translation feature:

• API responses from CCG or Stripe : Merchants are responsible for translating these responses as needed.
• Name and Nickname values entered by customers will not be translated.
• Privacy Policy : The Privacy Policy link shared with CCG should have its own translated version. Refer to Optum Privacy Policy.
• ACH mandate
• NPS survey/questionnaire
• ACH Consent Text
• Text and Email to Add (future feature)
• Terms and Conditions : Check with legal for more details.