Specification for LHV CONNECT

Version History

Overview

LHV Connect is an API offered by LHV that our customers can use to integrate different banking services directly into their software. Using these services you can execute payments, query account balances or transaction history and perform many other tasks as part of your own software - without need to log into Internet Bank or use any other time consuming channels.
Technically LHV Connect is RESTful web service with requests and responses in XML format, with high availability and fast processing speeds.

Agreement

To start using LHV Connect services you need:

• Valid customer and internet bank agreement with LHV
• Sign additional Connect agreement.

Certificates

Two different certificates are needed for using LHV Connect services:

• Customer specific SSL certificate - identifies and confirms on transport layer that messages were sent by customer's software to the Bank. LHV will generate this custom made certificate for the customer. Steps to be taken:
  1. Customer signs Connect agreement;
  2. LHV sends to the customer necessary data for generating the certificate request file (request.csr);
  3. Customer sends the request file to LHV and receives the certificate.
• Public root certificate for Connect.lhv.ee, that ensures that client is connecting the the right service - root CA is available here.

Additionally:

• Signing certificate - some services offered via LHV Connect need a valid digital signature. Currently we support signing certificates based on non-reproducible physical devices and these are: Estonian digi-ID (ID-card), Estonian Mobiil-ID.

Clients and connection schemes

There are two different connection schemes, how clients can connect and use Connect services:

Single clients

Client itself is the sole holder of the authentication certificate and connection software.

Service providers and end users using their services

In this scheme there are two kinds of clients:

• Service providers (software owner, technical aggregator) - they are directly connected to Connect
• End user clients, who use CONNECT through service providers - not directly connected to Connect

Only service provider connection software is using Connect services directly. End users are using the service provider software.
For all requests we also need to know the end user - the actual client that uses the service provider.
For this we require two HTTP headers in addition to regular expected input:

• Client-Code (registration code)
• Client-Country (country code (2 characters); issuing country of registration code)

If these are missing from the request, you will get a corresponding error.

Messaging

Client message container could be seen as an inbox. Client sends a request to the server and then polls the inbox for a response. If there are any, then it is possible to get the first message. The whole cycle of one message consists of three stages: sending the request, retrieving the response and deleting the response.

Sending request

POST https://connect.lhv.eu/{service-url}

Sample: POST https://connect.lhv.eu/account-statement (the body should contain the actual request)

After successful sending of the message CONNECT gives back a header, for example
Message-Request-Id: REQe38a3875c8a94cc0bf48c558a8c9ee82

This can be used for correlation purposes to later map all responses to the request. For example one can have a single payment request but many corresponding credit-debit notifications.

Retrieving the response

GET https://connect.lhv.eu/messages/next
Poll the client inbox with URL above. The response contains the following important headers:

• Message-Request-Id (optional) - the same id as the initial request. There are cases where request id can be missing, for example the automatic account statement report service.
  Sample: Message-Request-Id: REQe38a3875c8a94cc0bf48c558a8c9ee82
• Message-Response-Id (mandatory) - unique response id.
  Sample: Message-Response-Id: RES4ab8a01dd7ed4ed792f0605761ae532a

When executing the request you can receive following HTTP responses:

• 200 - there is a message waiting and there should be some content in the response XML
• 204 - there are no new messages

Confirm the successful reading of the response

Confirm that reading the response was successful by deleting the message from your inbox. For this, use the response id.

DELETE https://connect.lhv.eu/messages/RES4ab8a01dd7ed4ed792f0605761ae532a

This step is important, because you can’t retrieve the next message until you confirm reading the previous message. After delete was successful, you can retrieve the next message.

NB! Unread messages older than 5 days are automatically scheduled for deletion.

Response Codes

Error Handling

Service specific errors to Merchant Settlement Report Request and Account Statement Request are returned with following xml file.

List of error codes can be found at the service description.

Sample

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Errors>
    <Error>
        <ErrorCode>errStatement_PeriodInvalid</ErrorCode>
        <Description>From date cannot be later than to date.</Description>
        <Field>FrDt</Field>
    </Error>
    <Error>
        <ErrorCode>NotNull</ErrorCode>
        <Description>Name can't be null</Description>
        <Field>Name</Field>
    </Error>
</Errors>

General error codes

CONNECT Services

Communication Test

Heartbeat service for testing the validity of authorization certificate.

Payment Initiation

Customer to bank Payment Initiation (pain.001.001.03) covers SEPA and other payments at LHV Pank.
There are 3 different possibilities for sending payments via Connect:

• Payment files are sent by plain xml. All sent payments are seen at Internet bank under Pending payments and payments can be signed (only) there. Internet Bank daily and monthly limits and acceptance rate is applied
• Payment files are sent in a signed BDOC container. Internet bank daily and monthly limits and acceptance rate is applied. If payment requires more than one signature, all signatures must be included in the bdoc container and limits are subtracted from the last signer.
• Payment files are sent by plain xml and processed automatically without additional user verification. Connect specific daily and monthly limits are followed. Also Connect´s appendix has to be signed to use this possibility.

Payment Status Report (pain.002.001.03) is returned to inform about the status of imported payments. More than one status may be returned for one payment depending on the details.

Account Reports

Account Reports may be requested by the client with Account Report Request (camt.060.001.03) file. Based on which report is requested, response is returned with

• Account Statement (camt.053.001.02)
• Account Balance (camt.052.001.06).

When using service provider connection scheme - also HTTP headers Client-Code and Client-Country are included in the message response. Service providers should always verify these values to identify the correct end user.

Automatic Account Statement

Automatic Account Statement is similar to Account Statement, also based on camt.053.001.02 but is executed automatically each day.

Bank to customer Automatic Account Statement service is account specific as stated in the CONNECT agreement. Automatic Account Statement of the previous day is sent to the message queue every day at 5 AM and generated for all transactions done on previous day from 00:00 until 23:59. If no transactions are made on that day, an empty statement is sent with opening and closing balance.

When using service provider connection scheme - also HTTP headers Client-Code and Client-Country are included in the message response. Service providers should always verify these values to identify the correct end user.

Debit Credit Notification

Bank to customer account specific service for notifying clients of all incoming and outgoing (credit and debit) transactions on account. Notifications are sent with Debit Credit Notification (camt.054.001.02) file 24/7.

When using service provider connection scheme - also HTTP headers Client-Code and Client-Country are included in the message response. Service providers should always verify these values to identify the correct end user.

Statement of Accepting Card Payments

Bank to merchant Point of Sales (POS) Settlement report, which includes all single card payments, cancellations and returns. Transaction amount, charges and net amount is given per each transaction.

Virtual IBAN (VIBAN) services:

Virtual IBAN is a fully functional IBAN for the outside world. But internally it works more as a reference number to a particular customer/account of a PSP.
We do not keep track of the funds of a Viban, all funds are held on the master account. Vibans belong to PSP (our client) but they are allocated to a Viban holder (client of our client or End client).
End clients can be private or legal clients.
Viban is always connected to a master account. One Viban can only have one master account. One master account can have unlimited amount of Vibans connected to it. There is also no limit to how many master accounts one customer (user ID) can have.

• Virtual IBAN Open - used to request new Virtual IBAN opening
• Virtual IBAN Bulk - used for bulk opening nameless Virtual IBANs
• Virtual IBAN Modify - used to add Virtual IBAN holder data to nameless Virtual IBANs
• Virtual IBAN Info - used to request Virtual IBAN data
• Virtual IBAN Close - used to close Virtual IBAN
• Virtual IBAN Status Notification - used to notify client about Virtual IBAN status changes

Communication Test

Heartbeat service

GET https://connect.lhv.eu/heartbeat

Service for testing if system is up and authentication is configured correctly. Returns current system time.

Sample

<HeartBeatResponse>
    <TimeStamp>2016-01-06T11:42:33.491</TimeStamp>
</HeartBeatResponse>

POST https://connect.lhv.eu/heartbeat

Service for testing your BDOC request.

Request should contain signed BDOC containing request.xml file. Service takes authenticated user info, extracts BDOC signature data and request.xml content and composes response xml like below.

