1. Request for bank statement

Clients have the opportunity to receive the requested statement in two formats:

  • Final Statement [camt.053.001.05]

  • Interim statement [camt.052.001.05]

To receive a statement in camt.052.001.05 format from the client’s side, when requesting a statement, it will be necessary to send a new optional header: stmt_format = 'camt052', if it is specified, the statement is generated in camt.052.

If the header was not transferred or transferred, but stmt_format is not equal to 'camt052', then the statement will be generated in camt.053. Clients need to control the hit of the current date in the request period by themselves in order to receive a statement in the required format.

Important

Starting April 17th, 2024, there will be a limit on the maximum number of days specified in a bank statement for one request. The maximum number of days allowed will be 14.
To obtain a bank statement for a longer period, you will need to make several separate requests, each one covering a different time period.
The bank may change the maximum period of time at its discretion, without prior notification to customers.

Important

It is necessary to understand that the statement in the camt.053.001.05 format will be non-final (some operations in the statement may disappear or new ones may appear), if the current date falls within the request period. For example, statement in this format requested for today will be final only on the morning of the next day.

Request statement without signature

The possibility of requesting a statement without signing (Enhanced Qualified Electronic Signature (CCEP)) has been implemented. For this purpose it is necessary:

1) Pass parameters to Headers:

  • company-tin with the value TIN of the company

  • check-sign-message with the value false

2) <SgntrSt> leave empty.

3) To test integration it is recommended to use a test organization ООО «Тест Альфа-Линк без подписи».

URI

POST: /API/v1/ISO20022/Statements

XSD scheme

camt.060.001.03

Scheme description

Table 1. Headline (GrpHdr)
R/O Description Path Comment/Example

Absolute path Document.AcctRptgReq

1

R

Unique message ID

GrpHdr.MsgId

Statement request is made by virtue of identifier

2

R

Date and time the message was created

GrpHdr.CreDtTm

Date format
YYYY-MM-DDTHH:MM:SS

3

O

TIN of the company

GrpHdr.MsgSndr.Pty.Id.OrgId.Othr.Id

-

4

R

Unique package ID with request

RptgReq.Id

Statement request for each account number is required in a separate package

5

R

Get data by type Statement

RptgReq.ReqdMsgNmId

-

6

R

Account number

RptgReq.Acct.Id.Othr.Id

-

7

R

Period Start Date

RptgReq.RptgPrd.FrToDt.FrDt

-

8

R

Period End Date

RptgReq.RptgPrd.FrToDt.ToDt

-

9

R

Period Start Time

RptgReq.RptgPrd.FrToTm.FrTm

00:00:00

10

R

Period End Time

RptgReq.RptgPrd.FrToTm.ToTm

24:00:00

11

R

"Show all operations"

RptgReq.RptgPrd.Tp

Constant 'ALLL'

12

R

Name of the company

RptgReq.AcctOwnr.Pty.Nm

-

Signature Document.AcctRptgReq

13

O

Signature

SplmtryData.Envlp.SgntrSt[1..n]

-

ANSWER

HTTP code Type Body Description

200

OK

-

Statement request was accepted without errors.

400

Err

FrDt/ToDt is in the future

-

400

Err

Date period is not specified

-

400

Err

FrDt is later than ToDt

-

400

Err

MsgId is not unique

-

400

Err

XML does not match schema

-

400

Err

Duration period cannot exceed 14 days

-

401

Err

Wrong username or password

-

401

Err

User was not found

-

403

Err

User is disabled

-

500

Err

Warrant service error

-

403

Err

User does not have permission

-

406

Err

Signature is missing

-

403

Err

Certificate is not valid

-

403

Err

Signer’s warrant is expired

-

403

Err

Signer’s warrant is disabled

-

403

Err

Number of signatures is not enough for this operation type

-

403

Err

Certificate is disabled

-

403

Err

The signer certificate is not valid (revoked or not active)

-

406

Err

Signature value is not valid

-

406

Err

Internal sign check state error

-

502

Err

Bad Gateway

-

503

Err

Service Unavailable

-

504

Err

Gateway Timeout

-

500

Err

Internal Error

-

Statement request example
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.060.001.03" xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
    <AcctRptgReq>
        <GrpHdr>
            <MsgId>MsgId_Test_784817266</MsgId>
            <CreDtTm>2024-04-12T08:58:47.150</CreDtTm>
            <MsgSndr>
                <Pty>
                    <Id>
                        <OrgId>
                            <Othr>
                                <Id>7013602245</Id>
                            </Othr>
                        </OrgId>
                    </Id>
                </Pty>
            </MsgSndr>
        </GrpHdr>
        <RptgReq>
            <Id>Id_Test_784817266</Id>
            <ReqdMsgNmId>HMQSTASCF</ReqdMsgNmId>
            <Acct>
                <Id>
                    <Othr>
                        <Id>40702810200000000083</Id>
                    </Othr>
                </Id>
            </Acct>
            <AcctOwnr>
                <Pty>
                    <Nm>Общество с ограниченной ответственностью "Тест Альфа-Линк"</Nm>
                </Pty>
            </AcctOwnr>
            <RptgPrd>
                <FrToDt>
                    <FrDt>2024-04-05</FrDt>
                    <ToDt>2024-04-12</ToDt>
                </FrToDt>
                <FrToTm>
                    <FrTm>00:00:00</FrTm>
                    <ToTm>24:00:00</ToTm>
                </FrToTm>
                <Tp>ALLL</Tp>
            </RptgPrd>
        </RptgReq>
        <SplmtryData>
            <Envlp>
                <SgntrSt>
                </SgntrSt>
            </Envlp>
        </SplmtryData>
    </AcctRptgReq>
</Document>