Process Flow

Installation Instructions

To install this package please walk through the following proceedure:

1. Unzip the package to a directory on your computer
2. Import each zip archive found in the services folder to Transact Manager under the Services >> All Services menu item.
3. Review the Help Doc tab for each of the imported services and make any required adjustments to service parameters.
4. Review the Service Connection requirements under the same Help Doc tab for each of the imported services and make any required configurations to the Service Connection. Service Connections can be configured in Transact Manager under the Services >> Service Connections menu item.
5. Import each archive found in the libraries folder to Maestro. Importing these into the Organisation level libraries folder is recommended as this will make the components available to all projects, however they can be imported at the Project level if required.

greenID Verification Rules

Clients wishing to use the greenID service will be required to work with the greenID team to complete a Rules Checklist which will include defining preferences for rule sets, lock-out rules, background and interactive sources, enablement of watch lists and any other additional modules.

The API integration is set to use the default ruleId but this can be changed in the service parameters of the GreenID - Identity Verification dynamic data service.

Legal Considerations

Clients using electronic identity verification are required to understand the legal considerations of doing so and ensure their legal obligations are being met, such as ensuring the capture of an individuals agreement to the T&Cs prior to running the check.

Dun & Bradstreet Credit File (D&B)

If the Dun & Bradstreet (D&B) Credit File header database is utilised as a data source, the deployment is subject to a number of special conditions, such as obtaining the necessary consent, notification of failure, and offering an alternative ID verification option.

This package does not deal with these legal obligations which must be considered in the overall flow of the data capture experience. Further details can be obtained from "Rules Guide and Checklist" document typically provided by VIX Verify account manager. Below are two examples of D&B Credit File consent and failure notification wording.

    By accepting these terms and conditions you give consent for [[Reporting Entity]] to disclose
your name, residential address and date of birth to a credit reporting agency and ask the credit
reporting agency to provide an assessment of whether the personal information so provided
matches (in whole or in part) personal information contained in a credit information file in the
possession or control of the credit reporting agency to assist in verifying your identity for the
purposes of the Anti-Money Laundering and Counter-Terrorism Act 2006. The credit reporting
agency may prepare and provide [[Reporting Entity]] with such an assessment and may use
your personal information including the names, residential addresses and dates of birth
contained in credit information files of you and other individuals for the purposes of preparing
such an assessment. If you disagree with having your identity verified by a credit reporting
agency, please select another data source or contact [[Reporting Entity]] so that we can
discuss other options with you.

Dear [[first name]],
You recently opted to verify yourself against the Credit Bureau for [[customer]]. Your details
didn't match the records held on file by the Dun & Bradstreet Credit Reporting Agency. Don't
worry, this process doesn't leave any mark or in any way alter your credit history.
We're obligated by legislation to tell you that your details didn't match. However, If you've
already completed your ID verification, you don't need to do anything further.
If you've not yet completed your ID verification, you may like to try another self-verification
option or contact us to discuss other options.
If you want to check the details held by Dun & Bradstreet, you can order a copy of your Dun &
Bradstreet credit report online at https://www.checkyourcredit.com.au/Personal or by calling
Dun & Bradstreet on 1300 734 806 during business hours.
Kind regards,
[[customer]]

Supported Verification Sources

The following identity sources are supported:

• Australian Driver's Licence
  Supporting all 8 States of Australia, individuals are required to select their State and enter their Driver's Licence Number. Only DVS Driver's Licence sources are supported.
• Medicare Card
  Only the DVS Medicare source is supported.
• Australian Passport
  Only the DVS Passport source is supported.
• ASIC Personal Name Search
  This file contains the details of all individuals who are currently, or have been, directors of an ASIC registered company or other ASIC registered entity. This is a non-document source that is typically verified as a background check.
• Australian Tenancy File
  This file contains the details of Australian tenants living in rental properties. All applications undertake a 100 point ID assessment to verify their identity. This is a non-document source that is typically verified as a background source.
• Australian Electoral Roll
  All persons currently registered to vote will appear on the electoral roll. This is a non-document source that is typically verified as a background source.
• Dun and Bradstreet (D&B) Credit File Header Data
  Compiled and maintained by D&B as part of their Consumer Credit Reporting Agency activities. Number of records disclosed by FCS Online (a D&B entity): over 16 million. Special conditions apply to the use of this data source (see Legal Considerations). This is a non-document source that is typically verified as a background source.
• Birth Certificate
  A DVS source available to government agencies only.
• Change of Name Certificate
  Also known as DVS Change of Name Certificate (BDM) or Change of Name Certificate (DVS).
• Marriage Certificate
  Also known as DVS Marriage Certificate (BDM) or Marriage Certificate (DVS).

This list represents a subset of the available greenID data sources.

Usage Instructions

Use the following proceedure to configure GreenID in your form:

• Add the GreenID Verify component onto your page or GreenID Dialog into the Dialogs folder of your form. If using the GreenID Verify component you may find it better to add it to a section configured with Top To Bottom Layout (in the Additional Layout properties) to provide more horizontal space.
• Select the GreenID Verify component (if using the dialog you will find this inside the Dialog Content block) and on the Properties tab select the Options, Background Sources, and Interactive Sources you wish to support.
• Open the Input Fields section on the Properties tab and map all required fields into the input data maps.
• In the Rules section, add any processing rules to handle On Verified and On Failure events.

