Main Use cases

The API allows to:

send a package of unsigned domestic payments (hereinafter a Mass payment) to the bank in the pain.001.001 format
request for the status of the Mass payment in the format pain.002.001
request for the status of a each payment as part of the Mass payment in the pain.002.001 format
request the processing status of the Mass payment and each payment within it you in the pain.002.001 format

Sending an unsigned Mass payment to the bank

To send an unsigned Mass payment to the bank, you should:

get AccessToken
generate an xml file in the Pain.001.001 format containing domestic payments (see the format specification on the page Import format in the file Raiffeisen_API_isoxml_unsigned)
send a POST request message to the /iso20022 address, issuing the generated xml file in the body of the request
receive a synchronous response with message receipt status

An example of Pain.001.001 message

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.raif">
   <CstmrCdtTrfInitn>
		<GrpHdr>
			<MsgId>E0R3D6675cf54fb4b19d20443b21b389</MsgId>
			<CreDtTm>2022-12-31T04:24:38Z</CreDtTm>
			<NbOfTxs>2</NbOfTxs>
			<CtrlSum>10.53</CtrlSum>
			<InitgPty>
				<Nm>ООО Тестовая компания 888 КОРП</Nm>
				<Id>
					<OrgId>
						<Othr>
							<Id>111111111888</Id>
							<SchmeNm>
								<Cd>TXID</Cd>
							</SchmeNm>
						</Othr>
					</OrgId>
				</Id>
			</InitgPty>
		</GrpHdr>
		<PmtInf>
			<PmtInfId>4093D6675cf54fb4b19d20443b21b389</PmtInfId>
			<PmtMtd>TRF</PmtMtd>
			<Dbtr>
				<Nm>ООО Тестовая компания 888 КОРП</Nm>
				<Id>
					<OrgId>
						<Othr>
							<Id>111111111888</Id>
							<SchmeNm>
								<Cd>TXID</Cd>
							</SchmeNm>
						</Othr>
					</OrgId>
				</Id>
			</Dbtr>
			<DbtrAcct>
				<Id>
					<Othr>
						<Id>40702810900000000556</Id>
						<SchmeNm>
							<Cd>BBAN</Cd>
						</SchmeNm>
					</Othr>
				</Id>
				<Ccy>RUB</Ccy>
			</DbtrAcct>
			<DbtrAgt>
				<FinInstnId>
					<ClrSysMmbId>
						<ClrSysId>
							<Cd>RUCBC</Cd>
						</ClrSysId>
						<MmbId>044525700</MmbId>
					</ClrSysMmbId>
					<Nm>ЮЖНЫЙ ФИЛИАЛ АО “РАЙФФАЙЗЕНБАНК“</Nm>
				</FinInstnId>
			</DbtrAgt>
			<DbtrAgtAcct>
				<Id>
					<Othr>
						<Id>30101810900000000556</Id>
						<SchmeNm>
							<Cd>BBAN</Cd>
						</SchmeNm>
					</Othr>
				</Id>
				<Ccy>RUB</Ccy>
			</DbtrAgtAcct>
			<CdtTrfTxInf>
				<PmtId>
					<InstrId>61V3D6675cf54fb4b19d20443b21b561</InstrId>
					<EndToEndId>16</EndToEndId>
				</PmtId>
				<PmtTpInf>
					<SvcLvl>
						<Cd>NURG</Cd>
					</SvcLvl>
					<LclInstrm>
						<Prtry>01</Prtry>
					</LclInstrm>
				</PmtTpInf>
				<Amt>
					<InstdAmt Ccy="RUB">10.53</InstdAmt>
				</Amt>
				<CdtrAgt>
					<FinInstnId>
						<ClrSysMmbId>
							<ClrSysId>
								<Cd>RUCBC</Cd>
							</ClrSysId>
							<MmbId>044525700</MmbId>
						</ClrSysMmbId>
						<Nm>АО "РАЙФФАЙЗЕНБАНК"</Nm>
					</FinInstnId>
				</CdtrAgt>
				<CdtrAgtAcct>
					<Id>
						<Othr>
							<Id>30101810200000000700</Id>
							<SchmeNm>
								<Cd>BBAN</Cd>
							</SchmeNm>
						</Othr>
					</Id>
					<Ccy>RUB</Ccy>
				</CdtrAgtAcct>
				<Cdtr>
					<Nm>Ритейл Проперти 5 ООО</Nm>
					<Id>
						<OrgId>
							<Othr>
								<Id>7743876305</Id>
								<SchmeNm>
									<Cd>TXID</Cd>
								</SchmeNm>
							</Othr>
						</OrgId>
					</Id>
				</Cdtr>
				<CdtrAcct>
					<Id>
						<Othr>							<Id>40702810600001460598</Id>
							<SchmeNm>
								<Cd>BBAN</Cd>
							</SchmeNm>
						</Othr>
					</Id>
					<Ccy>RUB</Ccy>
				</CdtrAcct>
				<Purp>
					<Prtry>5</Prtry>
				</Purp>
				<Tax>
					<Cdtr>
						<TaxTp>773001001</TaxTp>
					</Cdtr>
					<Dbtr>
						<TaxTp>773101001</TaxTp>
					</Dbtr>
					<Rcrd>
						<TaxAmt>
							<Rate>20</Rate>
							<TtlAmt Ccy="RUB">9.09</TtlAmt>
						</TaxAmt>
						<AddtlInf>VTIN</AddtlInf>
					</Rcrd>
				</Tax>
				<RmtInf>
					<Ustrd>62487/7701 26221050 Прочее 05/2022</Ustrd>
					<Strd>
						<RfrdDocInf>
							<RltdDt>2022-12-31</RltdDt>
						</RfrdDocInf>
					</Strd>
				</RmtInf>
			</CdtTrfTxInf>
		</PmtInf>
		<PmtInf>
			<PmtInfId>85R3D6675cf54fb4b19d20443b21b389</PmtInfId>
			<PmtMtd>TRF</PmtMtd>
			<Dbtr>
				<Nm>ООО Тестовая компания 888 КОРП</Nm>
				<Id>
					<OrgId>
						<Othr>
							<Id>111111111888</Id>
							<SchmeNm>
								<Cd>TXID</Cd>
							</SchmeNm>
						</Othr>
					</OrgId>
				</Id>
			</Dbtr>
			<DbtrAcct>
				<Id>
					<Othr>
						<Id>40702810211111888888</Id>
						<SchmeNm>
							<Cd>BBAN</Cd>
						</SchmeNm>
					</Othr>
				</Id>
				<Ccy>RUB</Ccy>
			</DbtrAcct>
			<DbtrAgt>
				<FinInstnId>
					<ClrSysMmbId>
						<ClrSysId>
							<Cd>RUCBC</Cd>
						</ClrSysId>
						<MmbId>044525700</MmbId>
					</ClrSysMmbId>
					<Nm>ЮЖНЫЙ ФИЛИАЛ АО “РАЙФФАЙЗЕНБАНК“</Nm>
				</FinInstnId>
			</DbtrAgt>
			<DbtrAgtAcct>
				<Id>
					<Othr>
						<Id>30101810900000000556</Id>
						<SchmeNm>
							<Cd>BBAN</Cd>
						</SchmeNm>
					</Othr>
				</Id>
				<Ccy>RUB</Ccy>
			</DbtrAgtAcct>
			<CdtTrfTxInf>
				<PmtId>
					<InstrId>55C3D6675cf54fb4b19d20443b21b389</InstrId>
					<EndToEndId>82</EndToEndId>
				</PmtId>
				<PmtTpInf>
					<SvcLvl>
						<Cd>NURG</Cd>
					</SvcLvl>
					<LclInstrm>
						<Prtry>01</Prtry>
					</LclInstrm>
					<CtgyPurp>
						<Cd>TAXS</Cd>
					</CtgyPurp>
				</PmtTpInf>
				<Amt>
					<InstdAmt Ccy="RUB">30.23</InstdAmt>
				</Amt>
				<CdtrAgt>
					<FinInstnId>
						<ClrSysMmbId>
							<ClrSysId>
								<Cd>RUCBC</Cd>
							</ClrSysId>
							<MmbId>007182108</MmbId>
						</ClrSysMmbId>
						<Nm>СЕВЕРО-ЗАПАДНОЕ ГУ БАНКА РОССИИ//УФК ПО Г.САНКТ-ПЕТЕРБУРГУ Г САНКТ-ПЕТЕРБУРГ</Nm>
					</FinInstnId>
				</CdtrAgt>
				<CdtrAgtAcct>
					<Id>
						<Othr>							<Id>03100643123231412341</Id>
							<SchmeNm>
								<Cd>BBAN</Cd>
							</SchmeNm>
						</Othr>
					</Id>
					<Ccy>RUB</Ccy>
				</CdtrAgtAcct>
				<Cdtr>
					<Nm>УФК ПО ЯМАЛО-НЕНЕЦКОМУ АВТОНОМНОМУ ОКРУГУ</Nm>
					<Id>
						<OrgId>
							<Othr>
								<Id>2308024329</Id>
								<SchmeNm>
									<Cd>TXID</Cd>
								</SchmeNm>
							</Othr>
						</OrgId>
					</Id>
				</Cdtr>
				<CdtrAcct>
					<Id>
						<Othr>
							<Id>03100643000000017200</Id>
							<SchmeNm>
								<Cd>BBAN</Cd>
							</SchmeNm>
						</Othr>
					</Id>
					<Ccy>RUB</Ccy>
				</CdtrAcct>
				<Purp>
					<Prtry>5</Prtry>
				</Purp>
				<Tax>
					<Cdtr>
						<TaxTp>783801001</TaxTp>
					</Cdtr>
					<Dbtr>
						<TaxTp>783901001</TaxTp>
					</Dbtr>
					<AdmstnZone>40303000</AdmstnZone>
					<Rcrd>
						<Ctgy>ТД</Ctgy>
						<CtgyDtls>18210101012021000110</CtgyDtls>
						<DbtrSts>02</DbtrSts>
						<Prd>
							<Yr>2022</Yr>
							<Tp>MM02</Tp>
						</Prd>
						<AddtlInf>VTNA</AddtlInf>
					</Rcrd>
				</Tax>
				<RmtInf>
					<Ustrd>НАЛОГ НА ДОХОДЫ ФИЗИЧЕСКИХ ЛИЦ</Ustrd>
					<Strd>
						<RfrdDocInf>
							<RltdDt>2022-12-31</RltdDt>
						</RfrdDocInf>
						<CdtrRefInf>
							<Ref>0</Ref>
						</CdtrRefInf>
					</Strd>
				</RmtInf>
			</CdtTrfTxInf>
		</PmtInf>
	</CstmrCdtTrfInitn>