Service response can be retrieved via messaging service (GET https://connect.lhv.eu/messages/next).

Sample

<HeartBeatResponse>
    <TimeStamp>2016-01-06T11:42:25.709</TimeStamp>
    <AuthorizedUser>
        <Name>LHV Pank AS</Name>
        <Code>10539549</Code>
    </AuthorizedUser>
    <Signatures>
        <Signature>
            <Name>LHV Pank AS</Name>
            <Code>10539549</Code>
        </Signature>
    </Signatures>
    <UserRequest>Test</UserRequest>
</HeartBeatResponse>

Statement of Accepting Card Payments

Request Merchant Payment Report

POST https://connect.lhv.eu/merchant-report

Request message

Sample

<MerchantReportRequest>
    <Type>CAMT_SETTLEMENT</Type>
    <PeriodStart>2015-12-22</PeriodStart>
    <PeriodEnd>2015-12-22</PeriodEnd>
</MerchantReportRequest>

Response Merchant Payment Report

Message description

Message is used to get an overview about customer (merchant) card payments during the specified period.

Message structure

Group Header – mandatory, occurs once.
Notificaton – mandatory and repetitive per account number and currency. One notification block can include many entries.
Entry – optional and repetitive. Contains information about single entry.

Message root

Group header

Sample

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.054.001.02">
    <BkToCstmrDbtCdtNtfctn>
        <GrpHdr>
            <MsgId>625402016031520160315</MsgId>
            <CreDtTm>2016-03-15T17:17:56</CreDtTm>
        </GrpHdr>
        <Ntfctn>
            <Id>625402016031520160315EUR</Id>
            <CreDtTm>2016-03-15T17:17:56</CreDtTm>
            <FrToDt>
                <FrDtTm>2016-03-15T00:00:00.000</FrDtTm>
                <ToDtTm>2016-03-15T00:00:00.000</ToDtTm>
            </FrToDt>
            <Acct>
                <Id>
                    <IBAN>EE777700771000845879</IBAN>
                </Id>
                <Ccy>EUR</Ccy>
            </Acct>
            <TxsSummry>
                <TtlCdtNtries>
                    <NbOfNtries>1</NbOfNtries>
                    <Sum>84.26</Sum>
                </TtlCdtNtries>
                <TtlDbtNtries>
                    <NbOfNtries>0</NbOfNtries>
                    <Sum>0.00</Sum>
                </TtlDbtNtries>
            </TxsSummry>
            <Ntry>
                <NtryRef>4904</NtryRef>
                <Amt Ccy="EUR">83.030000</Amt>
                <CdtDbtInd>CRDT</CdtDbtInd>
                <Sts>BOOK</Sts>
                <BookgDt>
                    <Dt>2016-01-15</Dt>
                </BookgDt>
                <ValDt>
                    <Dt>2016-03-15</Dt>
                </ValDt>
                <AcctSvcrRef>4904</AcctSvcrRef>
                <BkTxCd>
                    <Domn>
                        <Cd>PMNT</Cd>
                        <Fmly>
                            <Cd>MCDR</Cd>
                            <SubFmlyCd>POSP</SubFmlyCd>
                        </Fmly>
                    </Domn>
                    <Prtry>
                        <Cd>87654321 001</Cd>
                    </Prtry>
                </BkTxCd>
                <NtryDtls>
                    <TxDtls>
                        <Refs>
                            <AcctSvcrRef>4904</AcctSvcrRef>
                            <ChqNb>12345</ChqNb>
                            <Prtry>
                                <Tp>532610******3339</Tp>
                                <Ref>1234567</Ref>
                            </Prtry>
                        </Refs>
                        <AmtDtls>
                            <TxAmt>
                                <Amt Ccy="EUR">84.26</Amt>
                            </TxAmt>
                        </AmtDtls>
                        <Chrgs>
                            <Amt Ccy="EUR">1.230000</Amt>
                        </Chrgs>
                        <RltdPties>
                            <Dbtr>
                                <Nm>Legal Merchant</Nm>
                            </Dbtr>
                            <DbtrAcct>
                                <Id>
                                    <IBAN>EE777700771000845879</IBAN>
                                </Id>
                            </DbtrAcct>
                            <Cdtr>
                                <Nm>Legal Merchant</Nm>
                            </Cdtr>
                            <CdtrAcct>
                                <Id>
                                    <IBAN>EE777700771000845879</IBAN>
                                </Id>
                            </CdtrAcct>
                        </RltdPties>
                        <RltdAgts>
                            <DbtrAgt>
                                <FinInstnId>
                                    <Nm>689MC</Nm>
                                </FinInstnId>
                            </DbtrAgt>
                        </RltdAgts>
                        <RmtInf>
                            <Ustrd>www.abcdef.com \Tallinn \10116 ESTEST</Ustrd>
                        </RmtInf>
                    </TxDtls>
                </NtryDtls>
            </Ntry>
        </Ntfctn>
    </BkToCstmrDbtCdtNtfctn>
</Document>

Error codes

Account Reports

Request Account Report

Account Statement POST https://connect.lhv.eu/account-statement
Account Balance POST https://connect.lhv.eu/account-balance

XML format (camt.060.001.03)

The ISO 20022 Account Report Request camt.060.001.03 standard is used.

Message root

Group header

Sample

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:iso:std:iso:20022:tech:xsd:camt.060.001.03">
    <AcctRptgReq>
        <GrpHdr>
            <MsgId>123</MsgId>
            <CreDtTm>2016-03-03T05:00:00</CreDtTm>
        </GrpHdr>
        <RptgReq>
            <ReqdMsgNmId>camt.053.001.02</ReqdMsgNmId>
            <Acct>
                <Id>
                    <IBAN>EE457700771000676899</IBAN>
                </Id>
            </Acct>
            <AcctOwnr>
                <Pty/>
            </AcctOwnr>
            <RptgPrd>
                <FrToDt>
                    <FrDt>2016-03-02</FrDt>
                    <ToDt>2016-03-02</ToDt>
                </FrToDt>
                <FrToTm>
                    <FrTm>00:00:00+02:00</FrTm>
                    <ToTm>23:59:59+02:00</ToTm>
                </FrToTm>
                <Tp>ALLL</Tp>
            </RptgPrd>
            <ReqdBalTp>  
                <CdOrPrtry>  
                    <Prtry>DATE</Prtry>
                </CdOrPrtry> 
            </ReqdBalTp>             
        </RptgReq>
    </AcctRptgReq>
</Document>

Error codes

Response Account Statement

XML format (ISO 20022 Account Statement Message camt.053.001.02)

The ISO 20022 Account Statement Message camt.053.001.02 standard is used to report account booked transactions and balances of a selected time period. The message includes information about the opening balance, the closing balance, and the available balance together with all booked transactions of a reporting period. The ISO 20022 format allows to include information that is not supported by LHV. That information is not provided by LHV.

Message structure

Group Header – mandatory, occurs once.
Statement – mandatory and repetitive per currency.
Balance – mandatory and repetitive. Contains elements such as Opening Booked Balance and Closing Booked Balance.
Entry – included in the Statement block. Contains information related to an entry on the account.
Entry Details – included in the Entry block. Contains detailed information related to the entry.

Message root

Group header

Statement

Sample

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.053.001.02" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:iso:std:iso:20022:tech:xsd:camt.053.001.02 camt.053.001.02.xsd">
    <BkToCstmrStmt>
        <GrpHdr>
            <MsgId>10001115</MsgId>
            <CreDtTm>2016-03-15T13:04:55</CreDtTm>
        </GrpHdr>
        <Stmt>
            <Id>10001115EUR</Id>
            <CreDtTm>2016-03-15T13:04:55</CreDtTm>
            <FrToDt>
                <FrDtTm>2016-03-10T00:00:00</FrDtTm>
                <ToDtTm>2016-03-15T13:04:55</ToDtTm>
            </FrToDt>
            <Acct>
                <Id>
                    <IBAN>EE457700771000676899</IBAN>
                </Id>
                <Ccy>EUR</Ccy>
                <Svcr>
                    <FinInstnId>
                        <BIC>LHVBEE20XXX</BIC>
                        <Nm>AS LHV Pank</Nm>
                        <PstlAdr>
                            <AdrTp>BIZZ</AdrTp>
                            <StrtNm>Tartu mnt.</StrtNm>
                            <BldgNb>2</BldgNb>
                            <PstCd>10145</PstCd>
                            <TwnNm>Tallinn</TwnNm>
                            <CtrySubDvsn>Harjumaa</CtrySubDvsn>
                            <Ctry>EE</Ctry>
                        </PstlAdr>
                    </FinInstnId>
                </Svcr>
            </Acct>
            <Bal>
                <Tp>
                    <CdOrPrtry>
                        <Cd>OPBD</Cd>
                    </CdOrPrtry>
                </Tp>
                <Amt Ccy="EUR">4497512.65</Amt>
                <CdtDbtInd>CRDT</CdtDbtInd>
                <Dt>
                    <Dt>2016-03-10</Dt>
                </Dt>
            </Bal>
            <Bal>
                <Tp>
                    <CdOrPrtry>
                        <Cd>CLBD</Cd>
                    </CdOrPrtry>
                </Tp>
                <Amt Ccy="EUR">4497505.65</Amt>
                <CdtDbtInd>CRDT</CdtDbtInd>
                <Dt>
                    <Dt>2016-03-15</Dt>
                </Dt>
            </Bal>
            <TxsSummry>
                <TtlCdtNtries>
                    <NbOfNtries>0</NbOfNtries>
                    <Sum>0.00</Sum>
                </TtlCdtNtries>
                <TtlDbtNtries>
                    <NbOfNtries>2</NbOfNtries>
                    <Sum>2.00</Sum>
                </TtlDbtNtries>
            </TxsSummry>
            <Ntry>
                <Amt Ccy="EUR">1.00</Amt>
                <CdtDbtInd>DBIT</CdtDbtInd>
                <Sts>BOOK</Sts>
                <BookgDt>
                    <Dt>2016-03-10</Dt>
                </BookgDt>
                <AcctSvcrRef>201603101009326802-011387139</AcctSvcrRef>
                <BkTxCd>
                    <Domn>
                        <Cd>PMNT</Cd>
                        <Fmly>
                            <Cd>CCRD</Cd>
                            <SubFmlyCd>FEES</SubFmlyCd>
                        </Fmly>
                    </Domn>
                </BkTxCd>
                <NtryDtls>
                    <TxDtls>
                        <Refs>
                            <AcctSvcrRef>201603101009326802-011387139</AcctSvcrRef>
                        </Refs>
                        <AmtDtls>
                            <InstdAmt>
                                <Amt Ccy="EUR">1.00</Amt>
                            </InstdAmt>
                            <TxAmt>
                                <Amt Ccy="EUR">1.00</Amt>
                            </TxAmt>
                        </AmtDtls>
                        <RltdPties>
                            <Dbtr></Dbtr>
                            <Cdtr></Cdtr>
                        </RltdPties>
                        <RltdAgts></RltdAgts>
                        <RmtInf>
                            <Ustrd>Card (..6748) monthly fee</Ustrd>
                        </RmtInf>
                    </TxDtls>
                </NtryDtls>
            </Ntry>
            <Ntry>
                <Amt Ccy="EUR">1.00</Amt>
                <CdtDbtInd>DBIT</CdtDbtInd>
                <Sts>BOOK</Sts>
                <BookgDt>
                    <Dt>2016-03-11</Dt>
                </BookgDt>
                <AcctSvcrRef>201603111009327754-011387982</AcctSvcrRef>
                <BkTxCd>
                    <Domn>
                        <Cd>PMNT</Cd>
                        <Fmly>
                            <Cd>ICDT</Cd>
                            <SubFmlyCd>OTHR</SubFmlyCd>
                        </Fmly>
                    </Domn>
                </BkTxCd>
                <NtryDtls>
                    <TxDtls>
                        <Refs>
                            <AcctSvcrRef>201603111009327754-011387982</AcctSvcrRef>
                            <InstrId>94</InstrId>
                        </Refs>
                        <AmtDtls>
                            <InstdAmt>
                                <Amt Ccy="EUR">1.00</Amt>
                            </InstdAmt>
                            <TxAmt>
                                <Amt Ccy="EUR">1.00</Amt>
                            </TxAmt>
                        </AmtDtls>
                        <RltdPties>
                            <Dbtr>
                                <Nm>Silver Kullassepp</Nm>
                                <PstlAdr>
                                    <Ctry>EE</Ctry>
                                </PstlAdr>
                                <Id>
                                    <PrvtId>
                                        <Othr>
                                            <Id>48107090295</Id>
                                            <SchmeNm>
                                                <Cd>NIDN</Cd>
                                            </SchmeNm>
                                        </Othr>
                                    </PrvtId>
                                </Id>
                            </Dbtr>
                            <DbtrAcct>
                                <Id>
                                    <IBAN>EE457700771000676899</IBAN>
                                </Id>
                            </DbtrAcct>
                            <Cdtr>
                                <Nm>Test Client</Nm>
                            </Cdtr>
                            <CdtrAcct>
                                <Id>
                                    <IBAN>EE867700771000681884</IBAN>
                                </Id>
                            </CdtrAcct>
                        </RltdPties>
                        <RltdAgts>
                            <DbtrAgt>
                                <FinInstnId>
                                    <BIC>LHVBEE20XXX</BIC>
                                    <Nm>AS LHV Pank</Nm>
                                </FinInstnId>
                            </DbtrAgt>
                            <CdtrAgt>
                                <FinInstnId>
                                    <BIC>LHVBEE20XXX</BIC>
                                    <Nm>AS LHV Pank</Nm>
                                </FinInstnId>
                            </CdtrAgt>
                        </RltdAgts>
                        <RmtInf>
                            <Ustrd>EUR payment</Ustrd>
                        </RmtInf>
                    </TxDtls>
                </NtryDtls>
            </Ntry>
        </Stmt>
        <Stmt>
            <Id>10001115USD</Id>
            <CreDtTm>2016-03-15T13:04:55</CreDtTm>
            <FrToDt>
                <FrDtTm>2016-03-10T00:00:00</FrDtTm>
                <ToDtTm>2016-03-15T13:04:55</ToDtTm>
            </FrToDt>
            <Acct>
                <Id>
                    <IBAN>EE457700771000676899</IBAN>
                </Id>
                <Ccy>USD</Ccy>
                <Svcr>
                    <FinInstnId>
                        <BIC>LHVBEE20XXX</BIC>
                        <Nm>AS LHV Pank</Nm>
                        <PstlAdr>
                            <AdrTp>BIZZ</AdrTp>
                            <StrtNm>Tartu mnt.</StrtNm>
                            <BldgNb>2</BldgNb>
                            <PstCd>10145</PstCd>
                            <TwnNm>Tallinn</TwnNm>
                            <CtrySubDvsn>Harjumaa</CtrySubDvsn>
                            <Ctry>EE</Ctry>
                        </PstlAdr>
                    </FinInstnId>
                </Svcr>
            </Acct>
            <Bal>
                <Tp>
                    <CdOrPrtry>
                        <Cd>OPBD</Cd>
                    </CdOrPrtry>
                </Tp>
                <Amt Ccy="USD">1216.13</Amt>
                <CdtDbtInd>CRDT</CdtDbtInd>
                <Dt>
                    <Dt>2016-03-10</Dt>
                </Dt>
            </Bal>
            <Bal>
                <Tp>
                    <CdOrPrtry>
                        <Cd>CLBD</Cd>
                    </CdOrPrtry>
                </Tp>
                <Amt Ccy="USD">1215.13</Amt>
                <CdtDbtInd>CRDT</CdtDbtInd>
                <Dt>
                    <Dt>2016-03-15</Dt>
                </Dt>
            </Bal>
            <TxsSummry>
                <TtlCdtNtries>
                    <NbOfNtries>0</NbOfNtries>
                    <Sum>0.00</Sum>
                </TtlCdtNtries>
                <TtlDbtNtries>
                    <NbOfNtries>1</NbOfNtries>
                    <Sum>1.00</Sum>
                </TtlDbtNtries>
            </TxsSummry>
            <Ntry>
                <Amt Ccy="USD">1.00</Amt>
                <CdtDbtInd>DBIT</CdtDbtInd>
                <Sts>BOOK</Sts>
                <BookgDt>
                    <Dt>2016-03-15</Dt>
                </BookgDt>
                <AcctSvcrRef>201603151009334556-011396061</AcctSvcrRef>
                <BkTxCd>
                    <Domn>
                        <Cd>PMNT</Cd>
                        <Fmly>
                            <Cd>ICDT</Cd>
                            <SubFmlyCd>OTHR</SubFmlyCd>
                        </Fmly>
                    </Domn>
                </BkTxCd>
                <NtryDtls>
                    <TxDtls>
                        <Refs>
                            <AcctSvcrRef>201603151009334556-011396061</AcctSvcrRef>
                            <InstrId>17793</InstrId>
                        </Refs>
                        <AmtDtls>
                            <InstdAmt>
                                <Amt Ccy="USD">1.00</Amt>
                            </InstdAmt>
                            <TxAmt>
                                <Amt Ccy="USD">1.00</Amt>
                            </TxAmt>
                        </AmtDtls>
                        <RltdPties>
                            <Dbtr>
                                <Nm>Silver Kullassepp</Nm>
                                <PstlAdr>
                                    <Ctry>EE</Ctry>
                                    <AdrLine>Tartu mnt, Tallinn, 11111</AdrLine>
                                </PstlAdr>
                            </Dbtr>
                            <DbtrAcct>
                                <Id>
                                    <IBAN>EE457700771000676899</IBAN>
                                </Id>
                            </DbtrAcct>
                            <Cdtr>
                                <Nm>John Smith</Nm>
                            </Cdtr>
                            <CdtrAcct>
                                <Id>
                                    <Othr>
                                        <Id>440532013000</Id>
                                    </Othr>
                                </Id>
                            </CdtrAcct>
                        </RltdPties>
                        <RltdAgts>
                            <DbtrAgt>
                                <FinInstnId>
                                    <BIC>LHVBEE20XXX</BIC>
                                    <Nm>AS LHV Pank</Nm>
                                </FinInstnId>
                            </DbtrAgt>
                            <CdtrAgt>
                                <FinInstnId>
                                    <BIC>DEUTDEBBXXY</BIC>
                                </FinInstnId>
                            </CdtrAgt>
                        </RltdAgts>
                        <RmtInf>
                            <Ustrd>USD payment</Ustrd>
                        </RmtInf>
                    </TxDtls>
                </NtryDtls>
            </Ntry>
        </Stmt>
    </BkToCstmrStmt>
</Document>

Response Account Balance

XML format (ISO 20022 Account Report Message camt.052.001.06)

The ISO 20022 Account Report Message camt.052.001.06 is used to report current account balance. The report returns two balances: current booked balance (without reservations) and current available balance (with reservations). If client has no balance in any currency, then 0 EUR balance is returned.

Message structure

Group Header - mandatory, occurs once.
Report - mandatory and repetitive per currency. Includes zero to many Balance blocks. Report does not include detailed entry data.

Message root

Group header

Report

Sample

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.052.001.06">
    <BkToCstmrAcctRpt>
        <GrpHdr>
            <MsgId>10042837</MsgId>
            <CreDtTm>2018-03-23T13:19:44.442</CreDtTm>
        </GrpHdr>
        <Rpt>
            <Id>10042837EUR</Id>
            <CreDtTm>2018-03-23T13:19:44.442</CreDtTm>
            <FrToDt>
                <FrDtTm>2018-03-23T13:19:44.442</FrDtTm>
                <ToDtTm>2018-03-23T13:19:44.442</ToDtTm>
            </FrToDt>
            <Acct>
                <Id>
                    <IBAN>EE317700771001417358</IBAN>
                </Id>
                <Ccy>EUR</Ccy>
            </Acct>
            <Bal>
                <Tp>
                    <CdOrPrtry>
                        <Cd>ITBD</Cd>
                    </CdOrPrtry>
                </Tp>
                <Amt Ccy="EUR">548.83</Amt>
                <CdtDbtInd>CRDT</CdtDbtInd>
                <Dt>
                    <Dt>2018-03-23</Dt>
                </Dt>
            </Bal>
            <Bal>
                <Tp>
                    <CdOrPrtry>
                        <Cd>ITAV</Cd>
                    </CdOrPrtry>
                </Tp>
                <Amt Ccy="EUR">553.83</Amt>
                <CdtDbtInd>CRDT</CdtDbtInd>
                <Dt>
                    <Dt>2018-03-23</Dt>
                </Dt>
            </Bal>
        </Rpt>
        <Rpt>
            <Id>10042837GBP</Id>
            <CreDtTm>2018-03-23T13:19:44.442</CreDtTm>
            <FrToDt>
                <FrDtTm>2018-03-23T13:19:44.442</FrDtTm>
                <ToDtTm>2018-03-23T13:19:44.442</ToDtTm>
            </FrToDt>
            <Acct>
                <Id>
                    <IBAN>EE317700771001417358</IBAN>
                </Id>
                <Ccy>GBP</Ccy>
            </Acct>
            <Bal>
                <Tp>
                    <CdOrPrtry>
                        <Cd>ITBD</Cd>
                    </CdOrPrtry>
                </Tp>
                <Amt Ccy="GBP">48.00</Amt>
                <CdtDbtInd>CRDT</CdtDbtInd>
                <Dt>
                    <Dt>2018-03-23</Dt>
                </Dt>
            </Bal>
            <Bal>
                <Tp>
                    <CdOrPrtry>
                        <Cd>ITAV</Cd>
                    </CdOrPrtry>
                </Tp>
                <Amt Ccy="GBP">48.00</Amt>
                <CdtDbtInd>CRDT</CdtDbtInd>
                <Dt>
                    <Dt>2018-03-23</Dt>
                </Dt>
            </Bal>
        </Rpt>
        <Rpt>
            <Id>10042837PLN</Id>
            <CreDtTm>2018-03-23T13:19:44.442</CreDtTm>
            <FrToDt>
                <FrDtTm>2018-03-23T13:19:44.442</FrDtTm>
                <ToDtTm>2018-03-23T13:19:44.442</ToDtTm>
            </FrToDt>
            <Acct>
                <Id>
                    <IBAN>EE317700771001417358</IBAN>
                </Id>
                <Ccy>PLN</Ccy>
            </Acct>
            <Bal>
                <Tp>
                    <CdOrPrtry>
                        <Cd>ITBD</Cd>
                    </CdOrPrtry>
                </Tp>
                <Amt Ccy="PLN">0.02</Amt>
                <CdtDbtInd>CRDT</CdtDbtInd>
                <Dt>
                    <Dt>2018-03-23</Dt>
                </Dt>
            </Bal>
            <Bal>
                <Tp>
                    <CdOrPrtry>
                        <Cd>ITAV</Cd>
                    </CdOrPrtry>
                </Tp>
                <Amt Ccy="PLN">0.02</Amt>
                <CdtDbtInd>CRDT</CdtDbtInd>
                <Dt>
                    <Dt>2018-03-23</Dt>
                </Dt>
            </Bal>
        </Rpt>
    </BkToCstmrAcctRpt>
</Document>

Debit Credit Notification

XML format (ISO 20022 Bank To Customer Debit Credit Notification camt.054.001.02)

The ISO 20022 Bank To Customer Debit Credit Notification camt.054.001.02 standard is used to report customer of payments on the account. Both credit and debit transactions are included.
The message does not include balance information.

Message structure

Group Header – mandatory, occurs once.
Notificaton – mandatory and repetitive per account number and currency. One notification block can include many entries.
Entry – optional and repetitive. Contains information about single entry.

Message root

Group header

Sample

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.054.001.02">
    <BkToCstmrDbtCdtNtfctn>
        <GrpHdr>
            <MsgId>10004486</MsgId>
            <CreDtTm>2016-03-31T15:58:40.072+03:00</CreDtTm>
        </GrpHdr>
        <Ntfctn>
            <Id>10004486EUR</Id>
            <CreDtTm>2016-03-31T15:58:40.074+03:00</CreDtTm>
            <Acct>
                <Id>
                    <IBAN>EE707700771000676255</IBAN>
                </Id>
                <Ccy>EUR</Ccy>
                <Ownr>
                    <Nm>Test Client</Nm>
                    <Id>
                        <OrgId>
                            <Othr>
                                <Id>10453211</Id>
                            </Othr>
                        </OrgId>
                    </Id>
                </Ownr>
                <Svcr>
                    <FinInstnId>
                        <BIC>LHVBEE20XXX</BIC>
                        <Nm>AS LHV Pank</Nm>
                    </FinInstnId>
                </Svcr>
            </Acct>
            <Ntry>
                <Amt Ccy="EUR">5.00</Amt>
                <CdtDbtInd>CRDT</CdtDbtInd>
                <Sts>BOOK</Sts>
                <BookgDt>
                    <Dt>2016-03-31</Dt>
                </BookgDt>
                <AcctSvcrRef>201603311009353671-011413012</AcctSvcrRef>
                <BkTxCd>
                    <Domn>
                        <Cd>LDAS</Cd>
                        <Fmly>
                            <Cd>NTLN</Cd>
                            <SubFmlyCd>PPAY</SubFmlyCd>
                        </Fmly>
                    </Domn>
                </BkTxCd>
                <NtryDtls>
                    <TxDtls>
                        <Refs>
                            <AcctSvcrRef>201603311009353671-011413012</AcctSvcrRef>
                        </Refs>
                        <AmtDtls>
                            <InstdAmt>
                                <Amt Ccy="EUR">5.00</Amt>
                            </InstdAmt>
                            <TxAmt>
                                <Amt Ccy="EUR">5.00</Amt>
                            </TxAmt>
                        </AmtDtls>
                        <RltdPties>
                            <Dbtr>
                                <PstlAdr/>
                            </Dbtr>
                        </RltdPties>
                        <RltdAgts>
                            <DbtrAgt>
                                <FinInstnId/>
                            </DbtrAgt>
                        </RltdAgts>
                        <RmtInf/>
                    </TxDtls>
                </NtryDtls>
            </Ntry>
        </Ntfctn>
    </BkToCstmrDbtCdtNtfctn>
</Document>

Payment Initiation

POST Payment

POST https://connect.lhv.eu/payment

Customer to bank Payment Initiation (pain.001.001.03) covers SEPA and other payments at LHV Pank.
There are 3 methods to send payments via Connect:

1. Payment files are sent by plain XML. All sent payments are seen at Internet bank under Pending payments and payments can be signed (only) there. Internet Bank daily and monthly limits and acceptance rate is applied.
2. Payment files are sent by plain XML and processed without additional user actions or confirmations. Separate daily and monthly limits for Connect payments are followed. Virtual IBAN payments are possible only using this option. Also additional contract appendix must be signed to use this possibility.
3. Payment files are sent in BDOC container. Internet bank daily and monthly limits and acceptance rate is applied. If payment requires more than one signature, all signatures must be included in the BDOC container and limit usage is taken into account for the last signer.

Payment Status Report (pain.002.001.03) is returned to inform about the status of imported payments. More than one status may be returned for one payment.

Payment types and time limits

Payments initiated through LHV Connect are processed as:

• Estonian Branch - SEPA Instant (SCT Inst), SEPA or SWIFT.
• UK Branch - Faster Payments, Intra-Bank payment (payments to other LHV Bank accounts).

Routing decisions are done automatically based on the payment currency and the beneficiary:

Estonian Branch

• If payment currency is EUR and the receiving bank is a member of the RT1 clearing and settlement system for Instant payments - payment is sent as SEPA Instant. List of participants can be found here.
• If Instant payment cannot be processed for different reasons it is changed to SEPA. First you will receive payment initiation response with status ACWC and description "Payment processed as SEPA" in <AddtlInf> tag. Then additional response about the actual SEPA payment.
• For other EUR payments in the EAA (European Economic Area) - SEPA payment.
• Other payments not in EUR or where beneficiary bank is not in the EEA - Swift payment.
• If customer initial wish was to process payment as Instant/SEPA and it is not possible, then payment is processed as SWIFT (with priority high and fee type SHA).

UK Branch

• If payment currency is GBP and the receiving bank is a member of the Faster Payments Service clearing and settlement system - it is sent using Faster Payments. The upper limit of payment amount is 250000 GBP.
  There are different methods to submit the beneficiary account as IBAN or UK domestic account nr with sort code. Examples added below.
• For Intra-Bank payment also other currencies are available, beneficiary account must belong to LHV UK or Estonian branch.

See also: https://www.lhv.ee/en/payments and Payments_Instructions_and_Time_Limits-EN.pdf

XML format (ISO 20022 Payment Initiation Message pain.001.001.03)

Content-Type: application/xml

The ISO 20022 Payment Initiation Message pain.001.001.03 is a payment initiation standard that covers SEPA and other payments made at LHV Pank. The ISO 20022 format allows to include information that is not supported by LHV. That information is not processed by LHV.

pain.001.001.03 message xml schema file is available at www.iso20022.org.

XML rules

Multiplicity (MULT.) Informs how many times an element can or must be used, as defined by ISO standard.

1. 1..1 One occurrence (required)
2. 1..n One or several occurrences (value for “n” represents total number of occurrences)
3. 1..3 Minimum one occurrence must be used and maximum 3 occurrences can be used. Note: True value of “n” represents unlimited number of occurrences.
4. 0..1 None or one occurrence to be used (optional)
5. 0..n None or several occurrences can be used (value for “n” represents total number of occurrences). Note: True value of “n” represents unlimited number of occurrences.

BDOC

Content-Type: application/vnd.etsi.asic-e+zip

XML message has to be signed and the created BDOC has to be put into the body of the message. Whoever signed the document has to have adequate limits and rights for the execution of the payment. XML file needs to be named as "request.xml".

Message structure

Group Header – mandatory, occurs once.
Payment Information – mandatory and repetitive. Contains information related to mostly the debit side of the payment.
Credit Transfer Transaction Information – mandatory and repetitive. Contains information related to the payment(s) included in the message.

Message root

Group header

Payment information

Sample

Typical EUR payment - including two payments in single file

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03
pain.001.001.03.xsd">
<CstmrCdtTrfInitn>
    <GrpHdr>
        <MsgId>10</MsgId>
        <CreDtTm>2016-07-09T10:16:58.696</CreDtTm>
        <NbOfTxs>2</NbOfTxs>
        <CtrlSum>3</CtrlSum>
        <InitgPty>
            <Nm>Test Testija</Nm>
        </InitgPty>
    </GrpHdr>
    <PmtInf>
        <PmtInfId>PMT1</PmtInfId>
        <PmtMtd>TRF</PmtMtd>
        <BtchBookg>false</BtchBookg>
        <NbOfTxs>1</NbOfTxs>
        <ReqdExctnDt>2016-07-11</ReqdExctnDt>
        <Dbtr>
            <Nm>Silver Kullassepp</Nm>
        </Dbtr>
        <DbtrAcct>
            <Id>
                <IBAN>EE457700771000676899</IBAN>
            </Id>
            <Ccy>EUR</Ccy>
        </DbtrAcct>
        <DbtrAgt>
            <FinInstnId>
                <BIC>LHVBEE22</BIC>
            </FinInstnId>
        </DbtrAgt>
        <ChrgBr>SHAR</ChrgBr>
        <CdtTrfTxInf>
            <PmtId>
                <EndToEndId>124</EndToEndId>
            </PmtId>
            <PmtTpInf>
                <LclInstrm>
                    <Prtry>NORM</Prtry>
                </LclInstrm>
            </PmtTpInf>
            <Amt>
                <InstdAmt Ccy="EUR">1</InstdAmt>
            </Amt>
            <ChrgBr>SHAR</ChrgBr>
            <CdtrAgt>
                <FinInstnId>
                    <BIC>AACABE41XXX</BIC>
                </FinInstnId>
            </CdtrAgt>
            <Cdtr>
                <Nm>Cross Border</Nm>
                <PstlAdr>
                    <AdrLine>Somewhere, Belgium</AdrLine>
                </PstlAdr>
            </Cdtr>
            <CdtrAcct>
                <Id>
                    <IBAN>BE68539007547034</IBAN>
                </Id>
            </CdtrAcct>
            <RmtInf>
                <Ustrd>Cross border payment</Ustrd>
            </RmtInf>
        </CdtTrfTxInf>
    </PmtInf>
    <PmtInf>
        <PmtInfId>PMT2</PmtInfId>
        <PmtMtd>TRF</PmtMtd>
        <BtchBookg>false</BtchBookg>
        <NbOfTxs>1</NbOfTxs>
        <ReqdExctnDt>2016-07-09</ReqdExctnDt>
        <Dbtr>
            <Nm>Silver Kullassepp</Nm>
        </Dbtr>
        <DbtrAcct>
            <Id>
                <IBAN>EE457700771000676899</IBAN>
            </Id>
            <Ccy>EUR</Ccy>
        </DbtrAcct>
        <DbtrAgt>
            <FinInstnId>
                <BIC>LHVBEE22</BIC>
            </FinInstnId>
        </DbtrAgt>
        <ChrgBr>SLEV</ChrgBr>
        <CdtTrfTxInf>
            <PmtId>
                <EndToEndId>125</EndToEndId>
            </PmtId>
            <Amt>
                <InstdAmt Ccy="EUR">2</InstdAmt>
            </Amt>
            <Cdtr>
                <Nm>SEPA Pay</Nm>
            </Cdtr>
            <CdtrAcct>
                <Id>
                    <IBAN>EE707700771000678583</IBAN>
                </Id>
            </CdtrAcct>
            <RmtInf>
                <Ustrd>SEPA payments</Ustrd>
                <Strd>
                    <CdtrRefInf>
                        <Tp>
                            <CdOrPrtry>
                                <Cd>SCOR</Cd>
                            </CdOrPrtry>
                        </Tp>
                        <Ref>3120</Ref>
                    </CdtrRefInf>
                </Strd>
            </RmtInf>
        </CdtTrfTxInf>
    </PmtInf>
</CstmrCdtTrfInitn>
</Document>

UK Faster Payments - with beneficiary account as IBAN:

...
<CdtrAcct>
    <Id>
        <IBAN>GB29LHVB60161331921111</IBAN>
    </Id>
</CdtrAcct>
...

UK Faster Payments - with beneficiary account as UK sort code and domestic account number concatenated (CdtrAcct.Id.Othr.Id - 14 char):

...
<CdtrAcct>
    <Id>
        <Othr>
            <Id>12345612345678</Id>
            <SchmeNm>
                <Cd>BBAN</Cd>
            </SchmeNm>
        </Othr>
     </Id>
</CdtrAcct>
...

UK Faster Payments - with beneficiary account as UK Sort Code and domestic account number as separate values (CdtrAgt.FinInstnId.ClrSysMmbId.MmbId - 6 char + CdtrAcct.Id.Othr.Id - 8 char):

...
<CdtrAgt>
    <FinInstnId>
        <ClrSysMmbId>
            <ClrSysId>
                <Cd>GBDSC</Cd>
            </ClrSysId>
            <MmbId>123456</MmbId>
        </ClrSysMmbId>
    </FinInstnId>
</CdtrAgt>
...
<CdtrAcct>
    <Id>
        <Othr>
            <Id>12345678</Id>
        </Othr>
    </Id>
</CdtrAcct>
...

Response

XML format (ISO 20022 Customer Payment Status Report pain.002.001.03)

The ISO 20022 Customer Payment Status Report (pain.002.001.03) message is sent to the client to inform about the status of a payment instruction sent via LHV Connect with Payment Initiation (pain.001.001.03) message.

Customer Payment Status Report refers to the original Payment Initiation message and provides positive, negative and pending status updates to original payments.
There can be many Customer Payment Status Reports per one Payment Initiation message - typically if any of the transactions was not accepted right away for any reason.

Statuses are reported on group level for the whole payment instruction (GrpSts and PmtInfSts tags) and separately for each payment (TxSts tag).
Group level statuses are reported only in the first payments response message after the initial request.
Further responses (if any) shall not contain GrpSts and PmtInfSts tags - you must process the result of every payment entry separately.

Group level statuses (OrgnlGrpInfAndSts.GrpSts and OrgnlPmtInfAndSts.PmtInfSts):

• RJCT – all payments in original pain.001.001.03 Payment Information block have been rejected.
• PDNG - pending, payments are waiting for confirmation in Internet Bank.
• PART – if some of the payments in original pain.001.001.03 Payment Information block have reached one of the accepted statuses (ACSC, ACSP, ACWC), but some also rejected, then status is partially accepted.
• ACSP - all payments in original pain.001.001.03 have reached at least one of the accepted statuses (ACSC, ACSP, ACWC), but not debited yet
• ACSC - all payments in original pain.001.001.03 are debited from client’s account.

Single payment statuses (OrgnlPmtInfAndSts.TxInfAndSts.TxSts):

• RJCT – payment has been rejected (final status).
• PDNG - pending. Payment is waiting for confirmation in Internet Bank.
• ACSP – accepted, settlement in process. Payment is being processed by the bank, it has not been debited from client account nor sent to clearing system. At least one more status update must follow (either accept or reject).
• ACWC – accepted with change. Payment is being processed by the bank, it is not debited from client account. LHV has changed something about this payment. The reason for change is given in <AddtlInf> (3.25) tag. The changes are minor and do not harm the client’s intention. At least one more status is sent about this payment (either accept or reject).
• ACSC – accepted, settlement completed and payment has been debited from client account (final status).

Every day all payments sent 00:00 - 18:00 (Estonian time) and partially accepted will be rejected 18:00+5 minutes (if conditions are not met by this time).
All payments sent 18:00 – 00:00 (Estonian time) and partially accepted will be rejected 5 minutes after sending.

Message structure

Group Header – mandatory, occurs once. Set of characteristics shared by all individual payments included in the status report message.
Original Group Information And Status – occurs once. Refers to original Payment Initiation Group Level information.
Transaction Information And Status – optional and repetitive. Includes information about the original payment and its status.

Message root

Group header

Group level errors

Transaction level errors

Sample

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.03">
    <CstmrPmtStsRpt>
        <GrpHdr>
            <MsgId>10007152</MsgId>
            <CreDtTm>2016-07-06T12:08:38.571+03:00</CreDtTm>
            <InitgPty>
                <Id>
                    <OrgId>
                        <BICOrBEI>LHVBEE20XXX</BICOrBEI>
                    </OrgId>
                </Id>
            </InitgPty>
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <OrgnlMsgId>10</OrgnlMsgId>
            <OrgnlMsgNmId>pain.001.001.03</OrgnlMsgNmId>
            <GrpSts>ACSP</GrpSts>
        </OrgnlGrpInfAndSts>
        <OrgnlPmtInfAndSts>
            <OrgnlPmtInfId>PMT1</OrgnlPmtInfId>
            <PmtInfSts>ACSP</PmtInfSts>
            <TxInfAndSts>
                <OrgnlInstrId>4327</OrgnlInstrId>
                <TxSts>ACSP</TxSts>
                <OrgnlTxRef>
                    <Amt>
                        <InstdAmt Ccy="EUR">1.00</InstdAmt>
                    </Amt>
                    <ReqdExctnDt>2016-07-11</ReqdExctnDt>
                    <Dbtr>
                        <Nm>Silver Kullassepp</Nm>
                    </Dbtr>
                    <DbtrAcct>
                        <Id>
                            <IBAN>EE457700771000676899</IBAN>
                        </Id>
                    </DbtrAcct>
                    <DbtrAgt>
                        <FinInstnId>
                            <BIC>LHVBEE22</BIC>
                        </FinInstnId>
                    </DbtrAgt>
                    <CdtrAgt>
                        <FinInstnId>
                            <BIC>AACABE41XXX</BIC>
                        </FinInstnId>
                    </CdtrAgt>
                    <Cdtr>
                        <Nm>Murakas Välis</Nm>
                    </Cdtr>
                    <CdtrAcct>
                        <Id>
                            <IBAN>BE68539007547034</IBAN>
                        </Id>
                    </CdtrAcct>
                </OrgnlTxRef>
            </TxInfAndSts>
        </OrgnlPmtInfAndSts>
        <OrgnlPmtInfAndSts>
            <OrgnlPmtInfId>PMT2</OrgnlPmtInfId>
            <PmtInfSts>ACSP</PmtInfSts>
            <TxInfAndSts>
                <OrgnlInstrId>4328</OrgnlInstrId>
                <TxSts>ACSP</TxSts>
                <OrgnlTxRef>
                    <Amt>
                        <InstdAmt Ccy="EUR">2.00</InstdAmt>
                    </Amt>
                    <ReqdExctnDt>2016-07-09</ReqdExctnDt>
                    <Dbtr>
                        <Nm>Silver Kullassepp</Nm>
                    </Dbtr>
                    <DbtrAcct>
                        <Id>
                            <IBAN>EE457700771000676899</IBAN>
                        </Id>
                    </DbtrAcct>
                    <DbtrAgt>
                        <FinInstnId>
                            <BIC>LHVBEE22</BIC>
                        </FinInstnId>
                    </DbtrAgt>
                    <CdtrAgt>
                        <FinInstnId>
                            <BIC>LHVBEE22</BIC>
                        </FinInstnId>
                    </CdtrAgt>
                    <Cdtr>
                        <Nm>Murakas Välis</Nm>
                    </Cdtr>
                    <CdtrAcct>
                        <Id>
                            <IBAN>EE707700771000678583</IBAN>
                        </Id>
                    </CdtrAcct>
                </OrgnlTxRef>
            </TxInfAndSts>
        </OrgnlPmtInfAndSts>
    </CstmrPmtStsRpt>
</Document>

Virtual IBAN Services

Virtual IBAN Open

POST https://connect.lhv.eu/viban/open

Service is used to request new Virtual IBAN opening. Only one Virtual IBAN can be opened with one service request.
It is mandatory to fill in minimal data set about Virtual IBAN owner and request message structure is slightly different for private and legal persons.
After receiving the request, background check is done by LHV for Virtual IBAN owner (the check is done in less than a second).

• If check is OK, then Virtual IBAN is activated at once.
• If check is not OK, then Virtual IBAN will remain in status ON_HOLD until decision about Virtual IBAN opening is made. CONNECT customer will be informed about the decision (status ACTIVE or REJECTED) via service Status notification.

Request

• viban.open.request.xsd
• viban.common.xsd

Message structure

Sample

Private person

<?xml version="1.0" encoding="UTF-8"?>
<VibanOpenRequest>
  <MasterAccount>EE837700771001625166</MasterAccount>
  <User>
    <Person>
      <Name>Donald Duck</Name>
      <BirthDate>1908-11-29</BirthDate>
      <BirthCountry>DE</BirthCountry>
      <Residency>DE</Residency>
      <DocumentNumber>A942819</DocumentNumber>
    </Person>
    <Address>
      <Country>EE</Country>
      <StreetNo>Majaka 47-10</StreetNo>
      <CityCounty>Xiao, Neverland</CityCounty>
    </Address>
  </User>
</VibanOpenRequest>

Legal person

<?xml version="1.0" encoding="UTF-8"?>
<VibanOpenRequest>
  <MasterAccount>EE837700771001625166</MasterAccount>
  <User>
    <Company>
      <Name>UK Ltd Version 2.0</Name>
      <CountryOfOrigin>GB</CountryOfOrigin>
      <TaxResidency>GB</TaxResidency>
      <RegistrationNumber>1849203</RegistrationNumber>
      <Representative>
        <Name>Harry Potter</Name>
        <BirthDate>2001-01-01</BirthDate>
        <Residency>GB</Residency>
      </Representative>
    </Company>
    <Address>
      <Country>GB</Country>
      <StreetNo>Waterloo Bridge 13</StreetNo>
      <CityCounty>London, Cold</CityCounty>
    </Address>
  </User>
</VibanOpenRequest>

Response

• viban.open.response.xsd
• viban.common.xsd

Message structure

Sample

Private person

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<VibanOpenResponse>
    <MasterAccount>EE837700771001625166</MasterAccount>
    <VirtualIBAN>EE867777000202527783</VirtualIBAN>
    <User>
        <Person>
          <Name>Donald Duck</Name>
          <BirthDate>1908-11-29</BirthDate>
          <BirthCountry>DE</BirthCountry>
          <Residency>DE</Residency>
          <DocumentNumber>A942819</DocumentNumber>
        </Person>
        <Address>
            <Country>EE</Country>
            <StreetNo>Majaka 47-10</StreetNo>
            <CityCounty>Xiao, Neverland</CityCounty>
        </Address>
    </User>
    <Status>ACTIVE</Status>
</VibanOpenResponse>

Legal person

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<VibanOpenResponse>
    <MasterAccount>EE837700771001625166</MasterAccount>
    <VirtualIBAN>EE497777000202527770</VirtualIBAN>
    <User>
        <Company>
            <Name>UK Ltd Version 2.0</Name>
            <CountryOfOrigin>GB</CountryOfOrigin>
            <TaxResidency>GB</TaxResidency>
            <RegistrationNumber>1849203</RegistrationNumber>
            <Representative>
                <Name>Harry Potter</Name>
                <BirthDate>2001-01-01</BirthDate>
                <Residency>GB</Residency>
            </Representative>
        </Company>
        <Address>
            <Country>GB</Country>
            <StreetNo>Waterloo Bridge 13</StreetNo>
            <CityCounty>London, Cold</CityCounty>
        </Address>
    </User>
    <Status>ACTIVE</Status>
</VibanOpenResponse>

Virtual IBAN Bulk

POST https://connect.lhv.eu/viban/bulk

Service is used for bulk opening nameless Virtual IBANs. Up to 1000 virtual IBANs can be opened with one request.

Nameless virtual IBANs remain in "PENDING" status and can not be used for making payments until Virtual IBAN owner's personal details are added via service Virtual IBAN Modify.

Request

• viban.bulk.request.xsd

Message structure

Sample

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<VibanBulkRequest>
  <MasterAccount>EE737700771001625166</MasterAccount>
  <Amount>2</Amount>
</VibanBulkRequest>

Response

• viban.bulk.response.xsd

Message structure

Sample

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<VibanBulkResponse>
    <MasterAccount>EE737700771001625166</MasterAccount>
    <VirtualIBANList>
        <VirtualIBAN>EE717777000200014007</VirtualIBAN>
        <VirtualIBAN>EE507777000200014094</VirtualIBAN>
    </VirtualIBANList>
</VibanBulkResponse>

Virtual IBAN Modify

POST https://connect.lhv.eu/viban/modify
Service is used to add Virtual IBAN holder data to nameless Virtual IBANs. Please note, that it is not possible to change Virtual IBAN holder data via CONNECT services if Virtual IBAN is already in "ACTIVE" status.

Only one Virtual IBAN can be modified with one service request. It is mandatory to fill in minimal data set about Virtual IBAN owner and request message structure is slightly different for private and legal persons. After receiving the request, background check is done by LHV for Virtual IBAN owner.
If check is OK, then Virtual IBAN is activated at once.
If check is not OK, then Virtual IBAN will remain in status "ON_HOLD" until decision about Virtual IBAN opening is made. CONNECT customer will be informed about the decision via service Status notification.

Request

• viban.modify.request.xsd
• viban.common.xsd

Message structure

Sample

Private person

<?xml version="1.0" encoding="UTF-8"?>
<VibanModifyRequest>
  <MasterAccount>EE837700771001625166</MasterAccount>
  <VirtualIBAN>EE717777000200014007</VirtualIBAN>
  <User>
    <Person>
      <Name>Donald Duck</Name>
      <BirthDate>1908-11-29</BirthDate>
      <BirthCountry>DE</BirthCountry>
      <Residency>DE</Residency>
      <DocumentNumber>A942819</DocumentNumber>
    </Person>
    <Address>
      <Country>EE</Country>
      <StreetNo>Majaka 47-10</StreetNo>
      <CityCounty>Xiao, Neverland</CityCounty>
    </Address>
  </User>
</VibanModifyRequest>

Legal person

<?xml version="1.0" encoding="UTF-8"?>
<VibanModifyRequest>
  <MasterAccount>EE837700771001625166</MasterAccount>
  <VirtualIBAN>EE717777000200014007</VirtualIBAN>
  <User>
    <Company>
      <Name>UK Ltd Version 2.0</Name>
      <CountryOfOrigin>GB</CountryOfOrigin>
      <TaxResidency>GB</TaxResidency>
      <RegistrationNumber>1849203</RegistrationNumber>
      <Representative>
        <Name>Harry Potter</Name>
        <BirthDate>2001-01-01</BirthDate>
        <Residency>GB</Residency>
      </Representative>
    </Company>
    <Address>
      <Country>GB</Country>
      <StreetNo>Waterloo Bridge 13</StreetNo>
      <CityCounty>London, Cold</CityCounty>
    </Address>
  </User>
</VibanModifyRequest>

Response

• viban.modify.response.xsd
• viban.common.xsd

Message structure

Sample

Private person

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<VibanModifyResponse>
  <VirtualIBAN>EE717777000200014007</VirtualIBAN>
    <User>
        <Person>
          <Name>Donald Duck</Name>
          <BirthDate>1908-11-29</BirthDate>
          <BirthCountry>DE</BirthCountry>
          <Residency>DE</Residency>
          <DocumentNumber>A942819</DocumentNumber>
        </Person>
        <Address>
            <Country>EE</Country>
            <StreetNo>Majaka 47-10</StreetNo>
            <CityCounty>Xiao, Neverland</CityCounty>
        </Address>
    </User>
  <Status>ACTIVE</Status>
</VibanModifyResponse>

Legal person

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<VibanModifyResponse>
  <VirtualIBAN>EE717777000200014007</VirtualIBAN>
    <User>
        <Company>
            <Name>UK Ltd Version 2.0</Name>
            <CountryOfOrigin>GB</CountryOfOrigin>
            <TaxResidency>GB</TaxResidency>
            <RegistrationNumber>1849203</RegistrationNumber>
            <Representative>
                <Name>Harry Potter</Name>
                <BirthDate>2001-01-01</BirthDate>
                <Residency>GB</Residency>
            </Representative>
        </Company>
        <Address>
            <Country>GB</Country>
            <StreetNo>Waterloo Bridge 13</StreetNo>
            <CityCounty>London, Cold</CityCounty>
        </Address>
    </User>
  <Status>ACTIVE</Status>
</VibanModifyResponse>

Virtual IBAN Info

POST https://connect.lhv.eu/viban/info

Service is used to request Virtual IBAN data.
Response message structure is slightly different for private and legal persons.

Request

• viban.info.request.xsd
• viban.common.xsd

Message structure

Sample

<?xml version="1.0" encoding="UTF-8"?>
<VibanInfoRequest>
  <MasterAccount>EE837700771001625166</MasterAccount>
  <VirtualIBAN>EE717777000200014007</VirtualIBAN>
</VibanInfoRequest>

Response

• viban.info.response.xsd
• viban.common.xsd

Message structure

Sample

Private person

<?xml version="1.0" encoding="UTF-8"?>
<VibanInfoResponse>
  <VirtualIBAN>EE717777000200014007</VirtualIBAN>
  <User>
  	<Person>
  	  <Name>Donald Duck</Name>
  	  <BirthDate>1908-11-29</BirthDate>
  	  <BirthCountry>DE</BirthCountry>
  	  <Residency>DE</Residency>
  	  <DocumentNumber>A942819</DocumentNumber>
  	</Person>
  	<Address>
  		<Country>EE</Country>
  		<StreetNo>Majaka 47-10</StreetNo>
  		<CityCounty>Xiao, Neverland</CityCounty>
  	</Address>
  </User>
  <Status>ACTIVE</Status>
  <!--Optional:-->
  <DateActivated>2018-01-01+02:00</DateActivated>
  <!--Optional:-->
  <DateClosed>2018-05-22+03:00</DateClosed>
</VibanInfoResponse>

Legal person

<?xml version="1.0" encoding="UTF-8"?>
<VibanInfoResponse>
  <VirtualIBAN>EE717777000200014007</VirtualIBAN>
  <User>
  	<Company>
  		<Name>UK Ltd Version 2.0</Name>
  		<CountryOfOrigin>GB</CountryOfOrigin>
  		<TaxResidency>GB</TaxResidency>
  		<RegistrationNumber>1849203</RegistrationNumber>
  		<Representative>
  			<Name>Harry Potter</Name>
  			<BirthDate>2001-01-01</BirthDate>
  			<Residency>GB</Residency>
  		</Representative>
  	</Company>
  	<Address>
  		<Country>GB</Country>
  		<StreetNo>Waterloo Bridge 13</StreetNo>
  		<CityCounty>London, Cold</CityCounty>
  	</Address>
  </User>
  <Status>ACTIVE</Status>
  <!--Optional:-->
  <DateActivated>2018-01-01+02:00</DateActivated>
  <!--Optional:-->
  <DateClosed>2018-05-22+03:00</DateClosed>
</VibanInfoResponse>

Virtual IBAN Close

POST https://connect.lhv.eu/viban/close

Service is used to close Virtual IBAN.
Once Virtual IBAN is closed, it can not be activated again.
Payments to closed Virtual IBAN are accepted up to 30 days after closing date.

Request

• viban.close.request.xsd

Message structure

Sample

<?xml version="1.0" encoding="UTF-8"?>
<VibanCloseRequest>
  <MasterAccount>EE837700771001625166</MasterAccount>
  <VirtualIBAN>EE717777000200014007</VirtualIBAN>
</VibanCloseRequest>

Response

• viban.close.response.xsd

Message structure

Sample

<?xml version="1.0" encoding="UTF-8"?>
<VibanCloseResponse>
  <VirtualIBAN>EE717777000200014007</VirtualIBAN>
  <Status>CLOSED</Status>
  <DateClosed>2018-05-22+03:00</DateClosed>
</VibanCloseResponse>

Virtual IBAN Status Notification

Service is used to send information to CONNECT customers about Virtual IBAN status changes.

XSD

• viban.status.notification.xsd
• viban.common.xsd

Message structure

Sample

Private person

<?xml version="1.0" encoding="UTF-8"?>
<VibanStatusNotification>
  <MasterAccount>EE837700771001625166</MasterAccount>
  <VirtualIBAN>EE717777000200014007</VirtualIBAN>
  <User>
  	<Person>
  	  <Name>Donald Duck</Name>
  	  <BirthDate>1908-11-29</BirthDate>
  	  <BirthCountry>DE</BirthCountry>
  	  <Residency>DE</Residency>
  	  <DocumentNumber>A942819</DocumentNumber>
  	</Person>
  	<Address>
  		<Country>EE</Country>
  		<StreetNo>Majaka 47-10</StreetNo>
  		<CityCounty>Xiao, Neverland</CityCounty>
  	</Address>
  </User>
  <Status>ACTIVE</Status>
  <!--Optional:-->
  <DateActivated>2018-01-01+02:00</DateActivated>
  <!--Optional:-->
  <DateClosed>2018-05-22+03:00</DateClosed>
</VibanStatusNotification>

Legal person

<?xml version="1.0" encoding="UTF-8"?>
<VibanStatusNotification>
  <MasterAccount>EE837700771001625166</MasterAccount>
  <VirtualIBAN>EE717777000200014007</VirtualIBAN>
  <User>
  	<Company>
  		<Name>UK Ltd Version 2.0</Name>
  		<CountryOfOrigin>GB</CountryOfOrigin>
  		<TaxResidency>GB</TaxResidency>
  		<RegistrationNumber>1849203</RegistrationNumber>
  		<Representative>
  			<Name>Harry Potter</Name>
  			<BirthDate>2001-01-01</BirthDate>
  			<Residency>GB</Residency>
  		</Representative>
  	</Company>
  	<Address>
  		<Country>GB</Country>
  		<StreetNo>Waterloo Bridge 13</StreetNo>
  		<CityCounty>London, Cold</CityCounty>
  	</Address>
  </User>
  <Status>ACTIVE</Status>
  <!--Optional:-->
  <DateActivated>2018-01-01+02:00</DateActivated>
  <!--Optional:-->
  <DateClosed>2018-05-22+03:00</DateClosed>  
</VibanStatusNotification>

Appendix

Code Set: Balance

Code Set: Credit and debit code

Code Set: Bank transaction codes

Code Set: Purpose

Code Set: Private person identification

Code Set: Organisation identification

Code Set: Payment priority

If payment priority is not provided or faulty, default values will be used. For additional information see Payment processing time limits and settlements.

Code Set: Category purpose

Code Set: Charges bearer

If the payment priority is not provided or faulty, default values will be used. For additional information see Payment processing time limits and settlements.