Confirmation of Payee - Responder

Description of Confirmation of Payee Responder service.

Service description

The CoP Responder Service enables other banks to request confirmation of creditor account details, including account name, type, and other required fields. To utilize this service, accounts must be synchronized with all mandatory CoP fields.

The documentation of account sync can be found here.

Upon receiving a request, a notification is generated. If you would like to receive these notifications, please contact your relationship manager.

Inbound CoP Request Notification

Body

Field	M/O	Description
Request.DebtorParty.AccountWith.BankName	O	Structure containing information about the debtor of the request. NB! This field is not currently supported.
Request.Data.Id	M	Name verification ID.
Request.Data.CreatedOn	M	Verification time.
Request.Data.Attributes.AccountClassification	M	Classification of the account to do a name verification on. Can be BUSINESS or PERSONAL.
Request.Data.Attributes.AccountNumber	M	UK account number of the account to do a name verification on.
Request.Data.Attributes.AccountNumberCode	M	Type of the account number, always 'BBAN'.
Request.Data.Attributes.BankId	M	UK sort code of the account to do a name verification on.
Request.Data.Attributes.BankIdCode	M	Type of bank ID, always 'GBDSC'.
Request.Data.Name	M	The name string to be checked for a match.
Request.Data.SecondaryIdentification	O	Secondary reference information to identify the account.
Response.Data.Attributes.Status	M	Admission status, indicates if the request has been successfully received from the counterparty and could be responded to. confirmed in case of success, failed otherwise.
Response.Data.Attributes.Answer	O	Indicator if the verification has produced a (full) match or not. CONFIRMED in case of a full match, REJECTED otherwise. Not populated if request failed.
Response.Data.Attributes.ActualName	O	The actual name of the account holder. Only present in case of a close match
Response.Data.Attributes.ReasonCode	O	Encoded reason for mismatch. Only populated if answer is rejected. Possible values.
Response.Data.Attributes.Reason	O	Human-readable description of reason code . Only populated if reason code is.

Samples

Full Match

{
  "Request": {
    "DebtorParty": {
      "AccountWith": {
        "BankName": "Some Bank Ltd"
      }
    },
    "Data": [
      {
        "Id": "4942f12c-5430-4d1b-8b56-c7f1c8a9118d",
        "CreatedOn": "2021-10-15T18:13:40Z",
        "Attributes": {
          "AccountClassification": "PERSONAL",
          "AccountNumber": "12345678",
          "AccountNumberCode": "BBAN",
          "BankId": "123456",
          "BankIdCode": "GBDSC",
          "Name": [
            "Joe Bloggs"
          ],
          "SecondaryIdentification": "123"
        }
      }
    ]
  },
  "Response": {
    "Data": {
      "Attributes": {
        "Status": "confirmed",
        "Answer": "CONFIRMED"
      }
    }
  }
}

Close Match

{
  "Request": {
    "DebtorParty": {
      "AccountWith": {
        "BankName": "Some Bank Ltd"
      }
    },
    "Data": [
      {
        "Id": "4942f12c-5430-4d1b-8b56-c7f1c8a9118d",
        "CreatedOn": "2021-10-15T18:13:40Z",
        "Attributes": {
          "AccountClassification": "PERSONAL",
          "AccountNumber": "12345678",
          "AccountNumberCode": "BBAN",
          "BankId": "123456",
          "BankIdCode": "GBDSC",
          "Name": [
            "Jo Boggs"
          ],
          "SecondaryIdentification": "123"
        }
      }
    ]
  },
  "Response": {
    "Data": {
      "Attributes": {
        "Status": "confirmed",
        "Answer": "REJECTED",
        "ActualName": "Joe Bloggs",
        "ReasonCode": "MBAM",
        "Reason": "String is a close match to the account name"
      }
    }
  }
}

No Match

{
  "Request": {
    "DebtorParty": {
      "AccountWith": {
        "BankName": "Some Bank Ltd"
      }
    },
    "Data": [
      {
        "Id": "4942f12c-5430-4d1b-8b56-c7f1c8a9118d",
        "CreatedOn": "2021-10-15T18:13:40Z",
        "Attributes": {
          "AccountClassification": "PERSONAL",
          "AccountNumber": "87654321",
          "AccountNumberCode": "BBAN",
          "BankId": "123456",
          "BankIdCode": "GBDSC",
          "Name": [
            "Joe Bloggs"
          ],
          "SecondaryIdentification": "123"
        }
      }
    ]
  },
  "Response": {
    "Data": {
      "Attributes": {
        "Status": "confirmed",
        "Answer": "REJECTED",
        "ReasonCode": "AC01",
        "Reason": "There is no account with the given account number."
      }
    }
  }
}

Sample of the flow

Confimation of Payee Responder

Step	Action	Description
1.	Sync accounts with details required for Confirmation of Payee.	To utilize this service, accounts must be synchronized with all mandatory CoP fields. The documentation of account sync can be found here.
2.	LHV will confirm the synchronization.	See possible error codes here.
3.	LHV receives inbound CoP Request.	LHV will receive inbound CoP Request from Debtor Party.
4.	LHV will provide notification of inbound CoP Request.	LHV will issue a notification regarding a previously received request. This notification will include details about both the request and response.