</Document>

After POST request execution the bank synchronously returns response with the message receipt status.

Response codes

Rest code	Message receipt status	Reason description ENG	Reason description RUS
200	Created	The message successfully is accepted by the bank	Cообщение успешно принято банком
400	Bad request	XML validation error	Ошибка валидации XML
401	Unauthorized	Authorization error	Ошибка авторизации
403	Forbidden	An access is denied	Доступ к запрошенному ресурсу запрещен
413	Payload too large	Size of the file exceeds the limit	Размер файла превышает допустимый
500	Internal Server Error	An unexpected error has occurred (server unavailablity, etc.)	Произошла непредвиденная ошибка (недоступность сервера и т.д.)

The message receipt status in Pain.002.001 format is returned by the bank additionally to the standard REST codes. It’s published in the body of the response message as well as an additional text description of the error.

In Pain.002.001 format response there are two possible statuses:

PDNG - message has received by the bank
RJCT - message has rejected by the bank

Example of a response when the message is successfully accepted by the bank (code 200+ISO PDNG )

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.12">
    <CstmrPmtStsRpt>
        <GrpHdr>
            <MsgId>087845946c5f490bad0d8ec19059357c</MsgId>
            <CreDtTm>2022-12-54T16:24:34.966268+03:00</CreDtTm>
            <InitgPty>
                <Nm>АО Райффайзенбанк</Nm>
                <PstlAdr>
                    <Ctry>RU</Ctry>
                </PstlAdr>
            </InitgPty>
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <OrgnlMsgId>E0R3D6675cf54fb4b19d20443b21b389</OrgnlMsgId>
            <OrgnlMsgNmId>pain.001.001.raif</OrgnlMsgNmId>
            <OrgnlCreDtTm>2022-12-31T04:24:38Z</OrgnlCreDtTm>
            <OrgnlNbOfTxs>2</OrgnlNbOfTxs>
            <OrgnlCtrlSum>10.53</OrgnlCtrlSum>
            <GrpSts>PDNG</GrpSts>
        </OrgnlGrpInfAndSts>
    </CstmrPmtStsRpt>
