iDx DirectoryReq (A)

Function	Request by the Merchant to the Acquirer for the most recent list of Issuers
Root	DirectoryReq
Data elements	`createDateTimestamp`
	`Merchant`	`Signature`
Sub-elements	`merchantID` `subID`	`SignedInfo` `SignatureValue` `KeyInfo`
Response	DirectoryRes (A')
Communication	HTTP POST request with an XML message to the AcquirerDirectoryURL
Security / authentication	Unilateral TLS connection (Acquirer holds SSL server certificate) Authentication of Acquirer based on Acquirer's server certificate Authentication of Merchant based on `Merchant.merchantID`, `Merchant.subID` and the Signature in the message.

(Sub-)element	Description
`createDateTimestamp`	Date and time at which this message was created More info Note: Because the field is included in the digital signature, the value of this field must be determined prior to generating the signature.
`Merchant`
`merchantID`	Made up of `Acquirer.acquirerID` (first four positions) and a unique number of six positions (together ten positions)
`subID`	A number from 0 to and including 999999 in which each value is related to a separate instance registered with the Acquirer. The default value is '0'.

Example message

<?xml version="1.0" encoding="UTF-8"?>
<DirectoryReq version="1.0.0" productID="NL:BVN:eMandatesCore:1.0"
	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">
	<createDateTimestamp>2001-12-17T09:30:471Z</createDateTimestamp>
	<Merchant>
		<merchantID>1234123456</merchantID>
		<subID>1</subID>
	</Merchant>
	<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
<!---Signature is placed here. See Signature section for specifications---!>
	</Signature>
</DirectoryReq>

Schematic representation