Versions Compared

Version Old Version 2 New Version 3
Changes made by

Roland Thijssen

Roland Thijssen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The following table describes which elements are sent to the Routing Service by the Creditor in the eMandate initiation request. Complex types are elements that don't have an actual value themselves. They function as containers for sub-elements that having the actual values.


Index

ISO Message Element

eMandates Requirement

<Document>

-<MndtInitnReq>
--<GrpHdr>

3

Message Identification

... <MsgId>

Max35Text Format: maxLength: 35, minLength: 1

4

Creation Date Time

...<CreDtTm>

DateTime

--<Mndt>

6

Mandate Identification

<MndtId>

eMandate.eMandateID

7

Mandate Request Identification

Must be: NOTPROVIDED

--<Tp>

---<SvcLvl>

10

Code

<Cd>

The identification code of the Scheme 
Must be: SEPA

---<LclInstrm>

12

Code

<Cd>

The identification code of the Instrument (Core /B2B)
Must be: CORE to indicate a Core direct debit. 

Usage Rule: The mixing of different Local Instrument values is not allowed in the same message.

--<Ocrncs>

14

<SeqTp>

eMandate.SequenceType

--<Cdtr/>

Must be empty, Intentionally not filled further by the Creditor, as this will be filled by the Routing Service

--<Dbtr>

39

+++ Identification

Optional eMAN, Complex type

40

++++  Private Identification

Optional eMAN, Complex type

41

+++++ Other

Optional eMAN, Complex type

42

++++++ ID

Optional eMAN 
eMandate.DebtorReference

43

++ Debtor Agent

Mandatory eMAN, Complex type

44

+++  Financial  Institution  Identification

Mandatory eMAN, Complex type

45

++++  BICFI

Mandatory eMAN 
Debtor.DebtorBankID

46

++ Referred Document

Optional eMAN, Complex type 
Usage rule: only one occurrence is allowed

47

+++ Type

Mandatory eMAN (if Referred Document is provided), complex type

48

++++ Code Or Proprietary

Mandatory eMAN (if Referred Document is provided), complex type

49

+++++ Code

Not allowed

50

+++++ Proprietary

Mandatory eMAN (if Referred Document is provided), eMandate.PurchaseID

eMandates mapping to ISO pain.009: Creditor to Routing Service


Code Block
languagexml
<?xml version="1.0" encoding="UTF-8"?>
<AcquirerTrxReq
	xmlns="http://www.betaalvereniging.nl/iDx/messages/Merchant-Acquirer/1.0.0"
	xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0.0" productID="NL:BVN:eMandatesCore:1.0">
	<createDateTimestamp>2015-04-29T13:29:51.974Z</createDateTimestamp>
	<Issuer>
		<issuerID>TESTNL2A</issuerID>
	</Issuer>
	<Merchant>
		<merchantID>1234512345</merchantID>
		<subID>000000</subID>
		<merchantReturnURL>https://betaalvereniging.nl/returnPage.php?param1=true&amp;param2=3%202</merchantReturnURL>
	</Merchant>
	<Transaction>
		<expirationPeriod>PT15M</expirationPeriod>
		<language>nl</language>
		<entranceCode>12345ABCDE</entranceCode>
		<container>
			<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.009.001.04" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
				<MndtInitnReq>
					<GrpHdr>
						<MsgId>Message1234567890</MsgId>
						<CreDtTm>2015-04-29T13:29:51.974Z</CreDtTm>
					</GrpHdr>
					<Mndt>
						<MndtId>1234567890</MndtId>
						<MndtReqId>NOTPROVIDED</MndtReqId>
						<Tp>
							<SvcLvl>
								<Cd>SEPA</Cd>
							</SvcLvl>
							<LclInstrm>
								<Cd>CORE</Cd>
							</LclInstrm>
						</Tp>
						<Ocrncs>
							<SeqTp>OOFF</SeqTp>
						</Ocrncs>
						<Cdtr />
						<Dbtr>
							<Id>
								<PrvtId>
									<Othr>
										<Id>12345-67890</Id>
									</Othr>
								</PrvtId>
							</Id>
						</Dbtr>
						<DbtrAgt>
							<FinInstnId>
								<BICFI>TESTNL2A</BICFI>
							</FinInstnId>
						</DbtrAgt>
					</Mndt>
				</MndtInitnReq>
			</Document>
		</container>
	</Transaction>
	<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
		!-- Message Signature is placed. See iDx Signature section for more details--!
	</Signature>
</AcquirerTrxReq>