</Document>

The message may not be accepted (code ISO=RJCT) in the following cases:

an authentication on the API Portal was not successful
an authorization in the CIB Ruble payments service was not successful:
- the user who initiates the request is not a user of the company on behalf of which the message is initiated
- the user who initiates the request does not have enough rights and permissions to execute this request
- the company does not have contracts that allow the use of this service
the xml file in the body of request does not match to the xsd scheme

Example of a response when the message is rejected by the bank (code 400+ ISO code RJCT)

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.12">
    <CstmrPmtStsRpt>
        <GrpHdr>
            <MsgId>e61f35da3d2e41889f3ebbecf8dc7ffe</MsgId>
            <CreDtTm>2023-06-19T07:55:23.147Z</CreDtTm>
            <InitgPty>
                <Nm>АО Райффайзенбанк</Nm>
                <PstlAdr>
                    <Ctry>RU</Ctry>
                </PstlAdr>
            </InitgPty>
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <OrgnlMsgNmId>pain.001.001.raif</OrgnlMsgNmId>
            <GrpSts>RJCT</GrpSts>
            <StsRsnInf>
                <AddtlInf>Schema validation error</AddtlInf>
                <AddtlInf>FATAL_ERROR: cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pain.001.001.raif":Sc</AddtlInf>
                <AddtlInf>hmeNm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pain.001.001.raif":Id}' is expected.</AddtlInf>
                <AddtlInf>line: 14; column: 8; </AddtlInf>
            </StsRsnInf>
        </OrgnlGrpInfAndSts>
    </CstmrPmtStsRpt>
