iDx AcquirerTrxReq (B)

Function	To transfer the transaction details to the Acquirer as composed by Merchant
Root	AcquirerTrxReq
Data elements	`createDateTimestamp`
	`Issuer`	`Merchant`	`Transaction`	`Signature`
Sub-elements	`issuerID`	`merchantID` `subID` `merchantReturnURL`	`expirationPeriod` `language` `entranceCode` `container`	`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

(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.
`Issuer`
`issuerID`	The ID of the Issuer selected by the Consumer. See 'Appendix: IDs' More info Based on `Issuer.issuerID`, the Acquirer selects the correct IssuerTrxURL for sending IssuerTrxReq (C) to the Issuer.
`Merchant`
`merchantID`	See 'Appendix: IDs'
`subID`	See 'Appendix: IDs'
`merchantReturnURL`	URL to which the Consumer must be redirected after authorisation of the transaction at the Issuer. 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`
`expirationPeriod`	The period of validity of the transaction request, measured from the receipt by the Issuer. More info Value according to ISO 8601: PnYnMnDTnHnMnS. Minimum value: PT1M or PT60S (1 minute); The Consumer must complete the transaction within the set period; otherwise, the Issuer sets `Transaction.status` to 'Expired'.
`language`	Code list according to ISO 639-1. (e.g. 'en' for English, 'nl' for Dutch) should be used. 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.
`entranceCode`	'Authentication identifier' created by the Merchant 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).
`container`	This container can contain any set of data elements. It is up to the product specific implementation guidelines what content is included for that product.

Example message

<?xml version="1.0" encoding="UTF-8"?>
<AcquirerTrxReq 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:473Z</createDateTimestamp>
	<Issuer>
		<issuerID>BANKNL2U</issuerID>
	</Issuer>
	<Merchant>
		<merchantID>1234123456</merchantID>
		<subID>1</subID>
		<merchantReturnURL>https://merchantwebsite.nl/returnPage.php?param1=true&amp;param2=3</merchantReturnURL>
	</Merchant>
	<Transaction>
		<language>nl</language>	
		<entranceCode>1234567890abcdefghijABCDEFGHIJ1234567890</entranceCode>
		<container> … any product specific content … </container>
	</Transaction>
	<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
  <!-- Signature is placed here. See Signature section for specification-->
   	</Signature>
</AcquirerTrxReq>

Schematic representation

Incassomachtigen/eMandates Implementation docs for Merchants and MSP's

iDx AcquirerTrxReq (B)

Analytics

Related content