iDEAL AcquirerTrxRes (B')

Function	To confirm receipt of the transaction details by the Acquirer while simultaneously transferring the redirect details to the Merchant
Root	AcquirerTrxRes
Data elements	`createDateTimestamp`
	`Acquirer`	`Issuer`	`Transaction`	`Signature`
Sub-element	`AcquirerID`	`issuerAuthenticationURL`	`transactionID transactionCreateDateTimestamp` `purchaseID`	`SignedInfo` `SignatureValue` `KeyInfo`
Request	AcquirerTrxReq (B)
Communication	HTTP response with an XML message.
Security / authentication	Unilateral TLS connection (Acquirer holds SSL server certificate) Authentication of Acquirer based on Acquirer's SSL server certificate The Merchant should validate the Acquirer's electronic signature to determine the authenticity of 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.
`Acquirer`
`AcquirerID`	Unique four-digit identifier of the Acquirer within iDEAL, assigned by iDEAL when registering the Acquirer. The `Acquirer.acquirerID` must be known to all Issuers with which the Acquirer makes agreements.
`Issuer`
`issuerAuthenticationURL`	The complete URL to which the Consumer is redirected by the Merchant for authentication and authorisation of the transaction.
`Transaction`
`transactionID`	Unique 16-digit number within iDEAL, assigned by an Acquirer. The number consists of a section from the Acquirer (`Acquirer.acquirerID`, first four positions) and a unique number generated by the Acquirer (12 positions). Ultimately appears on payment confirmation (statement and confirmation screen).
`transactionCreate DateTimestamp`	Date and time at which the transaction was created more info This places the transaction in a timeframe that is shared among Merchant, Acquirer and Issuer. It can be used for reporting and reconciliation purposes.
`purchaseID`	Identification of the order within the Merchant's system (does not have to be unique per se). Ultimately appears on the payment confirmation (statement and confirmation screen).

Example Message

<?xml version="1.0" encoding="UTF-8"?>
<AcquirerTrxRes
    xmlns="http://www.idealdesk.com/ideal/messages/mer-acq/3.3.1" version="3.3.1">
    <createDateTimestamp>2008-11-14T09:30:47.0Z</createDateTimestamp>
    <Acquirer>
        <acquirerID>0001</acquirerID>
    </Acquirer>
    <Issuer>
        <issuerAuthenticationURL>https://www.issuingbank.eu/ideal?random=1Y98dHjPwe2qq3s&amp;trxid=0001000000000001</issuerAuthenticationURL>
    </Issuer>
    <Transaction>
        <transactionID>0001000000000001</transactionID>
        <transactionCreateDateTimestamp>2008-11-14T09:30:50.125Z</transactionCreateDateTimestamp>
        <purchaseID>iDEAL21</purchaseID>
    </Transaction>
    <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">         
  <!-- Signature is placed here. See Signature section for specification-->
    </Signature>
</AcquirerTrxRes>

Schematic representation