</Document>

Detailed information about an error is sent in the AddtLInf tag of the response message by the following way:

<AddtlInf> Schema validation error </AddtlInf> - a general reason of message reject by the bank
<AddtlInf>FATAL_ERROR: cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pain.001.001.raif":Sc</AddtlInf> <AddtlInf>hmeNm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pain.001.001.raif":Id}' is expected.</AddtlInf> - detailed text description of an error
<AddtlInf> line: 1; column: 808; </AddtlInf> - the closing tag location within a file, where the error presented

The Schema validation error returns on the first error was found, thus only this error details will be reflected in the response message.

Example of a response when the message is rejected by the bank (code 401+ ISO code RJCT)

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.12">
    <CstmrPmtStsRpt>
        <GrpHdr>
            <MsgId>1b9b021c6e7c48d6abff17b5757f58eb</MsgId>
            <CreDtTm>2023-02-28T18:44:17.532542+03:00</CreDtTm>
            <InitgPty>
                <Nm>АО Райффайзенбанк</Nm>
                <PstlAdr>
                    <Ctry>RU</Ctry>
                </PstlAdr>
            </InitgPty>
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <OrgnlMsgNmId>pain.001.001.raif</OrgnlMsgNmId>
            <GrpSts>RJCT</GrpSts>
            <StsRsnInf>
                <AddtlInf>Authorization error</AddtlInf>
            </StsRsnInf>
        </OrgnlGrpInfAndSts>
    </CstmrPmtStsRpt>
</Document>

If the service is unavailable, only the code = 500 will be sent in the response

Mass payment status and payment status request

You can request the following payment processing statuses:

The Mass payment status
The Mass payment status and statuses of all payments within the Mass Payment
The status of a certain payment sent within the Mass payment

Mass payment status request

To request the Mass payment processing status you need to:

get AccessToken
send a GET request to the address /iso20022/message/{msgId}/status, where msgId is the message ID from original message you send to the bank
receive a synchronous response with the message receipt status

Mass payment statuses:

