LogoLogo
Connect
Connect
  • 🏡Welcome to LHV Connect API
  • 📺News and Updates
    • 📈Performance and Stats
    • 🔔Notice of Change
  • 🧭Quick Start Guide
  • 🎥Connect Fundamentals
    • Authentication and Certificates
    • Environments
    • Messaging Pattern
    • Service Provider model
    • Technical limitations
    • Encoding and Languages
    • Response Compression
    • Dates and Time Zones
    • Response Codes and Error handling
    • Onboarding
    • Live Proving
    • LHV UK and Estonia integrations
    • FAQ and Tips
  • 📖Service Catalogue
    • 💚Heartbeat
      • Heartbeat - GET
      • Heartbeat Advanced - GET
    • 📩Messages Services
      • Get next message
      • Get list of messages
      • Get list of messages V2
      • Get message by response ID
      • Count number of messages
      • Mark message as processed
      • Mark batch of messages as processed
      • Mark batch of messages as processed V2
      • Messages Metadata
      • Get compressed message for testing
    • 💰Account Information Services
      • Account Balance
      • Account Statement
      • Transaction Notification
        • Incoming Bacs Credit Notification
    • 💸Payment Initiation Services
      • Pain.001.001.09
      • Pain.002.001.10
      • Samples
      • Authentication methods
      • Payment Scheme Selection
      • Payment Return Initiation
      • Payments Service Idempotency
      • Payments Originating Overseas
      • Legacy documents
        • pain.001.001.03 format
    • ✅Confirmation of Payee Services
      • Confirmation of Payee - Requester
      • Confirmation of Payee - Responder
    • 😶‍🌫️VIBAN Services
      • VIBAN Open
      • VIBAN Bulk Open
      • VIBAN Modify
      • VIBAN Info
      • VIBAN Close
      • VIBAN Notification
    • 🔗Indirect Scheme Access
      • Agency Account Synchronization
      • RTF - Routing Table Files message
      • 🧾Payment Collection Services
        • 💷Bacs Direct Debit
          • Bacs Direct Debit Mandate Initiation Request
          • Bacs Direct Debit Mandate Initiation Response
          • Bacs Direct Debit Mandate Initiation Response Confirmation
          • Bacs Direct Debit Mandate Cancellation Request
          • Bacs Direct Debit Mandate Cancellation Response
          • Direct Debit Incoming Collection Notification Request
          • Direct Debit Collection Notification Response
          • Direct Debit Collection Notification Response Confirmation
          • Direct Debit Reversal Notification Request
          • Examples
    • 📨Webhooks
      • Webhook Format and Processing
      • Managing Webhook Configurations
      • Webhook Security
      • Webhook Metadata
      • Full Bodied Webhooks
  • 🗓️Reference
    • Glossary
    • Code Reference Tables
      • Balance Type Codes
      • Credit and Debit Transaction Codes
      • Payment Scheme Codes
      • Direct Debit Scheme Codes
      • Payment Reject Codes
      • Payment Return Codes
      • Bacs Direct Debit Mandate Reject Codes
      • Bacs Direct Debit Reject Codes
      • Bacs Direct Debit Reversal Reason
      • Bank Transaction Codes
      • Transaction Purpose Codes
      • Category Purpose Codes
      • Private Person Identification Codes
      • Organisation Identification Type Codes
      • Payment Priority Codes
      • Charges Bearer Codes
  • ☎️Support
    • Contact
Powered by GitBook
On this page
  • Service description
  • Inbound CoP Request Notification
  • Body
  • Example of the flow
  • Reason code values

Was this helpful?

  1. Service Catalogue
  2. Confirmation of Payee Services

Confirmation of Payee - Responder

Description of Confirmation of Payee Responder service.

PreviousConfirmation of Payee - RequesterNextVIBAN Services

Last updated 29 days ago

Was this helpful?

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 .

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

Incoming CoP Request Notification can be requested via the Messages Services.

HTTP Header Message-Response-Type: CONFIRMATION_OF_PAYEE_INCOMING

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

Response.Data.Attributes.Reason

O

Human-readable description of reason code . Only populated if reason code is.

Examples

{
  "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"
      }
    }
  }
}
{
  "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"
      }
    }
  }
}
{
  "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."
      }
    }
  }
}

Example of the flow

Step
Action
Description

1.

Sync accounts with details required for Confirmation of Payee.

2.

LHV will confirm the synchronization.

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.

Reason code values

ReasonCode
Description

AC01

Account not found. There was no account with the account number you provided. Please check and try again.

ACNS

Cannot check details. Confirmation of Payee is not supported by this account.

ANNM

The name you provided doesn't match the name for the account. You can still continue with the payment, but your money may be sent to the wrong account.

BAMM

The account details are a close match. However, it is a business account, not a personal account and the actual name on the account is (...).

BANM

The account details match. However, it is a business account, not a personal account.

CASS

Account no longer exists. This account has been switched to a new one.

Please contact your recipient for updated account details.

IVCR

Cannot check details. Unable to locate the account based on the Reference provided. Please check and retry.

MBAM

The name is a close match. The actual name on the account is (...).

OPTO

Cannot check details. Confirmation of Payee is not supported by this account.

PAMM

The account details are a close match.

However, it's a personal account, not a business account and the actual name on the account is (...).

PANM

Close match. The account details match, however it's a personal account, not a business account.

SCNS

Not a match. The sort code you provided doesn't match the account. Please check and try again.

Encoded reason for mismatch. Only populated if answer is rejected. .

To utilize this service, accounts must be synchronized with all mandatory CoP fields. The documentation of account sync can be found .

See possible error codes .

📖
✅
Possible values
Confirmation of Payee Responder
Drawing
here
here
here