iDEAL 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 SSL server certificate Authentication of Merchant based on `Merchant.merchantID`, `Merchant.subID` 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 five positions (together nine positions)
`subID`	A number from 0 to and including 999999 in which each value is related to a trade name registered with the Acquirer. The default value is '0'.

Example Message

<?xml version="1.0" encoding="UTF-8"?>
<DirectoryReq
    xmlns="http://www.idealdesk.com/ideal/messages/mer-acq/3.3.1" version="3.3.1">
    <createDateTimestamp>2008-11-14T09:30:47.0Z</createDateTimestamp>
    <Merchant>
        <merchantID>100000001</merchantID>
        <subID>1</subID>
    </Merchant>
    <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
      <!-- Signature is placed here. See Signature section for specification-->
    </Signature>
</DirectoryReq>

Schematic representation

iDEAL Acquiring Participants Implementation

iDEAL DirectoryReq (A)

Analytics

Related content