ISO CODE	STATUS	COMMENTS
RJCT	REJECTED	All payments within Mass payment were rejected by the bank
PDNG	PENDING	In queue for business validation
ACWC	DRAFT	Payment or some payments within Mass payment have errors under business validation and should be corrected
ACCP	IMPORTED or READY FOR SIGNING	Mass payment has no errors and it’s ready for signing
PSGN	NEEDS OTHER SIGNATURES	Needs other signature
FSGN	READY FOR SENDING	Ready to sending for processing
ACSP	PROCESSING	Payments within the Mass payment are processing by the bank
ATTN	NEEDS ATTENTION	Payment or some payments within the Mass payment need an attention (for example a lack of funds on an account to process the payment)
PART	PARTIALLY DONE	Not all payments within the Mass payment were executed
ACSC	DONE	All payments within the Mass payments were executed
DELT	DELETED	Mass payment was deleted by the client
NPMT	PAYMENT ID NOT FOUND	Mass payment with this ID was not found, please check the ID
DBLC	DUPLICATE	Mass payment was not created because it is a duplicate

Format of the pain002.001 message containing the Mass payment status

You can learn more about the message format in the section Import format in the file Raiffeisen_pain002001_payments_status. Please pay an attention single or some of payments can be removed or deleted from the Mass Payment via interface by the e-banking system user. Therefore, in the response we provide both Mass payment status and current state of the Mass payment:

the number of payments within the Mass payment at the time of the status request;
the total amount of payments within the Mass payment at the time of the status request.

Examples of message with Mass payment status

ISO Code - ACWC, Status - DRAFT

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.12">
    <CstmrPmtStsRpt>
        <GrpHdr>
            <MsgId>2f4d47d98a9449a5848b06d714037b80</MsgId>
            <CreDtTm>2023-02-16T13:47:54.235936Z</CreDtTm>
            <InitgPty>
                <Nm>АО Райффайзенбанк</Nm>
                <PstlAdr>
                    <Ctry>RU</Ctry>
                </PstlAdr>
            </InitgPty>
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <OrgnlMsgId>0000807015</OrgnlMsgId>
            <OrgnlMsgNmId>pain.001.001.raif</OrgnlMsgNmId>
            <OrgnlCreDtTm>2023-02-16T10:47:49Z</OrgnlCreDtTm>
            <GrpSts>PDNG</GrpSts>
            <NbOfTxsPerSts>
                <DtldNbOfTxs>1</DtldNbOfTxs>
                <DtldSts>ACWC</DtldSts>
                <DtldCtrlSum>980.00</DtldCtrlSum>
            </NbOfTxsPerSts>
        </OrgnlGrpInfAndSts>
        <OrgnlPmtInfAndSts>
            <TxInfAndSts>
                <StsRsnInf>
                    <AddtlInf>DRAFT</AddtlInf>
                </StsRsnInf>
            </TxInfAndSts>
        </OrgnlPmtInfAndSts>
    </CstmrPmtStsRpt>
</Document>

ISO Code - PSGN, Status - NEEDS OTHER SIGNATURES

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.12">
    <CstmrPmtStsRpt>
        <GrpHdr>
            <MsgId>e6e76fddc125477b89714d7d51620965</MsgId>
            <CreDtTm>2023-02-16T13:56:27.968372Z</CreDtTm>
            <InitgPty>
                <Nm>АО Райффайзенбанк</Nm>
                <PstlAdr>
                    <Ctry>RU</Ctry>
                </PstlAdr>
            </InitgPty>
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <OrgnlMsgId>005056B610B91REDA8DEE73161AF3BB5</OrgnlMsgId>
            <OrgnlMsgNmId>pain.001.001.raif</OrgnlMsgNmId>
            <OrgnlCreDtTm>2023-02-14T04:24:38Z</OrgnlCreDtTm>
            <GrpSts>PDNG</GrpSts>
            <NbOfTxsPerSts>
                <DtldNbOfTxs>1</DtldNbOfTxs>
                <DtldSts>PSGN</DtldSts>
                <DtldCtrlSum>30.23</DtldCtrlSum>
            </NbOfTxsPerSts>
        </OrgnlGrpInfAndSts>
        <OrgnlPmtInfAndSts>
            <TxInfAndSts>
                <StsRsnInf>
                    <AddtlInf>NEEDS OTHER SIGNATURES</AddtlInf>
                </StsRsnInf>
            </TxInfAndSts>
        </OrgnlPmtInfAndSts>
    </CstmrPmtStsRpt>
</Document>

