Application Settings

Default Locale

Select a language from the dropdown list to set your display language.

NOTE: If no language is selected, English (EN) will be displayed.

Choose from the following languages:

  • Arabic
  • Armenian
  • Bulgarian
  • Chinese (China)
  • Chinese (Hong Kong SAR China)
  • Croatian
  • Czech
  • Danish
  • Dutch
  • English
  • English (United Kingdom)
  • Estonian
  • Finnish
  • French
  • Georgian
  • German
  • Greek
  • Hebrew
  • Hungarian
  • Indonesian
  • Italian
  • Japanese
  • Khmer
  • Korean
  • Lithuanian
  • Malay
  • Norwegian
  • Polish
  • Portuguese
  • Portuguese (Brazil)
  • Romanian
  • Russian
  • Serbian (latin)

  • Serbian (cyrillic)

  • Slovak
  • Spanish
  • Spanish (Mexico)
  • Swedish
  • Thai
  • Turkish
  • Ukrainian

  • Vietnamese

Domain Name (prefix)

As an option, you can define a domain name that will appear as a prefix to the Jumio domain in the URL of the ID Verification page presented to your end users.

For example, if you enter mycompany as the value, and your integration is in the US data center, the URL domain that your end users will see will be:

https://mycompany.web.amer-1.jumio.ai

The domain name prefix needs to meet the following guidelines:

  • Allowed characters are letters a-z, numbers 0-9, and the dash symbol “-”
  • Must not start or end with the dash symbol “-”
  • A maximum of 63 characters is allowed

Max Attempts per User

This value is no longer used.

Authorization Token Lifetime

Specify the duration of time for which the authorization token will remain valid.

Note: The authorization token gets returned from the Account API.

Enter the value in minutes (minimum 5, maximum 86400).

Note: The default value for the Authorization Token Lifetime is 30 minutes.

Callback, Error, and Success URLs

Configure your redirect implementation by providing URLs as discussed below:

  • Callback URL: Define a Callback URL to automatically receive the status of each transaction.
  • Success URL: Define a Success URL to redirect the user after images are accepted for processing. If no Success URL is specified in either the Portal or the Account API request, the Jumio default success page will be displayed. Any custom images you have specified will also be displayed (see Customize Client).
  • Redirect URL: Define a Redirect URL to redirect the user when the verification process ends with an error or a failure. If no URL is specified in either the Portal or the Account API request, the Jumio default error page will be displayed. Any custom images you have specified will also be displayed (see Customize Client).

URL Requirements

  • HTTPS using the TLS Protocol (most recent version recommended)
  • Valid URL using ASCII characters or IDNA Punycode

URL Restrictions

  • IP addresses, ports, certain query parameters and fragment identifiers are not allowed.
  • Personally identifiable information (PII) is not allowed in any form.
  • Jumio appends the following parameters to your Success or Error URL to redirect your user at the conclusion of the user journey. These parameters cannot be used as part of your Success or Error URL:

    Name Description

    transactionStatus

    • SUCCESS for successful submissions.

    • ERROR for errors and failures after 3 attempts.

    customerInternalReference

    Your internal reference for the transaction.

    Values MUST NOT contain Personally Identifiable Information (PII) or other sensitive data such as email addresses.

    transactionReference

    Jumio reference number for the transaction.

    errorCode

    Displayed when transactionStatus is ERROR.

Capture Method

Specify how your user can submit their ID or document for verification. Choose from:

  • Webcam and image upload
  • Webcam only
  • Image upload only
Note: Selecting "Webcam only" means some mobile browsers will not be supported.

Footer Display Mode

Please contact Jumio Support to inquire about changing footer settings.

Allow Cross Device Journey

Select this checkbox to allow users to switch to Mobile Journey for image capture, if they are experiencing issues with their webcam or they don’t have a copy of their ID saved on their device. The cross device option will only be visible to users if Camera Capture has also been enabled for the verification.

The Cross Device Journey works in three ways:

  • Users can choose the Continue on Mobile option to complete the transaction on their mobile device.
  • Users can enter their email address to receive the link that will take them to the mobile browser screen to complete the transaction.
  • Users can scan the QR code from their phone to receive the link that will take them to the mobile browser screen to complete the transaction.

NOTE: Click Save and enter your Customer Portal password to save the changes. Otherwise, your changes will be reverted.