2.9.4.3 Inward VOP Requests - Name / Identifier Match Status Population

This topic gives information about the Inward VOP Requests - Name / Identifier Match Status Population.

Name matching is performed using the Primary Customer Name or any joint holder's name received from the ECA system. The Name Match status is derived based on the following criteria:

Table 2-32 Name Match Status and Conditions

Name Match Status	Conditions
MTCH - Match The name received in the VOP request is a match with the name received from ECA system for primary /any one of the joint holders.	Truncate leading or trailing spaces of Creditor Name received in the VOP request. Resultant name is same as the name in the response from Core system for primary or one of the joint holders. Match by considering Creditor Name received in the VOP requestin lower case and names from ECAsystemtoo in lower case. Apply Special character replacement as applicable for Network with scheme linked as SCT (if not available SCT Inst) to the names received in the request and from ECAsystemand match the names. Honorifics and titles (Dr., Mr., Ms.) in the name stringare removed.
CMTC - Close Match	If the name received in the VOP request is not a match with the name received in ECA system response, then second level match is done with the names available in Customer Account Name Match Maintenance Function ID: PMDCUSNM. If a match is found, system will send response as Close Match. Beneficiary actual name returned by ECA system will be populated in the VOP response in close match cases.
NMTC - No Match	Match/Close Match, status is marked as No Match.
NOAP - Not Applicable Verification Check Not Possible / Validation Check is not applicable	If error is returned from ECA system, status is marked as NOAP.

The Identifier Match status is derived based on the following criteria:

Table 2-33 Identifier Match Status and Conditions

Identifier Match Status	Conditions
MTCH - Match	Identifier received in the request matches to identifier returned by core system for the scheme code.
NMTC - No Match	If not matching, no match response is sent.
NOAP - Not Applicable Verification Check Not Possible / Validation Check is not applicable	If error is returned from core system, status is marked as NOAP.

Note:

OBPM does not derive the scheme code for Party Organization identifiers. It is expected both in the pre-validation request and ECA system response. If missing, OBPM returns a NOAP error.