[KYC Match / KYC Fill-in] Coexistence of aggregated fields and separate fields for Name and Address

[ToshiWakayama-KDDI]

Problem description

To consider coexisting of aggregated fields and separete fields for Name and Address attributes
(Spin off from Issue #65, item No.5)

BR

[HuubAppelboom]

In general, when you can expect spelling mistakes in parts of the data, I think we need to support separate fields to avoid having too many false negatives for the Match product.

For example, when there is a spelling mistake in a streetname or a streetnumber, this makes a large difference.

Example: the correct addres is "Weststreet 185".
If the CSP submits "Wetstreet" and "185", you could return as answer that the streetName matches for 95% (applying fuzzy name matching logic), and that the streetNumber is "true". That gives the CSP the possibility to accept the customer input (and optionally ask the end user to check the streetName once more.
In case the CSP submits "Weststreet 18" as a combined item, you don't have the possibiliy to apply fuzzy name matching logic, because that would give a wrong results, because the spelling mistake is now in the streetNumber.

For KYC fill-in this does not apply, here you can choose to work with combined fields (although many CSP's would appreciate to receive the data separate).

[HuubAppelboom]

Regarding providing givenName and familiyName as separte items, this way you can make a disctinction as a CSP between cases where there is no match at all between the data submitted and the data of the contract owner, case where only the family name matches (and you can still assume there is a relationship between the end user and the contract owner), or when there is a full match.

For KYC fill-in this does not apply, here you can choose to work with combined fields (although many CSP's would appreciate to receive the data separate).

For some use cases a match on just the family name can be acceptable (for example when placing an ecommerce order), and for other cases you may require an exact match on all fields (for cases where more privavcy sensitive data is being shared, or an age check is relevant). By providing the data separate you can let the CSP decide what to do.