ISO Code - NMPT, Status - PAYMENT ID NOT FOUND

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.12">
    <CstmrPmtStsRpt>
        <GrpHdr>
            <MsgId>7d534186414d45d7a8bc56d1343f8eda</MsgId>
            <CreDtTm>2024-07-03T12:21:33.846Z</CreDtTm>
            <InitgPty>
                <Nm>АО Райффайзенбанк</Nm>
                <PstlAdr>
                    <Ctry>RU</Ctry>
                </PstlAdr>
            </InitgPty>
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <OrgnlMsgId>8ffebe938878454fa549aeef980f7af2</OrgnlMsgId>
            <OrgnlMsgNmId>pain.001.001.raif</OrgnlMsgNmId>
            <GrpSts>NPMT</GrpSts>
            <StsRsnInf>
                <AddtlInf>PAYMENT ID NOT FOUND</AddtlInf>
                <AddtlInf>Mass payment with MsgId 8ffebe938878454fa549aeef980f7af2 was not found</AddtlInf>
            </StsRsnInf>
        </OrgnlGrpInfAndSts>
    </CstmrPmtStsRpt>
</Document>

Request the status of a Mass Payment, including the statuses of each payment within the Mass Payment

To request the processing status of the Mass payment and each payment within it you need to:

get AccessToken
send a GET request to the address /iso20022/message/{msgId}/status/full, where msgId is the message ID from original message you send to the bank
receive a synchronous response with the message receipt status

We provide the Mass payment status, current state of the Mass payment and each payment processing status in the response:

the number of payments within the Mass payment at the time of the status request
the total amount of payments within the Mass payment at the time of the status request
the current processing status of each payment in the Mass Payment

Mass payment statuses:

ISO CODE	STATUS	COMMENTS
RJCT	REJECTED	All payments within Mass payment were rejected by the bank
PDNG	PENDING	In queue for business validation
ACWC	DRAFT	Payment or some payments within Mass payment have errors under business validation and should be corrected
ACCP	IMPORTED or READY FOR SIGNING	Mass payment has no errors and it’s ready for signing
PSGN	NEEDS OTHER SIGNATURES	Needs other signature
FSGN	READY FOR SENDING	Ready to sending for processing
ACSP	PROCESSING	Payments within the Mass payment are processing by the bank
ATTN	NEEDS ATTENTION	Payment or some payments within the Mass payment need an attention (for example a lack of funds on an account to process the payment)
PART	PARTIALLY DONE	Not all payments within the Mass payment were executed
ACSC	DONE	All payments within the Mass payments were executed
DELT	DELETED	Mass payment was deleted by the client
NPMT	PAYMENT ID NOT FOUND	Mass payment with this ID was not found, please check the ID
DBLC	DUPLICATE	Mass payment was not created because it is a duplicate

Payment statuses:

ISO CODE	STATUS	COMMENTS
RJCT	REJECTED	Payment was rejected by the bank
PDNG	PENDING	In queue for business validation
ACWC	DRAFT	Payment has errors under business validation and should be corrected
ACCP	IMPORTED or READY FOR SIGNING	Payment has no errors and it’s ready for signing
PSGN	NEEDS OTHER SIGNATURES	Needs additional signature
FSGN	READY FOR SENDING	Ready to sending for processing
ACSP	PROCESSING	Payment is processing by the bank
ATTN	NEEDS ATTENTION	Payment needs an attention (for example a lack of funds on an account to process the payment)
CANC	REVOKED	Payment was revoked by the client
ACSC	DONE	Payment was executed
DELT	DELETED	Payment was deleted by the client
NPMT	PAYMENT ID NOT FOUND	Payment with ID was not found, please check the ID
DBLC	DUPLICATE	Payment was not created because it is a duplicate

Format of the pain002.001 message containing the Payment status

You can learn more about the message format in the section Import format in the file Raiffeisen_pain002001_payments_status.

Examples of message with Mass payment status