Help Display Option

This package provides an option to display help content during the interactive verification process. This help content includes document sample images indicating location of required information and related instructions. By default, this help content will be presented but may be disabled by deselecting the relevant configuration option.

Manual Verification Option

This package provides support for manual verfication should the user fail or opt out of the electronic verification. This feature can be enabled or disabled according to the usage requirements using the Allow Opt Out property on the GreenID Verify component.

Multiple Verification Sessions

If you need to perform id verifications on multiple individuals in a single transaction you will need to add an instance of the GreenID Verify component for each individual and specify a Role Identifier (found under Options on the Properties panel) for each instance. For example, if your form supports 2 applicants you would specify a Role Identifier of Applicant1 and Applicant2 respectively. This will ensure that the sessions do not interfere with each other.

Triggering the Background Checks

Typically you would trigger the GreenID background checks before the applicant is presented with the identity verification section of the form. This way, if the applicant is verified successfully on the background checks alone, then the identity verification section can be excluded from the applicant experience.

You can add the following call to a rule in your form to trigger the background checks automatically at an appropriate time:

Form.fireRule("click" ,"greenIdVerifyButton" , data);

Dialog Usage Patterns

Avoka's recommended usage pattern is to trigger the background verification process when the applicant clicks the Continue button and on a page where we have captured all personal details required to do so. For example, if you wanted to trigger this process when the applicant clicks the Continue button at the bottom of page 2 of the form you could add this script to the click rule:

if(Form.getCurrentPageNumber() !== 2 || data.verifyStatus === "VERIFIED"){
  // If the applicant is verified or we are not on page 2 then continue as normal
  Form.$Pages.move(true)
} else {
  // If we are on page 2 and we are not yet verified then reset and trigger GreenID
  data.greenidSelectSource = "";
  data.verifySources = "";
  Form.fireRule("click" ,"greenIdVerifyButton" , data);
}

Additionally, if we receive a successful validation result then we should automatically progress to the next page. We can achieve this by adding to the On Verified rule of the GreenID Verify component as follows:

Form.showDialog(""); // Default script
Form.$Pages.move(true); // Move on to the next page

Address Format Requirement

GreenID requires a physical address provided in Long format with an explicit breakdown of address components as follows:

Tamper Proofing

To help combat fraudulent applications this package includes a Groovy service that checks for data tampering to ensure that the data provided at submission time exactly matches the data used to complete the identity verification. To enable this capability you must add a call to the Tamper Check groovy service, passing in key personal information attributes at the time of submission. If all provided data exactly matches the original identity this service will return a successful result (true), otherwise a failure will result (false).

Note: you need to manually add this call to your pre/post submit processing functions in order to utilise this feature.

Note: Tamper Check Groovy service doesn't work with fluent functions because submit processing functions are not supported.

Licencing

Clients must ensure they are appropriately licences in order to use this package. Prior to using this package clients must establish a commercial arrangement directly with VIX Verify.

Compatibility

This package has the following compatibility requirements:

Release Notes

Version 4.2June 13, 2023

• Updated readme.html to Temenos branding.

Version 4.1November 16, 2022

• Added additional fields for AEC - Date of Birth and Property Name.
• Added additional help images for Change of Name Certificate and Marriage Certificate.
• Added additional help images for drivers licenses.
• Fixed AEC field creation that was using wp instead of aec.
• Fixed Birth Certificate Registration State field showing only 5 states.
• Fixed Birth Certificate Registration State field showing only 5 states.
• Updated spelling to 'licence'.

Version 4.0July 25, 2022

• Added two new source documents - Change of Name Certificate and Marriage Certificate.

Version 3.0Feb 28, 2022

• Enhanced to add new "Card Number" field for DVS Driver's Licence checks, dependent on the user's state

• Enhanced to allow the choice of birth certificate as an option to improve quality of identity verification
• Defect fix - remove mandatory check on Address Street Type field

• Defect fix - Citizenship source is missing Acquisition Date field.
• Removed white pages as interactive source because it's no longer supported.
• Added local mandatory check on Medicare expiry year field.
• Updated service connection endpoint in documentation.

• Enhanced to support the "Not contributing" source state from GreenID to avoid unnecessary verification requests calls.
• Defect fix - send passport details as part of a background source check.
• Added process flow diagram and fixed minor typos.

• Added support for Maestro language translation features.
• Added missing rule template to GreenID Verify Component.

• Medicare Expiry Year dropdown is now dynamically filled with valid values based on the current date and the selected month (Ref TPD-5062).

• Resolved defect where Country of Issue for Visa documents was being truncated to a single character (Ref TPD-5000).

• Added the Tamper Check groovy service. (See also Tamper Proofing)

• Added the GreenID Dialog component.(See also Dialog Usage Patterns)

• Added support for multiple verification sessions in a single transaction by optionally specifying a Role Identifier on the GreenID Verify component in Maestro.

• Created version 2 of the VIX Verify GreenID - Identity Verification dynamic data service. This service now passes dob (Date of Birth) to Medicare verification.