Page Comparison

Function	To transfer the transaction details (payment request) to the Acquirer as composed by Merchant
Root	AcquirerTrxReq
Data elements	`createDateTimestamp`
	`Issuer`	`Merchant`	`Transaction`	`Signature`
Sub-elements	`issuerID`	`merchantID` `subIDmerchantReturnURL`	`purchaseID` `amount` `currency` `expirationPeriod` `language` `description` `entranceCode`	`SignedInfo` `SignatureValue` `KeyInfo`
Response	AcquirerTrxRes (B')
Communication	HTTP POST request with an XML message to the AcquirerTrxURL.
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

Section

Column

width	675px

(Sub-)element

Description

createDateTimestamp

Date and time at which this message was created

Expand

title	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.

Issuer

issuerID

The ID of the Issuer selected by the Consumer. Consists of the international Bank Identifier Code (BIC). The Issuer.issuerID must be known to all Acquirers with which the Issuer makes agreements.

Expand

title	More info

Based on Issuer.issuerID, the Acquirer selects the correct IssuerTrxURL for sending IssuerTrxReq (C) to the Issuer.

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'.

merchantReturnURL

URL to which the Consumer must be redirected after authorisation of the transaction at the Issuer.

Expand

title	More info

The resource indicated by the URL must be the website or mobile app of the Merchant or a part thereof. (not necessarily beginning with http:// or https://)

Transaction

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).

amount

The amount payable in euro (with period (.) used as a decimal separator if required).

currency

Currency in which payment should be effected,

Expand

title	More info

expressed using the three-letter international currency code as per ISO 4217; 'EUR' is the only permissible code for euro.

expirationPeriod

(Optional)

The period of validity of the payment request, measured from the receipt by the Issuer.

Expand

title	More info

Value according to ISO 8601: PnYnMnDTnHnMnS. Minimum value: PT1M or PT60S (1 minute); maximum value: PT1H, PT60M or PT3600S (1 hour).

The Consumer must authorise the payment within this period. Otherwise, the Issuer sets Transaction.status to 'Expired'.
Note: If the Transaction.expirationPeriod is not provided by the Merchant, the Issuer will set it to PT30M.

language

Code list according to ISO 639-1. (e.g. 'en' for English, 'nl' for Dutch) should be used.

Expand

title	More info

This field enables the Issuer's site to select the Consumer's preferred language (e.g. the language that was selected on the Merchant's site), if this language is supported by the Issuer's site/app or mobile banking app. If a non-supported or non-existing language is entered, the standard language of the Issuer is used.

In case of error, this field enables the Acquirer’s site to select the Error.consumerMessage in the Consumer’s preferred language

description

Description of the underlying value or reason of the payment.

Expand

title	More info

Note: Characters that can lead to problems (e.g. those occurring in HTML editing codes) should be filtered.

entranceCode

'Authentication identifier' created by the Merchant

Expand

title	More info

to facilitate continuation of the session between Merchant and Consumer, even if the existing session has been lost (e.g. because the cookie expired). It enables the Merchant to recognise the Consumer associated with a (completed) transaction. The Transaction.entranceCode is sent to the Merchant in the Redirect to Merchant E (see 'Appendix: IDs').
The Transaction.entranceCode should have a minimum variation of one million, and it should comprise letters and/or digits (maximum 40 positions).

Column

width	100%

Example Message Message

Excerpt

Code Block

language	xml

<?xml version="1.0" encoding="UTF-8"?>
<AcquirerTrxReq
	xmlns="http://www.idealdesk.com/ideal/messages/mer-acq/3.3.1" version="3.3.1">
	<createDateTimestamp>2008-11-14T09:30:47.0Z</createDateTimestamp>
	<Issuer>
		<issuerID>RABONL2UXXX</issuerID>
	</Issuer>
	<Merchant>
		<merchantID>100000001</merchantID>
		<subID>1</subID>
		<merchantReturnURL>https://www.ashop.eu/paymentHandling</merchantReturnURL>
	</Merchant>
	<Transaction>
		<purchaseID>iDEALaankoop21</purchaseID>
		<amount>59.99</amount>
		<currency>EUR</currency>
		<expirationPeriod>PT3M30S</expirationPeriod>
		<language>nl</language>
		<description>Documenten Suite</description>
		<entranceCode>4hd7TD9wRn76w6gGwGFDgdL7jEtb</entranceCode>
	</Transaction>
	<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
  <!-- Signature is placed here. See Signature section for specification-->
   	</Signature>
</AcquirerTrxReq>

Schematic representation

Versions Compared

Old Version 3

New Version Current

Key