ISO Code - PART, Status - PARTIALLY DONE due to in the Mass Payment three payments of five were executed, the rest were rejected

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.12">
    <CstmrPmtStsRpt>
        <GrpHdr>
            <MsgId>7500032fd7fd4cc09867798f38fd70e4</MsgId>
            <CreDtTm>2024-06-24T09:28:15.110Z</CreDtTm>
            <InitgPty>
                <Nm>АО Райффайзенбанк</Nm>
                <PstlAdr>
                    <Ctry>RU</Ctry>
                </PstlAdr>
            </InitgPty>
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <OrgnlMsgId>1184946705</OrgnlMsgId>
            <OrgnlMsgNmId>pain.001.001.raif</OrgnlMsgNmId>
            <OrgnlCreDtTm>2024-03-07T13:28:49.000Z</OrgnlCreDtTm>
            <OrgnlNbOfTxs>5</OrgnlNbOfTxs>
            <OrgnlCtrlSum>9000.99</OrgnlCtrlSum>
            <GrpSts>PDNG</GrpSts>
            <NbOfTxsPerSts>
                <DtldNbOfTxs>5</DtldNbOfTxs>
                <DtldSts>PART</DtldSts>
                <DtldCtrlSum>9000.99</DtldCtrlSum>
            </NbOfTxsPerSts>
        </OrgnlGrpInfAndSts>
        <OrgnlPmtInfAndSts>
            <OrgnlPmtInfId>1154694812</OrgnlPmtInfId>
            <PmtInfSts>ACSC</PmtInfSts>
        </OrgnlPmtInfAndSts>
        <OrgnlPmtInfAndSts>
            <OrgnlPmtInfId>1163926138</OrgnlPmtInfId>
            <PmtInfSts>ACSC</PmtInfSts>
        </OrgnlPmtInfAndSts>
        <OrgnlPmtInfAndSts>
            <OrgnlPmtInfId>1054259923</OrgnlPmtInfId>
            <PmtInfSts>ACSC</PmtInfSts>
        </OrgnlPmtInfAndSts>
        <OrgnlPmtInfAndSts>
            <OrgnlPmtInfId>1162364846</OrgnlPmtInfId>
            <PmtInfSts>RJCT</PmtInfSts>
        </OrgnlPmtInfAndSts>
        <OrgnlPmtInfAndSts>
            <OrgnlPmtInfId>1108107023</OrgnlPmtInfId>
            <PmtInfSts>RJCT</PmtInfSts>
        </OrgnlPmtInfAndSts>
	 </CstmrPmtStsRpt>
</Document>

Status Request for payment sent within the Mass payment

To request the payment processing status you need to:

get AccessToken
send a GET request message to the /iso20022/message/{msgId}/payment/{PmtInfId}/status address, where msgId is the message ID from original message you send to the bank, and PmtInfId is payment ID
receive a synchronous response with message receipt status

Payment statuses:

ISO CODE	STATUS	COMMENTS
RJCT	REJECTED	Payment was rejected by the bank
PDNG	PENDING	In queue for business validation
ACWC	DRAFT	Payment has errors under business validation and should be corrected
ACCP	IMPORTED or READY FOR SIGNING	Payment has no errors and it’s ready for signing
PSGN	NEEDS OTHER SIGNATURES	Needs additional signature
FSGN	READY FOR SENDING	Ready to sending for processing
ACSP	PROCESSING	Payment is processing by the bank
ATTN	NEEDS ATTENTION	Payment needs an attention (for example a lack of funds on an account to process the payment)
CANC	REVOKED	Payment was revoked by the client
ACSC	DONE	Payment was executed
DELT	DELETED	Payment was deleted by the client
NPMT	PAYMENT ID NOT FOUND	Payment with ID was not found, please check the ID
DBLC	DUPLICATE	Payment was not created because it is a duplicate

Format of the pain002.001 message containing the Payment status

You can learn more about the message format in the section Import format in the file Raiffeisen_pain002001_payments_status.

Examples of message with payment status

ISO Code - ACCP, Status - READY FOR SIGNING

 <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.12">
    <CstmrPmtStsRpt>
        <GrpHdr>
            <MsgId>e01e9f19efb146798d9eec092d33e2b1</MsgId>
            <CreDtTm>2024-07-09T12:00:49.801Z</CreDtTm>
            <InitgPty>
                <Nm>АО Райффайзенбанк</Nm>
                <PstlAdr>
                    <Ctry>RU</Ctry>
                </PstlAdr>
            </InitgPty>
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <OrgnlMsgId>ORCR111UWIRE032012317717602</OrgnlMsgId>
            <OrgnlMsgNmId>pain.001.001.raif</OrgnlMsgNmId>
            <OrgnlCreDtTm>2024-07-03T05:54:55.000Z</OrgnlCreDtTm>
        </OrgnlGrpInfAndSts>
        <OrgnlPmtInfAndSts>
            <OrgnlPmtInfId>ORCRUWIRE0220202317717604</OrgnlPmtInfId>
            <PmtInfSts>ACCP</PmtInfSts>
            <TxInfAndSts>
                <OrgnlInstrId>HMSRUEFT7841913</OrgnlInstrId>
                <OrgnlEndToEndId>4</OrgnlEndToEndId>
                <TxSts>ACCP</TxSts>
                <StsRsnInf>
                    <AddtlInf>READY FOR SIGNING</AddtlInf>
                    <AddtlInf>Предупреждение: ИНН/КИО плательщика не прошел проверку контрольных чисел
</AddtlInf>
                </StsRsnInf>
            </TxInfAndSts>
        </OrgnlPmtInfAndSts>
    </CstmrPmtStsRpt>
</Document>

ISO Code - ACWC, Status - DRAFT

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.12">
    <CstmrPmtStsRpt>
        <GrpHdr>
            <MsgId>9968b942b9dc4a72abf1b36e683e4a65</MsgId>
            <CreDtTm>2024-07-09T12:09:27.839Z</CreDtTm>
            <InitgPty>
                <Nm>АО Райффайзенбанк</Nm>
                <PstlAdr>
                    <Ctry>RU</Ctry>
                </PstlAdr>
            </InitgPty>
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <OrgnlMsgId>ORCR111UWIRE032012317717602</OrgnlMsgId>
            <OrgnlMsgNmId>pain.001.001.raif</OrgnlMsgNmId>
            <OrgnlCreDtTm>2024-07-03T05:54:55.000Z</OrgnlCreDtTm>
        </OrgnlGrpInfAndSts>
        <OrgnlPmtInfAndSts>
            <OrgnlPmtInfId>ORCRUWIRE0220202317717604</OrgnlPmtInfId>
            <PmtInfSts>ACWC</PmtInfSts>
            <TxInfAndSts>
                <OrgnlInstrId>HMSRUEFT7841913</OrgnlInstrId>
                <OrgnlEndToEndId>4</OrgnlEndToEndId>
                <TxSts>ACWC</TxSts>
                <StsRsnInf>
                    <AddtlInf>DRAFT</AddtlInf>
                    <AddtlInf>Предупреждение: ИНН/КИО плательщика не прошел проверку контрольных чисел
Ошибка: БИК банка получателя дол</AddtlInf>
                    <AddtlInf>жен содержать 9 цифр
</AddtlInf>
                </StsRsnInf>
            </TxInfAndSts>
        </OrgnlPmtInfAndSts>
    </CstmrPmtStsRpt>
</Document>

ISO Code - ACSC, Status -DONE

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.12">
    <CstmrPmtStsRpt>
        <GrpHdr>
            <MsgId>9968b942b9dc4a72abf1b36e683e4a65</MsgId>
            <CreDtTm>2024-07-09T12:09:27.839Z</CreDtTm>
            <InitgPty>
                <Nm>АО Райффайзенбанк</Nm>
                <PstlAdr>
                    <Ctry>RU</Ctry>
                </PstlAdr>
            </InitgPty>
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <OrgnlMsgId>ORCR111UWIRE032012317717602</OrgnlMsgId>
            <OrgnlMsgNmId>pain.001.001.raif</OrgnlMsgNmId>
            <OrgnlCreDtTm>2024-07-03T05:54:55.000Z</OrgnlCreDtTm>
        </OrgnlGrpInfAndSts>
        <OrgnlPmtInfAndSts>
            <OrgnlPmtInfId>ORCRUWIRE0220202317717604</OrgnlPmtInfId>
            <PmtInfSts>ACSC</PmtInfSts>
            <TxInfAndSts>
                <OrgnlInstrId>HMSRUEFT7841913</OrgnlInstrId>
                <OrgnlEndToEndId>4</OrgnlEndToEndId>
                <TxSts>ACSC</TxSts>
                <StsRsnInf>
                    <AddtlInf>DONE</AddtlInf>
                </StsRsnInf>
            </TxInfAndSts>
        </OrgnlPmtInfAndSts>
    </CstmrPmtStsRpt>
</Document>